Priority Always Low

[Guest]

Hey guys, what's up? I'm having this problem on all of my PCs and it's starting to annoy me...

I have a powerful PC on my room that i use to play Doom on GZDoom, but it lagged sometimes, even on the lightest settings.
So i tried to make the process high priority and discovered it was on low. Changed to high and tried to play once more, but it still lagged.
Then i discovered that the process was on low again. I knew about the fact that ZDoom ports lower their priorities when out of focus, so i tried the -noidle switch, but the game lagged as well and the process priority was locked on normal instead of low.
Every time i go to the task manager and change the priority to high, when i come back, it was on normal.
I posted on this forum because it seems to affect all ZDoom based ports (Skulltag, GZdoom, Zdoom, etc.)
This way i couldn't play Brütal Doom or AEons of Death because the lag was horrible, and i'm sure my PC can handle them both without problem.

Please if anyone has any clue about what's happening here i would be very glad.

If i would, can i suggest a priority setting inside ZDoom's menus? (or as an option changeable via the console?)

[Blue Shadow]

Those two mods you mentioned are resources-intensive. It's no surprise they could lag your system, even if it is a powerful one.

If you're running other programs in the background, try and close (some of) them and see if that improves the performance.

Also, what are your system specs?

[TheDarkArchon]

If priority is really causing your computer to lag with those mods, something else is using a lot of CPU power and it would most likely be more effective to kill whatever that something is rather than fuck around with priorities. Also the words "a powerful PC" have no meaning without context.

[Graf Zahl]

You clearly don't understand what thread priority is there for. Setting it to high will cause serious degradation of overall performance and is an absolute no-go for any well-behaved application.

[Major Cooke]

What kind of graphics card do you have?

If you have something like Nvidia, try setting up a custom profile via the application manager.

That, and like Archon said, kill some extra programs running in the background (but don't touch any svchost.exe apps)

---

Go for maximum performance on everything. That should really help out a lot too.

[StrikerMan780]

You clearly don't understand what thread priority is there for. Setting it to high will cause serious degradation of overall performance and is an absolute no-go for any well-behaved application.

Still doesn't mean that there isn't bug relating to priority, if anything, the priority should be setting back to normal when back in focus, but it doesn't always do that, it stays at low. I've had that issue a lot. It's annoying too, as even little things such as background update processes, IMs, Driver-Related processes (Like SetPoint, or ZEngine), among all sorts of other possibilities, end up taking away precious cycles from ST/ZDoom/GZDoom and causing all sorts of small hitches... I personally think that should be fixed at the very least...

Though, I'm thinking a menu option for setting priority for the game while in focus would be nice as well, I know of a few games that do this. Maybe capping it at "Above Normal" priority would be in order though, so people don't inadvertently lock their PC up by setting it to realtime or high priority...

[randi]

if anything, the priority should be setting back to normal when back in focus, but it doesn't always do that, it stays at low.

Do you have something up to monitor its priority in realtime? Because the act of switching to the task manager to check the priority will naturally put it to low priority, since it's no longer the foreground application.

[Ziaeon]

I've been noticing this recently as well. Certainly I wouldn't expect Zdoom alone to care about cpu prio but Brutal Doom can be cpu intensive, and when I notice it to start to skip a bit, changing the priority to high fixes it. My question is why it keeps going back down to low, there should be a way to disable that somewhere.