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

dae vs kmz

robystar

robystar

Messages
5,214
Hi,

Now that I found out that you can make a GSU object and export it as a KMZ file whereby the location of the object is included and easily converted in to a 'placed' bgl, I wonder what the advantage still would be of importing a dae file into MCX? Are there some reasons for choosing a dae i.o. a kmz?
 
Well,..

I would think it would depend on the model so to speak,...

for instantance,... if the simple model or gneral structure, used all over, then DAE format would be more useful. On the other hand,... if the model is a specific building or structure then why not in a KMZ format.
 
Hi,

Inside the kmz there is a dae file for the model. The disadvantage in the previous version of sketchup was that all polygons are exported double sided to the kmz. So that's a bit overkill. I think version 8 still does that.

Send from my phone using Tapatalk, so excuse the short sentences and possible typos
 
arno said:
Hi,

Inside the kmz there is a dae file for the model. The disadvantage in the previous version of sketchup was that all polygons are exported double sided to the kmz. So that's a bit overkill. I think version 8 still does that.

Send from my phone using Tapatalk, so excuse the short sentences and possible typos
Click to expand...

Hi Arno:

Could you clarify this a bit more ? :confused:

I assume you are referring to earlier Sketchup versions such as 6.x and 7.x; 8.x is the current version I see available for download from Google.

http://sketchup.google.com/intl/en/download/index.html


FYI: The transfer of Sketchup's product line to "Trimble" does not seem to have changed the download page as of yet.



Was a work around identified which could be implemented in Sketchup 8 and/or ModelConverterX (aka "MCX") to eliminate export of double-sided polygons ?

My Sketchup models made for export to FS via MCX are nearly all "manifold" solids exported as *.DAE's, so I'm not certain I've encountered a problem with this before.


Thanks for any additional insight you could share with us on this. :)

GaryGB
 
Last edited:
Hi Gary,

I just checked with version 8. I made some geometry and I only applied a material on one side of the polygons in SketchUp, so the inside of my model is not there.

When I export for DAE format I have 30 triangles. When I export to KMZ I have 60 triangles. Inspection in ModelConverterX learns me that the KMZ file has polygons on the inside as well.

So even in the latest version this is still true. You get a higher triangle count with the KMZ format, that's why I prefer to use DAE. But the advantage of KMZ is the coordinates that are saved.

I don't think much can be done about it, I did not find settings in SketchUp for it. But maybe somebody else knows if there are.
 
Thanks, Arno ! :)

When I get a chance, I'll see if there might be a 3rd party Ruby plugin (ex: at SketchUcation) for Sketchup which allows deletion of the extra faces inside a "closed solid" model when exported as a KML.

If I can find one, I'll report back to this thread. ;)


PS: I recall reading that you were considering the *.OBJ file format as another possible option for import into MCX; would MCX import of that format also allow for elimination of the extra internal faces in Sketchup models ? :confused:


Thanks again,

GaryGB
 
Hi Gary,

ModelConverterX can read Wavefront OBJ. But my version of SketchUp does not export to that format. So I can't test if it includes the inner polygons or not.
 
Hi Arno:

I did find a Ruby script which removed inner faces from a example "block" object manually geo-located at the 34R Hold Short position at SeaTac in a Sketchup 3D model exported as either a separately exported single *.DAE or *.OBJ file, thereby reducing geometry complexity to a minimum for "closed solids".

[EDITED]

However, as you reported above, Sketchup export of a geo-located 3D object via a *.KML / *.DAE "KMZ" package results in the model having extra inner faces generated so that objects have 2 sides ("KMZ Export Options" dialog does not offer a check-box to disallow 'Export 2-sided faces'). :banghead:



Perhaps one may have to manually copy geo-location info from the Sketchup dialog into a placement dialog in MCX in order to successfully keep 3D model geometry complexity to a minimum actually required for most FS "closed solid" objects imported via ModelConverterX from separately exported single *.DAE or *.OBJ files ?

[END_EDIT]

Of course one might wish that when you have an opportunity to study this more, it would be very helpful to have MCX offer an option to delete the duplicate inner faces / sides from imported KMZ-packaged 3D models, so geo-location (and associated lighting / shadow info based on Sun position relative to object position / time of day on the World globe etc.) might be configured only once without a need to perform the extra data entry within MCX in addition to that already performed inside Sketchup. :idea:

But until such a new MCX feature is possible (if ever), many thanks again for your all your excellent work to date with MCX ! :)

GaryGB
 
Last edited:
Hi Gary,

Maybe an option to load both the dae and kmz file in modelconverterx would also work. Then you take the placement from one and the model from the other.

Send from my phone using Tapatalk, so excuse the short sentences and possible typos
 
Hi Arno:

The 2-file 3D model export to MCX sounds like a feasible and reasonably easy workflow for the Sketchup user; thanks for considering this option ! :wizard:


Note to Users of both Sketchup and ModelConverterX:

Until Arno may implement further features into MCX to deal with imported KMZ files and/or other 3D model files containing non-essential faces / sides within "closed solid" objects, Sketchup users who want to be 'doubly sure' they are removing such inner faces /sides in order to keep geometry complexity to a minimum ...may wish to try using several "Sketchup Plug-in" Ruby scripts linked via this thread:

http://www.fsdeveloper.com/forum/showthread.php?p=442778#post442778


Hope this helps ! :)

GaryGB
 
Last edited:
You must log in or register to reply here.
Back
Top