OK, I'll take a look at what's happening.
Posts by Jet-Pack (IPACS)
-
-
Hm perhaps the collision-box for the light pole below is not computed correctly.
-
The search lights turn on automatically if you have the assistance for landing lights turned on.
You can use key assignments for landing lights as well to control the search light
-
Do you use the OrbX Netherlands in FS 2 by chance?
-
To add a GPS unit you have to model the knobs and buttons just like any other part of the aircraft and add a screen object with a luminance input, just like the DR400 example GPS screen. Once that is modeled in the sim I can show you what parts need to be added to the TMD to get a working GPS.
-
Jet-Pack (IPACS) If it is not a trade secret, is IPACS even working on implementing Garmin-like G430, G530, G1000 panels for some version of Aerofly FS or is this just a pie in the sky and wouldn't it be nice kind of day dream?
GPS units 530 and 430 are already implemented. We implemented them for Aerofly FS 2 for Just-Flight and these two should still be in the executable and are available.
-
We currently do not have any display that you could re-use to fit into that landscape GPS display. And it is unlikely that I'll get time to develop this exact GPS display. The closest match would be the 787 PFD or you could use the display area for a moving map.
-
For the record, i updated the .tmd file of the a320 to tweak the values for SnapMinimumX and SnapMaximumX for detent 3 on both thrust lever (using 0.50 min and 0.60 max) and it seems that it solved my issue…
Jet-Pack (IPACS), I’m not sure if that makes sense ?
That does make sense, but that also affects other devices and VR hands. So there are side effects of increasing that snapping region.
Instead try adjusting the input_lever2 <[float64][Input0Detent0][0.55]> positions, e.g. increase it from 0.55 to 0.57. That value affects only the TCA quadrants and re-maps their first detent to a new value.
-
-
-
It is the EQUIVALENT STILL AIR DISTANCE.
Yes, that's the one.
-
3D audio is already available for the A320 for example. Other airplanes will follow over time.
-
Estimated air distance I think.
*Edit: Equivalent still air distance
-
The configuration trim is currently not active on the ground to avoid inadvertent changes to the takeoff pitch trim if you set the trim before extending the flaps. Normally before each takeoff the pilots are expected to compute the weight and balance and set the takeoff pitch trim accordingly. I am not sure if the configuration trim would be active in the real aircraft during a touch and go, e.g. above a certain airspeed and not depending on ground/air sensor.
In the videos we use the default controls as much as possible, with auto trim enabled where this issue does not exist.
-
We're still working on both of them
-
Could the mobile Learjet’s runaway flap trim in manual operation be considered for a fix please?
The Learjet 45 pitch trim has already been updated with the current Aerofly FS 2023 version and Aerofly FS 4. It now applies a fixed pitch trim offset so it should be 100% reversible regardless of the airspeed at which you extend or retract flaps. So what runaway trim issue are you referring to? Is it a new one I am not aware of yet?
-
Probably one from the pilot radar altimeter and another from the copilot radar altimeter. Did you set both sides?
-
Ok that is a bug and I was able to fix it in my developer build with a single line of code. So chances are high that this can be included in the next update round.
-
It's been two months. Not sure if that already counts as many...
We've made good progress on the 737 but of course we also had a pause during the Christmas holidays.
Not sure if we can already show something, but I'll ask.
-
Some of the numbers seem to be incorrectly entered by default, I'll change them.
The actual mass of the aircraft without fuel is 39200 kg or about 86420 lbs and the gross mass is 46000kg, with 6800kgs fuel on board.
With an empty mass of about 31950 kg the passenger mass the remaining payload is 7250 kg, 47 passengers and 3250 kg cargo.
The mechanical calculator shows the value in a wrong unit, it should multiply by 2.2 but it currently divides the value by it.
With the ZFW entered into the mechanical calculator you can enter your desired landing flap setting with the knob in the lower right and the needle will point at the Vref for landing. For now a Vref of 135 is a good value for Flap 40. It should actually be lower than that but we'll address this issue once we implement a proper way to set the fuel and payload in a menu in Aerofly, some time in the future.