Don’t worry little furry Otter, we still love you. We’re just too busy right now with the new shiny Boeing 247 and C414.
4 Likes
Anchor would be cool with Twotter. I was treading water with props feathered into wind to stay in place lol.
1 Like
Great idea
I have tracking enabled on this thread and every time a notification pops up I’m expecting it to say the new sounds are live in an update!! 
5 Likes
Same! And every time I’m disappointed 
5 Likes
Sorry ^^
I know it’s not fair, but there is a sound mod on the fitsim+ patreon that made the job. It costs 2 bucks.
1 Like
Coding is not something I do often, and sometimes the logic escapes me. Reverse Polish Notation is also not a strong suit of mine. I would like to understand your thought process here a little better. I do have AAO but use SPAD preferentially, for what it’s worth.
It looks like you are taking the current prop angle in degrees, adding 34 to it, then checking if that result is less than the result of the next expression and if true set that value into the spoiler value. Otherwise, turn spoilers off. This expression is where I get a little lost.
if{·34·(A:PROP·BETA:1,·degrees)·(A:PROP·BETA:2,·degrees) → What’s the purpose of 34 here again?
+·-·sqr·83 → Adding the negative square of 83? to the current prop beta? -6889? This can’t be right.
Then you have the multiplier (*), 
Can you translate? 
EDIT: Testing this in AAO, I get a result of 16268 at flight idle, you are treating this as an axis aren’t you? Range of 0 - 16268, not just setting % of 100. If so… tricky tricky…
I’ll try to explain bit for bit.
(A:PROP·BETA:1,·degrees)·(A:PROP·BETA:2,·degrees)·+·34·<·
If you take a look at the prop figure in the Aerosoft manual the beta range is below 17 degrees (when the engine doesn’t provide enough power to stay at the full constant speed (2000 rpm, I believe)).
The Aerosoft code just checks the left prop, but I thought it would be better to check both propellers so the first part of the code adds (+) prop1 and prop2 and checks if it’s less than (<)
34 then the rest of the operation starts ( if{ ).
This bit could be more advanced and check the props individually (AND or OR). However, I haven’t found a way to set left and right spoiler individually (A:LEFT SPOILER is read only).
34·(A:PROP·BETA:1,·degrees)·(A:PROP·BETA:2,·degrees)·+·-·sqr·83·*
In the next part is where RPN gets a bit complicated as the variables and operators stand in a long queue. Basically, the idea is to get a nonlinear increase in the application of the spoiler so the closer it is to full beta at idle power the more spoiler (the Aerosoft code is simply on/off). So, first the code adds prop1 and 2 and substrates the result from 34. This results in a range from 0 (both props at 17) to 14 (both props at full beta = 10). To get the nonlinear application the result is squared (sqr). The result is then multiplicated by 83 to match the event (>K:SPOILERS_SET) that behaves like an axis (0-16864).
els{·(>K:SPOILERS_OFF)·}
The final part ends the if statement with an else event. If the props aren’t in beta turn the spoilers off.
It’s just a simple hack done in an evening to solve the binary spoiler code, so it could probably be more elegant. If anyone finds it useful for their purposes, all the better.
1 Like
I got a linear version of this working nicely in SPAD now with expressions. I’m setting percentage of 100 vs axis, only Delta really. Works great.
100% @10deg UpTo 0% 17+
1 Like
You can make your own bvar to lvar translation and make the switches accessible for spad.next.
Check the DH6_interior.xml at the bottom of that file there is a section where this has already been done for quite some switches. Just add your own lines here for the switches you want.
1 Like
I remember them saying they had recorded the new sound set over a month ago. Not sure what’s taking them so long.
Probably taking their time to do it right, and not rush it, miss something, then get lambasted by the community over it.
I can’t blame them for that if that is the case.
1 Like
I’d imagine SU9 might have something to do with it.
1 Like
Might as well wait for SU10 then. Kidding. I’m sure you’re both right. Happy to wait for it to be done right at this time. Expecting it to be immersive hehe 
1 Like
Really weird today - I started the sim to find that the content manager was telling me the Twotter wasn’t installed.
Confused, I opened the hangar to find that sure enough - someone had pinched it!
Let the manager reinstall it and hopefully all is well. Weird, though. 
If you hear a really loud starter motor outside the hangar you might still have time to stop them!
1 Like
I’m considering getting this plane. I’m not too picky, so do you think it is worth my money?
It is really good fun, and nicely modelled.
Don’t expect study level(whatever that may mean), circuit breakers are e.g. inop.
The sounds are the weak spot, but they should improve.
1 Like
Certainly. It’s great fun. Plenty of variants (pax, cargo, skis, floats etc.) and lots of great liveries at flightsim.to. Beautiful model and cockpit. Some depth but not to complicated to start. Some people have complained about the sounds, but I don’t find it a showstopper the same way they do. Aerosoft say they are working at a new sound module, but it has yet to materialise.
1 Like
Definitely, go anywhere workhorse, enough complexity, commitment from the publisher to improve in line with the sim updates.
2 Likes