mga9, x64
Installed the updates without a problem.
Tried
$ fgfs --launcher
and tinkered with the controls of a Cessna at Hilo International but did not get very far.  The battery switch and others turned red when clicked.  Tried to set up a flight plan to Honolulu for a trip down memory lane but could not start the engine.  Stuck on the tarmac for a couple of hours.  Yeah and I don't have a licence either.  Over and out.

CC: (none) => tarazed25

No problem installing updates here, either. I ran it with a launcher from the Plasma menu under Games/Simulations. I looked into trying an aircraft other than the standard Cessna, adding the "hangar" and looking over the inventory, but I decided I wasn't yet ready for a multi-engine airliner, so I stuck with the Cessna.

Last time I had found a setting that started with my Cessna on the runway. The airport looked deserted - no doubt closed by the FAA because too many air traffic controllers had called in sick. That was good - fewer people to kill and maim.

There's an "autostart" button in the Cessna drop-down menu, so I used that to get the engine running. Pushed in the throttle and began to move. As I picked up speed i pulled back on the yoke, and I think I was airborne. I say think because it didn't last long. The rudder did what it wanted to do, and no fiddling with the yoke would make it straighten out and stay straight. Eventually I over corrected my over corrections too many times and wound up on the ground, upside down, the engine stalling. No sign of an ambulance or fire trucks, confirming that the airport must have been closed.

The simulation seems to work as it should; the pilot, not so much...

CC: (none) => andrewsfarm

It still does not work for me.

$ fgfs --launcher --enable-terrasync

and started to develop the flight-plan but the whole system froze up suddenly, not sure exactly where but the plan was on the screen and was accepting settings before freezing up.  The only way back was by power-cycling the computer.  

It had seemed safer to use defaults for most things but I set 300 (maybe) for the cruising speed and then tried to set the altitude but it was not accepting input so next thing was to press the fly button and somewhere along the line everything froze up completely - no access to the desktop.  I had hoped this might allow me have another go at starting the engine.

Found some instructions and started again hoping the introductory flight from SanFransisco would run but it suddenly switched back to Hilo.  Released the brake 'B' then tried 's' to start the engine and opened the throttle with 'PageUp' - no joy but no more freezes.  Used the menu to exit.

Still, if it works for Thomas then I shall abandon it.

(In reply to Len Lawrence in comment #3)
This sequence of error messages appears again and again in the launch terminal:

  952.23 [ALRT]:nasal      Nasal runtime error: nil used in numeric context
  952.23 [ALRT]:nasal        at /usr/share/games/flightgear/Aircraft/c172p/Nasal/particle-effects-manager.nas, line 19
  952.23 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/physics.nas, line 147
  952.23 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 667
  952.23 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 765
  952.50 [ALRT]:nasal      Nasal runtime error: nil used in numeric context
  952.50 [ALRT]:nasal        at /usr/share/games/flightgear/Aircraft/c172p/Nasal/particle-effects-manager.nas, line 19
  952.50 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/physics.nas, line 147
  952.50 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 667
  952.50 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 765
  952.76 [ALRT]:nasal      Nasal runtime error: nil used in numeric context
  952.76 [ALRT]:nasal        at /usr/share/games/flightgear/Aircraft/c172p/Nasal/particle-effects-manager.nas, line 19
  952.76 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/physics.nas, line 147
  952.76 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 667
  952.76 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 765
  953.02 [ALRT]:nasal      Nasal runtime error: nil used in numeric context
  953.02 [ALRT]:nasal        at /usr/share/games/flightgear/Aircraft/c172p/Nasal/particle-effects-manager.nas, line 19
  953.02 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/physics.nas, line 147
  953.02 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 667
  953.02 [ALRT]:nasal        called from: /usr/share/games/flightgear/Aircraft/c172p/Nasal/c172p.nas, line 765

This may be entirely irrelevant but I thought it worth mentioning.

Tried again with the autostart command but nothing happened.  Nobody about - must all be hiding in the trees.

And the error messages keep piling up.

Hi Len,
that's a bug and this is not supposed to happen, the Cessna should work.

Would you mind to try again, erasing the local user directry: "~/.fgfs" before.
Then attach the file "fgfs.log" that you will find within that directory, I'll try to reproduce.

thank you!

@Chris in reply to comment 6:
Ran a quick test after following your instructions and chose to start from Hilo International PHTO and tried to set up a flight plan to PHNL but the interface would not allow it.  It seemed to be preset to somewhere like VietNam.  Started on autopilot and it started off at night and immediately crashed into a building.  I guess you cannot take off on autopilot.  So this is going to take a while.  My chosen route is one I am familiar with which should 
help with getting to grips with the application.

I shall attach the log when I have time.

I never tried to file a flight plan, as I never expected to get off the ground. (Actually, not being a pilot, I didn't even think about that step.)

Perhaps that is what triggered the bug Len has found.

Created attachment 15160 [details]
Log from initial run of flightgear

Started from scratch.

Started again without a flight plan using autostart.  Seems to be working OK with newbie pilot => crashes at takeoff.  Just a matter of getting used to the controls, so that part works by the look of it.

Thanks Len.
Everything looks fine I would say. Indeed, the autopilot is not for taking off nor for landing, only to fly from waypoint to waypoint and changing altitude/speed etc...

Once into an incident/accident, systems are realistically damaged and you cannot expect to start again (it is expected to see various error messages in the console in that case). So, your last tests seems fine to me!

I tried creating a flight plan, and I was able to get it to load Edwards Air Force Base as a destination, and save it, but when I ran it a second time after crashing, and attempted to load the saved plan, I couldn't see where anything was loaded.

Probably user error. Acts like it.

Anyway, it seems to work for the things I can figure out, so I'll validate.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Whiteboard: (none) => MGA9-64-OK

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2025-0093.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED