 |
https://forum.zdoom.org/viewtopic.php?f=19&t=54843&p=967174#p967174 Download D4D here. |
 |
A little bit off-topic but still... Bleeding edge version asserts at src/scripting/vm/vmbuilder.cpp:285: |
|
|
Forgot to mention the most important thing: it works for me with .pk3's from here using the latest commit d5962b2. I tried on Doom II MAP01, Nightmare: two zombiemen gave me 40 armor points. What's the commit you are using? |
|
|
The same one. Are you using Bleeding Edge? |
|
|
Yes, D4D.pk3 has been updated since I tried but the grenade still works with the new one. I tried with own 64-bit macOS build and with 32-bit Windows devbuild from DRD, without .ini in both cases. |
|
|
I'm using RelWithDebInfo currently. Hmm... I don't know what to say about the assertion thing. Also Windows 10 Pro x64. |
 |
The assert is a bug, thanks to some very shortsighted design in the VM with those stupid pointer tags. It's a perfectly harmless condition aside from that debug code that raises an alert. I have been thinking about removing that stuff anyway, as it inflates runtime data structures and other stuff for some very minor debugging aid during compiler development. Originally this had a lot more pointer tags but as it turned out the system was totally unusable because it couldn't always keep track of them. |
|
|
I'm sorry that I have to say it this bluntly, but you are essentially asking to have your code debugged. This is first and foremost your own responsibility to ensure that it all works as you wish. This is simply not what the bug tracker is there for. If you can pinpoint a specific cause that's engine related, please report back but I really need to work on other things than debugging code I do not even fully understand how it's supposed to work. |
|
|
Just checked with 64-bit Windows RelWithDebInfo configuration and bleeding edge .pk3's downloaded a few minutes ago. It still works for me. No .ini, no other WADs, Doom II MAP01. |
|
|
It's strange because I never changed anything on my end, I was wondering if the armor scriptifying had something to do with it. Also I forgot to mention it's sporadic when it decides to stop working. I'm trying to investigate it as thoroughly as possible. |
|
|
I cannot reproduce this anymore so go ahead and close it. |
- Anonymous
