Long Loading Times
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.
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49071
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Long Loading Times
What Windows version do you use?
Re: Long Loading Times
Without physical access to hardware I can imagine the single thing that may help to figure out what's going on. It's a memory dump taken during a lag time frame.
Does anyone have other ideas? BTW process Explorer can also suspend a process to make this approach less critical to timing.
Does anyone have other ideas? BTW process Explorer can also suspend a process to make this approach less critical to timing.
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49071
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Long Loading Times
The only idea I have is that the MSVC2017 runtime is doing something this computer does not like. 3.3.0 was the first version built with that compiler so checking a recent devbuild may shed some light on it.