• 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 Taxi Light Attach Points?

tgibson

tgibson

Resource contributor
Messages
11,780
Country
us-california
Hi,

When I Import an FS2004 model with working landing and taxi lights, the landing lights are present as attachpoints with axes. But the taxi light location(s) do not include attachpoints, and I have to create new ones from scratch. Is there a way to keep those when Importing into MCX? BTW, there is a taxi light lens created (?) at that location with a Mouse Rectangle using switch_taxi_light, but this does not shine on the ground.

Thanks,
 
Last edited:
Do you have an idea how they are stored in the mdl file? If it is similar for the landing lights it should be possible to keep them.
 
Hi,

No, I don't know how they are stored. I could create a simple FS2004 MDL file with a box and a taxi light?
 
That would be helpful, then I can see how they are stored and why they don't show up.
 
OK, here is an untextured box with one taxi light. I tested it and it works in FS2004 with the taxi light switch. When imported into MCX, there is no attachpoint or other taxi light related object.
 

Attachments

Thanks, I'll have a look.
 
Hi,

If I set the value of the g_lightState variable to 8 I get 4 lights from the model.
 
Yes that explains it, thanks. But then I lose the landing lights...
 
Last edited:
I need to check what those different light state values mean. Maybe they can be combined, like using 12 or so.
 
Hah! I was just typing something similar. If not can you give the importer more than one value, something like 4,8?
 
And yes, 12 gives both landing and taxi lights - good thinking! Can we make 12 the new default variable for the Set Conditions box?
 
Yes, I will update the default value.
 
Hi,

Thanks, works fine.

I have found two more variables that need a default value in the Set Conditions box to avoid them disappearing upon MCX Import.

l_spoiler_key: 100
r_spoiler_key: 100

These are currently set at 0 and thus the spoilers will not appear when loaded into MCX.

Hope this helps,
 
OK, I have changed the default value of these two as well now.
 
Hi,

Thanks.

I have two more animations that need to be changed.

l_flap to l_flap_percent_key
r_flap to r_flap_percent_key

Not only are they listed as unknown animations and will be lost upon conversion, but if you change them to the proper animation tags manually and then convert, the flaps end up with the animation of an aileron! Luckily for now I can use the Animation Key Editor to fix that.

Hope this helps,
 
OK, I'll add these to the automatic mapping as well.
 
Hi,

I don't have any l_flap in my list of known variables at the moment, or did you mean left_flap?
 
OK, I have added the mapping and it will be in the next development release.
 
You must log in or register to reply here.
Back
Top