Posts by Joao_Gabriel

Quote from WAR_Capybara

We need more trainer aircrafts as there is too much cermercial aircrafts rn

I agree. The simulator is already full of commercial aircraft, it is past time for new general and executive aviation aircraft to arrive.

Quote from Jet-Pack (IPACS)

Is flaps 25 even a valid takeoff flap setting? As far as I know only flaps 1 to 15 are allowed, 25 would give you a config warning, pretty sure.

The flaps positions are probably not yet fully implemented and yes the v-speeds do not change with flap yet. I can fix this in the future when I have time for it. For now, it'd stick with flap 5 takeoff.

I found this photo demonstrating the 25 flaps on takeoff. I believe it can help with something.

Quote from Jet-Pack (IPACS)

Is flaps 25 even a valid takeoff flap setting? As far as I know only flaps 1 to 15 are allowed, 25 would give you a config warning, pretty sure.

The flaps positions are probably not yet fully implemented and yes the v-speeds do not change with flap yet. I can fix this in the future when I have time for it. For now, it'd stick with flap 5 takeoff.

Hello, 25 flaps are only used on very short runways. For example, at Santos Dumont Airport.

I also want to highlight that takeoff speeds do not change depending on the flap chosen. I hope this gets fixed.

Quote from Beto McFly

I discovered a flaw in the FMC. Several waypoints simply won't load. Initially the FMC even loads some waypoints but then an error message (format error) appears when I try to insert some more waypoints. There appears to be a disconnect between the FMC database and the fixes on the global map. To get around this error, I go back to the navigation menu and insert the missing waypoints of the route I want to take between airport A and B.

this problem also occurs on my device.

I noticed that the 737NG's FMC also does not accept flap setting 25 on takeoff.

Quote from Jet-Pack (IPACS)

Ok thank you. I am more interested in the part leading up to the takeoff. What actions do you make? You said just selecting the runway an then taking off did not cause the crash. So something from selecting the parking position to after takeoff might cause the issue, something I perhaps did not do that means it doesn't crash on my side... We would like to know the minimum steps or actions that are required to cause this crash.

Hello, were you able to find out the reason for these failures?

Quote from Fly_wu

I'm curious.

How did you know this?

I ended up finding out when I clicked on the screen to move the camera.

Quote from Beto McFly

This aircraft's GPWS test button is not functional. Did you notice this too?

I noticed, but I believe it was on purpose.

Quote from Thekingbuji333

Anything like this on the -I haven't bought the Boeing 737-500 yet.?

I found a feature on the 737NG by chance. Simply click on a screw (highlighted in the image below), present on the MCP, to activate TO/GA.

I found it very useful, as it avoids having to move the camera to click the TO/GA button on the levers.

I'm facing the same problem as you. This bug appeared on my device in Aerofly Fs 2023 beta and still remains in Fs Global. This occurs when I click on the cameras icon or the flaps icon, causing the simulator to crash and close immediately afterwards.

My device: Xiaomi Redmi Note 8 (2019) - Android 11.

I was already preparing a text reporting this problem.

I noticed that when the minimum selector is on BARO, the callouts "approaching minimums" and "minimum" do not sound.

Hello ipacs team, I come here to report some unforeseen issues with the current Aerofly Fs Global on my device. The current simulator has been experiencing crashes and screen freezes on the initial screen, these crashes occurred right after installing the additional packages, when I changed the graphic quality and also occurred when I chose an aircraft (Boeing 737NG).

Device: Xiaomi Redmi Note 8-2019, Android 11.

to update: When I clicked on the cameras icon, the simulator closed by itself. It happened shortly after takeoff.

Quote from Ethan's Aviation

I think my is bugged, it plays decison height no matter what I do. I reset it and it still played 'decision height' even with no alt set

Perhaps you are not setting the minimums on the copilot's EFIS and only setting the minimums on the commander's EFIS.

After the 20.23.01.32 update, which brought some features, among them are some improvements in the FMC of Boeing aircraft. I noticed that a new flap option 40 appeared on the approach reference page on the 777 and 787, and in real life both don't have that flap option to choose from. I hope this is the error analyzed.

(Sorry for any spelling mistakes, I used Google translator to translate into English)

I would particularly like to see the Cessna 210 on aerofly

Quote from Jet-Pack (IPACS)

That is very strange, I'll check out what might be happening.]

Do you use tilt to control the plane or the virtual analog stick on screen? When you put it on autopilot and roll the device, do you have any manual control over the spoilers?

Hello, I use tilt to control the plane. When the autopilot is on and I roll the device I have no manual control over the spoilers.

(sorry for any spelling mistakes, I'm not fluent in English and need to use Google translator)

Quote from Jet-Pack (IPACS)

Can you give me a bit more info on that? Was it flying on autopilot, did you manually deflect spoilers at this time and only one side came out or did you.

And can you please show me a screenshot from the two center screens in the cockpit from when this happens?

occurred again