fabian Posted February 11, 2019 On 2/10/2019 at 12:02 AM, Grazza said: Chocolate Doom (at least, the old version that I tested it with). Reveal hidden contents T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55376, sector: 114, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55376, sector: 115, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55376, sector: 116, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55377, sector: 114, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55377, sector: 115, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55377, sector: 116, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55378, sector: 114, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55378, sector: 115, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55378, sector: 116, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55379, sector: 114, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55379, sector: 115, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55379, sector: 116, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55380, sector: 114, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55380, sector: 115, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55380, sector: 116, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55381, sector: 114, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55381, sector: 115, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55381, sector: 116, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55382, sector: 114, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55382, sector: 115, complevel: 4 T_MovePlane: Stairs which can potentially crush may lead to desynch in compatibility mode. gametic: 55382, sector: 116, complevel: 4 I'd be curious to know which Choco version that was, because someone *ahem* changed the code to initialize the 'crush' field as well: https://github.com/chocolate-doom/chocolate-doom/commit/bfda08cf5275a70a705b3d290ca5271d40481993 Discussion leading to this commit; https://github.com/chocolate-doom/chocolate-doom/issues/368#issuecomment-76356171 0 Quote Share this post Link to post
Grazza Posted February 11, 2019 (edited) It was an ancient version (dated 13-02-2006) that happened to be the one in my Doom2 directory. Ah, so it seems that it is no longer true that Choc (and Crispy) do "not touch the memory manager and the sizes of all internal data" and therefore cannot retain general compatibility with vanilla in these cases. I didn't realize that had changed. Andrey chose values that fixed the cases he knew about at the time, but understood that it would not work in all cases (it happened to work for mm09-512.lmp too, as it turned out). So it seems that now none of these ports can reliably emulate the vanilla behaviour, but have different incompatibilities. That's a shame. If that can't be remedied, it would be nice if they could at least be consistent with each other. Incidentally, Dime seems to have been very unlucky in this respect. No other demos that I am aware of have desynched due to this happening on ev21 (single level or movies), and it has happened to him twice. Just to be clear: the stdout output that I quoted was from current Prb+. Edited February 11, 2019 by Grazza 0 Quote Share this post Link to post
Dime Posted February 11, 2019 (edited) Ty Andrea! My stream was dropping frames leading into the final maps of evilution and I commented to a chatter "no worries Im recording a demo so the final product will be untarnished". Excitedly I upload it and zeromaster comments in a speedrunning discord that the desync happened again in map 25. From elation to deflation. Back in 2014 I swapped from chocolate doom to cndoom because map 30 of plutonia is prone to crashing if you use the BFG while the redrock wall lowers to the icon of sin but cndoom and crispy brought in desyncs on administration. Edited February 11, 2019 by Dime 0 Quote Share this post Link to post
ZeroMaster010 Posted February 11, 2019 Clearly the only solution here is to run 30ev in dosbox :) Also this was actually the 3rd time it happened to dime, I never had it happen myself. I think if anyone is going to do 30ev again it's probably best to activate the stairs, then kill the imps, as this should gurantee no desync happens, at least in this case. I am just so happy that my nightmare run didn't desync to this. 0 Quote Share this post Link to post
j4rio Posted February 11, 2019 iirc there was the same issue with my old run in prb+ desyncing in vanilla 0 Quote Share this post Link to post
fabian Posted February 12, 2019 19 hours ago, Grazza said: Ah, so it seems that it is no longer true that Choc (and Crispy) do "not touch the memory manager and the sizes of all internal data" and therefore cannot retain general compatibility with vanilla in these cases. I didn't realize that had changed. Leaving this value in the struct uninitialized doesn't mean it gets the same random value as Vanilla would - that's impossible to achieve. Thus, we decided to initialize it with *some* value, but apparently the one I chose introduced bias. I am very sorry for this and apologize for my mistake! A PR to help mitigating the issue has already been filed: https://github.com/chocolate-doom/chocolate-doom/pull/1137 0 Quote Share this post Link to post
ZeroMaster010 Posted February 16, 2019 (edited) plutonia ep2 nm100s in 36:14 youtube, all episodes in 1 video: https://www.youtube.com/watch?v=8Lw1_1Cf83A If I ever attempt to do the d2all I will do every attempt on stream, since I never stream I'll most likely never complete it :) edit: re uploaded zip, thanks grazza, I have no idea where my mind was at when I wrote the times down, haha. 11ps3614.zip Edited February 17, 2019 by ZeroMaster010 14 Quote Share this post Link to post
Grazza Posted February 17, 2019 Nice. BTW, there is a mistake in the txt in the times for maps 15, 31 and 32. (I haven't checked them all, but these stood out.) 0 Quote Share this post Link to post
JCD Posted February 23, 2019 Plutonia Map01 in 7.83Pl01-007.zip 12 Quote Share this post Link to post
blob1024 Posted February 24, 2019 8 hours ago, JCD said: Plutonia Map01 in 7.83Pl01-007.zip monsters: what was that? 1 Quote Share this post Link to post
Bob9001 Posted March 6, 2019 (edited) TNT Ep2 ITYTD-Max in 60:43 evITYTDep2.zip Edited March 7, 2019 by Bob9001 Fixed the .txt in the zip 1 Quote Share this post Link to post
Bob9001 Posted March 7, 2019 TNT ep3 ITYTD-Max in 47:47 evITYTDep3-4747.zip 1 Quote Share this post Link to post
j4rio Posted April 15, 2019 Unhoarding time. tnt ep1 max in 37:46 tntep1-3746.zip 6 Quote Share this post Link to post
Bob9001 Posted April 19, 2019 TNT Map 32 UV-Max solo-net in 11:20 Cut over 3 minutes off my last time and infighting helped with the 3 cybers at the end :) ev32net-1120.zip 2 Quote Share this post Link to post
ZeroMaster010 Posted April 25, 2019 (edited) TNT uv-speed in 37:30 Desyncs in prboom+ at map 21, I completely misunderstood why dimes demo desynced, obviously just killing the imps first before activating the stairs fixes everything which is something I've always done except this time. yt: https://www.youtube.com/watch?v=P1cwLMqUykc 30ev3730.zip Edited April 25, 2019 by ZeroMaster010 8 Quote Share this post Link to post
Andrea Rovenski Posted April 29, 2019 (edited) On 4/19/2019 at 6:06 PM, Bob9001 said: TNT Map 32 UV-Max solo-net in 11:20 8:09 tnt32snmax809.zip Edited April 29, 2019 by Cyberdemon531 forgot to stipulate solo-net in .txt 0 Quote Share this post Link to post
Andrea Rovenski Posted April 29, 2019 and for fun, map 1 nomo100s in 26 tnt01nomos26.zip 3 Quote Share this post Link to post
Bob9001 Posted May 2, 2019 TNT Map 17 Nomo 100% in 1:01 Just posting this to fix an error that stood for a year LUL. ev17os101.zip 1 Quote Share this post Link to post
DoomGuy9001 Posted May 2, 2019 On the topic of NoMo 100%s, here's my paltry addition to the pile! Hopefully they should all work... TNTNoMo100s.zip 3 Quote Share this post Link to post
Aquasa Posted May 19, 2019 someone was telling me i should stop hoarding runs, so let's see... these are all for plutonia. map20 max in 3:28 map27 max in 2:07 (the only decent one) map04 -fast in 3:46 pl20-328.zip pl27-207.zip pl04f346.zip 6 Quote Share this post Link to post
elmle Posted May 19, 2019 A Couple TNT Nomo100s because bob ev09os140.zip ev17os57.zip ev28os115.zip ev29os136.zip ev31os148.zip ev32os216.zip 1 Quote Share this post Link to post
Bob9001 Posted May 19, 2019 9 hours ago, elmle said: A Couple TNT Nomo100s because bob ev09os140.zip ev17os57.zip ev28os115.zip ev29os136.zip ev31os148.zip ev32os216.zip I already lost all the records there bud. 0 Quote Share this post Link to post
elmle Posted May 20, 2019 15 hours ago, Bob9001 said: I already lost all the records there bud. You still had them when I recorded those demos. 0 Quote Share this post Link to post
tchkb Posted May 27, 2019 (edited) Plutonia D2ALL UV-Max in 2:05:00 By uploading this I'm breaking my promise to validate most of my relevant runs by streaming them, but unfortunately my current work situation and PC setup prevents me from recording, let alone streaming these days. I'll probably rerun this in the future once I can stream efficiently again. The run was really shit in a few maps, 12-15 especially were full of disastrous moments that cost half to a full minute each. Most of my multi-segment attempts were around 120-122 minutes range, so that definitely could be improved, especially since I forgot most of my routing I did last Autumn and I'm pretty shoddy at Doom in general as well. The route itself definitely has a lot of room for improvements as well - I'll spend the next week or two analyzing this demo along with IL UV-Max runs looking for them. plall-20500.zip Edited May 27, 2019 by tchkb 11 Quote Share this post Link to post
Philnemba Posted May 27, 2019 Hey @tchkb your Plutonia D2All demo de syncs on Map 02 at the invisible bridge section. I replayed it 3 times to be sure that it wasn't a compatibly level issue on my end on pr-boom plus. 0 Quote Share this post Link to post
vdgg Posted May 27, 2019 Fine for me. It's -iwad plutonia or -complevel 4, @Philnemba you must play it either with -file plutonia or -complevel 2 as doing it this way desyncs exactly there. 1 Quote Share this post Link to post
Philnemba Posted May 28, 2019 8 hours ago, vdgg said: Fine for me. It's -iwad plutonia or -complevel 4, @Philnemba you must play it either with -file plutonia or -complevel 2 as doing it this way desyncs exactly there. I goofed as I was using complevel 2 instead of 4 -_-; 0 Quote Share this post Link to post
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.