How are animated buttons and switches mapped? If a certain button or switch in a cockpit has a function that is normaly assigned to a the joystick, or maybe a custom function that isn't a normal FSX function like changing an MFD display, how is it assigned? Is there a file somewhere that tells it what to do or is it something in the model itself?

Yeah something like that. So it's done in the model. Is there a way to edit/add to these functions? See, I actualy got permission to use some avionics from one aircraft in another one, if I could figure out how to do it. I have it partialy figured out but not completely.

Travis wrote on Jun 29^th, 2009 at 12:03am:


Editing the original isn't even what I want to do. Never mind that. Okay suppose I got permission from someone to use their avionics in another airplane (which I did. It's the original Accel Pack FA-18. I talked to a guy over at FS developer and he said I use their stuff) and I put said avionics in another airplane and it works, sort of. But because this other airplane doesn't have the ultra cool 3D buttons that were mapped in the modeling process like the original airplane, I have very little control...in fact, none. The plane I want to mod is an old F-5F that I believe was originaly an FS9 plane...not even sure where I got it. I have modded the VC with some success. Would it be possible to map some of the functions of these avionics to say, a joystick or keyboard button? Maybe that FSUIPC4 program would allow that? Maybe...? Please...?

Travis wrote on Jun 30^th, 2009 at 11:19pm:

Most but not all...Most of the MFD commands that this avionics use appear to be very specific and unique to this system.

Just normal MFD functions, like changing it from the ADI to the engine display or the FCR.

Travis wrote on Jul 3^rd, 2009 at 1:56pm:


No. Remember that this FA-18 model has no 2d panel at all. The "buttons" around the PFD, MFD, EICAS, etc. are part of the 3d model, and the "mouse points" are defined in the Modeldef.xml file.

The OP has been told several times how to find the L:variable names used by simply looking through the Acceleration SDKs "Modeldef.xml" file, or by simply loading the FA-18_Interior.mdl file in Notepad.exe and searching for the L:var names, and the corresponding EventIDs.

For example, the first button defined is this:
Code:

  <PartInfo>
    <Name>ddi_l_btn_00</Name>
    <AnimLength>50</AnimLength>
    <Animation>
	<Parameter>
	  <Code>
	    (L:ddi_l_btn_00,number) 50 *
	  </Code>
	  <Lag>250</Lag>
	</Parameter>
    </Animation>
    <MouseRect>
	<Cursor>Hand</Cursor>
	<MouseFlags>LeftSingle</MouseFlags>
	<EventID>0x00011100</EventID>
    </MouseRect>
  </PartInfo>
 

The two important bits of information needed are the <Name> and <EventID> lines:

<Name>ddi_l_btn_00</Name>
<EventID>0x00011100</EventID>

The first tells us the XML "name" for the button, so that we have something to help us identify the EventID's purpose.

The second tells us the name for the EventID that must be sent to the sim, which is then passed to the controlling .dll, which in turn sets the value of the L:var so the 3d button on the model will respond.

This is all that is required to create an invisible XML gauge to control the buttons surrounding the FA-18s glass displays.