SteveFx

I took off from lee on solent airfield. Portsmouth is the only area of photogrammetry that I have found in the UK. The harbour is to the east of lee on solent, you should be able to see the spinnaker tower. Don’t use live weather as there is currently a gale blowing and the flight deck was undulating with what appeared to be waves on my first two approaches. HMS Queen Elizabeth is situated at the northern end of the naval dockyard. Using the Icon I am convinced that I touched down with the gear up and proceeded merrily along the flight deck for 100m before I hit something solid and crashed. The lack of a replay function makes my story hard to check, and so I am still uncertain if it is land or water!!

I meant this as a challenge rather than as a complaint. I think that you need the amphibian because I now believe that the ship is made of elevated water - there appear to be waves on the flight deck. I have sunk two Cessnas so far.

Anyone landed on it yet in Portsmouth harbour? There are trees on the flight deck...

Can you elaborate on which specific DX11 API calls are causing you issues? The FS is here https://microsoft.github.io/DirectX-Specs/d3d/archive/D3D11_3_FunctionalSpec.htm

I have nothing against capital H‘s ...

Bizarrely everyone I have ever ignored has a name starting with m.

I feel sorry for those guys running the MSFS Research Study. How are they ever going to explain to management why 200% of the population of Kiribita bought it on the launch day?

This is what Jim Young said to someone getting the same hresult in 2016.

Just to add detail to this. The underlying reason is that the real air duke uses a material property for a flat layer drawn on top of the display area of BLENDDIFFUSEBYINVERSESPECULARMAPALPHA (Snappy huh?). This has always been completely broken in both the dx9 and dx10 fsx shaders and nothing using it ever gets drawn as they fail to compile. My fixer corrects the bug in the shader and hence everything is drawn correctly based on the supplied texture. This texture has an adjustment to the alpha channel for the area where the default gps goes and hence you can see it . The Specular texture lacks this cutout in the area the 650 was placed and hence it was obscured. In dx9 this didn’t happen because of the broken shader... I have advised Marco how to disable the fix and rebreak the shader. There is some risk that some other aircraft will now not appear exactly as specified but if so they would have never have appeared correctly without the fixer ( and never appeared correctly in dx9) so it cannot be a big loss. if anyone else reports this then refer them to me.

I seem to remember that you use my DX10Fixer. If so remember to uninstall its libraries from its controller before you relocate fsx - you will then be able to change the path in the controller and reinstall to the new location. If you forget then the fixer will become confused and you will need to use the "emergency change of fsx directory" option to sort it out

If the controller says 5.4 then you have already installed the update. The update provides a new option for anti aliasing called cfas which is explained in the manual. This may be of interest to a small number of customers, but most customers will find no use for it. If you can successfully use supersampling set by Nvidia inspector or Radeon cc then you should ignore it and leave CFAS set off as they are much better quality. If you cannot run supersampling using those tools because fps drops too much in cloud then try cfas instead. If your fps falls too much then turn it off.

If you have successfully downloaded the new version it wouldn’t give you a repair option so something is wrong. Download again and check that you have downloaded a zip file called DX10SceneryFixer_5_4_155.zip. Extract the files and run the msi installer which is called DX10SceneryFixer_5_4_155.msi. As the version number is greater than the version currently installed you will not see a repair option.

As explained on the page linked to “check for updates” option you just install the new version and press the update licenses button. https://stevesfsxanalysis.wordpress.com/updating-to-a-new-version/

I imagine from the error that you have a flight sim store version of the fixer - they are defunct and have turned off all their license servers. Can you send me by pm, the fixer order number and date ( ie what iyou needed to enter into their license system) and the cloud shadows order number as well and I will sort you out.

The issue was that the controller correctly checked if the user could elevate. I had assumed that everyone would run the controller as a normal user. If run as administrator then the check returned false (as no further elevation was possible) and the incorrect error was displayed. I have disabled this check and released a new build of 5.4.

5.4 build 153 Some alpha textures (e.g trees in Orbx UK) could appear black if CFAS had never been enabled. Either toggle CFAS ON and OFF or upgrade to build 154 which fixes the issue. Some users were told that their users did not have admin rights when they did - this is under investigation but build 154 disables the check and avoids the issue.

Hi Some people may chose to set up their windows 10 system along the lines of linux with a standard user and a "root" user and it is this that the check is trying to detect. In this special case scenario the controller settings will be written to one location but if FSX is run as administrator by e.g. Active Sky then they will be read from a different location as the user involved will be different. 99.9% of customers will have the normal case where the main user is an administrator. So for my user "Steve" in the windows 10 user control panel "User Accounts" if I select change user type I see that the Steve user is listed currently as "administrator" which is the normal case. If I actually went ahead and changed the type of user "Steve" not to be an administrator then I would get the warning that you describe. If you are getting the warning and the user you are running the controller as is an administrator then the check (which involves accessing Windows's tokens) must be failing silently and returning a negative result. This check was added in version 5.4. Can you confirm again that your user is an administrator as I described above - if so provide me an email address via a pm and I will build a new version with some extra checks to determine the issue for you. Also is UAC enabled on your system? - perhaps if it isn't enabled then this occurs.

I would suspect that the problem with gauges might be that super sampling hasn't been turned on in Nvidia inspector (assuming its a Nvidia GPU) and that the gauge textures aren't mip mapped. Normal Anti alisaing will anti alias the edges of wings or the cockpit frame in the VC but won't do anything for textures used in gauges.

That’s good. Some people have reported lags with texture loading when switching view that seemed to relate to precipitX.

I would ignore most of the settings that you list at the end as I am unconvinced that any apply to the DX10 engine - but who knows - if you want to experiment then feel free. Display texture max load and the texture bandwidth multiplier are believed to form part of some equation to limit texture loading. Your affinity mask is set to not run FSX on core 0 - some people believe that this is a good idea- others believe that it doesn't matter on a 4 core processor (i5) but does matter on an 8 core (i7).

The are various small tray programs that you can find that simulate activity to block the screen saver, e.g caffeine is the name of one. I have never needed to use anything like this with fsx and so have never tested one, but in principle they might assist you, ie run one of these utilities when you launch fsx and close it afterwards.

There is no setting in fsx.cfg, I imagine that your best option is to disable the screen saver before running fsx.

Are you running FSX full screen - i would have expected it to block the screen saver either by activity or being full screen.

Its all in the manual with screenshots, but run nvidia inspector - select the Microsoft Flight Simulator 10 and then use the pulldown on "Antialiasing - Transparency Supersampling" and select 8x Sparse Grid Super Sampling.

I would suggest 8x in the Fixer DX10Controller (that will set 8x MSAA) and then 8x Smart Grid Super Sampling via Nvidia Inspector That card is a monster