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

FSXA Landing Lights?

Also... You must apply a Material to the landing light. Create a basic Material, name it Light_Landing (just like that), and give it a color, like bluish white, cream white, bright white, etc. Apply that to the Polygon. Assign it a UVW Map. Reset its Scale. Export a model and test in your sim.
Say what? Bill, I have never, ever had to any such thing in all the years I've been doing FS models, at least not for 'stock generic fx_landing.fx' type lights.

As it happens, I sent him a .max file with nothing but a set of landing light polygons. His problem is lack of the <Visibility> being read and respected...
 
Hmmmm... I thought you needed the materials applied to the polygons, lol... Oh well. One less step. This is good to know.
 
haha, all that crap comes from the default landing light effects attached with DC-3 provided in the SDK? have you guys ever checked it's user properties out? I thought maybe it had something to do with the effect ... right now I am trying to make default landing lights, so I haven't created any effects of my own.
 
and no i dont want to work with the polygons, they seem to act weird during foggy conditions.... i've always hated making those 3d apron lights in my sceneries :P
 
There is one -and only one- .fx file that will work: fx_landing.fx in the ..\Effects folder. This is because the name is reserved triggered by the sim's core code. It is not changeable.
 
Just tried with the attachpt and visibility tags but now the ground doesn't lighten up?? Is it only supposed to add a light effect or add a light polygon on the ground as well? .... that polygon on the ground that lights it up is the problem, i hope you understand what I am trying to say here
 
Which direction is your polygon pointing? What is the orientation of the pivot point?

In Max, when I click on one of my attachpt_landing_4 objects, and check, the blue axis is Up, red axis is Right, and green axis is Forward. Well, I actually have it angled downwards slightly to control the size of the 'ground splash', but it's mostly Forwards... :wizard:
.
LandingLight_01.jpg
 
Note also, it is the 'exterior' model that uses the landing lights which 'light up the ground'. The interior VC model does not use them for some odd reason, it uses the ones in the exterior model.
 
here you go....its the same way....i dont know but this makes me feel stupid for some reason that I cant get it to work! :P

Untitled-1.jpg
 
I've tried removing the attachpt and added the light to the aircraft cfg but still there is no light splash on the ground? :banghead:
 
The fx_landing.fx file cannot be called from the aircraft.cfg file entry. What version of Max are you using?

Here is the entry used for the light polygon shown previously. Note that the <Attachpoint name= must match the object name. This object is one of five such 'lights' and is number 4. These names are assigned automatically when using the Attachpoint Tool, so be very careful not to manually change them...

Also, in this case since this is one of the wingtip "recognition lights" I've used the <Visibility> entry for "light_recog_vis"...

FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_landing_4"> <AttachedObject> <Effect effectName="fx_landing" effectParams=""/> </AttachedObject> </Attachpoint> <Visibility name="light_recog_vis"> </Visibility> </FSMakeMdlData>
 
The fx_landing.fx file cannot be called from the aircraft.cfg file entry. What version of Max are you using?

Here is the entry used for the light polygon shown previously. Note that the <Attachpoint name= must match the object name. This object is one of five such 'lights' and is number 4. These names are assigned automatically when using the Attachpoint Tool, so be very careful not to manually change them...

Also, in this case since this is one of the wingtip "recognition lights" I've used the <Visibility> entry for "light_recog_vis"...

FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_landing_4"> <AttachedObject> <Effect effectName="fx_landing" effectParams=""/> </AttachedObject> </Attachpoint> <Visibility name="light_recog_vis"> </Visibility> </FSMakeMdlData>

I am using 3ds max 7 :( ...... also I am currently busy with studies, I'll let you know when I try this out with landing light visibility tag.. probably three weeks
 
Code:
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_landing_4"> <AttachedObject> <Effect effectName="fx_landing" effectParams=""/> </AttachedObject> </Attachpoint> <Visibility name="light_landing_vis"> </Visibility> </FSMakeMdlData>

I tried, it failed. Could there be a conflict between the config file and the *.air file with the use of attachpt tool landing light function?
 
No, neither the .air file or the aircraft.cfg file will affect effects...

Max7? So you are using the Prepar3D v1.4 SDK to export and compile?

Unfortunately, I only have Max9 and Max2012, so I cannot send you a working example. :oops:
 
Last edited:
Have faith. You will get it working. It might be something very very small that is causing this malfunction. You'll get it. Maybe work on other things and take a break from the problem and come back to it with a fresh outlook.
 
Silly question maybe, but do you have electricity for the landing lights? I encountered that my nav lights wouldn't work if I didn't assign electricity to them (via the [electrical] section in de aircraft.cfg)
 
No, neither the .air file or the aircraft.cfg file will affect effects...

Max7? So you are using the Prepar3D v1.4 SDK to export and compile?

Unfortunately, I only have Max9 and Max2012, so I cannot send you a working example. :oops:

I am using FSX SDK to export and then MCX 1.4 to export for FSXA and P3dv2

Have faith. You will get it working. It might be something very very small that is causing this malfunction. You'll get it. Maybe work on other things and take a break from the problem and come back to it with a fresh outlook.

Thats What I am doing right now :P

Silly question maybe, but do you have electricity for the landing lights? I encountered that my nav lights wouldn't work if I didn't assign electricity to them (via the [electrical] section in de aircraft.cfg)

Hmmmmm.... lets find out :stirthepo
 
Bill would you be willing to take a look at my project work so far?

I can send you source files as well as the model and textures?
 
I would be happy to do just that. Possibly I can spot what the problem might be...

From the File menu, look for Save As Archive. This should create a .zip file with the latest .max file and all materials & bitmaps into a single file.
 
I tried replying via email, but something went wrong and it got bounced back as undeliverable...

First, the proverbial "Good News" is that your landing light works perfectly! I suspect however that it's falling over dead because you are using MCX to compile the model. I have no idea, but does MCX even parse the modeldef.xml file when it compiles a .mdl file? If not, then that's why your light isn't turning on/off. The <Visibility> conditional XML script doesn't get read and added to the compiled .mdl file.

You can easily verify if this is the case by loading your .mdl file in Notepad or Notepad++ and checking the very last entry in the file:
Code:
attachpt_landing_4 ATTO„  | i  fx_landing  attachpt_landing_4

I used the Prepar3D v1.4 export module and then compiled the .x and .xanim files using the Prepar3D v1.4 xtomdl.exe compiler. I tested this as a substitute for the default C172 and aside from contact points, and .fx light positions, and a totally opaque canopy glass, it looks just fine. I recompiled using the Prepar3D v2.2 xtomdl.exe compiler and tested in Prepar3D v2.2.1. It appears just as it did in FSX/A.

Here are some practices you need to correct moving forward:

1. The export module really doesn't like Material names that begin with numbers, such as 01-Default. While the exporter will add an X in front, it's a massive pain in the butt to get pestered with popups when exporting.

2. All your materials are "Standard". You truly do need to create new "FSX Materials" so that you can configure the advanced properties afforded, otherwise your massive 4096x4096 textures (rather much of an overkill for a plane this tiny!) will be wasted.

My suggestions would be to take care of the above issues, then learn to use the XtoMdl.exe compiler supplied with the Prepar3D v1.4 SDK.

It's a real shame I can't save this project back to a Max7 format, but Max2012 won't support that option. I can only 'back-port' two versions: 2010 and 2011.
 
Last edited:
Back
Top