Another Lesson Learned

[falcon409]

I installed the Aerosoft BushHawk this morning using the EMT. Everything worked as it should except that when I went in to fly, I discovered that the mapping for my joystick and CH Throttle were gone. Looking at the install time/date stamp and the time/date stamp for the "controls (xml)" file. . .identical. For whatever reason, it wiped that file clean, back to default settings. So lesson learned. . .anything in the P3D folder that houses the cfg file that can possibly be overwritten is now saved to a separate folder to be available, just in case.

 

[gman5250]

I'm treading pretty lightly in P3D2 until the update shows up. Looks like we're short for 2.05. I've probably installed V2 twenty times testing various scenery bugs etc. The DAK was fine until MJ did a new model file to fix a tiny flicker in the window frame. The updated .mdl file crashed V2 and necessitated a re-install. Go figure. I went back to the old .mdl file and everything was fine.

The propensity in V2 for tiny code tweaks to cause disaster is keeping me from going deep until LM tightens up the ship and the various developers synch with the updated sim.

Nothing against P3D2, it's just a complicated integration of overlapping tech and code that will have to be sorted through.

 

[OleBoy]

I did the same back up routine weeks back.

I've had a couple FSUIPC settings issues where they had been wiped out entirely. Not knowing why I just reprogrammed them again. Prior to the settings getting wiped out while I was flying, a box popped up as if the scenery was loading again like when you first start it up. The next time I started all FSUIPC settings were gone.

This is when I backed up the whole Prepar3D v2 folder that resides in C:\Users\YOUR NAME\AppData\Roaming\Lockheed Martin\Prepar3D v2, and anything relevant settings also found inside the Prepar3D\Modules folder (FSUIPC.ini)

Not meaning to sound glad this happened to you. More that I feel better knowing it's happening to others so that LM can investigate the issue of the problem.

I'll be glad to see an update from LM that addresses the texture resolutions.

 

[Lionheart]

Man, that sounds crazy, a program restarting its installation right in the middle of a flight.

And GMan, 20X installations?? ACK! That's too many. Sorry you guys are having issues. Ive loaded mine once and its been running fine. Hardly any crashes at all, perhaps 2 or 3 total, and I light this baby up like 50 to 100X a day checking my aircraft with testing.

I can only think, as you said GMan, that addons need to get things sorted out.


One thing that has been bugging me in the back of my mind is that Migration Tool. I used that and its been in my mind that it might have been a bad thing in that it can 'fool' the intelligent installers but those installers install smart software and if they are in an alien folder system other then FSX, then they will have issues because they aren't supposed to be there (like CapSim planes) so I wonder if doing these migrations is wise. Installing addons that aren't 100% running/tested yet on P3D V2 could be the number one nightmare that people are having. Things that require FSX folder layouts, things that need FSX FSUIPC are probably freaking out and trying to reinstall, causing all this mess.


Man, 20 reinstalls... How do you do it? That's a heck of a lot of down time.

 

[gman5250]

Man, that sounds crazy, a program restarting its installation right in the middle of a flight.

And GMan, 20X installations?? ACK! How do you do it? That's a heck of a lot of down time.

LOL....yeah, that's a lot. I got it right on about number 5, but I've been running a series of tests to shake out some terrain display anomalies relating to ORBX/LM autogen. I'm running a lean setup in P3D2 and focusing on autogen definitions till we get a handle on the conflict.

My current install of P3D2 is running FTX Global and that's all good. Just put in Global Vector yesterday and so far only a couple of tiny bugs.
Concurrently I'm running my own high res photoreal with autogen in a limited area of California. This is running stunningly well. It's stable and absolutely gorgeous with excellent FPS easily making 30 and averaging 50-70 when set to unlimited. These PR tiles are higher resolution tiles than Project Blue Sky. I put these together for R&D/future projects. If I can run these big boys with that kind of performance I think we're looking at a strong platform. It's all in the GPU.

Also to praise FSX, I installed Steve's DX10 Fixer and gained about 60% performance across the board in FSX and effectively killed the micro stutters, bringing FSX into a new level of performance. Again this is down to the GPU.

I'll agree with you on the migrator though. I'm not doggin' the product at all, I think it's great, but I'm doing a bunch side by side comparison installs and I think P3D2 is very sensitive to what goes inside. Force feeding it, for lack of a better term, may lead to a serious re-install down the line. I think V2 is just going to take a bit of patience. IMHO