• 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.

FSXA Ground Poly Wizard Errors

Shaun said:
What solution? I'm having this problem with mcx? And others are too by the seems of it. Might be that it's from blender. But I had a similar issue with a
Mdl from gmax a while ago. Have to use an older version of mcx. But that doesn't seem to be helping here.
Click to expand...

I don't think its from Blender. I use 3DS Max 2015 and I've had the problem.I suppose my suggestion to minimize moving of vertices is not the best yet. Arno would have to look at MCX then.
 
nz255 said:
Simple polygon x file:

Ground Poly Wizard: Missing polygons after Convert
http://www.fsdeveloper.com/forum/index.php?threads/Ground-Poly-Wizard:-Missing-polygons-after-Convert.435154/
Click to expand...

I'm going to try to reproduce the issue. But the object Shuan provides is much too complex for debugging (it has over 2000 triangles and covers many kilometers). When I talk about a simple file that demonstrates the bug I mean something like 10 or 20 triangles. Then I can manually check what's going on for all of them.

I'll try with the object from the post quoted above, if I can get hold of the X file.
 
I just had another look at the object from Shuan. Actually if I strip it down to just one material (c5.dds) and run that through the GPW I can reproduce a missing polygon. And with just one texture and polygon, I think it might be simple enough to reproduce. I'm going to have a look tomorrow at that.
 
arno said:
I just had another look at the object from Shuan. Actually if I strip it down to just one material (c5.dds) and run that through the GPW I can reproduce a missing polygon. And with just one texture and polygon, I think it might be simple enough to reproduce. I'm going to have a look tomorrow at that.
Click to expand...
Sorry I missed that earlier. I just sent you the isolated simple plane. It's very strange indeed! To begin with it was the asphalt texture having created phantom polygons, now it's some missing. Even happens with the version of MCX that has worked perfectly to date on all my other sceneries!
 
Well after hours of messing about only subdividing that single plane seems to work. So at least I have the problem sorted.
 
Hi,

I had another look at the bug, but I have some trouble to reproduce it consistently. Like I wrote before I used only the parts with the materials c5 and c6.

If I load the X file in the GPW, remove all other materials and then run the GPW two triangles are indeed missing.

If I load the X file, remove all other materials, then save the polygons as a MDL and afterwards run that MDL through the GPW I don't see the missing polygons.

The bounding box of the two files is the same, so I can only imagine very minor rounding issues between the two versions. If I run the entire X file through the GPW after converting to MDL first it also seems to work.

For those who encounter this bug, are most of you using X file as input format?
 
arno said:
Hi,

I had another look at the bug, but I have some trouble to reproduce it consistently. Like I wrote before I used only the parts with the materials c5 and c6.

If I load the X file in the GPW, remove all other materials and then run the GPW two triangles are indeed missing.

If I load the X file, remove all other materials, then save the polygons as a MDL and afterwards run that MDL through the GPW I don't see the missing polygons.

The bounding box of the two files is the same, so I can only imagine very minor rounding issues between the two versions. If I run the entire X file through the GPW after converting to MDL first it also seems to work.

For those who encounter this bug, are most of you using X file as input format?
Click to expand...
Yeahp my files are usually .X files
 
Could you try to make a mdl of the x file and see if that also solves it? Might help me to find what goes wrong.
 
arno said:
Could you try to make a mdl of the x file and see if that also solves it? Might help me to find what goes wrong.
Click to expand...
I exported the x file to an mdl (via MCX) I opened the mdl after exporting it and it looked correct.
Then running the mdl through the ground polygon wizard resulted in more pieces scattered and broken than running the original x file.
 
So in your case the mdl was worse? Humm, that's the opposite I see from the test objects I have here.

But like I stressed before it would help me a lot if this bug can be reproduced with a simple object (less than 10 triangles). I don't fancy going through thousands of triangles in the debugger to find out which one goes wrong and way.
 
Hi,

Go back a couple of steps and I am convinced you will find the answer in avoiding overlapping groundpolys or find ones that are on the same layer:twocents:.
MCX works fine for me.

PS: I do not have MCX on my laptop so I cannot tell you which version I have but it was the latest one when I left home in November last year.
 
Here's a 2 tri runway and you get the problem. I'm on the latest dev version.
The x file is exported with 3ds max 2015 via the p3dv3 SDK

x file and final bgl:
http://s000.tinyupload.com/index.php?file_id=13951140773088237774

http://s000.tinyupload.com/index.php?file_id=08481738934769146871

NveQ0QG.jpg


Yg0a4aC.jpg
 
Thanks, hopefully with this file I can reproduce it better.
 
Shaun said:
What solution? I'm having this problem with mcx? And others are too by the seems of it. Might be that it's from blender. But I had a similar issue with a
Mdl from gmax a while ago. Have to use an older version of mcx. But that doesn't seem to be helping here.
Click to expand...

I have something which seem to be the same problem.
I use Sketchup and have tried exporting as DAE and OBJ file, and the problem is the same, only that the DAE gives even worse missing polygons.

All looks fine in Sketchup, but not in MDCX, and it did work before just as you said.
Sketchup vs MDCX of same areas.
 

Attachments

  • SketchUp 2016-11-26 11-14-54-82.png
    SketchUp 2016-11-26 11-14-54-82.png
    548.5 KB · Views: 264
  • SketchUp 2016-11-26 11-14-45-22.png
    SketchUp 2016-11-26 11-14-45-22.png
    195.8 KB · Views: 296
  • ModelConverterX 2016-11-26 11-09-26-17.png
    ModelConverterX 2016-11-26 11-09-26-17.png
    595.3 KB · Views: 265
  • ModelConverterX 2016-11-26 11-07-59-90.png
    ModelConverterX 2016-11-26 11-07-59-90.png
    114.2 KB · Views: 231
You must log in or register to reply here.
Back
Top