Elevation issues in V4

[ScottyJ]

Copied my flytampa directory to a P3Dv4 add-on folder in it's entirety.

Directed p4 to that folder and installed the 3 scenery entries manually.

Worked fine for all other FlyTampa products?

[emilios[flytampa]]

i suspect you might have missed some files which are not obvious. The file controlling airport elevation for example, which you can find here (on your previous p3d root folder)

>>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Scenery\World\scenery\AFX_EHAM_flytampa_dummy.bgl

grab that and copy into the relevant folder in v4

there might be other files too (i.e. effects), which can be found into :C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Effects

generally i would recommend using the installer instead of manually transferring the sceneries (direct the installer into p3dv4 root when asked)

[ScottyJ]

Hey Emilios!

That did the trick! Many thanks for your help. Would never have even thought to look there!

You're a star!

[skymaine]

Emilios' solution worked for me as well. Very happy about that! In celebration I did touch and goes at several FT airports -- EHAM, LOWW, KTPA, and KMDW. I suspect that KBOS will be my next destination.

Regarding the effects files, I just copied over any one that had flytampa in the name and pasted them into V4. Probably like a lot of customers I thought I was doing the EHAM conversion properly but those files never made it over, not to mention the critical elevation file. The other three airports were updated without a hitch, so the process seemed to work for them but not EHAM.

As an FYI, the way I found out EHAM's elevation was causing problems was at the end of a 10+ hour VATSIM flight in my PMDG 747. I was devastated (as was the 747!) to see the plane crashing into terrain above and around me. Not a happy ending to a very long flight!

In any case, FT has regained its exalted place as the premier scenery designer for yours truly. The work is truly lovely to see.

-- SkyMaine

[JJdayo]

Does anyone know how to get rid of the elevation issue?

I tried everything.

I actually installed EHAM and it only works WITHOUT the patch. No clue how but it runs fine:

Prepar3d V4: FRESH INSTALL
EHAM: Original installer for v3.4

No issues UNLESS I apply v4 patch, then elevation issues.

[Senchai]

Hi
I have some serious elevation issues in V4. I have installed 1.1 as well and the v4 fix. Any ideas. As soon as the scenery loads, everything looks fine then the issues start. Any ideas? This is a brand new install of V4 with no other sceneries added.

May i know wich v4 fix everyone is talking about? I search the page now for a while but cannot see anything. Nor did simmarket, where i bought it, provide me with any updates. So what is everyone talking about?

That beeing said, i dont seem to have any issues too, without this "fix". But i didnt do it by installer, i just copied folder from v3. Works fine so far.

[Rongor]

May i know wich v4 fix everyone is talking about? I search the page now for a while but cannot see anything.

Prepar3DV4 Compatibility Updates

[Senchai]

May i know wich v4 fix everyone is talking about? I search the page now for a while but cannot see anything.

Thank you very much.

Just installed like guide says, no elevation issues (not before and not after). Thanks for the link.

[tcummings56]

Done all said above and still having issues. Any help? thanks

[Terblanche]

Done all said above and still having issues. Any help? thanks

Are you sure the both Amsterdam Scenery and Amsterdam_LC are installed and active in you Scenery.cfg file??

It's only when I checked that I realised the LC folder was not added in the scenery.cfg file and then I added it manually and voila, everything works 100%

SceneryConfigEditor v1.1.9 was launched to include P3D4 and there it is easy to edit and make changes.

Hope you get it fixed because EHAM is awesome in P3D4.

[G-CIVA]

The issue lies with the AFCAD.

The elevation of EHAM is -11 feet - BELOW Mean Sea Level.

If you use some kind of freely available AFCAD editor you may well find that the AFCAD & the 'flytampa_dummy.bgl' that came with this product are not actually positioned correctly at this height.

They are actually set at 4.918ft ABOVE Mean Sea Level.

Add this to the actual elevation & you end up with an error of -6.082ft hence the 'elevation' issues you are all talking about such as scenery objects submerged etc. Add into this mix other scenery enhancements like Orbx etc & the issue is compounded. The AFCAD must be set at the correct elevation to 'drive the scenery' to the correct elevation.

From a developer who charges so much money this issue is really a 'day one week one' problem, just like the incorrectly set ILS Headings for the Localiser Beams for the RWYs at YSSY, which are all easily 'correctable' via the AFCAD file & a suitable AFCAD editor.

As are these really lengthy install procedures for p3Dv4. Most other rivals are forging ahead with totally new installers. I am not installing ANY Fly!Tampa products into p3Dv4 until they get off their proverbial & create bespoke installers like the rest of the pack, it can't be that hard & for they money they charge its the lease we can expect.

I have not yet tried these fixes in p3Dv4; they DO WORK in p3Dv3 - with & without ORBX products installed.

If you want to try an AFCAD with the corrected elevation then contact me, hopefully you can find my e-mail address buried somewhere inside my profile.

Best

Stephen Bell

[Manny]

.