Rendezvous Window Resolution

[abr35]

Hello,

I recently switched NASSP over to a new computer, and with the same install and at the same resolution (1920 x 1080) the rendezvous windows and optics panels no longer fill the screen. They look scaled for a 4:3 ratio. I didn't have this issue at this resolution before. Reinstalled NASSP and still have the issue.

Anything that could cause this?

 

[Thespacer]

Just to add a related issue: all the cockpit textures (with exception of CSM main panels 1-3) are “windowed” while running full screen res on an ultrawide monitor. The outside visuals are visible on either side of the panels. Not a huge issue but perhaps related to the above and fixable?

 

[abr35]

I think we're describing the same issue. Didn't happen on a wide monitor to me before, though. What resolution are you at?

 

[jalexb88]

The panels are mostly designed for 16:9 monitors, some are also compatible with 16:10 and 4:3. Other aspect ratios (such as ultra-wide) unfortunately may have the outside view showing at the extremities.

abr35, the following might be what you're experiencing: There is an issue that I have come by before where if I by mistake launch Orbiter in "True Full Screen" mode, the scaling gets all messed up and the panels that showed correctly before, now are scaled much smaller with the sides showing the outside. The only way I could avoid this is by always using "Full Screen Window" in the Orbiter launchpad "video" tab.

Now once the damage is done, the only way I could find to fix it is to rename the Orbiter directory to something else. It seems windows 10 associates the directory to the new scaling and even if you re-install, but keep the same directory name, the issue persists. There may be a way to tell windows not to mess with the scaling for a directory but I haven't yet found out how.

 

[abr35]

The panels are mostly designed for 16:9 monitors, some are also compatible with 16:10 and 4:3. Other aspect ratios (such as ultra-wide) unfortunately may have the outside view showing at the extremities.

abr35, the following might be what you're experiencing: There is an issue that I have come by before where if I by mistake launch Orbiter in "True Full Screen" mode, the scaling gets all messed up and the panels that showed correctly before, now are scaled much smaller with the sides showing the outside. The only way I could avoid this is by always using "Full Screen Window" in the Orbiter launchpad "video" tab.

Now once the damage is done, the only way I could find to fix it is to rename the Orbiter directory to something else. It seems windows 10 associates the directory to the new scaling and even if you re-install, but keep the same directory name, the issue persists. There may be a way to tell windows not to mess with the scaling for a directory but I haven't yet found out how.

Thanks! I did briefly run Orbiter on an HD screen and the panels were sized very large, not sure if that could have caused it. Renamed the directory, I have Windows resolution at a 16:9, Orbiter at 16:9 and reinstalled NASSP. Still no luck, not sure what the next step would be?

 

[jalexb88]

Thanks! I did briefly run Orbiter on an HD screen and the panels were sized very large, not sure if that could have caused it. Renamed the directory, I have Windows resolution at a 16:9, Orbiter at 16:9 and reinstalled NASSP. Still no luck, not sure what the next step would be?

Hmm that is a weird one. Are you sure you are set to Full Screen Window, and not True Full screen?

 

[abr35]

Hmm that is a weird one. Are you sure you are set to Full Screen Window, and not True Full screen?

Yes to full screen window. I'm running full screen window in the dx11 client. Orbiter_ng

 

[jalexb88]

Yes to full screen window. I'm running full screen window in the dx11 client. Orbiter_ng

Are you running the D3D9 client found here: http://users.kymp.net/~p501474a/D3D9Client/ ? NASSP 8 Beta is only compatible with Orbiter Beta and the corresponding beta version D3D9 client as described in the installation instructions thread. By dx11 client, are you talking of this thread: https://www.orbiter-forum.com/showthread.php?t=26147 ? If so, I have no experience with that client and dont know if it is properly compatible with NASSP 8.0 Beta.

 

[abr35]

My mistake, I meant the d3d9 client.

 

[abr35]

Curious if anyone has any other ideas on the rendezvous window resolution bug. Running the d3d9 client, in 1920 x 1080. Tried changing to several other resolutions but still having experiencing the mis-sized window.

 

[jalexb88]

Curious if anyone has any other ideas on the rendezvous window resolution bug. Running the d3d9 client, in 1920 x 1080. Tried changing to several other resolutions but still having experiencing the mis-sized window.

To better understand the issue, can you post a screenshot of it?

 

[abr35]

Here is a screenshot of the right hand rendezvous window. LMP window and optics also have the same issue.

 

[jalexb88]

Here is a screenshot of the right hand rendezvous window. LMP window and optics also have the same issue.

So the issue is that the 4:3 bitmap is being selected, rather then the 16:9 one which it definitely should do. The Project Apollo Configurator has code which detects the user's aspect ratio and should automatically select the proper bitmap, but it seems this has failed in your case. Are you running the latest version of NASSP 8? Also, can you confirm you have ProjectApolloConfigurator.dll present in Modules\Startup and does "Project Apollo Configuration" show up in Extra/Vessel configuration in the Orbiter launch pad?

 

[abr35]

The dll is in the Modules/Startup folder, but not in the Extra tab on the Orbiter configuration. I am running the latest build of NASSP 8.

 

[indy91]

Can you post your Orbiter log? If you have no configuration menu, then this line would probably be missing or have some errors.

000000.000: Module ProjectApolloConfigurator.dll  [Build 200429, API 190228]

 

[abr35]

Here is the full log:

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 1e-007 sec
000000.000: Found 1 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
============================ ERROR: ===========================
Failed loading module Modules\Startup\ProjectApolloConfigurator.dll (code 126)
[Orbiter::LoadModule | .\Orbiter.cpp | 600]
===============================================================
============================ ERROR: ===========================
Failed loading module Modules\Plugin\ProjectApolloMFD.dll (code 126)
[Orbiter::LoadModule | .\Orbiter.cpp | 600]
===============================================================
============================ ERROR: ===========================
Failed loading module Modules\Plugin\ApolloRTCCMFD.dll (code 126)
[Orbiter::LoadModule | .\Orbiter.cpp | 600]
===============================================================
000000.000: Module LunarTransferMFD.dll .. [Build 160829, API 160815]
000000.000: Module D3D9Client.dll ........ [Build 170705, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000: Module LuaConsole.dll ........ [Build 160828, API 160828]
000000.000: Module LuaMFD.dll ............ [Build 160828, API 160828]
000000.000: Module MtimerMFD.dll ......... [Build ******, API 060425]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module CRT.dll ............... [Build 161210, API 100830]
000000.000: Module LolaMFD.dll ........... [Build 101108, API 100830]
000000.000: Module ExtMFD.dll ............ [Build 160828, API 160828]

 

[indy91]

Someone had the same error code a few years ago in our old forum: http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=2879.msg23191#msg23191

Seems like you might be missing some Visual Studio Redstributable packages. Try installing the Microsoft VS C++ 2017 Redistributable (x86) Package.

 

[abr35]

That solved it. Thanks a lot!