Floating at KMEM P3D 5.3 HF2

[Butch]

 I sent you a PM

[PierreFSX]

Thanks Butch,

I will try it shortly. I also re-installed the airport using the new installer, and I think it did fix the elevation issue. I still have some test to do. I will report back soon.

Pierre

[Butch]

Although the "fix" will make the tires contact the ground,  a lot of the concrete disappears. Back to square one I guess,


https://i.postimg.cc/8559FNpn/Memphis.jpg


EDIT: I have to agree with one comment about this issue made at FS Developer

https://www.avsim.com/forums/topic/621385-fsdt-kmem-floating-aircraft/?tab=comments#comment-4806484

[Butch]

 I noticed that when GSX is disabled, the floating aircraft will descend and the tires will come in contact with the ground with an simultaneous crash sound.
When I activate GSX, the aircraft will raise off the ground.  Not Good!!!!!

[PierreFSX]

Unfortunately the re-install did not fix the problem, the plane is still floating in the air. see attach picture.

[PierreFSX]

I just did the GSX test and I am getting the same result, also when I disable GSX the airport scenery disappear. Not sure what going on? We need someone from FSDream to look at this. I did the same test at other FSdream airport and GSX his working perfectly. So it seems that the KMEM and GSX combination is the issue.

[yurirodin]

This issue exists also in KJFK KCLT and KDFW

[Papacoach]

Yes, I see the others too. Following this thread...

[Sholay]

Is it fixed by now?
I am contemplating buying this scenery, but if it has obvious issues not fixed for several months, I am starting to wonder.
Especially since looks like KIAH also has this problem with little hope for a fix.
I understand that MSFS take precedence, but again - just look when this thread started with first issue report.

&

[yurirodin]

Is it fixed by now?
I am contemplating buying this scenery, but if it has obvious issues not fixed for several months, I am starting to wonder.
Especially since looks like KIAH also has this problem with little hope for a fix.
I understand that MSFS take precedence, but again - just look when this thread started with first issue report.

&

The way I solved this issue is to uninstall P3D Client for V5.3 and install the Client for V5.2. I had some visual issues with vegetation like splatter across the screen but that got fixed by installing ORBX Terra Flora V2 and Trees HD. It sounds complicated, but this will fix many airports that are bugged this way (such as Flightbeam KPHX and ORBX KTEX) and are probably not going to be fixed anytime soon, if ever. Version 5.3 broke a lot of airports in this way.

[pilotny]

We'll look into that.

So is been a year since this issue has been reported, where is the solution from developer or statement about it? and yes Im aware  about "P3D V5, we strongly suggest to download the Trial version before purchasing them".

[Geddy_2112]

So it's been way over a year since this was reported and I understand you're busier with MSFS than P3D, But this all happened with a simple GSX update. Can't you spare a couple of days to rectify this? Seems like this could have been done many months ago. I know we're just simple P3D customers but still, customers none then less

[virtuali]

But this all happened with a simple GSX update.

Then why it doesn't happen if you go back to P3D 5.2 ?

There are issues with 5.3 and elevation which seems to be bugs in the sim ( sometimes stuff appear in the air for no reason ) and, since KMEM was never advertised as a P3D 5-compatible product, the Disclaimer on the FSX product page KMEM is located on, still stands:

Prepar3D Compatibility
While these products were originally made for FSX, they can be installed in all versions of Prepar3D, up to 5.1.

However, due to several changes in backward compatibility in P3D V5,some of the older products might shows some visual problems so, if you intend to used them in P3D V5, we strongly suggest to download the Trial version before purchasing them.

[okupton]

Just as an update, this floating issue is fixed with P3dv5.4

[Jenser2811]

I still have the same problems with V5.4.