September 25, 201312 yr Commercial Member 1. Dawn/Dusk.There is a problem at the transition from dawn and dusk to day. At legacyairports the ground may appear like chrome. I have a fix which will beavailable by early next week.Fixed in build 192. bkg.bmp/envmap.bmp If somehow these have been converted to a .dds thenthe installation will fail. I have updated the manual to say this. You needto restore the original bkg.bmp and remove the dds. I hope to be able towork around this more gracefully.Added Additional Checks in Build 17 and Build 193. envmap.bmp As a separate issue if your envmap.bmp is still there but isa different size to the original then all is well until you try and disableeffects. An error will appear "envmap.bmp not recognized" and you cannotre-enable effects. Uninstall/install the libraries to resolve this.Added Additional Checks in Build 17 and Build 194. Standard User Account. If your main user does not have admin rights thendisabling 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 MSFixed 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 My FSX Analysis Blog
September 26, 201312 yr 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. -Anthony Young- "For once you have tasted flight you will walk the earth with your eyes turned skywards, for there you have been and there you will long to return." - Leonardo da Vinci
September 26, 201312 yr 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. Rich Sennett
September 26, 201312 yr 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. -Anthony Young- "For once you have tasted flight you will walk the earth with your eyes turned skywards, for there you have been and there you will long to return." - Leonardo da Vinci
September 27, 201312 yr Thanks Steve! -Anthony Young- "For once you have tasted flight you will walk the earth with your eyes turned skywards, for there you have been and there you will long to return." - Leonardo da Vinci
January 7, 201412 yr Author Commercial Member 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 My FSX Analysis Blog
January 18, 201412 yr Author Commercial Member All three issues now fixed in Build 35 My FSX Analysis Blog
January 31, 201412 yr 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 WIN 11 64 Pro, Gigabyte Z790 Aorus Elite AX, I7 13700K, be-quiet Loop Silent 2 WK, RTX 4080 S, 64 GB DDR5 Kingston Fury Beast EXPO, 4x Nvme Samsung PRO, MS2024, be quiet SP11 850 Watt
January 31, 201412 yr Author Commercial Member 1. No it's included 2. See replies to other posts My FSX Analysis Blog
March 15, 201412 yr Author Commercial Member 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 My FSX Analysis Blog
March 15, 201412 yr 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
March 15, 201412 yr Author Commercial Member 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? My FSX Analysis Blog
March 16, 201412 yr 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.
Archived
This topic is now archived and is closed to further replies.