True, this wouldn’t be normal procedure but it does illustrate a problem somewhere.
However, what’s interesting is that once you have adjusted the prop levers, returning them to their original position doesn’t cause the problem, which makes me think the default settings is something you can’t normally do with the levers.
It’s not HD yet but who cares!
well that sure looks like an ASBO 
Do we have a changelog for the update? 
Quick question - should the AP have enough control authority to keep the plane in level flight below ~ 95kts ?
Yours is the only twin I regularly fly, but later I can try to reproduce with the Baron.
But you are right, in normal operation you would never see this, and I suspect hitting Ctrl+E, or me rotating my starter key on my Logitech switch panel would start both engines at the same time. My assumption is that the lurch is maybe asymmetric thrust. The switch on my panel effectively flips the starter switch in both directions at once.
I would be interested to find out what the initial values of the proper lever are. I will also re-install version 1.2.2 to try that. It’s possible this is the result of you adding prop feathering?
depends on Weight, Cog and Power but more importantly current altitude ??
But yeah should do
we did NOT ADD Prop feathering ??
Been trying to get it working since V1.2 !
Where are you getting this from ?
If you haven’t already, check out flightsim.to - almost every airport in the Caribbean has been done by someone there, and many of them are frankly just brilliant. St. Eustatius comes to mind, along with any of the Guadeloupe airports, St. Kitts and Nevis, all the little islands in the Grenadines north of Grenada. I have videos of nearly all of them:
My amateur fumblings in your engines.cfg.
I ran a diff between the 1.2.2, and 1.3.0 config files, as I usually do, looking for changes.
I can see I had misread one of the lines, and it was to do with auto_feathering anyway, and you had disabled it. Sorry, that was my mistake. I think I mistook one pane for the other in Notepad++. 
I’ll re-test the above with 1.2.2 shortly.
No I think in my blind wanderings through the “SDK OF CONFUSION AND LIES” I may have inadvertently fooled the system into some unachievable state .. i.e. Props are Featherd LOL
I am working on a solution that “MAY” Be the cure all
(But in the meantime .. ahem… stick to the POH And set levers for full fine before starting )
I can confirm that version 1.2.2 does not have this issue. Leaving the levers in their initial states, I can still start either engine without that lurch I demonstrated.
Congratulations on achieving the impossible with 1.3.0. 
Downloaded and installed 1.3.
Just completed a quick flight from Lands End to St Mary’s (UK). One of my favourite short hops, (thanks Superspud for your scenery!).
Nice to see the improvement to the Attitude Indicator.
The aircraft is not so enthusiastic in it’s climb away now. Also easier to control speed and altitude on descent.
As a side point, do folks still have engine cut out problems? Since version 1 I have had no problems here. Both at sea level (as per the Lands End flight) nor when enjoying the thrills of PNG.
Have been an Islander fan for years. Love it!!
Thanks Blackbox.
Also, my startup is issue free.
Looking forward to downloading the update. So much unpacking to do still and errands… grrrrrr…
Yeah, would love to see a change log.
thank goodness for that…no wonder it won’t map!!!
I’ve noticed it will if you let the RPM’s drop too far. I had digital readouts going on my Logitech mutli-panel, and from memory they would cut out at around 400-500 RPM. I’ve not retested this with 1.3.0.
Maybe I have just been fortunate, but with the throttles at minimum and RPM around 600, I think, I have not had that problem.
Both sea level and at around 5000 feet it was ok for me.
I’m testing at about 1500ft with 50% fuel and pilot and 1 passenger COG is 21.59% MAC and Calm Preset. RPM is 2500 and I’m lowering the Manifold pressure from about 17" to about 15" to drop the speed from 100 to 90kts. AP mode is HDG at ALT after using ARM to get to 1500ft.
AP doesn’t seem able to hold the plane level below 95kts - if I turn off the AP and trim manually it’s fine - its like the AP isn’t being allowed to apply enough elevator to maintain enough nose up.
I’ve pretty much given up on the AP for things like ILS approaches. It just doesn’t seem to be able to trim rapidly enough, and cannot maintain the glideslope. It has no problem getting on to the localiser, and always lines up dead centre, but other than that its useless. During cruise it works fine though.
Compare this to the 172, and its night, and day. In the 172 you can be quite aggressive with the throttle, and the AP will climb, and dive to keep on the glideslope. It’s not the end of the world, but it does look like it still needs some work in that aspect. I think its the only plane that has this issue that I regularly fly.
I never agreed with the notion of “It’s not an AP aircraft”. If it has the system, it should work properly. It’s very easy to hand fly an ILS, the AP just can’t seem to do it.
What you should be able to do is adjust throttle to increase speed, as the AP pitches up, and down to maintain the glideslope. The 172 does this really well. What will happen here is, say you are just under the glideslope, it will trim up to get back on to it, overshoot, then not trim down fast enough, pushing you into a stall.