by gwHero » Tue Mar 06, 2018 1:32 pm
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).
- Attachments
-
- gzdoom-henkj.txt
- (14.58 KiB) Downloaded 30 times
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).