The Home of FlyInside Flight Simulator FFS FSX P3D and X-PLANE Message Board

I am new to Flyinside but am finding an issue that is a total deal breaker for me.

I am flying the IRIS Simulations PC-21 in P3D v4.5 with WMR/SteamVR and have found the projected HUD image is cut off below the horizon.
When nose up the whole image is there, but when on the ground, the lower half is missing and when nose down the entire image disappears. It is as if there is something obscuring any projection that occurs below the horizon.
The point where is is cut off aligns with the top of the Flyinside menu panel that pops up in the sim when on the ground, but the problem exists before accessing the panel and even if the panel is placed elsewhere.

I have a mate with the same issue and we haven't been able to find a solution. Everything functioned fine before installing Flyinside.

I am hoping someone has a solution to this, otherwise I will have to go back to native.

Cheers.

Hi mate and welcome, is this just with that particular aircraft ?

Tony

I haven't tried any other aircraft as I only use P3D for the PC-21. I'll see if I have any others with HUDs and see if it occurs there too.

Just checked with the default F-22 and have exactly the same issue with the HUD.

Can you try deleting your p3d configuration or renaming it and let me know ??

Tony

I renamed Prepar3D.exe.config with no change, if that's the file you were referring to.

I have attached some snips to show what I'm seeing.

Hi Tony and Helical,

This has been a long reported problem (see the disappearing HUD thread in the bugs section, first opened in 2017!).

Don't think a solution was ever found.

It also truncates prop disks and Windscreen/Canopy textures below a certain angle.

Hope to see a P3D v5 version soon! Having to take the headset off to change aircraft is a pain, really miss Flyinside.

Hope this helps

Andy

Hey Andy,

I had a read through that thread before I started this one, thought with the age of that one and the references to an older version of P3D that it was worth asking again. The descriptions also sounded slightly different to what I am seeing, though I could have just read it wrong.
Also, given the problem only occurs with FlyInside, not native P3D, so I feel it's not a problem with P3D and hoping an update to that will fix it like mentioned in the other thread seems like wishful thinking to me.