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

FS2004 Part read and render problems, split parts.

S

Shessi

Messages
39
Country
unitedkingdom
MCX 1.4 24-7-13 Arado.JPG MCX 1.4 7-2-14 Arado.JPG Arado splits.JPG

Arno,
I have noticed that over the last six months the ability of MCX to read and render Fs2004 mdls has greatly improved.

Unfortunately now, when exporting as an FSDS .fsc file there is a major problem with mdl parts being split up and part of those parts being added to another part (if that makes sense!).

So instead of having whole parts to deal with you have to find the other part of it and join them, and often a part is split over 3 or parts seperate bits.

Ok, you can join them, but again unfortunately they leave tears/seams in that part, which are easily seen, when compiling again. Often seeing through it as a gap when flying.

TBH I use 1.4 24-7-13, which does not do this, but as you develop the capabilities of MCX I want to use the latest version (especially when we can export Fs9 animations!), is there anything you can do about this please?

See above, pic 1 the floats are a whole part (MCX 24-7-13), pic 2 the floats are split up, see the front and sides (MCX 7-2-14), pic 3 the splits as seen as fine dotted white lines on the fuselage and engine.

This happens will all ac, made with Gmax or FSDS

Many thanks

Shessi
 
Hi,

I would have to check what changed, but I remember there was an issue with exporting too many polygons to fsc. So that's probably why things are split.

Splitting doesn't give gaps though, since the vertex positions are not altered.
 
Arno,
Unfortunately they do show up, and I've tried to manipulate the points to try and close the tears but no luck. I have resorted to putting in seperate polys behind the tears to block out the light, not ideal.
I think it may have been after you put the auto smooth function in, but not directly?

I have tried the Ar196 mdl with various versions of MCX and v 24-7-13 is the last version that exports whole parts to FSDS. All versions after that export part of parts with resulting tears.

Thanks for taking a look.

Shessi
 

Attachments

  • tear 1.JPG
    tear 1.JPG
    83 KB · Views: 481
  • tear 2.JPG
    tear 2.JPG
    94.5 KB · Views: 475
  • tear 3.JPG
    tear 3.JPG
    91.5 KB · Views: 487
Hi,

Yes, I was thinking later that the split probably has to do with the smooth groups in the FSC file. That's probably why you see the difference.

Since the smoothing is also not perfect yet, maybe I should make it an option. Than you can disable it if you don't want it (I forgot it I already made it an option or not actually).
 
Hi Arno,
That would be great, many thanks.
As the later versions of MCX read more mdls and have a lot of extra features, that I'd like to use. If by not having the smooth function set automatically we can have whole un-split parts again, then great, a much prefered option.

It's really no big task to go through and smooth each part, so yes please make it an option, and bring back whole parts!

Shessi
 
Hi,

I have added an option now. So if you grab the development release tomorrow it should not split those parts anymore. The option is called SetSmoothing and is in the ObjectWriter settings. By default it is false already.
 
Arno,
Yes! back to whole parts with no 'tearing'.

Many thanks for taking the time to tweak it.

Cheers

Shessi
 
You must log in or register to reply here.
Back
Top