In line with the above, it is significantly necessary to train new pilots from a realistic approach, keeping in mind the existing piloting reviews from old fellows of that aircraft to adopt for a dynamically changing environment whether that be in terms of standard operating procedures (SOPs) of flight, systems, or navigation.
For this reason, high-fidelity FDM is a concerning aspect. As the hiring and training of new pilots is expensive, for this reason internationally, ground training with respect to particular aircraft is being catered by flight simulators. The current dire need of flight simulators is captured from the high rate of hiring of new pilots and indulgence of the airlines whether it is in Pakistan or international forum. I hope you like the changes, for me they were essential to provide instrument flight capability and the panel is now a little higher and matches reality much better.It’s a question of interest, why one should design FDM?, because the FDM is a heart for flight simulator. >commented out Electrical.nas because it deactivated the nav displays after some time (but I don't know how)Ĭode: Select all Aircraft/C130/Nasal/Electrical.nas->ģ.)in interior.xml rise the panel1 a bit:Īircraft/C130/Models/Interior/Panel/panel1.xmlĤ.)added ADF to panel1.xml where it belongs: You better create an additional small png or borrow one of the hundrets around.Ģ.)In order to get the instruments working I changed in base-set.xml: As yours go from top to about half, I had to split the factor eg: 0.1 -> 0.05 to display correct distances. One notice on the TACAN distance display: It is working correctly now, but for a normal factor/step animation, the numbers should cover the whole vertical space on the png image. Instrumentation/heading-indicator/offset-deg Instrumentation/nav/heading-needle-deflection Instrumentation/tacan/indicated-bearing-true-deg Instrumentation/heading-indicator/indicated-heading-deg
instrumentation/navcomputer/indicated-distance-nm -> Instrumentation/tacan/indicated-distance-nm Hi helijah, thanks for applying, the c130 works very well nowĪs the hsi display did not work, and instrument flight is necessary sometimes, I did some more changes:ġ.)hsi: changed some paths and values to get it working, now VOR/ILS and TACAN work I think the result should appeal to many:) Even if the versions should be slightly different (this is not the case yet) The fuselage should greatly amuse Melchior (he estimated that it is not useful to be very close to the real forms ). So, replacing the "camber="0.18" by "camber=0147" in the wing section, we get :Ĭode: Select all Solution results: Iterations: 2266įor the rest. The closer to 0 as possible, but still positive. Well, I always made sure that the value "AOA Cruise" is always positive. When using prop-reverse to taxi, use breaks with caution, better use normal forward props to stop the aircraft.Ĭode: Select all Solution results: Iterations: 2114 With Del you can toggle the prop reverse (prop pitch will put to 0), so increase prop-pitch if you want to take off again.
Setprop("controls/engines/engine/propeller-pitch",0) Helijah, could you please replace the old yasim.xml?Īdditionally, I added thrusters to simulate the prop reverse, put the following in the c130-keyboard.xml: Hi, I've fideled around with the FDM and tuned it a bit more, here is the result:
0 kommentar(er)
