Strange behaviour mods on latest dev build

[gwHero]

Hi,

with the latest devbuild (64 bit, build of today Mar 6th) it seems impossible to run (certain?) mods normally.
By dropping pk3's on the GZDoom executable the following happens:
- extremely light display ..??
- mods open in low value of screenblocks ..??

Tested with several mods, mod's with and without maps. Full games with Iwad (Doom2, my own game (pk3 + ipk3) seem to work okay.

[Rachael]

What mods are doing this, and what system (Windows/Mac/etc) are you using?

[gwHero]

What mods are doing this, and what system (Windows/Mac/etc) are you using?

It seems any mod that's not an iwad. There is a difference in software renderer vs openGL: in software renderer the colors seem alright, but this is for instance how Doom looks when I start the sprite shadow mod 1.6 in software viewtopic.php?f=37&t=54992

I use Windows 10 64bit on a 1920*1080 resolution and have never experienced this before; it only happens with the builds that were made today (64bit as well as 32bit); builds of 3 days ago are still working okay.

Like I said, the strange thing is that when I start Doom2 normally or my own game that contains an Iwad, all seems to work fine.

[Rachael]

I am still unable to reproduce this, and this is using the exe that I compiled earlier and posted.

[gwHero]

Did a quick test on my previous laptop: Windows 10, 64bit, resolution 1366*768; same behaviour as on my current system: only latest dev build not working.
Maybe it's good to wait if others have problems with the build.

[Graf Zahl]

I cannot reproduce this by dropping some random files onto the EXE of today's debuild.
This almost sounds like it's picking up some INI from elsewhere. Did you start the game without an INI in the folder or did you copy some old one there?

[gwHero]

Without an existing ini. I did actually the same what I always do when downloading a new build: create a new folder, copy the Doom2 iwad, launch GZDoom exe and start configuring the keys. Tested the first Doom level for a bit, quitted the game and after that dropped a custom .pk3.

But now you mention ini files: it's related to that, and not to iwad or mod as I first thought. I now removed the ini from the new build and started the mod again; worked fine. But after that, the game itself now gave problems. So it's ini related indeed, because when I delete it again, the problem is over. But when I quit and start it again, the problems are back.

So I opened the ini, and it looks like all variables are saved with initial values (booleans false, colors zero etc); see attached ini (attached as txt).

[gwHero]

Did some more testing: it looks like that when you have an existing ini, there are not much problems, but when you delete it and the game saves a new one after a restart, all's screwed.

[_mental_]

I think it’s my fault, will check soon. Fixed in 72831c9.

[gwHero]

Thank you