[Bryan See]

Hello,

I've completed my migration from a desktop PC (with a 1080p monitor) to a notebook PC with 1368x768 display. When I run the nightly build of FS2 Open 3.7.3 via the latest version of wxLauncher, I found that regardless of what current resolution is running, it appears with pillarboxed 1024x768 resolution at 4:3 aspect ratio, which is the maximum since the release of FS source code.

It would be better if this maximum is removed, allowing arbitrary screen resolutions to be supported like modern game engines of this generation.

[Cyborg17]

I believe the pillar-boxing happens only in the menu and can be turned off using the command-line.  Missions are never pillar-boxed and should run at the resolution specified.

[The E]

As always, any time the engine does something wrong, provide a log.

[niffiwan]

Also sounds like there could be a launcher/registry issue.

What version of wxLauncher are you using? 0.10.1?
Are you running it as administrator?

If yes to both we'll have to dig up that registry permissions script The_E created & post it here for you.

[jr2]

Also sounds like there could be a launcher/registry issue.

What version of wxLauncher are you using? 0.10.1?
Are you running it as administrator?

If yes to both we'll have to dig up that registry permissions script The_E created & post it here for you.

Here it is:

Please try this:

• Step 1. Run the fs2.reg file from the steam version. If you do not have it, copy the following text into notepad and save it as fs2.reg, then doubleclick on it.
  

Code: [Select]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition\FreeSpace2]
"EregCount"=dword:00000003
"Videocard"=hex(2):44,00,69,00,72,00,65,00,63,00,74,00,20,00,33,00,44,00,20,00,\
  2d,00,20,00,50,00,72,00,69,00,6d,00,61,00,72,00,79,00,20,00,44,00,69,00,73,\
  00,70,00,6c,00,61,00,79,00,20,00,44,00,72,00,69,00,76,00,65,00,72,00,20,00,\
  28,00,33,00,32,00,20,00,62,00,69,00,74,00,29,00,20,00,28,00,31,00,30,00,32,\
  00,34,00,78,00,37,00,36,00,38,00,29,00,00,00
"CmdLineOptions"=hex(2):00,00
"Interlaced Movies"=dword:00000000
"Movie Fast Clear"=dword:00000000
"D3DFast"=dword:00000000
"D3DTextureOrigin"=dword:00000001
"ForceWFOG"=dword:00000000
"Detect Glide"=dword:00000000
"Detect D3D"=dword:00000001
"DisableZbias"=dword:00000000
"Soundcard"=hex(2):44,00,69,00,72,00,65,00,63,00,74,00,53,00,6f,00,75,00,6e,00,\
  64,00,00,00
"LauncherSoundEnabled"=dword:00000001
"EnableJoystickFF"=dword:00000000
"EnableHitEffect"=dword:00000001
"ComputerSpeed"=dword:00000002
"NetworkConnection"=hex(2):4c,00,41,00,4e,00,00,00
"ConnectionSpeed"=hex(2):46,00,61,00,73,00,74,00,00,00
"SkipVerify"=dword:00000000
"PXOBanners"=dword:00000001
"ForcePort"=dword:00000000
"Language"=hex(2):45,00,6e,00,67,00,6c,00,69,00,73,00,68,00,00,00
"StraightToSetup"=dword:00000000
"Gamma"="1.80"
"LastPlayer"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition\FreeSpace2\Version]
"Major"=dword:00000001
"Minor"=dword:00000014
"Build"=dword:00000000


[/li]

[li]Step 2. Open regedit (Windows-R, enter "regedit", press return)
Go to HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\
You should have a key named "Volition" there.[/li]


• Step 3. Right-click on it, and select "Permissions".
  When I did this, the "Group or user names" field was blank. If it is, click "Add".
  In the dialogue that now pops up, Enter "ALL APPLICATION PACKAGES" into the "Enter the object names" field.
  Click OK. The dialogue should now be populated.
• Step 4. Go to the FreeSpace2 subkey under the Volition entry. Check permissions as above, and if necessary, fix as above.

[Bryan See]

I'm using wxLauncher 0.10.1 without administrator rights. This is due to m!m removing registry helper, in which I and many other users welcomed it.

Although I would have my thanks for the above solution by jr2, I prefer without registry, because it's necessary to develop the game/launcher in accordance with the times.

[The E]

You seem to be having some difficulty understanding this issue.

Point 1: FSO nightly builds are using, and will continue to use, the registry on Windows until such time as we've a) Merged in the SDL everywhere branch and b) Have support for registry-less operation on Windows in wxLauncher. This has not happened yet and will not happen until after we release 3.7.4.
Point 2: No matter what you would prefer, if the solution above is necessary to fix your issue, you need to use it.
Point 3: Speaking of issue, it is not clear at this time that there even is one. As pointed out, menus default to a scaled view that does not distort the graphics right now and leaves black bars to the left and right of the menu, this behaviour is governed by a commandline parameter. The true test is to enter a mission or the F3 lab, if that renders correctly, then everything is working right.
Point 4: To repeat myself, whenever you believe the engine is doing something wrong, you should run a debug build and read the log. I've written a guide to interpreting it that you can find here. If you still have questions afterwards, post the log here or on IRC and someone more knowledgable will help you.

[AdmiralRalwood]

Removing the registry helper didn't mean wxLauncher no longer used the registry; it's just a change in how it goes about accessing it.

[Bryan See]

I understand, at least until FSO 3.7.4 is released. Thanks for that!

[Bryan See]

Also sounds like there could be a launcher/registry issue.

What version of wxLauncher are you using? 0.10.1?
Are you running it as administrator?

If yes to both we'll have to dig up that registry permissions script The_E created & post it here for you.

Here it is:

Please try this:

• Step 1. Run the fs2.reg file from the steam version. If you do not have it, copy the following text into notepad and save it as fs2.reg, then doubleclick on it.
  

Code: [Select]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition\FreeSpace2]
"EregCount"=dword:00000003
"Videocard"=hex(2):44,00,69,00,72,00,65,00,63,00,74,00,20,00,33,00,44,00,20,00,\
  2d,00,20,00,50,00,72,00,69,00,6d,00,61,00,72,00,79,00,20,00,44,00,69,00,73,\
  00,70,00,6c,00,61,00,79,00,20,00,44,00,72,00,69,00,76,00,65,00,72,00,20,00,\
  28,00,33,00,32,00,20,00,62,00,69,00,74,00,29,00,20,00,28,00,31,00,30,00,32,\
  00,34,00,78,00,37,00,36,00,38,00,29,00,00,00
"CmdLineOptions"=hex(2):00,00
"Interlaced Movies"=dword:00000000
"Movie Fast Clear"=dword:00000000
"D3DFast"=dword:00000000
"D3DTextureOrigin"=dword:00000001
"ForceWFOG"=dword:00000000
"Detect Glide"=dword:00000000
"Detect D3D"=dword:00000001
"DisableZbias"=dword:00000000
"Soundcard"=hex(2):44,00,69,00,72,00,65,00,63,00,74,00,53,00,6f,00,75,00,6e,00,\
  64,00,00,00
"LauncherSoundEnabled"=dword:00000001
"EnableJoystickFF"=dword:00000000
"EnableHitEffect"=dword:00000001
"ComputerSpeed"=dword:00000002
"NetworkConnection"=hex(2):4c,00,41,00,4e,00,00,00
"ConnectionSpeed"=hex(2):46,00,61,00,73,00,74,00,00,00
"SkipVerify"=dword:00000000
"PXOBanners"=dword:00000001
"ForcePort"=dword:00000000
"Language"=hex(2):45,00,6e,00,67,00,6c,00,69,00,73,00,68,00,00,00
"StraightToSetup"=dword:00000000
"Gamma"="1.80"
"LastPlayer"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition\FreeSpace2\Version]
"Major"=dword:00000001
"Minor"=dword:00000014
"Build"=dword:00000000


[/li]

[li]Step 2. Open regedit (Windows-R, enter "regedit", press return)
Go to HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\
You should have a key named "Volition" there.[/li]


• Step 3. Right-click on it, and select "Permissions".
  When I did this, the "Group or user names" field was blank. If it is, click "Add".
  In the dialogue that now pops up, Enter "ALL APPLICATION PACKAGES" into the "Enter the object names" field.
  Click OK. The dialogue should now be populated.
• Step 4. Go to the FreeSpace2 subkey under the Volition entry. Check permissions as above, and if necessary, fix as above.

It doesn't work. FSOpen still stuck at 1024x768 at 4:3 aspect ratio, no matter what resolution at any aspect ratio I'm using.

[General Battuta]

Is it only that way on the menus, or is it also 4:3 in-game?

[The E]

It doesn't work. FSOpen still stuck at 1024x768 at 4:3 aspect ratio, no matter what resolution at any aspect ratio I'm using.

Run debug and check the log to see what resolution FSO is actually using. Or run a mission and see what resolution is used there. Or use windowed mode to see what resolution is in use.

This is the last time I will post this. Any single one of these steps will tell you what is actually happening. Until we know that, we simply cannot help you.

[zookeeper]

...why is anyone assuming this isn't about the intended pillarboxing this is obviously most likely about because he's not said anything to the contrary? If he'd know about the intended pillarboxing then naturally he would have said so because he'd know it'd be terribly silly not to because of the resulting ambiguity.

[Bryan See]

Run debug and check the log to see what resolution FSO is actually using. Or run a mission and see what resolution is used there. Or use windowed mode to see what resolution is in use.

I ran debug with window mode enabled and checked the log as attached below. So, the resolution is 1280 by 720.

It is interesting to note that, after switching another mod, let's just say "MediaVPs_2014" and run the same debug build, FSOpen will appear in that resolution. I was so amazed. I think it's not configured properly. Switching to a base mod like the MediaVPs will solve the problem, since it is the bare bones of FSOpen.

EDIT: I've changed to another widescreen resolution, and FSOpen appears in that resolution as well! I think switching from a mod to a base mod in wxLauncher solves the higher resolutions stuck in 1024x768 by 4:3 aspect ratio problem!

And I've already took note of The E's latest post.

[attachment DELETED!! by Strong Bad]

[FSW]

I am having the same issue.

FS2Open runs in 1024x768, both in-game and in menus, even though the launcher is set to 1920x1080.

The debug log is attached. I note the quoted entry, but do not know why it happens.

Initializing OpenGL graphics device at 1024x768 with 32-bit color...
 

[attachment DELETED!! by Strong Bad]

[The E]

Have you tried the fix jr2 posted above? If yes, and if that didn't work, you can set the resolution manually via the "-res" commandline parameter (for example: -res 1920x1080)

[FSW]

The registry fix by jr2 unfortunately does not solve the issue.
To clarify my attempt at following jr2's instructions: The registry fix adds an entry to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition. Later, the guide asks the user to go to HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node. There is nothing there in my registry. I instead edited the permissions for HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition.

Manually setting the resolution by command-line flag does work. Menus remain pillarboxed, but gameplay is fullscreen. Thank you, The E!

[jr2]

The registry fix by jr2 unfortunately does not solve the issue.
To clarify my attempt at following jr2's instructions: The registry fix adds an entry to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition. Later, the guide asks the user to go to HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node. There is nothing there in my registry. I instead edited the permissions for HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Volition.

Manually setting the resolution by command-line flag does work. Menus remain pillarboxed, but gameplay is fullscreen. Thank you, The E!

The registry fix is by the E, I just linked it.

Do you have 32 bit or 64 bit Windows? 

Click Start, type

Code: [Select]

System Information, open "system information" or "about your PC" and see if it says x86 or x64 for system type.  If you have XP, right-click on "My Computer" and click Properties.

[Vladislav]

I have the same issue. Thanks for mentioning the -res fix, I completely reinstalled my drivers and actually downgraded them (new AMD drivers are kind of broken) because I thought the old ones made it work.
Maybe this is a Windows 10 issue instead? Back when I was using Windows 7 I had no such problem.

[jr2]

I have Win 10, no issues so far that I'm aware of. 

Win 10 users should make sure that they are on TH2/10586, not TH1/10240, as I gather that some bugs related to gaming have been fixed since TH1.