Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: CT27 on September 28, 2015, 12:13:46 pm
-
On my Windows 7 computer, when playing FS mods the screen has been condensed (black bars on the side of the pilot select screen and in the ship halls). I was told that this is relatively normal and it happened after a certain build was released.
However, when I tested out FS and some mods on another family computer (this one running Windows 8.1), the pilot select screens and menu/ship hall screens filled the whole screen.
For both I was using a 3.7.3 nightly build. I also don't know if this would make a difference, but on the 8.1 computer I put my FS2 folder in a drive other than "C".
Does playing on a different OS change the way FS and mods are displayed? Also, if this isn't the proper forum, could a mod move it please?
-
Please post your fs2_open.log file. Instructions on how to do this can be found in this post. Do this using the Windows 8.1 machine.
-
I'll do that in a couple days or so. For what it's worth I was playing Blue Planet.
-
Most likely explanation (assuming you didn't have -stretch_menu enabled) is that FSO was running in a 4:3 resolution and the stretching was therefore caused by the monitor, not FSO.
-
If it helps, here's the log.
I tried it on a couple other campaigns on my 8.1 machine and didn't get black bars on the side of the screen either. It also seemed like text was bigger in game, whereas on my 7 machine, going to mediavps2014 made hud stuff in gameplay look smaller.
[attachment deleted by nobody]
-
Initializing OpenGL graphics device at 1024x768 with 32-bit color...
As I said.
-
I looked in my wxlauncher window and I had video resolution set to something that wasn't 4:3 though.
Also, what is the correct ratio I should be looking for?
-
I looked in my wxlauncher window and I had video resolution set to something that wasn't 4:3 though.
Do you have 0.10.1 or 0.10.0? 0.10.0 was setting the wrong registry values (and resolution is one of those values that's read from the registry).
-
Yeah, I had a feeling that you were running in 1024x768 and that the display was being stretched.
Do make sure that you're using wxLauncher 0.10.1 (http://www.hard-light.net/forums/index.php?topic=67950.0) and not 0.10.0, or else you won't be able to change the resolution from 1024x768.
Also, what is the correct ratio I should be looking for?
Using your monitor's native resolution should be sufficient. If you need to reduce the resolution for some reason, pick one whose aspect ratio matches that of your monitor's native resolution. Keep in mind, though, that wxLauncher doesn't place almost-16:9 resolutions like 1366x768 in the 16:9 section, even though they're practically 16:9.
-
AdmiralRalwood: On my Windows 7 machine that was performing normally I had the newest wxlauncher (.10.1) and I just realized I was using an older wxlauncher on my 8.1 machine (the one having these issues). I think my W 8.1 machine was using .94...the main release before .10 IIRC
Yarn: I don't know if this matters or not, but for the 8.1 the monitor wasn't a dedicated computer monitor. The monitor for that one was a 'Spectre' monitor that had a number of plugins in the back and you have to use a remote to select the source you want to use (TV/AV/HDMI1/HDMI2/PC).
-
I updated wxlauncher on my W 8.1 machine to the newest version (.10.1) and I still have the stretched menu/intro screens and the 'bigger hud' items in MediaVPs 2014.
-
Hrm, maybe that "disable display scaling on high DPI settings" option in compatibility needs to be selected? (The FSO .exe, not wxLauncher).
-
How do I do that?
-
Right-click FSO .exe > Properties > Compatibility > click 'disable display scaling on high DPI settings' checkbox
-
I'm almost certain that the problem is FSO playing in 1024x768 resolution, not high DPI.
CT27, can you verify that wxLauncher is remembering the resolution setting on the Windows 8.1 machine? If it is, and the display is still stretched, can you post another log (from the same machine)?
-
I'll try that when I can get to my 8.1 machine again.
Last time I tried it with the current version of the wxlauncher (.10.1) the screen was still stretched out even when I tried to change the ratio in wxlauncher. It's almost like the TV I use (that I have the 8.1 machine hooked to) wants to change the screen for gaming.
-
You use a TV? Check to be sure it isn't set to fill the screen by stretching as well if it's not a perfect 16:9
-
The TV I use for my W8.1 machine is a Sceptre if that makes a difference.
-
What's the model number?
-
I'll see if I can dig up the model number later, but a piece of info for now: on the front of the tv on the top left corner it says "LED TV".
-
Another piece of information: the W8.1 machine I'm using is an ASUS.
For some reason, no matter what resolution I select in wxlauncher, the TV changes it when I go into the game.
-
I very highly doubt that your TV is the problem. Rather, the problem is most likely one of these:
- wxLauncher not saving the resolution setting
- wxLauncher saving the resolution setting to the wrong location in the registry (this happened in version 0.10 but should be fixed in 0.10.1)
- FSO not reading the resolution setting despite it being saved to the correct location
To help me determine what the problem is, please follow the advice that I gave you earlier:
CT27, can you verify that wxLauncher is remembering the resolution setting on the Windows 8.1 machine? If it is, and the display is still stretched, can you post another log (from the same machine)?
-
I've tried setting the wxlauncher video resolution to 1920x1080 and 1366x768
1024x768 is what comes up when I start the game though (a box in the upper right corner of the TV with the first line being "PC", second line "1024x768 @60Hz"). It seems no matter what I pick in wxlauncher it goes to the stretched screen.
-
What happens if you restart wxLauncher? Does the resolution displayed in wxLauncher (not the actual game!) reset to 1024x768? (When I asked you to "verify that wxLauncher is remembering the resolution setting," this is what I wanted you to do. This test is meant to help me determine whether wxLauncher is actually writing the resolution to the Windows registry on your machine.)
-
The option for 1024x768 is there in the video resolution list, but I've never selected it and I've never seen it when I've started wxlauncher or closed it then brought it back up.
-
It looks like wxLauncher actually keeps its settings, including resolution, in its own location in the user's AppData folder; only when the game is launched does wxLauncher write anything to the registry. So, while wxLauncher is remembering its settings, it could still be failing to write the resolution to the registry.
Try running wxLauncher as an administrator. On Windows 7 at least, this can be done by right-clicking wxLauncher's shortcut and clicking "Run as administrator"; I don't know whether it's done differently on 8.1.
And just so I know, are you running 32-bit or 64-bit Windows?
-
My 7 and 8.1 are 64-bit.
-
I get the same problem. Whatever I do I get 1024x768, even with older launchers. Running win10.