Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: golgoth on June 12, 2014, 03:46:59 pm
-
Just started a new game with FSOpen (win 8.1, nVidia GTX 780 Ti) and i noticed these two issues:
1) when i play FS2 MediaVPs 2014 my native resolution (2560x1440) works, but text is almost unreadable because of the small size. Is there a way to increase it?
2) FSPort MediaVPs 3.4 and any other mod don't run at 2560x1440, but at 1440x900 or something like that, even though i set 2560x1440 inside FS2 Open Launcher. Why?
Thanks
-
Please post your fs2_open.log file. Instructions on how to do this can be found in this post.
-
For point 1, I'm reasonably willing to bet that it'll be the lack of gauge scaling causing this issue, it's been reported by some other people using 1440p.
golgoth: try following the steps in this post:
http://www.hard-light.net/forums/index.php?topic=87656.msg1750829#msg1750829
The only trick is to ensure that windows doesn't append a .txt to the file when you create it. Here's a link on how to display them in Windows 8.1:
http://blog.laptopmag.com/show-file-extensions
(and you should still generate a log as suggested by DahBlount so we can investigate your FSPort issue further)
-
For point 1, I'm reasonably willing to bet that it'll be the lack of gauge scaling causing this issue, it's been reported by some other people using 1440p.
golgoth: try following the steps in this post:
http://www.hard-light.net/forums/index.php?topic=87656.msg1750829#msg1750829
If i understood right i have to put that tbm file inside MediaVPs_2014/data/tables. If that's what i was supposed to then the fix doesn't work, and with that file in 1440p resolution stops working even with FS2 :(
Here's my log, thanks a lot for your help!
[attachment kidnapped by pirates]
-
First of all, make sure that you're using FSO 3.7.2 RC3 (http://www.hard-light.net/forums/index.php?topic=87764.0), which has better support for long path names.
Can you post screenshots of the two cases in your original post (one with the 2014 MediaVPs, another with FSPort)?
-
Sure! Here they are
[attachment kidnapped by pirates]
-
FSPort is running at 2560x1440; just the HUD is stretched, because the FSPort MediaVPs reference the 3.6.12 MediaVPs, the HUD file for which is somewhat outdated.
As for the first image, FSO is still scaling the HUD gauges. Are you sure it's a .tbm file, and not a .txt file the extension of which is being hidden by Windows?
-
Oh well, i was sure that it wasn't running at 2560x1440 because of the stretched hud. Nothing more wrong :)
And now that you mention it, after applying the fix for FS2 i get the same stretched hud, but nonetheless the resolution looks the same.
Sorry for the topic, everything worked fine after all (except for the non stretched hud in FS2) :)