barneycanoe

Ah, I did get it working with the original fsx configuration, no aero tweak or restart, ie vsync in full screen mode and no vsync in windowed mode. Interesting side note: With FSTramp in full screen, if I enable it I lose the vsync but FSTramp works in fullscreen mode. Dave

I have to run with the AERO tweak, if I try without it I get flashing and random intermittent graphics in full screen mode. I have tried the fsx.cfg vsync settings under both graphics and displays and neither works for me. Dave

+100. Fabulous support and looks like the problem is sorted. One thing though, anyone have the MilViz 310 working successfully. I have a ref file for it and it won't work. Everything else is AOK! DISREGARD - 310 Now working! Dave

Now, I did load up FS9 once and had no issues with default or add-on aircraft. FS9 is installed on C Drive. (Another reason I have FSX on F: is that it is a SSD drive.) So that once again points to the F: drive installation as being somehow the culprit, right? Surely the hardware if it is the issue would affect both sims? Intel Ivy Bridge Core i7 3770 Socket 1155LGA at 3.4GHz, Asus P8H77-M Motherboard Western Digital 2 TB WD2002FAEX-007BA0 ATA drive INTEL 60Gb SSDSC2CW060A ATA drive Cheers Dave

Ah, I wondered what happened to them on my rig also. Dave

Amazing, I can now see my Pilatus Porter (FSD), the ATR 72 (with some transparency) and my Carenado 182RG! Fabulous. Thank you Steve. Dave ps YYZ freeware airport scenery now works at night!

Still trying to identify a common factor for the failures. I guess if I didn't have so many add-on aircraft it might not be so bad. Dave

Well, thanks Paul. I will have to remember to read the HOW TO more frequently

By Golly! This works. Here is what I did and what I think RNGR was trying to say. 1) Download ballast.txt file, rename to ballast.fx and place in FSX effects folder. 2) Make backups of fx_navred.fx, fx_navgre.fx, fx_navwhi.fx files from the same folder 3) Open ballast.fx, select everything from the [Emitter.0] to the last line, i.e. the entire rest of the file down to and including "Extrude Heading Max=0.00") 4) Open one of the three fx files and paste the copied text into the file at the END. 4) Starting with the beginning of your paste, rename your just-pasted [Emitter.0] to [Emitter.4], [Particle.0] to [Particle.4] and so on (if you are changing the fx_navred.fx for instance). The next three entries would be renamed to .5 5) Save, start up FSX and check for nav and strobe lights. Works for me! Dave

Mark, any news on this problem? I'm still stuck with some a/c working, most not?

This seems to work, Thanks! Dave

I have been back and forth with MCE support for a week or so. It's very funny that it ONLY fails with add-on aircraft, and works perfectly fine with everything else though, don't you think? You can see my pc and sim specs in my profile, I was wondering if there was something we had in common. Since I NEVER fly the default a/c I'm in a bit of a pickle, though it works as advertised in the PMDG. Dave

All the Carenado Aircraft Please

Mark, I am having the exact same issue. So far we have got nowhere with it. It fails with every add-on a/c except the PMDG. Real Air, Carenado, Digital Aviation, all no good. Failing somewhere with the aircraft recognition. When it works, as with the default Cessna, everything works perfectly. Still Stumped Dave

Just remember that Addon Converter X will not change night, dusk or dawn textures for, for instance, the Flight 1 ATR. It will work for the daytime only. And Toronto CYYZ is the same. I got a refund for that program and just fly those sceneries in the day when they work fine. Dave