search

Realm667 / WolfenDoom

"WolfenDoom - Blade of Agony" | Important: This is only meant for development and testing purposes. You are NOT ALLOWED to use material from this repository for your own projects. Important: This repository is for development and testing purposes, you are NOT ALLOWED to use the copyrighted material for your own projects without our permission!
http://boa.realm667.com
259 stars 26 forks source link

Crashing after defeating the boss of the Eisenman mission #587

Closed Tormentor667 closed 3 years ago

Tormentor667 commented 3 years ago

From FreddyTheMonkey (Realm667 forums):

Hi everyone, I downloaded the latest version of Blade of Agony with chapter 3, and I'm replaying the whole thing.

When I defeat the boss of Operation Eisenman and blow up the three crates, the game crashes. It occurs just as the "Objective Completed" popup appears.

I get the message "VM execution aborted. Tried to read from address zero" followed by some other lines (I'll write them too if it can be helpful).

VM execution aborted: tried to read from address zero. In function parameter "type" Called from FireSpawner. SpawnEffect at boa.ipk3: scripts/actors/effects/fire.zs, line 84 Called from FireSpawner. StateFunction.3 at boa.ipk3: scripts/actors/effects/fire.zs, line 43 Called from EffectGiver. Tick at boa.ipk3: scripts/actors/effects/miscellaneous.zs, line 97 Called from Actor. Spawn [Native] Called from state FireSpawner.3 in FireSpawner Called from Thinker.Tick [Native]

https://www.realm667.com/index.php/en/forum-board/wolfendoom-blade-of-agony/1595-crashing-after-defeating-the-boss-of-the-eisenman-mission

x3003 commented 3 years ago

There's no info what system he's running.

FreddyTheMonkey commented 3 years ago

Sorry, I didn't think about it.

My sistem is as follows: GPU: MSI nVidia GeForce GTX 970 CPU: Intel Core i7-4790 3,6GHz RAM: 16 GB DDR3

AFADoomer commented 3 years ago

This error makes no sense unless the parent fire spawner actor was removed while the function was running. And I don't know how that could happen.

AFADoomer commented 3 years ago

This should be fixed after 09a01cec944348470b9290d4e2e18f57a0321f91. I can't reproduce it easily, though.

FreddyTheMonkey commented 3 years ago

This should be fixed after 09a01ce. I can't reproduce it easily, though.

Thanks a lot! Should I do something on my part for resolving the issue? Download a different build or edit some files?

AFADoomer commented 3 years ago

If you'd like to, you can replace fire.zs in the boa.ipk3 file (it's just a .7z archive) with the version in the commit (full file is here), or just move/update the two lines as detailed in the commit.

Honestly, this shouldn't interfere with continued play either way; I haven't been able to reproduce this even once - I'm just trying to cover any possible case where the command in your report could possibly be passed an invalid value.

FreddyTheMonkey commented 3 years ago

Thank you very much, the problem is fixed for me! Can't wait to continue onwards!

Tormentor667 commented 3 years ago

Thank you very much, the problem is fixed for me! Can't wait to continue onwards!

Thanks for reporting back :)