Are you using Developer Mode or made changes in it?
no
Brief description of the issue:
It is impossible to start the Dornier J Wal (Local legend III) from cold and dark following the checklist
Provide Screenshot(s)/video(s) of the issue encountered:
n/a
Detailed steps to reproduce the issue encountered:
Start a flight from the world map selecting a parking/docking position. The plane will load cold and dark. Following the checklist procedures including turning on the fuel valves and the starter will not start the engines. The start motor can be heard briefly and the prop turns, but after a short while the prop and engine comes to a stop. The plane can only be started with the rather immersion breaking Ctrl-e auto start.
There seem to be two bugs causing the engines to be unstartable.
- The fuel cut-off valve. The (English language) tooltip and starting position of the fuel cut-off valve is wrong. It is on/open in the 3 o’clock-9 o’clock position (the tooltip says ‘open’) and off/closed in the 12 o’clock position (the tooltip says ‘open’). If you zoom in the cockpit decal says “zu” (closed) in the 12 o’clock position. This tooltip error is made worse by the fact the aircraft spawns with the valve in the 3-9 position (open), but you would expect it to be closed as there is a checklist item to turn it on.
Fix: correct the tooltip and starting position of the shutoff valve.
Edit to this point. It seems the tooltip is ok, when starting on the water runway. Perhaps the cut-off-valve is linked to a toggle command, so the first time you manipulate the switch it simply switches to the opposite state (but the tooltip doesn’t account for that, asuming it’s on from the start).
Without fuel the plane cannot start, but another bug is hampering this as well.
- Magnetos are off. Although there is no way in the cockpit to manipulate the magnetos the engines need them. The engines cannot start with the magnetos being off. A user can circumvent this by turning the magnetos to both with a keybind, but the magnetos aren’t in the checklist nor in the historical plane.
Fix: change the left and right starter to engage the events “MAGNETO1_START” and “MAGNETO2_START” rather than the simple start events like TOGGLE_STARTER1 or whatever the code uses now.
Edit to this point: a simple edit to apron.flt to set the magnetos to true would possibly also do the trick.
With the cut-off valve in the correct position and magnetos on, it is possible to start the engines.
PC specs and/or peripheral set up if relevant:
n/a
Build Version # when you first started experiencing this issue:
I downloaded the plane in April, but according to this forum this issue has been there since release of the aircraft add on.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video: