Sign in to follow this  
SteveFx

DX10 Scenery Fixer Known Problems

Recommended Posts

1. Dawn/Dusk.

There is a problem at the transition from dawn and dusk to day. At legacy
airports the ground may appear like chrome. I have a fix which will be
available by early next week.

Fixed in build 19

2. bkg.bmp/envmap.bmp If somehow these have been converted to a .dds then
the installation will fail. I have updated the manual to say this. You need
to restore the original bkg.bmp and remove the dds. I hope to be able to
work around this more gracefully.

Added Additional Checks in Build 17 and Build 19


3. envmap.bmp As a separate issue if your envmap.bmp is still there but is
a different size to the original then all is well until you try and disable
effects. An error will appear "envmap.bmp not recognized" and you cannot
re-enable effects. Uninstall/install the libraries to resolve this.

Added Additional Checks in Build 17 and Build 19

4. Standard User Account. If your main user does not have admin rights then
disabling effects can fail as the installation failed to create a directory - Now fixed in the current build on FSS (17).

5. The wrong font was used on the main DX10Controller Screen its currently Aerial Unicode MS

Fixed in Build 19

 

6.  Zoom for HD Shadows was set too high causing false shadows in smaller Jets.

 

Fixed in Build 19.

 

7.  AI Long Range Visibility

 

      Addressed in Build 24  (v1.1)  - but success may vary with AI package.

 

8.  Legacy Airport lighting  turning off at certain viewing angles

 

    Addressed in Build 24 (v1.1)  - can never be 100% but much improved I think.

 

9.  Some lights were appearing black in the day - collision with Fence Patch

 

      Fixed in Build 24(v 1.1)

 

10. Some people have reported not having fx_2.bmp - extra check added in Build 25

 

11. Bias offsets too small for some aircraft in Build 24 - causing z fighting - bias offsets increased in Build 25

 

12.  Effects scanning does not work if effects are enabled as part of library install - fixed in Build 26

 

13.   Uninstalling without light package installed shows errors re navlights.  Its totally harmless but annoying nonetheless - fixed in Build 26

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi Steve,

 

Thanks for the update.

 

I'm assuming we'll be notified here on the forums when the fixes are released?

 

Just a question, how will the fixes be made available, through a seperate download or do we have to reinstall from FSS?

 

Cheers.

Share this post


Link to post
Share on other sites

FSS Store will distribute the fixes I believe, the only thing I dont like about that is they do not tell you the file is new you have to download it and see if its different in size or name but no heads up that I have seen yet.

Share this post


Link to post
Share on other sites

 

 


the only thing I dont like about that is they do not tell you the file is new you have to download it and see if its different in size or name

 

Hmmm that's what I was thinking would be the case too. Oh well, I'm sure we'll have it posted here that a new update is available anyway.

 

Never bought anything else through FSS Store before.

Share this post


Link to post
Share on other sites

Thee are three issues with 1.3

 

A) The rain shader hide texture change is implemented incorrectly - to stop the black flashes set the option to be unticked (which is the default)

 

B) the reflective bloom shader does not work

 

C) there is a patch which was left enabled which affects some buildings and roofs. To fix this do the following

 

 

1) run notepad as administrator

 

2) open c:\Program Data\DX10SceneryFixer\DX10Patches.ini

 

3) find this section

 

 

// added in build 30

[VitalySplash]

Type=2

On=17039361

//Off=-1

Disable=1

Debug=0

ForceDepth=1

ForceBlend=1

SrcBlend=2

DestBlend=2

 

 

Change the line Disable=1 to Disabled=1

 

4) write the file out

 

5) run DX10Controller go into the general dialog and hit ok

 

6) run fsx

Share this post


Link to post
Share on other sites

Hallo Steve

 

I use your Programm Version 1.4

 

1. Must i install the fix from avsim dx10 runway Patch 3.2.2 or is it include of Version 1.4.

 

2. When i shut down my Fsx in fullscren mode the Fsx crashes.(unknown module)

When i shut down in Window Mode it works

The fixer Are Works perfekt when i use fsx.

Sorry about my bad englisch

 

Frank froh EDDM

Share this post


Link to post
Share on other sites

1. No it's included

 

2. See replies to other posts

Share this post


Link to post
Share on other sites

Version 2.0 build 42

 

1) UK2000 PAPI light appear square at night - disabling Version2.0 Transparency in Legacy Dialog will fix this - I am working on a new version

Share this post


Link to post
Share on other sites

Hi,

 

after installing version 2.0 I have no more PAPI lights at LOWI - using the scenery from Aerosoft "APPROACH INNSBRUCK". Is there anything I can do to get the lights back?

 

Regards,

Hanse

Share this post


Link to post
Share on other sites

The only change that could really affect the visibility of something is the legacy->v2.0 Transparency rules (and lesslikely the general-> DX10 Transparency bug fix) - try disabling and report back.

 

Also is your legacy slider in the same place as previously?

Share this post


Link to post
Share on other sites

I have an odd issue I just noticed, so I'm not sure that it is new with version 2.0.  I pulled up the kneeboard and everything came to a strange halt, with movment at something like 1 FPS, including TrackIR looking around the cockpit.  This is only in windowed mode.  If I switch to full screen, everything is fine.  Anyone else have this issue?

 

I haven't used the kneeboard since installing and switching to DX10 a few weeks ago, until today.  

Share this post


Link to post
Share on other sites

The only change that could really affect the visibility of something is the legacy->v2.0 Transparency rules (and lesslikely the general-> DX10 Transparency bug fix) - try disabling and report back.

 

Also is your legacy slider in the same place as previously?

 

I unchecked all three Legacy Options but still no change e.g. no PAPI lights and I never touched the slider. But what I recognized is that the lights are on if I manually place the plane on or near to it those two LOWI runways. But when approaching LOWI during a normal flight those lights are off  (during day and night operation).

 

Hanse

Share this post


Link to post
Share on other sites

Oh that's normal then, you just need a light field see the end of effects chapter

Share this post


Link to post
Share on other sites

Oh that's normal then, you just need a light field see the end of effects chapter

 

Hi Steve,

I did everything what is explained in the manual (e. g. copied the file into the scenery folder of the add-on airport LOWI) and with "TRANSPARENCY" unticked I now have no more problems during a night approach. But still there are no red/white lights (left and right of the runway) during day operation. Is there anything I can do regarding this issue?

 

Hanse

Share this post


Link to post
Share on other sites

One person suggested that at one airport in Alaska he needed to select the destination first before switching to the starting point if it is more than 10km away. I haven't been able to reproduce this.

Share this post


Link to post
Share on other sites

One person suggested that at one airport in Alaska he needed to select the destination first before switching to the starting point if it is more than 10km away. I haven't been able to reproduce this.

 

I tried this proposal e.g. first loading the arrival airport / runway (lights are on) and then changing to the departure airport. But unfortunately no change during daytime approach e.g. mentioned lights are off. Only when switching to dawn, dusk or night the lights went on.

Share this post


Link to post
Share on other sites

Ok have you tested what happens in DX9? and are you sure that they worked in an earlier version of DX10SF?

Share this post


Link to post
Share on other sites

Steve,

 

I just did the same flight using DX9 and no problems with those lights. In previous versions of DX10 it also worked. You can see that in the YouTube video I prepared

http://youtu.be/ScrJ3Xh5K1E

app. at the position of 37:00 ........

Share this post


Link to post
Share on other sites

Did you test disabling the d10 transparency fix in general? That's the only remaining difference between the previous version.

Share this post


Link to post
Share on other sites

Version 2.0 build 42

 

1) UK2000 PAPI light appear square at night - disabling Version2.0 Transparency in Legacy Dialog will fix this - I am working on a new version, there are some other sceneries that have issues for the same reason.

 

2) AMD aa options are implemented wrongly, what you see when you launch it is correct so if it says 4x it is 4x but when you make a change the options are interpreted incorrectly. 2xEQ is treated as 4x and 4x is treated as 8x and other options are ignored.

Share this post


Link to post
Share on other sites

Did you test disabling the d10 transparency fix in general? That's the only remaining difference between the previous version.

 

I just deinstalled and newly installed "Approaching Innsbruck" as well as the "DX10 Scenery Fixer". Then I disabled the DX10 transparency option. But still the same result e. g. during day-approach no lights (4 red/whites left and right to the rundway) at all. When switching to night all PAPi lights came up......

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this