So here's my issue: I can play most mods and the vanilla games with solid 200 fps with vsync off. Sometimes, playing map packs, I start a level with this fps, then this is gradually lowered until it reaches zero (even if i stand completely still at the starting location), making the game completely unplayable in a minute or so. I tried playing the same level on Zandronum without a problem, but honestly, I don't want to play on Zandronum XD.
I think this COULD be something related to particles: I was playng "Temple of the Lizard Men 2", a map pack for doom 2. I enter the first level, fps starts at 200 and begins to drop gradually. I rush through the level to see if something changes if I move to another area, and I get to an open area with a bonfire of sorts in the distance.
[imgur]https://i.imgur.com/uE1grHo.jpg[/imgur]
FPS is around 40 at this point. I take some steps forwards, and the fire completely glitches out, bringing my FPS istantly to 0
[imgur]https://i.imgur.com/NUOfDny.jpg[/imgur]
Things I tried:
- disabling various lighting options
- limiting the particles number
My specs (sorta):
Nvidia Geforce GTX 970
16 GB RAM
i5 processor (can't remember the model)
Windows 7
Can someone help me?
FPS brought to zero on decent PC
Moderator: GZDoom Developers
Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
-
drfrag
- Vintage GZDoom Developer
- Posts: 3141
- Joined: Fri Apr 23, 2004 3:51 am
- Location: Spain
- Contact:
Re: FPS brought to zero on decent PC
It's a known problem with that mod, it keeps generating actors without control. It worked on old versions tough and i don't remember why.
There's a more recent version that might be fixed at the Temple IV thread, the idgames versions were obsolete.
Edit: found it. viewtopic.php?f=7&t=61658&p=1068427
It's fixed in the newer version. viewtopic.php?f=19&t=49164
There's a more recent version that might be fixed at the Temple IV thread, the idgames versions were obsolete.
Edit: found it. viewtopic.php?f=7&t=61658&p=1068427
It's fixed in the newer version. viewtopic.php?f=19&t=49164
Re: FPS brought to zero on decent PC
Well, this actually worked, thank you!
But this happened to me in other mods (league of heroes for example). Can you confirm that this is always a problem on gzdoom's end? An if so, why doesn't Zandronum have the same issue?
But this happened to me in other mods (league of heroes for example). Can you confirm that this is always a problem on gzdoom's end? An if so, why doesn't Zandronum have the same issue?
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49067
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: FPS brought to zero on decent PC
I cannot say anything about other mods, but the Temple of the Lizardmen mods are all very sloppily constructed. You cannot expect a mod that spills an endless amount of warnings that were never dealt with to continue to run. By ignoring the warnings its maker took some undefined behavior for granted and once that undefined behavior got defined the mod started showing some issues.
The problem with the duplicate classes is that the engine never knows which one it should take, and in this case it greatly mattered which one was picked. When ZScript was added, the mechanism to deal with this was changed by necessity, and after that certain actors who were supposed to self-terminate did not anymore.
The problem with the duplicate classes is that the engine never knows which one it should take, and in this case it greatly mattered which one was picked. When ZScript was added, the mechanism to deal with this was changed by necessity, and after that certain actors who were supposed to self-terminate did not anymore.