• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Does GPW convert correctly?

Thank you very much! But if i don’t go back to MCX, how can I adjust the location of my polygon?
And what to do next? How do I apply BGLcomp? I have always used only MCX and have no idea how to use BGLcomp
 
You place the polygon at the location you want with the GPW first. In MCX you make sure that in the exporter options you enable the KeepMDL and KeepXML options. Now with the BGL file also the sources are saved.

Then with RADItor you tweak the MDL as Tom explained. Once the MDL is modified, you compile the BGL file again using BGLComp (you need the XML and the MDL file for that).

If you don't know how to use the SDK tools like BGLComp, you better read a bit more in the SDK first.
 
Arno, thank you so much! Having the MCX saved me from using the SDK. But now I read necessarily.
 
Arno, I am eternally grateful to you and to everyone who tried to help me! You did it and I did it, friends! I'm certainly very happy that everything worked for me fully! I think that the problem has been solved at this stage, but I would not want to rush to completely close the topic, since this was only the first part of the of my project. As well as this topic can still be useful to someone to solve similar problems.
Guys, I have a working runway, this is fantastic! :) :wave:
 
Hi,

I'll still continue to see if this is actually a bug in P3D. Increasing the bounding box is only a work around as I see it. If it's a bug, LM should be made aware of it. But I need to test a bit more to be sure it's a bug.
 
Hi Arno! I'm not hurrying! Of course, you can check and no matter how long it takes. I have now made two more layers using GPW in standard mode on top of my worker. I can also confirm that the first layers with the correction of bounding box remain stable, and new ones that are not corrected disappear as before. Now I will edit all the new added layers according to your method.
 
Just fixed two new layers - the runway works fine!
Arno, if this turns out to be a LM bug, it is not known when they will correct this error. I have a question - is it possible to add a new option in the GPW "Size of the bounding box x2"?
Sorry maybe this is brazen of me, but at the moment it’s very relevant. It's just like an idea ...
 
Last edited:
arno said:
Hi,

I'll still continue to see if this is actually a bug in P3D. Increasing the bounding box is only a work around as I see it. If it's a bug, LM should be made aware of it. But I need to test a bit more to be sure it's a bug.
Click to expand...

Hi Arno! Any news or changes? At the moment, I still have no problems in the work, only time takes a little more using RADItor.
 
Hi,

No, didn't have the time yet to test this further.
 
Still have the same problem. How to fix it using MCX? I cannot change bbox using 3ds max (otherwise I have to add fake geometry).
I see smth called MDL tweaker but seems it does not save new bounding box defined in MCX. Also here is FSX Curve Editor, don't know is it OK for P3D 4.5 and how to use it

Any solutions? Flickering ground is a blocker for my project.
 
Hi there! So as @b2soft mentioned we have some issues with GP. Textures start to disappear on the edges of the runway. We made flatten layer and use airport ALT. It's the same everywhere!
 

Attachments

  • 1.jpg
    1.jpg
    612.5 KB · Views: 253
  • 2.jpg
    2.jpg
    494.9 KB · Views: 222
  • 3.jpg
    3.jpg
    456.6 KB · Views: 221
  • 4.jpg
    4.jpg
    409 KB · Views: 230
  • 41836b304eb472b13866998808cbfe24.jpg
    41836b304eb472b13866998808cbfe24.jpg
    459.5 KB · Views: 234
  • 7ea12c36b00c757814e026ea9f8dc22d.jpg
    7ea12c36b00c757814e026ea9f8dc22d.jpg
    442.1 KB · Views: 231
  • eff85a26df07acdf8cf208150c27d0fb.png
    eff85a26df07acdf8cf208150c27d0fb.png
    35.6 KB · Views: 223
Considering that ADE-GP is now also having issues with flickering:

www.fsdeveloper.com

FSX - 1.78 GP Height Offset Issue

Hi Jon, I am finding that airports that previously compiled without producing flashing GP objects under 1.76 are now doing so. I've tried adjusting the GP Offset to slightly higher values without success. What was the default for the 1.76 please? Could it be something else? Martin
www.fsdeveloper.com www.fsdeveloper.com

and that I believe Don got some of his GP code from Arno (?), it seems that something is going on indeed. If Don did *not* get new code from Arno during this time, then instead it might be a video driver or OS update issue?
 
tgibson said:
Considering that ADE-GP is now also having issues with flickering
Click to expand...

Yeah, but we've created GP in 3dmax. Or you mean that ADE exporting any objects (runways, taxiways, etc.), that are inside the afcad higher than they should be?
 
What I'm saying is that ground polygons from TWO different sources are suddenly exhibiting flickering. That seems very suspicious to me.

I assume it has nothing to to with other ADE components.
 
Ok, we've managed to fix this.
First of all, we manually sliced all over polygons. Then we've added small 1x1 cm squares far away from our objects, one for each corner. That's made the bounding box twice bigger.
In the final step, in MCX we unchecked "Slice polygons", "Group polygons" and "Prevent...."
Preaty awkward, but at least it works.
 
You must log in or register to reply here.
Back
Top