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

Sketchup Make 2017 Glitches

Messages
33
Country
us-california
I just switched from SU 2016 to SU 2017 a couple days ago. Several buildings I have in progress, not particularly complex ones, were started in SU 2016 and placed via MCX in FSX. They are "draft" versions and used mainly as placeholders.

Yesterday, I loaded them in SU 2017, added a little texture, then loaded the *.dae in MCX as a check. All but two faces in the model were entirely missing in the MCX view. Fortunately, I build with a lot of components so it was easy to narrow down where the problem was, but I couldn't narrow down what the cause was. I ended up scraping that component (it wasn't all that complex), then redrawing it and saving it in SU 2017. It worked fine with no problems in MCX.

They apparently made extensive changes in SU 2017 that are transparent to users...at least to users who aren't building FSX models! There are several nice features in SU 2017 that make things a lot easier and more accurate, but be watchful for things that look fine in SU, but don't translate well to MCX. I'm not blaming either. I'm saying, some things seem to translate differently, though they can easily be fixed in SU 2017 so that they work.

Test new components using "Export only selected set" option keeps things honest.

Eric
 
Messages
1,132
Country
us-texas
Importing .dae in SKU is always prone to problems. Sometimes you are missing faces, sometimes you get additional faces you don't want.

Try importing the .skb or .skp instead....typically much cleaner!!

David
 
Messages
33
Country
us-california
Importing .dae in SKU is always prone to problems. Sometimes you are missing faces, sometimes you get additional faces you don't want.

Try importing the .skb or .skp instead....typically much cleaner!!

David

Thanks, David, but I think you misunderstood me. I wasn't trying to import the dae file into SU. I didn't even know that was possible!

My problem was with projects built in SU 2016 and successfully placed in FSX. With MINOR texture changes in SU 2017, they no longer worked without some edits. However, making the same texture changes in SU 2016 caused no problems in FSX.

Anyway, it is no longer an issue as all models started in SU 2016 have been fixed and new ones are all SU 2017.

As always, I learned something here. Now that I know I can import dae into SU, I'll avoid it! :)
 
Messages
33
Country
us-california
Importing .dae in SKU is always prone to problems. Sometimes you are missing faces, sometimes you get additional faces you don't want.

Try importing the .skb or .skp instead....typically much cleaner!!

David

Thanks, David, but I think you misunderstood me. I wasn't trying to import the dae file into SU. I didn't even know that was possible!

My problem was with projects built in SU 2016 and successfully placed in FSX. With MINOR texture changes in SU 2017, they no longer worked without some edits. However, making the same texture changes in SU 2016 caused no problems in FSX.

Anyway, it is no longer an issue as all models started in SU 2016 have been fixed and new ones are all SU 2017.

As always, I learned something here. Now that I know I can import dae into SU, I'll avoid it! :)
 
Messages
33
Country
us-california
Importing .dae in SKU is always prone to problems. Sometimes you are missing faces, sometimes you get additional faces you don't want.

Try importing the .skb or .skp instead....typically much cleaner!!

David

Thanks, David, but I think you misunderstood me. I wasn't trying to import the dae file into SU. I didn't even know that was possible!

My problem was with projects built in SU 2016 and successfully placed in FSX. With MINOR texture changes in SU 2017, they no longer worked without some edits. However, making the same texture changes in SU 2016 caused no problems in FSX.

Anyway, it is no longer an issue as all models started in SU 2016 have been fixed and new ones are all SU 2017.

As always, I learned something here. Now that I know I can import dae into SU, I'll avoid it! :)
 
Top