Hard Light Productions Forums
Hosted Projects - FS2 Required => Blue Planet => Topic started by: Freon on November 05, 2015, 01:53:13 am
-
I've been lurking for a while watching the BP Voice Acting thread and lost my head when it was released :D
BUT...I got in and I thought "gee this doesn't look as good as it used to..."
I thought immediately that it was a resolution issue. The jaggies were just so real...
Specs:
- 3rd Nov 2015 AVX build
- i5-4690 @ 3.50GHz
- 24GB DDR3
- Radeon 7950
I want to make it clear that in the wxlauncher, the resolution is set to 1920x1080. Just so that's clear to start.
These are the steps I took finding out what was happening:
- Took a screenshot (not really cocher but anyway...) and determined that the main screen (I have 3 but only 1 that fullscreen games run on) was only about 1024x768 ish
- Tried running the old stuff (as in the BP before BP complete). Same deal, weird resolution.
- Ran the debug build and got this fs2_open.log (https://dl.dropboxusercontent.com/u/37301843/fs2_open.log) - in it, I see "initialise openGL 1024x768"
----- Also got some errors on first run about the Hyperion model. Unfortunately I can't seem to reproduce them...
I'm running the latest (10.1 or something) wxlauncher, even though in the in-tool changelog it says its 0.9, with 1920x1080 at 32 bit colour.
If I missed any details you need, please let me know and I'll get them.
I should have participated in the beta a few weeks ago, cos this always happens to me...I must have a weird computer.
I'm so keen for the voice acting in WiH. Soooo keen :D I didn't watch the stream so I could have an unspoiled playthrough of glory.
EDIT: Clarification of the issue.
-
You may be affected by this bug:
Launcher gives an error message "Cannot write to registry" (Launcher 5.5g) or "Unhandled error in setting HKLM key" (wxLauncher)
This error can happen on Windows 10. Here's how to fix it:
- 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.
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]
- 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. - 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.
-
Appreciate the reply The E, but alas. No dice.
Applied that reg edit, and forgot to mention that I'm on Windows 10.
The ALL APPLICATION PACKAGES was already populated, but I gave it Full Permissions anyway.
fs2.log still indicates 1024x768. :(
-
In the Launcher's custom commandline field, enter "-res 1920x1080". This should force the exe to ignore the registry setting.
-
Did you try running wxLauncher as an administrator?
-
Running as Admin did nothing different, but running with the -res flag did everything as expected.
I don't have enough time to test thoroughly but off the bat, it looks as I expected except for the menus to start. I suppose that's where "stretch menus" comes in.
Anyway, for now, thanks muchly. I shall test more thoroughly when I get time :D
-
yo - should we ask the wxlauncher peeps to change the way they handle the res; quit trying to write it to the registry & instead always use the -res flag?
-
yo - should we ask the wxlauncher peeps to change the way they handle the res; quit trying to write it to the registry & instead always use the -res flag?
I am all for anything that can get us away from the registry.
-
I hacked up a quick PR (https://github.com/scp-fs2open/wxLauncher/pull/123) for wxL, I'll see what IssMneur has to say about it.
-
OK, that -res flag did the trick entirely.
I'd vote to use it instead of the registry if my vote counted for anything :)
Now to experience the Voice Acted BP in all its glory :D