LZdoom OpenGL mode runs extremely slow sometimes after PC reset.

[Lazav]

Today I played 1 hour with LzDoom on OpenGL mode with no issues. Just right after I restarted my PC, Lzdoom started performing so bad that even running vanilla doom would run slow to the point where the start menu would take literally 5 seconds to react to a single keystroke.

Now, I restarted my PC again and for some reason the problem got solved. Of course this issue has been fixed temporarly since I've experienced this problem many times enough to know I will experience it again. I'm not sure if deleting the lzdoom.ini file contributed to fixing the issue or not, but that's what I did before restarting my PC as well.

So, in short, for some reason restarting my PC makes LzDoom run extremely slow on Open GL mode.

Additional Note: Lzdoom wasn't using resources (e.g 99% of the CPU/RAM) so I find it odd that it runned that slow. Also, maybe this problem could happen on GZdoom as well, I just couldn't asses that because GzDoom Open GL mode with Wtfi tool doesn't work on my machine for some reason.

Specs:
Lastest LZdoom version with wtfi tool installed.
I3 2120.
No GPU.
8 GB Ram.
Windows 10 64 bits.

[drfrag]

The integrated GPU was the HD Graphics 2000 and supported OpenGL 3.1 i think. Probably you changed some graphics option in the ini.

[Rachael]

Also, maybe this problem could happen on GZdoom as well, I just couldn't asses that because GzDoom Open GL mode with Wtfi tool doesn't work on my machine for some reason

Try running with "+vid_preferbackend 3" or selecting "OpenGL ES" in the startup dialog, just for the purposes of the test.

---

Also please post your startup log from LZDoom too, if possible, if you experience the issue again and it's really slow, I'd like to see what it is detecting from your system at the slow times and hopefully it shows in the log.

[Lazav]

These past 2 days I haven't experienced that extreme lag I mentioned on my first post. However, I noticed that for some reason LZdoom would take quite a long time to load a map, a thing which I have never have experienced before. The game freezes temporarly, and It takes about 6 seconds to load a map. This issue also applies whenever I finish a mission and the game loads the intermission screen.

So to sum it up, these are the type of scenarios I've encountered:

Scenario 1: No issues.
Scenario 2: No lag, but issues with loading speed with maps and intermission screen.
Scenario 3: Lag.

I made a backup of the .ini file I had when I wasn't experiencing issues, but using that .ini file didn't solve the issue.


----------------------------


[quote] Probably you changed some graphics option in the ini.[/quote]

I though I did initially, but I reinstalled Lzdoom and despite not touching any graphic settings (besides resolution and fullscreen mode on/off) I still experienced this issue.


----------------------------


[quote] Try running with "+vid_preferbackend 3" or selecting "OpenGL
ES" in the startup dialog, just for the purposes of the test.[/quote]

Now with that setting GZdoom works. The only problem I noticed is that the game freezes for 3 seconds after I begin the next map by finishing the previous one. However, switching the maps with ''nextmap'' command doesn't cause this freezing issue. Maybe it freezes due to the autosave process?

Here's the startup log from GZDoom just in case: https://imgur.com/a/EVGXNCJ


----------------------------


[quote] Also please post your startup log from LZDoom too, if possible, if you experience the issue again and it's really slow, I'd like to see what it is detecting from your system at the slow times and hopefully it shows in the log.[/quote]

https://i.imgur.com/TmSNEnn.png

I find it odd that the log says I am using windows 8. I am using Windows 10, and I don't have the compatibility option enabled on Lzdoom nor on Gzdoom. I did put W8 compatibility mode in the past though, since someone on the forum suggested it on another thread, and it worked back then to make possible to run lzdoom with wtfi mode installed run on my machine (although now it isn't necessary to enable it for some reason)


----------------------------


EDIT: sorry for the edit, but I had to try to format my post it a little better since BBCode is disabled on my end for some reason.

[Rachael]

The wtfi tool enables compatibility mode in the application's manifest, so if you ran it on those executables and patched them, then they will startup showing Windows 8 - this is fine, and does not impact the application's performance, all it does is make it show the wrong operating system when it starts up. (Unfortunately with the Intel drivers this is a "good" thing, since seeing a kernel version number that's too new is what is oddly causing them to not work in the first place)

The only other suggestion I have is overheating. If you ran a map for a period of time and it was heavy on resources (CPU resources or GPU resources, it doesn't matter) and if that caused your laptop to get hot, and it can't otherwise be explained away by RAM usage, the CPU may be self-throttling in order to keep itself cool and to prevent itself from burning out. With laptops there isn't much you can do to fix this without opening it up and getting to the nitty gritty deep inside, but if you are comfortable enough doing that (or have a friend who would, or can take it to a shop) they might be able to take off the thermal plates and heat sinks and reapply thermal paste - it may have aged and got cakey and dry - and then put it back together again.

This can also easily explain why certain settings you may have had in the past could have caused this, but wiping your .ini suddenly "fixed" it. Some settings are more intensive for the GPU to handle and can cause it to throw off more heat.

[Lazav]

Again, sorry for the poor formatting, I can't figure out how to enable BBCode.

Anyway, yesterday I had to reset my PC two times to fix the issue in LZDOOM. That time I had no issue, no freezing after autosaving nor extreme lag.

This is the output I got on LZDOOM. https://imgur.com/rBGaPOk . I notice the console says I am using Windows 7 this time (As opposed to saying I was using Windows 8 as it happened 2 days ago) so I find this odd.


>>>> The only other suggestion I have is overheating. If you ran a map for a
>>>> period of time and it was heavy on resources


I made the testing using vanilla doom and I tested the game for 30 seconds, so it's odd that this saving process freezes my game for around 5 seconds. I also didn't have my PC turned on for long time when I made the testing. It's very odd that this freezing issue dissapears just by resetting my PC (sometimes I have to reset it 2 times to fix it).


>>>> and it can't otherwise be explained away by RAM usage, the CPU may be
>>>> self-throttling in order to keep itself cool and to prevent itself from
>>>> burning out.

I am using PC. I cleaned my entire PC and changed the thermal paste 2 months ago. It's winter in my country and my room is usually very cold, so my PC components have reasonable temperatures.


>>>> but wiping your .ini suddenly "fixed" it.

Sorry, I didn't understand this part. I'll just clarify that wiping my .ini never fixed the issue. The only thing that fixes the issue until I turn my PC off is resetting my Windows Operating system.