• There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Steve's fixer update v2.... now available

Roger

Senior Administrator
Seems like a lot of new fixes, especially FTX Dx10 issues are now fixed. Unfortunately there seems to an issue with the flightsimstore presently as I cannot access my account.
 
Dave it fixes nearly all Dx10 issues in FsX. Finally managed to get a download from flightsimstore!

Here's some legacy self shadowing just implemented for this new version (all three aircraft are port-overs)...

IgFf2.jpg


sOC8u.jpg


lLZpM.jpg
 
does it add shadows automatically to the VC like p3d does at all?

Yes and No. If the VC Model has a 'shadows enabled' bit set by the developer, then yes, they automatically appear in DX10. If the bit is not set, it can be manually set by the user (that's you) using the DX10 Fixer Tool Box supplied with the fixer. This is a one-time operation and works for most models, but not all. Also, for the best appearance, the developer needs to have modeled the VC with an exterior shell. If not, the sun shines right through the fuselage and cast shadows of the interior frame and fixtures in the VC, which can look a bit strange.
 
does it add shadows automatically to the VC like p3d does at all?

Not to legacy models. All the port-overs I have tested have external shadows but not in the vc...yet? In the Fixer toolbox there is a facility to add vc shadows to most FsX models that don't presently have them. This has to be done by individual models.
 
FSX new way in DX10!

Screenshot62064_zps78e0f341.jpg~original


fsx2014-03-0723-54-54-66_zpsef01e246.jpg~original


Screenshot144088_zpsd70898bc.jpg~original


btw. with Shade, SweetFX, RadeonPro and External Limiter 30 fps - smooth like a butter! :redfire:
 
Can you switch this fixer on and off, so you can alternate between DX9 and DX10 in FSX without any configuration headaches?


Sent from my iPad using Tapatalk
 
Yes you can. The Fixer can be switched Dx10 or Dx9. nvidia inspector settings are different for Dx10 but you can import and export settings as .nip files. So to switch back properly there are just 2 things that need to be changed.
 
Yes you can. The Fixer can be switched Dx10 or Dx9. nvidia inspector settings are different for Dx10 but you can import and export settings as .nip files. So to switch back properly there are just 2 things that need to be changed.

Would you please indicate specifically which NI settings should be changed when going from DX10 to DX9? I've always just left the DX10 'optimized' settings - maybe I'm short-changing DX9.
 
The proper nVidia settings for DX10 are in Paul's guide. There are no common settings for DX9 as every system is different. If your DX10 settings work for DX9 as well, why mess with it? But, in general, you could play with your AA settings.
 
Someone knows how to install the updated Fixer correctly?
Avsim and the DX10 forums are still not online and i installed v2 over the old version.
That isn´t correct---i know.
Thanks
Mike
 
Here you go Mike

1 .Download the latest build from the FSS store...go to "My Account"

2. Double and Triple Check that your current version is installed in a sub directory of program files. If not see note at end.

3: Open your current version of the "Fixer" and select "uninstall libraries" - if you run FSX using multiple user accounts follow the instructions in the manual!

3: Go to Windows Control Panel and "Programs & Features" "Uninstall a program" and select Steve's DX10 Fixer and uninstall

3a: Reboot computer

4: Select the latest version of the installer you just downloaded and "Run as Admin"

5. Enter license if prompted.

5a:Reboot Computer

6: Right click the Fixer icon that should be residing on your desktop, and select advanced, tick the box "Run as Admin"

7: Reinstall the libraries in the fixer and check your other options.

8: Run FSX and make sure all is good.
 
The proper nVidia settings for DX10 are in Paul's guide. There are no common settings for DX9 as every system is different. If your DX10 settings work for DX9 as well, why mess with it? But, in general, you could play with your AA settings.

I have excellent settings for DX10. Just curious. Whenever I switch to DX9, ... meh. Wondered if there was anything specifically that needs to change for DX9, but it's coming back to me now... as I recall there were quite a few NI filter/AA settings that worked in DX9 that did not function in DX10.

Sorry if my question seemed obtuse, but I am among the few who used DX10 from the get-go.I only starting FSX about 18 months ago and naively assumed DX10 was the way to go. Fortunately, time (and Steve Parsons) has proven this to be true. The only times I've ever used DX9 was to check if a problem was specific to DX10 or not.
 
I have excellent settings for DX10. Just curious. Whenever I switch to DX9, ... meh. Wondered if there was anything specifically that needs to change for DX9, but it's coming back to me now... as I recall there were quite a few NI filter/AA settings that worked in DX9 that did not function in DX10.

Sorry if my question seemed obtuse, but I am among the few who used DX10 from the get-go.I only starting FSX about 18 months ago and naively assumed DX10 was the way to go. Fortunately, time (and Steve Parsons) has proven this to be true. The only times I've ever used DX9 was to check if a problem was specific to DX10 or not.

ADi's Dx9 NI setup looks good

http://www.google.co.uk/url?sa=t&rc...vYGIBA&usg=AFQjCNHmovlULUpxHxzxdndFW1np27T2ag
 
Yes you can. The Fixer can be switched Dx10 or Dx9. nvidia inspector settings are different for Dx10 but you can import and export settings as .nip files. So to switch back properly there are just 2 things that need to be changed.

Great, thank you!



Sent from my iPad using Tapatalk
 
Back
Top