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

Combining objects

Messages
29
Country
kazakhstan
Hi Arno,

I have tried to merge 2 objects today after one of them was already merged out of 2.

I got the following error:
Duplicated file lables found with name: RIFF-MDLD-REFL-REFP_MCX_CURCOR_end

Everything looks correct to me but nevertheless I cannot save the combined file.

Any idea what is going on?

Thanks
Mike
 
Hi,

Sounds like it could be related with attachpoints in the object. I'll give it a try to see if I can reproduce it.
 
Hi,

Haven't had the time yet. I was in Paris for my work the last few days.
 
Hi,

I have fixed the problem that duplicate attachpoint names could be created while merging. So with the development release of tomorrow it should not happen anymore.
 
Hi Folks

Arno -
Mean't to ask about this a while ago, (along with some other bits)
but been away from home dealing with family matters.

On the matter of duplicate attachpoints -

Been using MCX as a preview tool
whilst I was re-texturing a series of FSDS models,
which contain old ASM light effects.

Happened to accidentally click & display the "shadow model".

Noticed that all the ex-ASM attachpoints
were now being duplicated into the "shadow model"

Has that always been the case ?
Was/Is it intentional ?

HTH
ATB
Paul
 
Hi Paul,

What do you mean with shadow model? Did you click the button to show the shadow. That only renders the shadow, not additional attachpoints.
 
Not sure, I'll try to reproduce what you are seeing.
 
Hi,

I do not know if this is something that went wrong in MCX or not because I never had this problem.
I did try to merge several mdl's a couple of times but for a specific reason.
Arno then suggested I'd add the second, third etc. mdl as a LOD variant.
So, if you are not using 'lodded' mdl's, you could add the second one as a LOD 99, the third one as a 98 LOD, etc.
My LOD 100 did not have the attached objects but the others did and it worked fine.
Mention this just for info, you never know what it is good for:).

PS: I suppose you are talking about FSX?
 
Hi Folks
What do you mean with shadow model?
Did you click the button to show the shadow.
That only renders the shadow, not additional attachpoints.
Arno -
Yes - I'd accidentally clicked the button to show the shadow.
It did show "shadow model" attachpoints,
each exactly matching their equivalent positions in the "visual model"

My apologies Arno,
for my original post's misleading information.

On revisiting our models in MCX
the shadow-model's duplicated attachpoints issue
was only present in our original un-edited G-Max source versions.

i.e.
They must have compiled by our G-Max modeler, (and not by any MCX recompilations).

Again my apologies Arno. :o

HTH
ATB
Paul
 
Last edited:
Hi Paul,

No problem. I'll still try to check what is going on, because no attachpoints should be rendered for the shadow.
 
I have to apoligize too, the effect problem have nothing to do with the shadow issue, It was that the effect have values in the offset section. the effect was made with fx editor from sdk, and assign an offset value, why don't know, but happy to know where was the mistery.anyway this had a very strange behaviour.
 
Back
Top