-
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.
XML programed parts in gmax
- Thread starter Xpand
- Start date
In the FFDS forum, check "Working XML COde" posts
http://www.aerodynamika.com/cgi-bin/yabb/YaBB.cgi?board=XML
I'm quite sure this has been posted before.
http://www.aerodynamika.com/cgi-bin/yabb/YaBB.cgi?board=XML
I'm quite sure this has been posted before.
- Messages
- 10,163
- Country
Yep, Felix is on it..
Basically you open up the Part Code list with Notepad. This will have all your animations codes. This is what the compiler uses when it compiles your plane.
Note that you can then copy/paste/modify a part name and change it to one that you wish.
But, you must make a 'new' name and any L:var custom animations must be different (in naming) then any other part in that list, or it will mimick other parts that share the same name.
Example; (L:SunVisorLeft, bool) <-- if you have any other parts with that code in it, they will all work at the same time, so you must change it, such as 'SunVisorLeftA, SunVisorLeftB, etc..
Same for parts name tags. You cannot have two or more parts with the same name tag.
When going out to make such custom "new" animations, make periodic backup copies of your master parts list. If you mess it up, you can always backstep. Remember, one small symbol will cause the rest of the entire stack of code to not function, which means when you burn a MDL, the animations will not work until you find out what symbol you messed up.
Learning code will be another thing to do. Very difficult at first. Best to use 'similar parts' to go by and gradually learn how they work. Ask questions on code here or in Gauges to find out meanings of things. The best area to find out all the lists of commands and aircraft readouts (base codes) is in the FS2004 Panel SDK in the Docs folder. Some brilliant reading in there, and all tag and readouts are in there as well.. (Well, most of them, some exist and are found at Nick Pikes great website).
Once you start to learn how to make your own code, you will be addicted. You'll have so many wild animations going on.. Your list will double in size.
Just be careful and be patient.
Bill
Basically you open up the Part Code list with Notepad. This will have all your animations codes. This is what the compiler uses when it compiles your plane.
Note that you can then copy/paste/modify a part name and change it to one that you wish.
But, you must make a 'new' name and any L:var custom animations must be different (in naming) then any other part in that list, or it will mimick other parts that share the same name.
Example; (L:SunVisorLeft, bool) <-- if you have any other parts with that code in it, they will all work at the same time, so you must change it, such as 'SunVisorLeftA, SunVisorLeftB, etc..
Same for parts name tags. You cannot have two or more parts with the same name tag.
When going out to make such custom "new" animations, make periodic backup copies of your master parts list. If you mess it up, you can always backstep. Remember, one small symbol will cause the rest of the entire stack of code to not function, which means when you burn a MDL, the animations will not work until you find out what symbol you messed up.
Learning code will be another thing to do. Very difficult at first. Best to use 'similar parts' to go by and gradually learn how they work. Ask questions on code here or in Gauges to find out meanings of things. The best area to find out all the lists of commands and aircraft readouts (base codes) is in the FS2004 Panel SDK in the Docs folder. Some brilliant reading in there, and all tag and readouts are in there as well.. (Well, most of them, some exist and are found at Nick Pikes great website).
Once you start to learn how to make your own code, you will be addicted. You'll have so many wild animations going on.. Your list will double in size.
Just be careful and be patient.
Bill
n4gix
Resource contributor
- Messages
- 11,674
- Country
You didn't say what sim version, FS9 or FSX?
That's important because they use two completely different techniques!
In either case though, the answers may be found at http://freeflightdesign.com using a Search.
That's important because they use two completely different techniques!
In either case though, the answers may be found at http://freeflightdesign.com using a Search.
- Messages
- 10,163
- Country
Ok, thanks!
Just another doubt: my landing lights are always facing down even when I rotate the pivot, do you know what's the matter? I did it the right way: with a triangle and then apply the material but it always shows the light faced down.
What call tag did you label the landing lights with?
Bill
n4gix
Resource contributor
- Messages
- 11,674
- Country
In that case, you need TWO polygons, both with the Material named LIGHT_LAND applied.
One of the polys is Linked as a Child of the other. The top level poly's axis is aligned such that the Blue Arrow points in the opposite direction from where the beam of light should point...
...the Child poly's axis remains "Align(ed) to World."
Last edited: