3.5.0 slow startup on OpenBSD

Need help running G/Q/ZDoom/ECWolf/Zandronum/3DGE/EDuke32/Raze? Did your computer break? Ask here.

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.
Post Reply
Guest

3.5.0 slow startup on OpenBSD

Post by Guest »

The game loads quite slow on OpenBSD. When I start the game with simple "gzdoom" it prompts the WAD to use and starts to load and messages start to flow in console. Then SDL window appears which is blank and the game loading seems to take around 10 seconds seemingly doing nothing and then the game enters the menu and is running.
Is that kind of 10 second "pause" normal during the startup and what might be causing it?

Here's the console output before the pause:

GZDoom <unknown version> - - SDL version
Compiled on Aug 3 2018

M_LoadDefaults: Load system defaults.
Please select a game wad (or 0 to exit):
1. The Ultimate DOOM (doom)
2. DOOM Shareware (doom1)
Which one? 1
W_Init: Init WADfiles.
adding /usr/local/share/games/doom/gzdoom.pk3, 627 lumps
adding /usr/local/share/games/doom/zd_extra.pk3, 132 lumps
adding /usr/local/share/doom/doom.wad, 2306 lumps
I_Init: Setting up machine state.
CPU Vendor ID: GenuineIntel
Name: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Family 6, Model 58, Stepping 9
Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 HyperThreading
I_InitSound: Initializing OpenAL
Opened device SndIO Default
EFX enabled
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 361.29 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
Using video driver x11
GL_VENDOR: Intel Open Source Technology Center
GL_RENDERER: Mesa DRI Intel(R) Ivybridge Mobile
GL_VERSION: 3.3 (Core Profile) Mesa 13.0.6 (Core profile)
GL_SHADING_LANGUAGE_VERSION: 3.30

Max. texture size: 8192
Max. texture units: 16
Max. varying: 128
Max. uniform block size: 65536
Uniform block alignment: 16

After the pause it prints the "Resolution: 640x480".
_mental_
 
 
Posts: 3812
Joined: Sun Aug 07, 2011 4:32 am

Re: 3.5.0 slow startup on OpenBSD

Post by _mental_ »

Most likely it’s caused by compilation of shaders because this version of Mesa3D has no shader cache.
Guest

Re: 3.5.0 slow startup on OpenBSD

Post by Guest »

So nothing to be done but wait for mesa3d to be updated?
User avatar
Rachael
Posts: 13561
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

Re: 3.5.0 slow startup on OpenBSD

Post by Rachael »

Or compile your own.

Keep in mind, there's a reason why OpenBSD fell off the support list at least twice now. I'm sorry but the operating system's components are just not able to keep up with the dependencies that GZDoom needs.
Post Reply

Return to “Technical Issues”