General Category > General Discussion

Upgraded to Windows 10 - Partly missing terminals and black spaces **SOLVED**

<< < (2/3) > >>

virtuali:

--- Quote from: Gerpilot on August 01, 2016, 09:36:07 pm ---Has it something to do with viewpoints, Zoom settings, etc.?
--- End quote ---

Only if the video driver has a problem with a tweak OR if the Compatibility mode is enabled. It looks as if LODs are entirely screwed up, and they ARE dependent on BOTH the zoom setting AND the video resolution. Maybe, because of a video driver issue, the sim calculates LOD wrongly, because it reads the wrong screen size.

That's the only explanation I have. LODs are obviously needed (not all developers use them, that's why their fps is usually worse), but if there's a bug in their calculation, due to problems in the video drivers, is nothing we have any control over.

Gerpilot:
Hi Umberto.

Thanks for your reply.

I just redownloaded and installed the most up to date video driver (clean install). No improvement. At that moment no graphic card tweaks applied.

Testing the PMDG 777 all buildings are there as they should. But still not with the default glider, the QW757 and PMDG 737NG.

Is it a problem of the current driver?
Do you have hints what FS related programs could run in compatibility mode? As i already mentioned i checked those written in the exe.xml of FS.

Thank you and kind regards

Dirk

virtuali:

--- Quote from: Gerpilot on August 02, 2016, 01:04:25 pm ---Is it a problem of the current driver?
--- End quote ---

We all use the current driver, and never able to replicate on any of our systems before, with every Windows version, every version of the driver and every possible tweak.

The only reason why we suggested this, which we were never able to witness first-hand, is according to users report that HAD this problem, even in other driver releases and other Windows versions, which was ALWAYS cured by either:

- Resetting the video settings to default

- Ensuring that NO FSX addon or FSX itself runs in Compatibility mode.

There are no other KNOWN solutions. Which doesn't obviously mean there might not be other solutions, just we don't know about them because, as I've said, the only knowledge of this problem comes from users reports and users reports about how they fixed it.


--- Quote ---Do you have hints what FS related programs could run in compatibility mode? As i already mentioned i checked those written in the exe.xml of FS.
--- End quote ---

Anything that starts in the EXE.XML, or the DLL.XML, or that launches FSX.

Gerpilot:

--- Quote ---Anything that starts in the EXE.XML, or the DLL.XML, or that launches FSX.
--- End quote ---

In dll.xml are only dll modules. I don't know how to check those if they are running in any compatibility mode. I don't think that is possible, isn't it?
All programs stated in exe.xml are checked from my side and they are not running in compatibility mode.

virtuali:

--- Quote from: Gerpilot on August 02, 2016, 03:34:23 pm ---In dll.xml are only dll modules. I don't know how to check those if they are running in any compatibility mode. I don't think that is possible, isn't it?
--- End quote ---

You don't, but if they do something that would cause the sim to run AS IF it was in Compatibility mode, there would be nothing you could do. Except disabled them.

Have you tried to disable *everything* ( setting the <Disabled>True</Disabled> line in the XML file ), except our modules, bglmanx.dll in the DLL.XML file and Couatl.exe in the EXE.XML ?

And, have you checked if you haven't mistakenly set a Compatibility mode for Couatl.exe itself ?


--- Quote ---All programs stated in exe.xml are checked from my side and they are not running in compatibility mode.
--- End quote ---

Maybe you have a program that start with Windows that does that. Something that have an interaction with the video drivers, like a screen capture or screen overlay, or something similar.

If not, it must be a video driver problem. As I've said, they are the only KNOWN causes for this problem and, right now, EVERY single user that ever had it, fixed it as already explained: resetting the video driver AND the FSX.CFG OR removing a program that ran into Compatibility mode.

Navigation

[0] Message Index

[#] Next page

[*] Previous page