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

What am I missing?

Messages
21
Hi everybody!

I know this is probably "old hat" to some of you, as I've read post covering the same issue on this forum that I'm currently having. I'm trying to model a carrier based aircraft where the catapault and recovery systems are built into the model using 3ds max 9. I've followed the instructions that have been posted here:

http://indiafoxtecho.blogspot.com/2008/09/how-to-animate-launch-bar-in.html

and

http://www.fsdeveloper.com/wiki/index.php?title=Catapult/Arrestor_Operations_(FSXA)

I cannot get the launch bar or tailhook to animate for the life of me using the attach points listed. The tailhook animation only works with the tailhook section in place in the aircraft.cfg

Here are the steps I took.

1. Created and animated the launch bar and tailhook. launch bar= 0-100 frames, tailhook= 0-100

2. Created empty attach points (with / without geometry) titled exactly:
attachpt_Launch_Bar_Pivot, attachpt_Launch_Bar_Lug,
attachpt_tailhook_pivot and attachpt_tailhook_hook and positioned and attatched them to their respective parts.

3. Removed the "_n" from the tags in the object properties xml.


Can anyone tell me what it is that I am doing wrong? smile

Thanks!!!
 
Yes! As I said, the tail hook works, but only when there is an entry in the aircraft.cfg for the tailhook section.
 
Well, what's so bad about an entry?

It's amateurish.


Why are you doing this:

3. Removed the "_n" from the tags in the object properties xml.

I just checked the attachpoint xml for my working tailhook and they read:

Code:
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_tailhook_hook"> </Attachpoint> </FSMakeMdlData>

for the hook and

Code:
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_tailhook_pivot"> </Attachpoint> </FSMakeMdlData>

for the pivot.

The hook attachpoint is attached to the tailhook mesh, although the hinge isn't.

If you've changed the names of the attachpoint objects that may cause a problem as they'll both be attachpt_undefined, rather than attachpt_undefined_0 and attachpt_undefined_1.
 
Hey SkippyBing,

Thanks for the info! Sorry for the late response, had to take care of some family business.

Ok, I've got the animations working as they should, along with the proper fuctioning, the launch bar activates the launch sequence and the tailhook grabs the (invisible!!LOL) cable, but now the attach points are also glowing as if they are lights. Tried everything I could think of to remedy the problem, but nothing I do works. Any suggestions?

Thanks again for help thus far!! smile
 
Hmm, odd, the only thing I can think of is that there's also a light effect attached to the mesh you're using as the attach point for the hook ends. Can you post what's in the attachpoint xml for your hook, copy it direct from the object properties in Max/gMax in case something else has snuck in there!
 
Thanks! Here is all four sets:

Code:
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_Launch_Bar_Lug"> </Attachpoint> </FSMakeMdlData>

Code:
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_Launch_Bar_Pivot"> </Attachpoint> </FSMakeMdlData>

Code:
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_tailhook_hook"> </Attachpoint> </FSMakeMdlData>

Code:
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_tailhook_pivot"> </Attachpoint> </FSMakeMdlData>


BTW: I've deleted and recreated these attach points at least a dozen times, sometimes I only end up with one "light" and other times I have all four attach points "glowing". I've deleted all of the other attach points I had created, but I still get at least one of them illuminated!
 
Last edited:
Now that I really don't understand!

I don't think the problem is with the attach points which would mean it's either the model itself or something in FSX. I take it you've checked the aircraft.cfg for any effects in there?
 
Yep!! Deleted any and everything I could think that would be the cause. And as far as FSX goes, I'm doing a re-install of both Acceleration and the SDK for it as we speak. Once everything is back up, I'll do a "merge" of all the parts to a fresh "page" in Max and recompile and see what happens.

Be back shortly! smile
 
Ok, turned everything inside out, and still no joy!! I hate to think that I'm going to have to go through the model part by part and remodel everything!!:eek: I've been working on this project since the middle of April and was hoping these attach points and two other small items would be the last thing I'd have to do!

Oh well.................LOL

Thanks for your help SkippyBing!!
 
OK, I refuse to rebuild this project from scratch, so I need to get a bit of information from you guys regarding attach points.

It seems either my install of Max9 or FSX Acceleration considers ALL attach points to be lights or some other effect. Any new attach point I create is illuminated, although in the matter of the launch bar / tailhook pivot, lugs and hook, they function the way they are supposed to, they are also visible as lights. Is there anywhere in any configuration files for Max, FSX or the SDK that would cause ALL attach points to be considered as lights?

Other insteresting I found looking at the default DC3 in the SDK was that in the attach points properties, there was additional configuration info I hadn't seen before, check it out:

Code:
Mass = 0.000000
Ellasticity = 0.300000
Friction = 0.300000
Optimization_Level = 0.500000
Unyielding = 0
Simulation_Geometry = 2
Proxy_Geometry = <none>
Use_Display_Proxy = 0
Display_Children = 1
Disable_Collisions = 0
Inactive = 0
Display_Proxy = <none>
FSXML = <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Attachpoint name="attachpt_landing_2"> <AttachedObject> <Effect effectName="fx_landing" effectParams=""/> </AttachedObject> </Attachpoint> <Visibility name="general_light"> </Visibility> </FSMakeMdlData>

I copied that landing light over to my model and compiled, and noticed a difference in those attach points, two of the four weren't glowing as before, so I'm assuming that the extra code on the DC3 landing light is some sort of "controller" or general configuration for attach points with effects, or in general. Can anyone shed anymore light on this?

Back to the immediate problem: in order to find out what's going on with this, I may need to get some sort of confermation from a second party in order to find out if it's my computer or the model itself, would anyone care to volunteer to grab a copy of the .mdl and or Max9 files and test it on their machine? I can't send the entire project, just the afflicted parts so I can find out what's the hell is going on!! If so, pm me and let me know what you can work with (Max9, FSX .mdl ect...) and I can give you a download to pick up the files.

Thanks again!
 
Last edited:
Right-click on the attachpoint(s) in Max and copy/paste the exact entries in the Object Properties entry in your reply.

There should be no .fx included with the entries.
 
Hi n4gix,

The entries for the attach points to my model were posted earlier in the thread up at the top. The code I posted after that was from the SDK DC3 example for the attached lights. In my model there aren't any references to any type of .fx, and still I get the light thing happening.

I played it for hours yesterday, frustrated because there apparently seems to be a bug somewhere, I uninstalled/reinstalled EVERYTHING and still no change. I ended up doing what another guy did who experienced something similar with his model, he had smoke coming out of his launch bar attach points. I just coded a vis condition in the modeldef.xml applied it and have since moved on so I can finish this thing!!! smile

Code:
<PartInfo>
    <Name>attach_point_off_vis</Name>
      <Visibility>
            <Parameter>
        	<Code>
                  (A:GROUND VELOCITY, knots) 2000 &gt;                  
        	  if{ 1 } els{ 0 }
	       </Code>
            </Parameter>
        </Visibility>
</PartInfo>

I am still curious about the additional code in the DC3 attach points though, I would love to have more info on that.

Thanks!!!
 
I am still curious about the additional code in the DC3 attach points though, I would love to have more info on that.
Any attachpoint can have multiple "things" assigned to it:

  1. Name of Attachpoint
  2. Effect file (.fx)
  3. Visibility condition
  4. Mouse control

In this instance, this entry from the DC3 has three entries, which I've rearranged below with indentation to make it easier to visualize the "structure" of the script.
Code:
<Attachpoint name="attachpt_landing_2"> 
   <AttachedObject> 
      <Effect effectName="fx_landing" effectParams=""/> 
   </AttachedObject> 
</Attachpoint> 
<Visibility name="general_light"> </Visibility>
The Attachpoint name is of course obvious. It must be unique and exactly match the object's name in the .max/.gmax scene. If you Clone an object with an Attachpoint already created, the object's name will be auto-incremented, but the Attachpoint name in the Object Properties will not be changed. You must then edit that entry manually or reapply the Attachpoint Tool to affect the required name match.

The Effect chosen is the default "fx_landing.fx" file, which the sim uses to create the landing and/or taxi light "ground splash" (the visible light on the ground).

The Visibility chosen is the default modeldef.xml script for "general_light" which frankly is a rather silly name, since if you look at the script you'll notice it is controlled by the (A:LIGHT LANDING,bool) variable! Why didn't they simply name it "Landing_Light" to begin with?
 
Last edited:
Hi n4gix,

Thanks for the breakdown, confirms what I was thinking, but what I was referring to wanting more information on was:

Code:
Mass = 0.000000
Ellasticity = 0.300000
Friction = 0.300000
Optimization_Level = 0.500000
Unyielding = 0
Simulation_Geometry = 2
Proxy_Geometry = <none>
Use_Display_Proxy = 0
Display_Children = 1
Disable_Collisions = 0
Inactive = 0
Display_Proxy = <none>

Like I said, I haven't see or read about any of these properties being included in attach point properties or what they are or what they could be applied to. How do they affect an attach point? What do they control? Are these universal properties that can be applied to any type of attach points, or any other parts of the model?

Smile
 
To be honest, I've never really looked that closely at the sample DC3 source file.

I've never seen anything like them described in any of the SDK's for FS or Prepar3D...

...and the Attachpoint Tool certainly doesn't add them to the Object Properties! :confused:
 
Last edited:
Back
Top