Jump to content

Floating Building South of YPJT P3dv4.5


Recommended Posts

G'day Brian,

 

As the other guys have alluded to - it's a mesh issue, we just need to track down which mesh is causing you problems. I see you have Hoglermesh AU installed (which is good), alongside the Pilot's mesh. Could you please post a couple of shots similar to your first ones (both of the building, and from the runway) with the Pilot's meshed unticked in the scenery library? No need to uninstall/re-install it at this point.

 

Please untick both these entries in your scenery library: 

 

- FS Global Ultimate DL - Oceania

- FS Global Ultimate DL - Local Meshes

 

Cheers,

Jarrad

Link to comment
Share on other sites

Hi Jarrad, 

 

I already have uninstalled Pilots and Black Marble, I'm just flashing up he flight sim to take some fresh Picture's Please bare with me.

Its almost as if my mesh is messed up?

Regards Brian

 

 

 

 

Link to comment
Share on other sites

Or mine either - the issue is most certainly caused by a mesh of some kind. The only ORBX mesh that would affect this area is our AU Holgermesh, and if we discount the Pilots mesh we'll need to find what other meshes may be installed. 

 

Could you please send through copies of both your current scenery.cfg (updated since the version you sent yesterday) and scenery_add-ons.xml? 

 

Cheers,

Jarrad

Link to comment
Share on other sites

Nick, Jarrad,

I just noticed all my entries in my terrain.cfg for Tongass x for Misty Moorings was missing?

Don't know whether that would throw things out.(NO HAD NO BEARING)

I have a lot of excess. orig, bu, old files in program data, can they be removed?

 

Brian

Link to comment
Share on other sites

NICK

 

Everything has returned to NORMAL, NO floating building?

Now I guess I enable one by one to see what is corrupt?

Your a breath of fresh air, I thank you.

What do I do next.

Surely it couldn't be any of my RTMM MISTY MOORINGS, it would have to be Ozx, or something local that is not compatible with 4.5.

Nick I'm up to whatever you think I should do????

WOW

Regards

 

Brian

Link to comment
Share on other sites

I would suggest that you re-enable what you have in your conventional in-game scenery library first.

If that brings the problem back, disable half of them and try again.

If that fixes it, re-enable half of the disabled ones and so on until you find the culprit.

If asked, I would also guess that it is something in OzX, as did Jarrad.

 

Then, if necessary, do the same with the xml added ones.

 

It is a true pain but the process of elimination is really the only way.

Link to comment
Share on other sites

Thanks Nick and to  your wonderful support team Doug, Jarrad, and to Bruce (Life Member)

I'm sure you have read the whole history here.

This is my lifeline to the outside world.

I will let you know the culprit for anyone with future problems.

 

 

THANK YOU ONE and ALL

 

Kindest Regards

 

BRIAN (BJ from OZ)

Link to comment
Share on other sites

Thanks Nick

Will report back tomorrow, it isn't OZx, it`s either RAAF GinGin, PEARCE, or Modified Perth, or Lucy`s Trucks, or Envtex.

 

Have to save  a marriage, talk tomorrow.

 

Kindest of Regards

Brian (BJ from OZ)

Link to comment
Share on other sites

Looks like your getting closer to finding the solution. I doubt it is any of the OZx scenery causing this, I have it all and don't see what you're seeing. The only issue found between OZx scenery & P3Dv4 onwards was a texture incompatability causing some buildings etc to appear black.

This has been rectified & a new OZx Sc Lib for P3D is available

Link to comment
Share on other sites

Thanks Bruce,

Yes, it was by pure accident that I realised it wasn’t Ozx, when I disabled everything, I thought I had done everything, except ORBX, I had forgot to disable Ozx.

So I then enabled all scenery except for those I mentioned in the earlier post.

So today, I should be able to find the offending scenery, then reinstall Ultimate Terrain and Marble Black.

Its really a great feeling, when the hobby that is your life, is all up and running.

Thanks for your support, we are a unique bunch.

 

Kind Regards 

 

Brian

Link to comment
Share on other sites

G'day Brian, glad you got it sorted :) 

 

I've just had a look at the Gingin package, if you'd like to still keep that scenery active, the file that is causing the problem is RAAF Base Gingin WA\Scenery\RAAF_GinGin_ElevDataWA.bgl

 

If you rename this file to RAAF_GinGin_ElevDataWA.bgl.OFF , it will de-activate the file and get rid of all elevation issues. 

 

Cheers,

Jarrad

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...