Welcome to ZDF!

oh, thank you so much! You're awesome.

I happen to have written that code and the rest in that directory! Go to line 146 in ro.pk3/moonspeak/tip_menu.txt and edit let box_height = height / resolution.y * (4 + tip_line_count * line_height); to something like let box_height = height / max(1, resolution.y) * (4 + tip_line_count * line_height); and it should be fine. It seems to happen because the Drawer function might happen before Ticker.

You're welcome. You could in theory fix this yourself, but you would need to understand how the mod works, and who does other than PillowBlaster himself

ooooh, ok. Gotcha. Thanks more making this more understandable.

It's a bug in the mod(s), or a compatibility issue. Go over to wherever PillowBlaster is now (Doomworld, I believe) and ask him.

Dividing by zero is undefined, and since GZDoom doesn't know what to do, it closes the map and stops the execution of mod code. If it weren't run in a Virtual Machine (VM), GZDoom would actually crash, with a Very Fatal Error, with FreeDoomguy dying.

That's why it's a mere VM abort* (someone screwed up, stop the ship and make them walk the plank!) and not the aforementioned Very Fatal Error (the captain is ramming into an iceberg!). Those happen when GZDoom itself fucks up HARD, like the native C++ code trying to read 0x00000000 (that's hexadecimal for 0). Very Fatal Errors are usually driver related these days, however.


*Cuz it's an error in the ZScript VM, not a C++ error, which would result in the program core dumping.

I'm shamefully new to Doom. Still, I'll try to provide as much information as I can possibly supply here. Before I get into the issue, here's some specs:
Windows 11, version 10.0.22621, Build 22621
Nvidia 2070 Super running driver version 546.29 (released on 12/04/23)
Running the newest version of GZdoom I can find, 4.11.3
Using my copy of Doom 2 on Steam, it's as up to date as it can be
Mods and maps being used: Russian Overkill, Sunder (both downloaded in their most recent state)
Things I've done to try and fix this: update Nvidia drivers, download latest version of GZDoom, make sure I'm using the newest version of Russian Overkill, verified Doom 2's installation is good and there aren't any files missing, and finally, deleted all doom content from my PC and started again from scratch (just to make sure)

I wanna play some Pillowblaster mods on slaughter maps for some easy neuron activation but I'm running into a VM Execution error. Like I said, I don't know anything about this stuff, but a cursory search of these forums has VM Execution stuff come up a lot, though I don't really know what it means. All I'm doing is clicking and dragging Russian Overkill and Sunder's wad and pk3, respectively, onto GZDoom. RO loads in fine, but I want to tweak some settings first, and any time I click on the "cheaty options" menu it crashes to the same error message, provided as an attachment here. If you don't feel like squinting at an image, it seems to say "VM execution aborted: division by zero. Called from RO_TipMenu. Drawer at RO.pk3:moonspeak/tip_menu.txt, line 146". I can enter the Sunder maps just fine and play with the RO weapons, but it'll eventually crash to a similar message, although I can't tell what the trigger is in that scenario. This happens if I load RO raw alone into GZdoom, too, so I'm pretty sure Sunder isn't an issue here. I'm trying to provide as much info as possible here, but it's very likely I'm still missing critical stuff that'd allow you guys to help me. If that's the case, just let me know. Hell, a "for idiots" explanation of what a VM Execution error alone would be a massive help. And yeah, I know the screenshot says to show it to the RO devs but seeing as that thread is locked down now I'm posting this here, hoping casting a wider net helps.