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

cat and mdltweaker?

Horst18519

Horst18519

Moderator
Resource contributor
Messages
2,385
Country
germany
Hi Arno,

I'm experiencing an absolutely new way of working with FS since I came across your unique tools. :)

I'm working on some more gimmicks for my airport. It would be great if I could create objects that appear only on some occasions and then play an animation controlled by a second variable. But this would mean of course, tweak the mdl twice - once with cat and then (or before) with mdltweaker. I reckon that's not possible. Is there a way to do this?
 
I think I can answer this by myself. It seems to be possible since cat modifies the asm and then lets mdlmaker compile a "normal" mdl which can be tweaked as every other mdl. :)

I experimented a little with a windsock. I created three mdls of it - for light, medium and heavy winds. Is it possible that those three mdls are treated as one if I place it at the same spot (which should be intended of course) and as seperate objects if I place them beside each other? Because unless I placed another object directed to the wind in the scenery I only got the right result by placing them beside each other... FS is so creepy sometimes... :o
 
Hi Thorsten,

As you already found out you can indeed combine MDLTweaker and CAT. That works fine.

About the position for the wind variable, I am not sure about that. That is something you would have to try.
 
Well, they are not treated as one if placed at the same spot - they don't appear ever. :eek:

It sure looks like tweaked mdls cannot be placed upon each other. I tried it several ways with SGX and they only appear if placed beside each other.

Of course that destroys the hole idea of the animated and rotated windsock. :(

I don't give up though. I'll try it with Objectplacer tommorrow and if that won't work either, I'll try seperate BGLs.

Is this a known limitation of tweaked MDLs? I haven't read anything about it.
 
Hi Thorsten,

Should be able to place them all at the same location without trouble, but I think it is the wind bug that you encounter. Object interacting with the wind don't appear unless there are multiple of them active on your screen. So maybe that is the reason why they do not work when all placed together.
 
No - at least not in my FS. :confused:

I don't use the rotate-to-wind-parameter.

I created 6 versions of my windsock, one for every 60°. I place them all next to each other and everyone shows only with the right winddirection - that means that at every time only one is displayed. That works fine.
Now I'm placing them at the same spot - and nothing shows up in FS, anyway from where the wind blows. :confused:
 
Humm, that is weird. Can you show the XML code used for the placement. Maybe the problem is there.
 
It's absolutely weird.

I tried it again with SGX. As it looks, not only the "rotate to wind" needs more than one object but also objects that use the "wind direction"-parameter. Got that.

But now:

I finally placed 6 windsocks at the spot and another windsock, that's only used whe the wind is slower than 5kts. But nothing happens. I move this windsock a little - and both this and the right one of the other 6 are showed as they should. :confused:

I don't get it.

I attached a cutdown xml including the windsocks (00-30 are the "rotated", the "low" is another temporary one that should assure, that the windsocks are not alone (it's rotated with the wind), and the "low_r" is the one for the low winds, in this case a little away from the 6.
But when moved at the same spot, nothing works. :confused:
 

Attachments

Sorry, one more thing, but I now am sure that the objects interfere when placed at the same spot:

I placed the "low-windsock" back upon the other 6 - and now the first of those shows in FS allways - at any windvelocity and direction. :eek:

There definetly is some interference.
 
One more curious thing:

I experimented only with one object now (beside all the windsocks), that shows the active runway. Finally I found this problem:
MDLTweaker can not handle min/max-winddirection, that cross the 180°-line. That means you have to use one object for min-179° and one for 180°-max. Together with the 360°-problem (which is more obviously) you have to create 4 (!) different MDLs just to create a working object that shows the active runway. :banghead: :banghead:

...the more answers I get, the less I know... :o
 
Last edited:
Well, this is a monologue... :o

Finally (really! :D) I finished the object that shows the active runway (needed 4 MDLs for that and it works fine) and the windsock! :)
I had to create 14 different MDLs for the windsock, but now it's animated, it rotates with the wind and it shows three states of windvelocity. :)

Anyway, I still had the problem, that I couldn't place the lowwind-windsock, which is only tweaked with windvelocity-parameter at the same spot as the others, which are tweaked with windvelocity and winddirection. This finally seems to be a bug (in FS?), but I was - after trying for hours - able to avoid it by using a little trick. :)

All in all this seems to be my problem only, but I thought I'd share the complications the tweaking may bring with you. ;)
 
You must log in or register to reply here.
Back
Top