'); var yuipath = 'clientscript/yui'; var yuicombopath = ''; var remoteyui = false; } else // Load Rest of YUI remotely (where possible) { var yuipath = 'clientscript/yui'; var yuicombopath = ''; var remoteyui = true; if (!yuicombopath) { document.write(''); } } var SESSIONURL = "s=c32f9d9838f2458a026e72aef61f1eb4&"; var SECURITYTOKEN = "guest"; var IMGDIR_MISC = "https://files.42amsterdam.net/samforum/images/styles/GamerBlue/misc"; var IMGDIR_BUTTON = "https://files.42amsterdam.net/samforum/images/styles/GamerBlue/buttons"; var vb_disable_ajax = parseInt("0", 10); var SIMPLEVERSION = "4112"; var BBURL = "https://42amsterdam.net/samforum"; var LOGGEDIN = 0 > 0 ? true : false; var THIS_SCRIPT = "showthread"; var RELPATH = "showthread.php?page=2&t=2112"; var PATHS = { forum : "", cms : "", blog : "" }; var AJAXBASEURL = "https://42amsterdam.net/samforum/"; // -->
So: I can learn about ".dem" structure on 1.10 SDK, but there isn't a program that opens them... Do I have to compile it in C++, based on ".dem" structure? Correct?
No, it didn't give me any bst for this demo. I didn't combine it previously (2+ weeks ago, when I didn't update Fix42Mod yet), because I manually checked all parts before.
I have to check other demos and see if there are any broken. Eventually, would be Notepad++ enough for opening bst files?
Yes but why ?...unless you planning to contribute to the project ...
Yep..
Also once you'll get the .bst file .... - you can control when demo will be cut ...
(open for editing the ".bat" file ....you'll see the the command: "tools\42DemoFileCombiner.exe Combined_Demo 1")
That first parameter is the filtering value for bad-syncs ...(default =1 .... cut at first bad sync)
Attachment 6610
In the .bst file - you can see that player had bad syncs ...but recovered a few times....1,2...RECOVERED.... 1,2...RECOVERED
So ....you can play with the parameter ....and set it to ...for example 14 ...(after 14 counted bad syncs demo will be cut)
This will allow to get bit more of possibly OK frames into working demo ...or even skip the demo splitting ...if there were just few bad syncs. (Max filtering value is 1200 = 60 sec)
Last edited by Ostap; 11-05-2019 at 21:05.
....... Always Look On The Bright Side of Life
Minor update on tweaking the "cut off" parameter:
After checking some demos - If I correctly understand the way it all works - then amount of bad syncs is VERY relative number
It all depends if player had any interactions during bad sync time
If he was just running around without shooting anyone or being shut by anyone - huge possibility that even at high count of bad syncs - demo will still be OK !
Last edited by Ostap; 09-08-2019 at 18:15.
....... Always Look On The Bright Side of Life
I want to UP this because I did the experiment last september. Well, I saved a lot of 42demos since 2013.
I gave the combiner a try with a demo from september, but 2018 (Sep-29-2018, a high score of BadBoy by 34-0*, in which I was part of; he played under the alias of BUBLIK; Map: The Lost Tomb, on Frag 07).
Basically the combiner does the job, but when playing the demo, it just freezes when it reaches the, let's say, point-break of the first part. For instance: if a random demo's Part #1 ends at 3:01, the combined old demo will freeze at that point.
So, my question is: how did you find out that demos prior Nov-30-2018 don't work, while after that date they do? Is the combiner coded specifically for newest demos? Which are the parameters that caused this?
Note: I took the combiner exe and files needed from a random demo (a recent one, from 2020) and then I started my test.
*Indeed it was actually 33-1, since I managed to throw him into the trap!![]()
There are currently 1 users browsing this thread. (0 members and 1 guests)