It's still a couple of weeks, thus LM might present a hotfix or whatever inbetween. Otherwise, I tend to 3.3 which served me quite well and stably so far.

 

I need neither VR nor avatar weapons either,.jpg screenshots would be nice, perhaps.

 

Kind regards, Michael

 

 

I do not need VR support, avatars or avatars weapons (why that later feature? We want a sim, not a kid toy).

 

Chris the reason is because we simmers are not the customer that LM is focused on. You and I are not much more than Beta testers. The applications for Avatars and weapons creates huge opportunities within the virtual training world.

Did anyone else discover after updating only the client this issue (content update may be required, but may break airplanes?) that FSDT and coautl menu keyboard shortcuts do not work?  I was hoping to avoid the update of the content, for fear of having to reinstall airplanes and scenery addons (effects folder, or is this only aircraft effects)

Did anyone else discover after updating only the client this issue (content update may be required, but may break airplanes?) that FSDT and coautl menu keyboard shortcuts do not work?

 

Did you upgrade the FSDT add on manager?

Did you upgrade the FSDT add on manager?

Yes I did.. basically reran the setup for it, which it then pulled down the latest version.  From what i read elsewhere, it appears that the shortcuts wont work without a content update.  Hoping this isnt true.

Did anyone else discover after updating only the client this issue  I was hoping to avoid the update of the content, for fear of having to reinstall airplanes and scenery addons (effects folder, or is this only aircraft effects)

The content update leaves your airplanes and sceneries untouched. No worries. It overwrittes the files in the autogen folder though, so that you need to backup them if you use FTX Global, or reinstall FTX Global.

The content update leaves your airplanes and sceneries untouched. No worries. It overwrittes the files in the autogen folder though, so that you need to backup them if you use FTX Global, or reinstall FTX Global.

 

I had imaged my p3d drive and did the content update.. since then i restored prior to doing this.. when i ran this before (uninstall content, then update).. it broke several of my planes, like the Legacy which had pop up errors for missing sound files and other files.   Autogen wise, i guess i'd just back that up or reinstall in my case GEX, not sure why last attempt resulted in broken planes.

The content update leaves your airplanes and sceneries untouched. No worries. It overwrittes the files in the autogen folder though, so that you need to backup them if you use FTX Global, or reinstall FTX Global.

 

I reinstaled Content and Client and had no problem with the FTX products. I didn't have to do anything.

Global, EU OpenLC, North germany... all working.

As confirmed by Rob's AVSIM P3D Guide (page 19), content will inter alia do overwrite these autogen files:

 

…\Lockheed Martin\Prepar3D v3\Autogen

AutogenDescriptions.spb
Default.xml
Extrusions.spb
RoofDescriptions.sbp

 

If you have not backuped them, you are NOT using the original (Orbx) files anymore. You will not notice it unless you come into certain situations. For intance, all entries of Aerosoft VFR Germany (and other devs) are included in ORBX Default.xml, but not in the P3D Default.xml file. Just compare the file size. There will be no autogen using these photo sceneries unless you re-install ORBX libraries again, or replace the autogen files with your backuped files.

Hmm, now I have a dilemma. New rebuild on it's way back to me, ready to install P3D or FSX SE over the weekend. I had made the decision to go P3d, but now I'm not sure 

 

Get the both of them! FSX SE is often in sale at a fiver!

Jay

As confirmed by Rob's AVSIM P3D Guide (page 19), content will inter alia do overwrite these autogen files:

 

…\Lockheed Martin\Prepar3D v3\Autogen

AutogenDescriptions.spb

Default.xml

Extrusions.spb

RoofDescriptions.sbp

 

If you have not backuped them, you are NOT using the original (Orbx) files anymore. You will not notice it unless you come into certain situations. For intance, all entries of Aerosoft VFR Germany (and other devs) are included in ORBX Default.xml, but not in the P3D Default.xml file. Just compare the file size. There will be no autogen using these photo sceneries unless you re-install ORBX libraries again, or replace the autogen files with your backuped files.

I backed these up as well as some of the other folders and ran the update (after uninstalling).. all ok now, i can see the windows pop up now 

 

Thanks for the suggestions all

To those who suffer from VAS issues in P3D v3.4.9:

 

Have you tried deleting your cameras.cfg in the same folder where you can find your prepar3d.cfg-file?  Doing so has apparently alleviated the problems for some users, as the VAS issue might be related to the new cameras LM has added.

 

In the rebuilt camera.cfg-file, can you then delete all entries following:

[CameraDefinition.011]
Title = Multiplayer Planes

 

At least it's worth a try.

What if the autogen files get over-written is there nothing to do but re-install airport or other sceneries since I have no way of checking whether they rely on an autogen entry? I know Ultimate Terrain and Orbx stuff when running the config tools will re-set their entries automatically.

The content update leaves your airplanes and sceneries untouched. No worries. It overwrittes the files in the autogen folder though, so that you need to backup them if you use FTX Global, or reinstall FTX Global.

 

You need to do neither. You simply have to execute FTX Central again. That will write all the necesarry entries.

I backed these up as well as some of the other folders and ran the update (after uninstalling).. all ok now, i can see the windows pop up now 

 

Thanks for the suggestions all

I should add, that on the content update.. i backed up the autogen and then did the restore of that folder plus the other related content ones, telling it to NOT overwrite..

I thought this was done and good.. i did get fsdt menus etc.. however..

 

PNW was messed up autogen wise.. running ftx central 2 with a sync did NOT fix it in my case.. so i ended up copying WITH overwrite the autogen folder i backed up, and now it all looks good again.