This is probably the last I will do on this before Flight Night, unless some serious mistakes are uncovered in the models and animations I have done. No night flying until someone does the instrument lighting. I think the autopilot could be better.
Over to you to modify and release a new version if / when you want.
Apologies for missing out on the first outing of this after all the hard work you put in, Warty.
Do you have any plans moving forward for it? It seems like an excellent platform and got a lot of promise. Willing to muck in where needed to get this to a high standard. It's one that deserves the love.
I only just noticed when I came to download the latest version today that it is CC-BY-NC-SA v4. I was using an old version as my basis (that I had from 2015) that didn't have a licence file in it so I assumed it was GPL. Maybe it was back then - who knows? Whatever. My GitHub account doesn't allow me to distribute CC-BY-NC-SA stuff and personally, I only do GPL anyway.
But you already have the modified aircraft model and its animations.
Will let you know when any significant changes are made to the FlightDeck
Sound related, what I added to the model is just the start. I am still trying to find the right signature sound but I am on it.
To be able to go on with the sound design, I will need the engines and the propellers run the right way. As soon as the engines reached nominal N2 props will run at constant reduced rpm. Thrust will be produced by changing blade angle, either manually (in ground or beta) or automatically (PMU) in the air. That creates different sounds and that would be what I am after.
Would be too cool to have that twisted roaring sound when the blades are turning.
Starter question would be. Are the engines designed to work like general turbojets and can they be controlled that way?
A little more advanced question would be: If they are working that way, how can we control Blade Setting and come up with a thrust value and actually create force on the aircraft to move it?