For those who haven't noticed...

[DaveG]

Apparently there there are issues with FSUIPC at the moment. Something must have changed between the last beta and the release versions of P3d. Pete Dowson is on holiday at the moment, but I'm sure he'll sort it out in a day or two.

[J0hn]

Ah - thanks for that.

[TSR2]

Possibly a limitation on my Graphics card, but some of the ground models do a weird spinning thing for a few second before settling down. Its as though they spin the Z axis until the card catches up. Its only a few things, Souter Lighthouse and the Angel of the North our two examples. Also, on the Vanguard, the rear of the engine under the wing is black on No.1 and No. 4. Otherwise, the systems in Frasers panel seem to work as expected from a cold start, but haven't tried the AP yet.

[GHD]

To get FSUIPC to work, rename SimConnectP3D2.dld in modules\ to SimConnectP3D2.dlD.

The FSUIPC VAS display also works

[TSR2]

Cheers George, I'll give that a go. I noticed that I had a lot of "flooding" around Heathrow, but then I realised that my GenX and UK2000 scenery was all in the wrong order, so I suspect that might be the problem there. Some of the older FS9 models seem non to keen on displaying some of their light, particularly the Nav and Landing lights, beacons don't seem to be a problem though.

[GHD]

It is also worth setting afinity in the cfg, by default it uses only 3 cores on a 4 core processor.

[airboatr]

Ben, those screenies are quite entertaining....

naughty man.



I'd love to have this PD 3 , but no PC to run it on.

[J0hn]

Thanks for the tip on FSUIPC - I'll try that later, when I've woken up!

Never mind 'wake up', I was getting a bit wound up last night, when I couldn't get REX to agree that I have paid the P3D licence. After reading lots of irrelevant blurb on their support forums I suddenly had a thought "Hmm, I wonder if applying a saved back-up config will work?". I can't even remember saving a back-up (which requires a user name and password), but it seems I did, and guess what? Yup - now working with P3D.

According to the 'blurb' I read in the forum, the fog(mist?) needs to be turned off in REX for P3D else it clashes with the default 3D fog:

REX Essential Plus / Overdrive works well with Prepar3D v 2; however, because of some changes to weather features such as 3D fog, we recommend that you disable the volumetric fog option within Prepar3D or turn off “Enable realistic Visibility” within REX. These precautions are in place ONLY if you're using the REX weather engine.
All other features operate correctly with Prepar3D v 2.

We'll be issuing a public beta of Service Pack 3 which includes fixes to handle the volumetric 3D fog, as well as the added support for PMDG 777 wind import features.

George, I was wondering if it was set to use only 3 of 4 cores so that the fourth one was available for use by ancillary programmes - like REX, for example

No idea, but just a thought. Right, I'm off to do some more installing

[J0hn]

Does anyone know what happened to the scenery.cfg file? I can't find it anywhere. I went to the P3D site to check and it should be where I expected it to be - but it isn't!

Finding the UI a bit clunky, I'm afraid, but I guess I'll get used to it. I installed some missions, but have no idea as yet, how to access them - but this scenery config is the biggest issue at the moment. Although the scenery has installed to P3Dv2, it has made the entries in the FSX scenery config file and I need to swap it over. Had to do the same for the entries into the dll.xml file.

Also - George, you mentioned changing simconnectP3D2.dld to simconnectP3D2.dlD - well I'm not sure what you mean, as the file in modules is simconnectP3D2.dll

[PeteP]

Not sure if this helps but my scenery.cfg is in C:\ProgramData\Lockheed Martin\Prepar3D v2
Pete