- Messages
- 33
- Country
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
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