JerseySeven

After a couple of flights in the vFlyte Turbo Otter, my 750 and 650 would not turn on either. I went and copied the RealityXP.GTN.ini file from the same plane in X-Plane 11 to the Turbo Otter folder in X-Plane 12 and they are both working again. Many of the lines in the .ini in X-Plane 12 were missing, and that may have contributed. Whether they were like that from the start, or got corrupted somehow, I don't know. I'll be saving copies from now on, for sure!

Ok, well that's something at least. Somethings different between your 747 and other aircraft. On my stock Cessna 172 in the "Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\panel" folder I have the following under [window00] gauge21=Cessna172!Panel_Lights_Switch, 342,418, 30, 34 Do you have a corresponding entry? For comparison, my 747 panel.cfg has this under [window04] gauge08=Boeing747-400!Panel Lights Switch, 357, 1 The actual gauge info should be in .dll files in the "Gauges" folder. Mine are all dated 9/20/2007 around 5:10 PM or so. I've never messed inside the dll files and I suspect you have not either. Just check they are there. Also, any chance that you have a joystick or throttle controller button programmed to "Shift+L" that is conflicting?

I think you've identified why "L" is not turning on your cockpit lights. "shift+L" should turn on the cockpit illumination. If its not, something is wrong. You've probably already checked the keyboard assignments in the configuration, and since you see a momentary flash, the key must be trying to turn them on. Are you running DX9 or DX10? If DX10, have you installed Steve Parsons' v3.2.2 shader pack?

Pocketwatch50 On reflight I turned on the "carb heat" and prop de-ice. Helped a bit but I still had to descend to 5,000 ft to regain full engine power. Needed the carb heat the rest of the flight until landing, even though I was out of the icing conditions. Speed was highly variable on approach. I found I had to constantly adjust the throttle to maintain 100 kts. Normally only 19-20" MP needed - I was all over from 20-30". Seems like a buggy flight model...

Thank you for the suggestion. The list of keyboard commands shows carb heat as 'H' (which apparently does other things in the Mooney). I'll try reflying and see if it helps.

Flying at 9000 feet with OAT = 5C. Encountered light rain. After a few minutes the MP started dropping and I could not maintain altitude. Pitot heat was on. I hit 'H' to turn on Alt Air and Prop de-ice, but these did not help. I see no other ice control switches in the cockpit. I tried assigning an additional key combo to "de-ice" in settings but this did not help either. Mixture settings and prop rpm were properly adjusted for level cruise at this altitude. In the Beech Baron, this problem was easily fixed by turning on a set of anti-ice switches in the VC. MP would almost instantaneously return to normal. Is there anything I can do with the Mooney in this situation other than turn around and land? If not I'll have to avoid this aircraft. Thanks

I purchased IF10 a few weeks ago, based largely on what I've seen in threads like this. I have not been disappointed. Though I am listed as a newbie, I've been simming since MS Flight Simulator first arrived on the PC back in the early-mid 80's. Gorgeous 4 color CYMK graphics and 1-2 FPS on landing approach! Those were the good old days, eh? I quit flying simulators a few years ago, when I realized that I was spending more time planning flights than actually flying. I typically used 4 or 5 different programs, including a two I wrote myself. Not to say that planning is not enjoyable in itself, but I guess I got kinda burned out. IF10 has played a big role in jumpstarting a renewed enjoyment of computer flying. Thanks, SteveW et al. Looking forward to the updates!

I read this week where MS is stopping further development of DirectX. Several possibilities suggest themselves: 1) They are working on an alternate technology; 2) DirectX is deemed as perfect as it can get and no further tweaks are necessary; 3) they are abandoning the PC as a gaming platform.

FWIW: I noticed the cone-shaped rotating beacon with my recent stock FSX install and DX10-preview checked. As I posted elsewhere in this section, the fix turned off all airport lights in my setup, so I restored the default .fx and .bmp files ... but I still have cone-shaped airport beacons just like before. You think your beacons changed only after you tried the night-light fix? Funny how systems can differ. I'm using NVidia - is your GPU ATI/AMD?

Hi all, Getting back into sim flying after a 2 year hiatus now that I have the rig to do it right (NVIDIA GeForce 680GTX; driver ver 310.90; intel i73770 3.5 GHz; 16 GB memory; win 7 x64). Was flying with DX10 preview ignoring the occasional artifact when I saw Paul J's sticky in this forum on "How To". Long story short - went through Steve's pdf (Thank you for the improved shaders!). All was fine until I added the changes listed under "Nav and Strobe Lights" fix and the "Runway Lighting" fix. Basically these last few files and tweaks did the exact opposite for me. Turned off the aircraft lights as well as all of the runway lights. Fortunately I had the vanilla effects and texture files backed up and replaced the "fixes". Now I have lights on my plane again (flying the stock Beech Baron 58 currently) and the runways lights are back. I'm not using any additional scenery that would have changed the lighting, so...? Just thought I'd post in case someone else had this issue. Best,