February 3, 20188 yr I've noticed this before subconsciously, but I never really looked into it. I'm running Prepar3D v4.1. When I go to an airport or select an airport from the scenario launch screen, it looks like Prepar3D is omitting the rest of list of starting locations with elipses (...). Is this on purpose? I tried with LAX. LAX has the following runways: 7L / 25R 7R / 25L 6R / 24L 6L / 24R As you can see below, my Prepar3D just lists the first number of the runway, then omits the rest with a ... for six out of the eight runways.
February 3, 20188 yr It looks like conflict in font sizing between P3d and Windows. What DPI (% of default) is your monitor set to in the Windows Display applet? http://windows10_dpi_blurry_fix.xpexplorer.com/ Also, if you are running Win10 there are a couple of display settings in the properties of the P3d exe file/shortcut that also can him up the works if set wrong. Lastly, if you switch from single to multiple monitors within one Windows session, this also happens, courtesy of a bug in the nVidia video driver.
February 3, 20188 yr Author It's set at 100% default, and the only thing I'm doing "special" on the P3D shortcut is running it as an administrator for when I use PMDG aircraft. I restarted and made sure not to change my monitor config in Windows, but I still get the P3D issue.
February 4, 20188 yr I'm still trying to figure out what I meant by him up the works. I guess my spell checker doesn't chew gum. Anyway, it still seems like some conflict between the screen resolution in P3d and Windows, so all that I can suggest is changing the monitor resolution to one step lower and then back again. Or maybe update to the most recent video driver. You don't by any chance have Dynamic Super Resolution (DSR) or a custom resolution set in the nVidia control panel?
February 5, 20188 yr Author Ok, I tried changing the monitor resolution, didn't work either. No DSR enabled in the Nvidia control panel, and running driver version 23.21.13.8871 (according to the Windows 10 control panel). I think I figured it out - I saved a custom scenario and made it the default. Once I selected the scenario that comes with Prepar3D to be the default and restarted Prepar3D, I didn't see the issue anymore. Any chance you can try it on your system and see? I'm running Prepar3D version 4.1.7.22841 with SimConnect version 4.1.0.0.
February 6, 20188 yr I couldn't duplicate that behavior and I use custom scenarios all the time as default, one for each aircraft model. But they all start at the default airport KVPS. I then load a flight plan and move the aircraft to the departure airport. Sorry.
Archived
This topic is now archived and is closed to further replies.