billn53

And the TB-10 is variable pitch vs the 9's fixed pitch prop.

This I can't resist... I got my PPL in a TB-9 at KFME... :-)) Posted too fast... looks like the OP misspoke. It's a TB-10 & 20, but no TB-9 :mad:

The offending file is halo.bmp For triple-monitor systems you need to use a modified halo.bmp to prevent overly-large lights. Do a search in the library or google it and you should find a link to the necessary halo.bmp file.

Same here... watching this topic with interest, waiting for things to settle out and a less involved install procedure. Keep up the good work!

I have the Flight1 standalone and used it with some success while I was earning my instrument rating.

Like the other Bill, above, I've been so long that to list the many aircraft I've flown on is near-impossible. I will say that my first airline flight, as a child, was on a Piedmont DC-3...50-odd years later I still remember that experience! Planes I've piloted since earning my PPL two years ago include: Socata TB-9, Cessna-172, Cessna-182, Piper Warrior, Piper Archer, Super Decathlon, Extra 300L, SIAI Marchetti SF-260 (3 flights with Air Combat USA), and a Blanik L-23 glider. Bill

Very much looking forward to this!

I am an instrument-rated pilot who flies with G1000 all the time. The artificial horizon only shows the attitude of the aircraft relative to the true horizon. The required attitude to maintain level flight is a function of aircraft weight and airspeed. For example, if I am in level flight and I reduce power but keep the aircraft attitude level, the aircraft will descend. Conversely, with reduced power I can keep the aircraft at constant altitude simply by trimming for a nose-up attitude.

Recommend you force a rebuild of your shaders. When FSX was run the first time, a cache was created under the C:\Users\<user name>\AppData\Local\Microsoft\FSX folder. It contains a sub-folder called Shaders (some systems may have an additional folder called Shader10) in which instructions and codes that are frequently accessed by FSX are stored. Every time FSX is run, contents of the cache will be optimized further to improve overall system performance. However, this cache is prone to be messed up when settings of fsx.CFG are changed or system is toggled between DX9 and DX10, etc. To fix the issue, go to the folder mentioned above and delete everything inside the folder. The cache will be refreshed and rebuilt the next time FSX is run.

I've followed all of the suggested fixes (including the FSUIPC wind-smoothing option) and still get an occasional 'ambient weather' crash. I'm hopeful HiFi gets this ironed out soon. At the very least, trap the error so that when ASN 'hiccups' it doesn't cause FSX to crash. Next time I get this error, I'll be opening a support ticket with all the relevant info.

If they haven't advertised night textures, then they probably don't have 'em.

Good discussion. I run triple monitors using two GTX 680s. Frame rates are ok, but not great, and complex scenery or heavy clouds causes performance to plummet. Would I expect to see much performance improvment if I upgraded to dual 780ti's?

I was using Experience X up until I bought FTX Global. Now it's redundant, the FTX-G lights are so nice.

I have a bizarre problem with the Saitek multi-panel in P3Dv2. The landing gear lever, engine rotary switch, and switches for avionics and fuel pump work fine, but the switches for controlling aircraft lights are doing something very strange... Specifically, in the FSX C-172 (ported to P3Dv2 by simply copying over the aircraft folder), when I toggle switches on the multi-panel I can see the appropriate switches moving in the VC. What's strange is that the aircraft lights aren't responding correctly even though the VC switches toggle correctly in response to the multi-panel input. Most of the light switches have no effect on the aircraft lights. The switch for the landing light controls instead the aircraft's beacon. The panel is also not working properly with the F-22's lights. I do have 'Pilot controls aircraft lights' checked in settings. The panel works fine in FSX. I'm using the Saitek panel drivers, not SPAD.

I have this with the stock P3D v2 moon. I tried an alternative set of moon textures (downloaded from the Avsim library) but saw no improvement.