Duplicate post...

Edited June 28, 20223 yr by Lorby_SI

Thanks again

Does all this 'happen' in the "behavior definition XML file"? Do I assume correctly that the file is in the ModelBehaviorDefs folder and if sop which particular xml file? And maybe that file is the  DHC6_Templates_Pedestal.xml   which contains stuff like -

<ModelBehaviors>
    <Template Name="DHC6_Pedestal_Template">
        <UseTemplate Name="DHC6_Fuel_Wing_Tanks_Template"/>
        <UseTemplate Name="DHC6_Fuel_Qty_Left_Wing_Template"/>
        <UseTemplate Name="DHC6_Fuel_Qty_Right_Wing_Template"/>
        <UseTemplate Name="DHC6_Pedestal_Misc_Template"/>
        <UseTemplate Name="DHC6_Fuel_Wing_Pump_Fail_Tests_Template"/>
    </Template>

Lastly how do I edit that file as it is in the Community Folder which doesn't seem to have many 'rights'.

With respect to this data I am a 'noob'.

7 hours ago, Jarnie said:

Lastly how do I edit that file as it is in the Community Folder which doesn't seem to have many 'rights'.

Sorry, no idea. This is just a theoreticaly concept, I am using one of the apps (natually). Those don't mess with files in the sim.

And you shouldn't try that on the DHC6, since it uses custom code for the gust lock on top of the visibility of the yokes. That needs a lot more thought. Check the file "DHC6_Interior.xml" right at the beginning and the update component at the end. The latter would be a good place to add the "no yoke" code = the yokes will never show.

What I am sure of: you cannot implement a "binding" to an external button this way.

All you can do is to add code that the yoke doesn't show from the beginning. Or piggyback another button or knob in the VC that you know that you can already bind. 

Edited June 30, 20223 yr by Lorby_SI

33 minutes ago, Lorby_SI said:

Or piggyback another button or knob in the VC that you know that you can already bind. 

That doesn't seem to be an option with the DHC 6 either. The plane doesn't react to any default events that could be safely used this way. I can bind the yoke visibility to the seat belt switch, but I found no way to actuate that from the outside either (except by using an app...that is what they are for...and then I don't need any of this). I could bind it to the yaw dampener switch, that can be triggered from the outside. But that is not terribly useful I think, when you have to switch YD on/off ot hide the yokes.

Edited June 30, 20223 yr by Lorby_SI

Thanks for your support. I will leave it as it is and assign a numpad key to a view of the base of the pedestal and then LMB to remove (or replace) it and then (thankfully) pressing the same assigned key will take me back to the previous view.

BTW (I tried to create a new thread on the aerosoft.com forum to ask this question but even though I was logged in I could not see anywhere to 'create new thread'.

My question is - normally CTRL E will start engines in most aircraft but it doesn't seem to work with the Aerosoft Twin Otter. Did I miss something (sometimes I just want to taxi and fly)?

2 hours ago, Jarnie said:

My question is - normally CTRL E will start engines in most aircraft but it doesn't seem to work with the Aerosoft Twin Otter. Did I miss something (sometimes I just want to taxi and fly)?

Well, the code in the DHC6 behavior file suggests that the feature is present. There is a BVar "(B:PROCEDURE_Autostart_Set)", this suggests that there should be a binding for Autostart somewhere in the MSFS controller assignments (sorry, I'm not really familiar with that) or in the plane itself (clickspot, config option?)

In fact - DHC6 documentations says, that Ctrl&E is supposed to work (Manual_eng.pdf, page 153)

Edited June 30, 20223 yr by Lorby_SI

Thanks.  I searched the manual and didn't see that (but now I do after you advised page 153). I will check again and if I still cannot get it to work will send a message to Aerosoft.

It does state CTRL e (lower case). Maybe I was in upper case.

[added later] I just checked again and tried CTRL E and CTRL e and neither resulted in an engine start.

Edited June 30, 20223 yr by Jarnie
[added later] added

I have also checked and found CTRL E starts the engine(s) on the A320, B737 and C152.

I contacted the Aerosoft technical help who suggested I have changed something and to check the operation with other aircraft.

I had done that but forgot to mention it to them so have replied advising them.

I also unlocked the yokes without success.

Lastly I 'mapped' a button on my joystick for auto engine start and it does exactly what CTRL E does - makes a sound and nothing else.

Not your problem I know but I would have thoughts other owners of this aircraft would have complained about the same thing. Obviously I am not happy

Edited July 1, 20223 yr by Jarnie
'mapped' a joystick button

Just trid Ctrl&E in the DHC6, seemed to work for me. Had to turn on the DC Master switch first, and select "External", but then it fired up. Maybe the event is just for the actual engine start?

 

Maybe it would be better if you created a new thread? Nobody is expecting a question about the DHC and autostart in a "remove yoke" thread 

Edited July 1, 20223 yr by Lorby_SI

31 minutes ago, Lorby_SI said:

Had to turn on the DC Master switch first, and select "External",

That is it!    I will start a new thread (should have before, sorry) as no other aircraft require this to be done first and as such I believe it is NOT correct.

1 hour ago, Jarnie said:

That is it!    I will start a new thread (should have before, sorry) as no other aircraft require this to be done first and as such I believe it is NOT correct.

I'm pretty sure that the developers can do whatever they want.

I've just created an autostart script in my tool (AAO) and bound it to a joystick button. It removes the gust lock, sets a couple of switches, pushes the condition levers forward, turns on the fuel and then starts the engines. Just as a proof of concept.

 

0·(>L:DHC6_GUSTLOCK_VISIBLE,·Bool)·
1·(>L:DHC6_GUSTLOCK_REMOVED,·Bool)·
1·(>K:NAV_LIGHTS_ON)·
1·(>K:TOGGLE_BEACON_LIGHTS)·
1·(>L:ASDHC6_STROBES_TOGGLE,·Number)·
1·(>L:ASDHC6_NO_SM_TOGGLE,·number)
1·(>L:ASDHC6_SEATBELTS_TOGGLE,·number)
1·(>L:ASDHC6_DC_MASTER_TOGGLE,·Number)·
3·(>L:ASDHC6_DC_SOURCE_SET,·Number)·
6·(>K:FUEL_SELECTOR_SET)·
7·(>K:FUEL_SELECTOR_2_SET)·
2·(>L:ASDHC6_COND_LVR1_SET,·Number)·
2·(>L:ASDHC6_COND_LVR2_SET,·Number)·
1·(>K:ENGINE_AUTO_START)·
1·(>K:TOGGLE_TAXI_LIGHTS)

 

And this is the script to toggle yoke visibility, can also be bound to a joystick button with AAO:
 

1·(L:DHC6_YOKE_HIDDEN,·Bool)·-·(>L:DHC6_YOKE_HIDDEN,·Bool)

 

Edited July 1, 20223 yr by Lorby_SI

Thanks

I would like to find out more of what you did usi9ng AAO, whatever that is, and where this is placed to work. Any web sites would be appreciated.

52 minutes ago, Jarnie said:

Thanks

I would like to find out more of what you did usi9ng AAO, whatever that is, and where this is placed to work. Any web sites would be appreciated.

AAO is short for "AxisAndOhs", a payware app along the same lines of FSUIPC, SPAD Next, etc. Any of those will do for advanced controller configurations. They all handle controllers separately from the sim and expand what you can do with your joysticks and other external controllers.
They all operate differently, and all have their pros and cons. Which one is right for you is your personal preference and depends on what use cases you have.

Edited July 1, 20223 yr by Lorby_SI