ZDoom

Could I have permission to pinch some code out of this for an addon i'm working on for a mod? I'll give you credits. Yeah that's cool Silent darkness 8-) I'd add additional null checks for everything referencing the "mo" of the player, as apparently some people are still getting VM aborts in rare ...

Yeah I may as well drop the dogaflop and leap frogging names now that the menus are much smaller and can fit more text. I can try making those a toggle too but not sure if there will be problems when it comes to restoring their values. I'll see if I can make those changes today if I'm not too tired ...

Heya PhysixCat. Thanks for your insights! To answer your questions in order: -Assuming you mean the cvarinfo entries, those ve_a_doautoaim etc lines were meant to be commented out as they don't serve a function anymore. The fact they are declared true is just to provide a default for first time use ...

I see what you mean, I'm getting the same problem with certain resolutions (I never noticed because I usually stick to my native one). It does it without even loading vanilla essence so I think this is just how GZDoom works, because it uses integers to scale the UI.

If you go to Options > Vanilla Essence > Interface and set the UI Scale slider to max (and retoggle vanilla) does that solve the problem?

Appreciate the info everyone... I haven't had as much time to work on things or do much testing, so I'm going to post this version as a release candidate here instead of the OP. The changes that I can remember: It won't override changes you've made in the proper menu while it was active. There's ...

Awesome, thanks for your help Rowsol

Glad to hear it

Does this mean that the task manager isn't required to quit anymore?

Oh okay, I see now. It's trying to do stuff despite a crash already happening. Thanks for the vid!

I'm not sure if this will work but it's an attempt at preventing the message from looping at least:

Very strange. It sounds like another mod has this one built in, if you're getting that error without this even being loaded. But then I didn't think mods could share the same handler name (MBlurHandler) or GZDoom would have errored out. What happens if you remove all other mods except this one?

Thanks for letting me know PhysixCat. I knew the current way was limited but was unaware that it wasn't resetting correctly. I have plans to simulate extra compatmodes by setting compatflags1+2 directly as Graf suggests so that will hopefully fix the problem. My train of thought is to have a 'Doom ...

Tis indeed. If you set the walk and jump strength sliders to 1 then it should have the same behaviour as 1.03.

If you're interested you can already use a CRT palette it generated: Screem - the Palette

It's using GZDoom's shader system. I sort of rushed it forward out of a WIP project which allows you to keep it on permanantly. Hopefully that one won't be too far away. Btw, if anyone wants to improve the low-res visuals in VE before it's next update, open the pk3 and move to shaders/VanRes.fp ...

Kudos, that was fast