Author Topic: no hud at 2560x1440?  (Read 1569 times)

0 Members and 1 Guest are viewing this topic.

no hud at 2560x1440?
so I had set all this up ages ago at 1920x1080 so maybe there was some step in the process I forgot or something? back around 3.6.14 era.

so basically, since then i've gotten a new monitor and decided to start playing again. fired up the launcher, changed the resolution on the video tab to 2560x1440 (and nothing else), and fired it up. everything works except...absolutely no hud once i'm in the ship. not even text.

if i exit and go back to launcher and change resolution back to 1920x1080, everything works as it should. just refuses to work with new resolution

i updated to 3.7.0 to see if that resolved it and same issue (but also working fine at 1920x1080)

i'm stumped. anyone got any ideas?

 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: no hud at 2560x1440?
Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

 
Re: no hud at 2560x1440?
sure thing, attached. for what its worth, running the debug exe shows the fps/memory statistics/etc, but still no hud

[attachment deleted by an evil time traveler]

 

Offline Yarn

  • 210
Re: no hud at 2560x1440?
First, some cleanup (none of which is really related to your HUD problem):

Code: [Select]
  -mipmap
This flag is deprecated (I think) and is known to cause problems (and it's not actually necessary for mipmapping). Please disable it. You can find it in the launcher flags list under "Troubleshoot" (look for "Enable mipmapping").

Code: [Select]
  -spec
  -glow
  -env
Deprecated flag '-spec' found. Please remove from your cmdline.
Deprecated flag '-glow' found. Please remove from your cmdline.
Deprecated flag '-env' found. Please remove from your cmdline.
As those messages say, remove those flags. Look for them in the custom flags list.

Code: [Select]
Found root pack 'D:\Program Files (x86)\Freespace 2\...
Installing FSO to Program Files is just asking for trouble, especially if you're running Windows Vista or later. Move your "Freespace 2" folder to a place like D:\Games.


All right, now to actually fix your problem.

Your log shows that you're running FSPort 3.3, which is outdated. The latest version is 3.4, which can be found here. Everything there except Warble has been updated since 3.3.

If that doesn't solve the problem, then create and post another log.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 
Re: no hud at 2560x1440?
i'll give all those a whirl, thanks

how painful is it to just drop in a new fsport/mediavps?

  
Re: no hud at 2560x1440?
update: not painful at all lol

and hooray it works! it looks like theres a mention of hud fixes buried up in the fsport 3.4 changelog, shoulda thought to try fs2 or something to see if it had problems too

removed all that outdated/deprecated stuff as well

thanks for the help!