Roy Holmes
Resource contributor
- Messages
- 1,805
- Country

In FSXA there are many entries in modeldef for parts that define mouse rectangles and the actions that result from clicking on the parts. As I understand it in the SDK, for GMAX with the attachment tool you can select from the list of mouse rectangle parts in modeldef.
FSDS does not have an attachment tool and this is generally resolved by entries in the PartsDataDef file that exactly follow the format in the SDK for PartData in Modeling File Formats. The examples under Template Part Data include some that are already included in the FSDS PartsDataDef file. These include effects, visibility and platform entries. These all appear to work:
For example the following PartsDataDef entry is the same as in the SDK
platform_CONCRETE_0 <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Platform name="platform_CONCRETE_0" surfaceType="CONCRETE" > </Platform> </FSMakeMdlData>
However there are no entries for Mouse rectangles like the SDK example:
MouseRect <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <MouseRect name="lever_pfd_mfd_select_4"> </MouseRect> </FSMakeMdlData>.
I want to use the button_map_range_increase modeldef part, so I tried adding an entry to PartsDataDef as folllows:
button_map_range_increase <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <MouseRect name="button_map_range_increase"> </MouseRect> </FSMakeMdlData>
This and similar attempts gave no indications of being recognized by FSDS. although they were included in the _interior.x file. I had no mouse hand and nothing happened when I clicked on the point where the part was.
Can anyone point me at where I can find the solution for this issue?
Roy
FSDS does not have an attachment tool and this is generally resolved by entries in the PartsDataDef file that exactly follow the format in the SDK for PartData in Modeling File Formats. The examples under Template Part Data include some that are already included in the FSDS PartsDataDef file. These include effects, visibility and platform entries. These all appear to work:
For example the following PartsDataDef entry is the same as in the SDK
platform_CONCRETE_0 <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <Platform name="platform_CONCRETE_0" surfaceType="CONCRETE" > </Platform> </FSMakeMdlData>
However there are no entries for Mouse rectangles like the SDK example:
MouseRect <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <MouseRect name="lever_pfd_mfd_select_4"> </MouseRect> </FSMakeMdlData>.
I want to use the button_map_range_increase modeldef part, so I tried adding an entry to PartsDataDef as folllows:
button_map_range_increase <?xml version="1.0" encoding="ISO-8859-1" ?> <FSMakeMdlData version="9.0"> <MouseRect name="button_map_range_increase"> </MouseRect> </FSMakeMdlData>
This and similar attempts gave no indications of being recognized by FSDS. although they were included in the _interior.x file. I had no mouse hand and nothing happened when I clicked on the point where the part was.
Can anyone point me at where I can find the solution for this issue?
Roy