24 minutes ago, Ray Proudfoot said:

Dave, the only Manchester available for P3D from Aerosoft is a very old one for P3Dv3 and FSX. That would explain the wrong runway designations.

If that’s the one you have then I’m not surprised you’re having problems. It’s unlikely to be compatible with v5.

Try disabling Aerosoft Manchester and restore the ORBX files. Report back.

Hi Ray,

it appears that it's the Orbx runway ID that is wrong, when loaded without the Aerosoft/IDS scenery, the runways are marked 06/24. The EGCC scenery has them as 05/23

8 minutes ago, stevendt said:

Hi Ray,

it appears that it's the Orbx runway ID that is wrong, when loaded without the Aerosoft/IDS scenery, the runways are marked 06/24. The EGCC scenery has them as 05/23

Interesting. The ORBX package was released well after the runways were changed. That’s naughty of them. Might be worth posting that on the ORBX forum and see what Nick Cooper says.

24 minutes ago, Ray Proudfoot said:

Dave, the only Manchester available for P3D from Aerosoft is a very old one for P3Dv3 and FSX. That would explain the wrong runway designations.

If that’s the one you have then I’m not surprised you’re having problems. It’s unlikely to be compatible with v5.

Try disabling Aerosoft Manchester and restore the ORBX files. Report back.

Hi Ray,

it appears that it's the Orbx runway ID that is wrong, when loaded without the Aerosoft/IDS scenery, the runways are marked 06/24. The EGCC scenery has them as 05/23

6 minutes ago, Ray Proudfoot said:

Interesting. The ORBX package was released well after the runways were changed. That’s naughty of them. Might be worth posting that on the ORBX forum and see what Nick Cooper says.

The manuals for both the Orbs and |IDS/Aerosoft products are dated 2017

20 minutes ago, stevendt said:

The manuals for both the Orbs and |IDS/Aerosoft products are dated 2017

Point that out to ORBX support and mention Manchester runways changed ten years earlier.

47 minutes ago, Ray Proudfoot said:

Point that out to ORBX support and mention Manchester runways changed ten years earlier.

I can't register on the Orbx support forum, the reCAPTCHA verification seems to be broken

11 minutes ago, stevendt said:

I can't register on the Orbx support forum, the reCAPTCHA verification seems to be broken

Try again tomorrow. It’s still active.

It has been years since I used P3d, but did you set your insertion points in ORBX Central? It was vital to do it properly yet most didn't do it at all and ORBX got a bit of a bad rap because of their failure to do so.

15 hours ago, Dave_YVR said:

It has been years since I used P3d, but did you set your insertion points in ORBX Central? It was vital to do it properly yet most didn't do it at all and ORBX got a bit of a bad rap because of their failure to do so.

Hi Dave,

thanks for the message. I just discovered that option today (before I read your message).

I had not used the insertion option in Orbx, but I had messed around with the scenery order in P3D itself, would that not do the same thing?

I will try it though, putting the Orbx insertion point below Manchester, and see if that changes anything

regards

Dave

21 hours ago, Ray Proudfoot said:

Try again tomorrow. It’s still active.

Same thing today . . .

"ERROR for site owner: Invalid site key" in the reCAPTCHA box :-(

Sounds like Orbx have a licencing issue with reCAPTCHA!

3 hours ago, stevendt said:

I had not used the insertion option in Orbx, but I had messed around with the scenery order in P3D itself, would that not do the same thing?

Sort of yes but as the Orbx folders need to stay in a particular order to each other it's meant to maintain that order as well as for in with the users library.

If I recall correctly you want the first option (FTX Regions and Airports or something close to that) set to insert just above Bathymetry. The other one stays set to below the FTX Regions and airports.

Also if you have FTX England or other regions, they all come with airport ade's aka afcads and technically they will conflict with other airports so you should remove or disable any conflicts. For instance again, you might see 3 files named starting with something like FTX_ENG_EGCC, those will conflict with addon scenery regardless how high above it is in your library order.