Michael Cependa

I see this all the time. I don't think there's any fix.

I am using Opus FSI without any apparent problems.

Try excluding the Lockheed Martin folder in your anti virus program. That worked for me.

With this version, is it possible to push the Orbx night lights a decent distance out from the viewpoint? Aside from the OOM errors, this is pretty much the last problem (except for perhaps the water) preventing me from enjoying P3D v2.

Truly bizarre.

I installed the patch over an existing 2.0 installation with a few addons. The patch installed OK, but the sim would crash a moment after loading. I then removed the four folders of app data as recommended by LM and everything seemed to work after that. I noticed that any changes to controls will not be saved until you exit the sim. If you change flights after changing the controls, your changes will be lost. So best to make the changes and then exit the sim immediately. The only hitch I had is that when I tried to save a profile of my controller settings, I cannot type text in the box to give the file a name. I see others have reported that as well. Anyhow, it didn't matter as I found how to make the changes stick, as related above. 2.1 definitely runs smoother for me and looks better in a number of ways that are hard to pin down exactly. The terrain shadowing looks better somehow. I also seem to have a lot more autogen than with 2.0 to the point where I think I can lower my settings a bit -- I have never seen such dense autogen as I had with 2.1 running FXT Gobal and True Landscape France. I had an OOM over Paris, but not surprising really with the insane amount of autogen I had displayed while flying a jet at 500 knots.

They have finally taken note of the problem at Orbx and "will try to get it looked into". Apparently, they had only used the lights on a beta P3DV2 before releasing it and it seems LM changed something at the last moment.

I only use real weather and don't care for the look of near unlimited visibility (which does not occur in nature), so setting the weather to minimize the problem is not really an option for me. I tried dummy bgl files, but the sim behaved as if they weren't there. Someone who does scenery design could probably create a file in the right format that wouldn't display anything visible, but I don't propose to put in the time to learn how myself. Orbx simply will not post in any thread dealing with this issue on their forums -- why I have no idea. I guess it will get sorted in the end.

I have found that if I set the startup to the scenario set up screen I can get away with a single flight anywhere with the 3D light files deleted. However, the sim will CTD on exit, so you can't change any settings in this mode and expect them to stick. I seem to get a CTD if I rotate an external view a lot, but I don't know if this is related. The sim looks amazing with FTX Gobal and no white boxes.

Removing the files sounds like a good idea, and I tried it, but it caused p3d to crash every time I attempted to leave the default flight..

Do you know what the files are called and where they are?

The regions (except maybe the one released today) have a different type of lighting that as far as know doesn't exhibit the problem. Are you using FTX Gobal outside an FTX region with volumetric fog off without seeing white boxes?

I have a number of OrbX products installed in FSX, but nothing OrbX in P3D except FTX Global.

Is anyone running FTX Global on P3DV2 without the white boxes around the the FTX lights during daytime? Anyone not seeing the boxes with volumetric fog turned off? (The problem is not as obvious with fog turned on.) You need to be over an urban area to see the boxes. The threads on this problem at the FTX forums seem largely ignored and I am left wondering if this is a universal problem or something only a few people are experiencing. This is a bit of a show stopper for me as I have little interest in running P3D with default terrain textures.

I have the virtual fsx installation enabled. I have the navdata installed. I can't figure out why it doesn't work for me. Maybe I should reinstall. Anyhow, I'm thinking of putting P3D V2 aside for a while as with FTX Global installed I have little white boxes all over the landscape that I really don't care to see every time I start the simulator.

I get the fatal error even without any flight loaded.

I can't get it working. I installed with Estonia migration and copied the gauges over, but I get a fatal VoxAtc error when I click "enable".

There's an affinity mask tweak to add to your .cfg file. If you do a search you'll find it. It completely solved the problem for me. Although, I'm a long way from maxed setttngs.

Good to know there is a workaround for this, as this problem has been something of show stopper for me. If I make any change in settings my FPS plummets. Up till now I would restart the sim to get them back, but tonight I will try the methods in this thread.

I'm in. Thanks.

Thanks for the very fast reply. By the way, I am really wanting to get into the support forums and have sent the necessary email information.

I can't get the autopilot to track an outbound VOR radial. The aircraft just rolls until inverted. Is this a known problem?

By way of a general comment, I think the Milviz 737 is one of, if not the absolute best, classic jet airliner on the market for FSX. Having said that, the system of registration for the support forum strikes me as a little bizarre. Having to engage in email correspondence with every single customer and then manually register them must represent a colossal waste of time for the developer and is certainly frustrating for the customers, not knowing when they will receive access. Surely this process could be automated?

Actually, on re-reading the thread, it's not the same problem I'm having now. What I get now is the controller asking "did you copy" over and over again, with no way to move on.

The problem has come back. I recently updated Vox to the latest version, updated all navdata for programs that use navdata, and ran the Vox indexer again -- not sure if any of those things could contribute to this problem. Is anyone running FlyTampa Montreal with Vox successfully?