DavidV935

Ryan... great photos! I've never had clouds look like that in my XP11. What did you do to get those? Thanks for sharing!

Charlie...you rock, man!! Before seeing your last post, I copied the lights section in your earlier post and pasted that into my aircraft.cfg. Everything looks normal now, so thank you so much!!

Okay Charlie, I just compared the [LIGHTS] section in my 737-800 and it's different than yours. Your lights go from .0 to .9 while my section goes to .10 and skips .7. ???? How does that happen when the only thing I did was add texture folders for additional liveries? [LIGHTS] light.0=3, -24.60, -57.50, 3.90, fx_navred , light.1=3, -24.60, 57.50, 3.90, fx_navgre , light.2=2, -71.32, 0.00, 5.92, fx_strobeh , light.3=2, -25.50, -58.30, 4.20, fx_strobeh , light.4=2, -25.50, 58.30, 4.20, fx_strobeh , light.5=2, -7.55, 0.00, -5.50, fx_beaconb , light.6=1, 2.00, 0.00, 8.70, fx_beaconh , light.8=3, -29.00, -56.60, 3.70, fx_navwhi , light.9=3, -29.00, 56.60, 3.70, fx_navwhi , light.10=6, 41.85, 0.00, -6.80, fx_navwhih,

Charlie... in flight, gear up, nose gear door closed. See below. This is just the Delta texture for the default B737-800 in FSX. The Microsoft default liveries show the same thing.

The default B737-800 in FSX has a green anti-collision light fixed a few feet under the nose gear door. Does anyone know where to go to eliminate that? Thanks.

Jim...I will always defer to your insights since your depth of knowledge is far greater than mine. I was just trying to connect dots to find the root cause. I guess the coincidence here is the logbook.bin becoming corrupt when I exited FSX the first time. I used your CTD Guide to methodically go through things, but you can't look at the logbook.bin and know something is wrong. I am really thankful that I routinely do a system image backup because I obviously overwrote the good documents\flight simulator X files folder with a bad one.

Thought I’d share my recent experience with FSX when it failed to load. This is a new variation not covered in the AVSIM CTD Guide. I have FSX Deluxe with SP2 installed on a Windows 10 PC. The evening before the failure, I had started a short flight from EDDT to EGLL, but changed my mind about the plane I was using and exited FSX. When I came back, I clicked to FSX icon to launch the program and the splash screen appeared, and then FSX just hung up. I had to use Task Manager to kill FSX. Tried several times with no success, so figured I had a corrupt file and put the DVD in and ran the Repair FSX. FSX continued to hang at the splash screen. Next, I pulled out Jim Young’s fabulous AVSIM CTD Guide v 5.0 and double checked all the recommended settings – all settings and recommendations in place, but still no success. Next, backed up all my personal data folders (documents, pictures, music), then retrieved my other backup drive and restored my latest system image. SUCCESS – FSX launched all the way into the program and I could fly again!! After feeling relieved, I restored my personal data folders to bring back the latest emails, documents and photos. On my next attempt to launch FSX, it failed at the splash screen again! Restored from my system image again, and FSX worked (again). So, this time, I pulled over individual folders within my backup Documents except the Documents\Flight Simulator X folder. FSX launched successfully. Finally, I went into the Documents\Flight Simulator X folder on my backup data drive and deleted the last flight plan I had created from EDDT to EGLL (IFR Tegel to Heathrow.PLN). Everything works fine now!! Lesson here is that a corrupt flight plan file (.PLN) in your Documents\Flight Simulator X folder can prevent FSX from launching. Go figure…

My FSX logbook stopped recording flights after I installed a particular add-on. I downloaded that fslogrecovery11.zip from the library. I have no idea of what it actually fixed after I pressed the "analyze" button, but it fixed whatever was wrong and logbook now works!! Wow!

I just purchased REX Sky Force 3D this past weekend and have encountered an issue I don't know how to resolve. First, let me say that I use FSX w/ SP2 on an average PC with an i5 processor 3.3GHz, 16GB system RAM, AMD Radeon R7 360 video card with 2GB RAM. Installation was not intuitive since their README is incorporated into their installer, so you can't read it before you attempt installation. After going to their website forum for help, I learned that anyone who purchases this software MUST disable your anti-virus software BEFORE beginning installation, and must add the program folder to the Exceptions list in your AV settings. If you don't, your AV will forceably stop REX from installing or working after installation. I discovered and downloaded and installed their Hotfix 1. I also discovered the hard way after installation, that when you run FSX and you select the weather component for your flight, you MUST select "Weather Themes" at the top left, and then find "REX" in the list of themes. If you select anything else, the REX weather will not come into your flight environment (I think). This wasn't mentioned in the README file, so I didn't even think to look for it and selected my usual Real Weather Updates every 15 minutes. Once installed, I discovered the new cloud formations are pretty fantastic - especially the cumulus and cumulo-nimbus. I did several flights picking places in Europe or USA with active showers or storms and loved the transitions from low to high through rain clouds and descent back from high to low through reasonably thick cloud layers. I especially like the reduced visibility at the surface for fog or haze associated with winter storms. Now the problem: I discovered the winds do not import into FSX properly. I believe the surface winds are accurate, but once you take off, winds aloft are not imported and updated as you change altitudes in your climb, cruise, or enroute descent. Additionally, while my Indicated Air Speed on my B737 was 300, my TAS remained very close to IAS and my Ground Speed was only affected by the initial surface wind speed. Example: while cruising at FL330, IAS = 300; TAS was only 290, and GS showed only 289 (IAS minus surface wind speed of 11kts). That's not possible. TAS and GS should have been up around 475-525. The impact is that your flight takes a lot longer because your ground speed is only 300 instead of 500. I don't know whether this is one problem or two problems. When I reflew that flight in FSX using the same B737 without using REX, I got normal TAS and GS at all altitudes. I've posted these observations in the REX forums, so I'm hoping REX staff recognizes what the issues are and puts out another Hotfix.

I just purchased REX Sky Force 3D this past weekend and have encountered an issue I don't know how to resolve. First, let me say that I use FSX w/ SP2 on an average PC with an i5 processor 3.3GHz, 16GB system RAM, AMD Radeon R7 360 video card with 2GB RAM. Installation was not intuitive since their README is incorporated into their installer, so you can't read it before you attempt installation. After going to their website forum for help, I learned that anyone who purchases this software MUST disable your anti-virus software BEFORE beginning installation, and must add the program folder to the Exceptions list in your AV settings. If you don't, your AV will forceably stop REX from installing or working after installation. I discovered and downloaded and installed their Hotfix 1. I also discovered the hard way after installation, that when you run FSX and you select the weather component for your flight, you MUST select "Weather Themes" at the top left, and then find "REX" in the list of themes. If you select anything else, the REX weather will not come into your flight environment (I think). This wasn't mentioned in the README file, so I didn't even think to look for it and selected my usual Real Weather Updates every 15 minutes. Once installed, I discovered the new cloud formations are pretty fantastic - especially the cumulus and cumulo-nimbus. I did several flights picking places in Europe or USA with active showers or storms and loved the transitions from low to high through rain clouds and descent back from high to low through reasonably thick cloud layers. I especially like the reduced visibility at the surface for fog or haze associated with winter storms. Now the problem: I discovered the winds do not import into FSX properly. I believe the surface winds are accurate, but once you take off, winds aloft are not imported and updated as you change altitudes in your climb, cruise, or enroute descent. Additionally, while my Indicated Air Speed on my B737 was 300, my TAS remained very close to IAS and my Ground Speed was only affected by the initial surface wind speed. Example: while cruising at FL330, IAS = 300; TAS was only 290, and GS showed only 289 (IAS minus surface wind speed of 11kts). That's not possible. TAS and GS should have been up around 475-525. The impact is that your flight takes a lot longer because your ground speed is only 300 instead of 500. I don't know whether this is one problem or two problems. When I reflew that flight in FSX using the same B737 without using REX, I got normal TAS and GS at all altitudes. I've posted these observations in the REX forums, so I'm hoping REX staff recognizes what the issues are and puts out another Hotfix.

Jim...as always, I've been saved by this reference document several times and have been grateful that you've kept it up. Thanks for your diligence to this product! If we ever meet again, you will drink for free all evening!! :-)

I took your suggestion and copied the Northwest file "rouen2.bmp" and pasted it into the Provincial and FlyBe texture folders overwriting the ones there and it worked. Now that I know that works, and I see your Provincial Saab photo, I think you've quite skillfully helped me figure this issue out. Fixing DX10 helped resolve one set of issues while forcing me to accept that my CRJ 100/200 will just have to go. Thanks so much, Charlie for helping me with this!

Steve...thanks for the response. Obviously, I didn't have the contents of your manual stored in my RAM ;-) so sincerely appreciate the specific guidance. I noticed the wheel texture name in all three Saabs was rouen2.bmp, so will see if simple copy and paste works for those planes.

Charlie...now that I look at the readme for the PAD Saab340, the included jpg show clear windows and crew in the cockpit which means the window textures are missing too.

Got the Saab from PREMIER AIRCRAFT DESIGN SAAB 340B FOR FSX/SP2 (Ver 2 02-Oct-2009) Aircraft, panel and sound package including dynamic VC with custom gauges. Textures look like they could have been originally for FS2004, but don't know for sure.

While I posted this issue of missing wheels in the main MS-FSX forum, I thought I would also post here for visibility in the DX10 discussion just in case this is a DX10 issue. Last month, I bought and installed SteveDX10Fixer v3.3.103 and most of my missing textures showed up. However, I am still missing the wheels on some of my planes and I can't figure out the problem pattern especially when my Saab340 addon shows one livery with wheels and another livery without wheels (see below). Could this be an AMD Radeon setting, or does this have anything to do with the shader cache? I'm stumped. System info: MS-FSX Deluxe with SP2; i5 processor with 16GB RAM; AMD Radeon R7 360 graphics card with 2GB

Charlie... DX10 Preview is checked; and I'm using FSX Deluxe with SP2 installed; i5 processor, 16GB RAM, mediocre AMD Radeon R7 360 graphics card with 2GB video RAM. When this started happening early last month, I bought and installed SteveFSXfixer which seemed to solve several texture issues for many of the planes, but I still have a few addon planes that this persists.

I have others that are missing too...

Any idea of why wheels would be missing? I'm stumped especially when the textures are for the same Saab340.

vortex681 and Charlie Aron...thank you! I just unticked that box and tried one of my aircraft that showed no textures and it painted fine right away!

I have it ticked, but not accidentally. On page 9 of Jim's FSX Basic Configuration Guide, it shows it checked, so that's what I did.

The screenshot on my computer that comes from pictures\Flight Simulator X Files\ does not show the white polygons for clouds or the white polygons on the ramp surface. Have no idea why they show now???

I am stumped. This just started a few weeks ago after I updated my AMD Radeon graphics driver. I have addon aircraft downloaded from the library that are completely white - no external fuselage textures at all; some with partial textures - fuselage textures but no gear/strut textures OR vice versa, and others show all fuselage, gear and strut textures. I'm trying this embedded code for the first time hoping it shows you what I see. Any advice or insights is greatly appreciated.

Reading this chain tells me you guys are real pros at painting, so I'm going to take a shot in the dark and ask if you have experienced the problem I suddenly have. I'll start by saying I upgraded my AMD graphics card driver in June and things haven't been quite right ever since. Recently, I discovered that many of my downloaded add-on planes do not show all the textures, and I get several variations like: the body textures display okay, but aircraft wheels and struts do not show (but they are there); the complete aircraft is white and no paint textures display at all; the wheels and struts textures display, but the body is white without textures. What I cannot fathom is that all the FSX default aircraft display normally. Do the addons have something that the default aircraft don't? Is there something common to all these partial displays of textures? Is there some setting in my graphics card that I should look for? I'm stumped by the inconsistency of effects across the myriad aircraft I have. Any insights or advice would be greatly appreciated. Thanks for your time.

Thanks (once again) Jim. Got it going, but it appears this sudden issue was somehow connected to Norton AV quarantine of GEX interface and exe which seems to defy my reasoning abilities! When I restored GEX from Norton quarantine and then retried launching FSX, it rebuilt the fsx.cfg and completed the launch sequence. I notice those two shader_cache lines at the top of the graphics section and everything worked. I made the changes in the FSX Configuration Guide. I don't seem to have the same quality of scenery details that I previously had, but will have to continue tinkering with that. Thanks again, JIm!