I understood how to create checklists because it is well documented, thank you
for this. Nevertheless, I couldn’t do what I saw in only 1 aircraft: the P-51
Mustang Miss America. In this aircraft, for each checklist item, clicking the
eye icon moves the camera to the panel object that must be used, and it is
highlighted in blue, this is great. I couldn’t find the way to do the same and
the P-51 checklist is not accessible. I tried to use the parameter in the
checklist XML to designate the object PART_ID from the interior model, but it
didn’t work as expected. Any help is greatly welcome. Thanks.
To have the camera move to the location for the interactive checklist follow
these steps: 1. Create a camera position that you want to point to.
Checklist/Checklist.xml file you need to add Checkpoint info like this where
you include the name of the camera.
Note this matches the name in step #1. 3. Inside the aircraft_interior.xml
file you must add the name to a template or if you are calling to an Asobo
template.
CONTROL_LOCK_STOW_1
4. Inside the folder Checklist/Library.xml file you need to include the name
for the Checkpoint code that matches the name.
Note this matches the name in step #3. Please mark answered.
This is exactly what I did. Moving the camera works perfectly, as expected,
but defining the instrument does not work, even though I am sure it matches
the name of the PART_ID. I mean I don’t see this cockpit part highlighted. I
saw this works in the C172 G1000 so I will look into that checklist file.
In the C172 checklist XML file, I see it uses
Avionics_Switch_Bus_1_And_Bus_2_Off, and looking into this checkpoint, I saw
this:
Looking in to the C172 interior XML file, I couldn’t find this. I found
ELECTRICAL_Switch_Avionics_Master_1 and
ELECTRICAL_Switch_Avionics_Master_2 as NODE_IDs, but no PART_ID designated
as ELECTRICAL_Switch_Avionics_Master Where did I go wrong?
Sorry, please ignore my previous message. I just had to restart the flight…
Now all works perfectly, thanks for your help !!
As said on https://devsupport.flightsimulator.com/t/3804, the development
workflow is painful, sometimes I even had to restart the sim to see my changes
taken into account, which is why I initially thought it was not working.