Can I ask if you'd take a look at Ilyushin Il-14P and confirm what happens when it runs out of fuel ?

... you could find the script part defining the amount and set it to 80 KG. Im sure it runs out pretty soon and you can attempt an engine-less glide for a rough landing.

Logged

We are still undeveloped as long as we don´t realize, that all our science is still descriptive, and than beyond that description lies a whole new world we just haven´t even started to fully understand.

Can I ask if you'd take a look at Ilyushin Il-14P and confirm what happens when it runs out of fuel ?

I just did a quick test, and right after it runs out of fuel, the engines start losing power, and therefore losing altitude, forcing you to do an emergency landing . But for some reason, the engines never shut down automatically.

As PytonPago said, you can always try it yourself by setting the fuel content in each tank editing the 'Ilyushin_Il14P.xml' file.

Or, you can set the fuel content through the script as well.Write under function initialize(reload):

I just did a quick test, and right after it runs out of fuel, the engines start losing power, and therefore losing altitude, forcing you to do an emergency landing . But for some reason, the engines never shut down automatically.

... well, normally, propellers still turning due to great air-speed (the airflow just) - auto rotation as also by the helicopters, doe without the partial lift effect. They could doe block themselves if an engine gets critically damaged (causing the axle to get blocked), but normally, it should still auto-rotate till a certain speed, where the airflow force isnt enough to turn the propellers ( but dont ask me how to calculate that speed for the Il ).

« Last Edit: August 11, 2014, 03:46:58 am by PytonPago »

Logged

We are still undeveloped as long as we don´t realize, that all our science is still descriptive, and than beyond that description lies a whole new world we just haven´t even started to fully understand.

I just did a quick test, and right after it runs out of fuel, the engines start losing power, and therefore losing altitude, forcing you to do an emergency landing . But for some reason, the engines never shut down automatically.

... well, normally, propellers still turning due to great air-speed (the airflow just) - auto rotation as also by the helicopters, doe without the partial lift effect. They could doe block themselves if an engine gets critically damaged, but normally, it should still auto-rotate till a certain speed, where the airflow force isnt enough to turn the propellers.

Of course, I know that, but the thing is that I landed the plane, put the brakes on, and the engines are still running, until you press 'E' to shut them down.

Also, talking about engines, it would be very nice to be able to slowly start the engines, not suddenly. Just like the way you shut them down.

ok thanks for your discussion, it pointed me in the correct direction...

1) JSBsim file within Outerra must ALWAYS contain an engine.2) For a glider the thrust and power tables in the prop need to be reduced to zero.

Levi, I think the code for the sound needs to use 'engine running' rather than rpm to play the sound.

propulsion/engine[0]/set-running = 0 or 1

You're very welcome! Glad it helped.

And thanks! I didn't know about that property I think I'll use it on the A380

Doe, it would be very useful to have a full list of all JSBSim properties, as I spent a considerable amount of time just searching for the wanted property

Well I'm attempting to get my flight models to run in both Flightgear and here...

This is because FG has a better debug tool that allows me to see all the properties within the flightmodel.... it's something that the dev here need to look at as it's virtually impossible to do a complex flight model without this facility.

I also assume you have the jsbsim manual ?

One of the advantages of being able to see the properties used within JSBsim is that they don't update the manual on too regular a basis and being able to look at the list of properties and think "I've not see that before" can get you doing the right investigation work as to its functionality and extended uses.

« Last Edit: August 11, 2014, 04:00:40 pm by bomber »

Logged

"If anyone ever tells you anything about an aeroplane which is so bloody complicated you can't understand it, take it from me - it's all balls" - R J Mitchell

This is because FG has a better debug tool that allows me to see all the properties within the flightmodel.... it's something that the dev here need to look at as it's virtually impossible to do a complex flight model without this facility.

... what stuff can you look at there ? Or you can get any thing from the functions you like to see ?

« Last Edit: August 11, 2014, 11:46:47 pm by PytonPago »

Logged

We are still undeveloped as long as we don´t realize, that all our science is still descriptive, and than beyond that description lies a whole new world we just haven´t even started to fully understand.

Well I'm attempting to get my flight models to run in both Flightgear and here...

This is because FG has a better debug tool that allows me to see all the properties within the flightmodel.... it's something that the dev here need to look at as it's virtually impossible to do a complex flight model without this facility.

I also assume you have the jsbsim manual ?

One of the advantages of being able to see the properties used within JSBsim is that they don't update the manual on too regular a basis and being able to look at the list of properties and think "I've not see that before" can get you doing the right investigation work as to its functionality and extended uses.

I will have to take a look at that Flight Gear's debug tool, sounds very interesting.

Yes, I have the JSBSim manual, but I didn't used it too much. Now you mentioned about it, I did a quick search for 'set-running' in the manual, and voila! I found the list I was looking for! I must be very blind to miss that

But, as you said, the manual isn't being updated too frequently (last version is from 6/9/2011), and they may have changed/added some properties and other things since then...

Then, the best way to see all and latest properties, is using FG's debug tool, right?

Yes that's the best way of seeing every available property at present.... I'd prefer to do that here tho rather than FG.

Whilst were talking animation, the engine cowls would more realisticaly be animated using engine temp rather than rpm... if we had extended keyboard functionality we could create an engine cooling system (already written) and use a property from that to animate with.

Logged

"If anyone ever tells you anything about an aeroplane which is so bloody complicated you can't understand it, take it from me - it's all balls" - R J Mitchell

I'm not 'advertising' FG, I'm just thinking that it does no harm to 'cherry pick' the good stuff.

I don't know if you already know this, but in Outerra, you can see them in 'real time' as well in the console, within JavaScript Don't worry about 'advertising' FG, any positive "advertising" is very welcomed

Yes that's the best way of seeing every available property at present.... I'd prefer to do that here tho rather than FG.

Whilst were talking animation, the engine cowls would more realisticaly be animated using engine temp rather than rpm... if we had extended keyboard functionality we could create an engine cooling system (already written) and use a property from that to animate with.

I knew sometime, somebody will say something about that I don't really know how cowls works, they open to cool the engine or something? I animated them just for eye candy because I like the way they open and close

I also searched for the property to show fuel and oil temperature to animate the gauges, but I didn't found anything

And yes, we really need extended keyboard functionality, or even better, clickable cockpits. But we just have to wait until that's implemented

I also have to mention that I have a very little experience/knownledge with JSBSim and/or aviation. My first interacting with JSBSim/JavaScript, was when I started working on the Basler. Not too long time ago, so I have a lot of things to learn