Flightgear is a leaf group of packages. Reproducible: Steps to Reproduce:
Keywords: (none) => BackportAssignee: bugsquad => qa-bugs
Packages to install to test : - simgear - flightgear-data - flightgear To test, only lauch it with the command-line : fgfs.
Status: NEW => ASSIGNED
Source RPM: simgear flightgear flightgear-data => simgear flightgear flightgear-data fgrun
Sorry, I forgot to mention the GUI launcher : fgrun. Complete list of SRPMS : fgrun-3.2.0-1.mga4 flightgear-3.2.0-1.mga4 flightgear-data-3.2.0-1.mga4 simgear-3.2.0-1.mga4 RPMS list is the same, with simgear-devel added.
Before I launch into flying ( no pun intended :)) this package a question. On Mageia M4 would you expect flightgear to use a common USB Joystick and or something like: http://www.saitek.com/uk/prod/yoke.html Thanks
CC: (none) => wilcal.int
Yes, you just have to activate it in the menu.
In VirtualBox, M4, KDE, 64-bit Package(s) under test: fgrun flightgear flightgear-data simgear default install of fgrun, flightgear, flightgear-data & simgear [root@localhost wilcal]# urpmi fgrun Package fgrun-1.7.0-5.mga4.x86_64 is already installed [root@localhost wilcal]# urpmi flightgear Package flightgear-2.12.1-1.mga4.x86_64 is already installed [root@localhost wilcal]# urpmi flightgear-data Package flightgear-data-2.12.1-1.mga4.noarch is already installed [root@localhost wilcal]# urpmi simgear Package simgear-2.12.1-1.mga4.x86_64 is already install Gotta Thrustmaster T.16000 to play with this thing. Was able to take off from San Francisco airport and land without crashing. The fgrun thing launches but is a complete mystery to me as to how to work with this app. install fgrun, flightgear, flightgear-data & simgear from backports_testing [root@localhost wilcal]# urpmi fgrun Package fgrun-3.2.0-1.mga4.x86_64 is already installed [root@localhost wilcal]# urpmi flightgear Package flightgear-3.2.0-1.mga4.x86_64 is already installed [root@localhost wilcal]# urpmi flightgear-data Package flightgear-data-3.2.0-1.mga4.noarch is already installed [root@localhost wilcal]# urpmi simgear Package simgear-3.2.0-1.mga4.x86_64 is already installed Was able to take off from San Francisco airport again and land without crashing, well maybe once or twice. The fgrun thing launches but is a complete mystery to me as to how to work with this app. I've attached a screenshot of the fgrun window. What's next? Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver Thrustmaster T.16000 joystick
Created attachment 5683 [details] fgrun screenshot
Wow you have some skill William :-) I've played around a bit with flightgear with an earlier version, but I found the learning curve was quite steep for newcomers.
CC: (none) => remi
(In reply to Rémi Verschelde from comment #7) > but I found the learning curve was quite steep for newcomers. Ya, this is a very complex game for sure. I've read that pros use this to practice. Another factor here is you really need a high performance platform to run it on so I'm using my video editing machine and real hardware. I got the fgrun thing to work, kinda, once then it keeps presenting the screen shot attached. So I suspect José will be able to coach us on that works. Clearly 3.2.0-1 is way better then the one we're presently using, 1.7.0-5. Also you really need a very good Joystick or Yoke to make this work at all. Both 1.7.0-5 & 3.2.0-1, as well as Mageia, recognized the Thrustmaster T.16000 joystick. All that even uses the many buttons on the stick for various functions, without a special setup. Now if I've got a year or two to waste maybe I'll get to understand about half this thing. :-))
Looking at your screenshot, there seems indeed to be an issue with fgrun. Here on Mageia 5, all fields are prefilled with the correct value (/usr/bin/fgfs for the binary, /usr/share/games/flightgear for the data, etc.).
OK after tinkering again with this again I've come to the conclusion that most, if not all, of the errors I saw here were pilot errors. No pun intended. I have been successful to install the 3.2.0-1 version on M4.1 and that with a previously installed version 1.7.0-5. Note that launching fgfs ( FlightGear ) creates the .fgfs directory in the user space which contains its configuration files. Launching fgrun ( FlightGear Launch Control ) initially creates directory .fltk which contains it's own configuration files then it launches fgfs that creates the .fgfs directory. If you launch FlightGear ( fgfs ) before fgrun then that seems to change settings enough such that fgrun can't deal with it and does not run properly. Erasing both the .fltk and .fgfs directories resets everything and you can once again start anew with fgrun. I'm of a mind to validate this backport and will do so in 24-hours if José & Rémi are happy with what I have found. A side note here this is the first time I've used a Joystick with Mageia and I was quite impressed with how it was handled. Seems that FlightGear easily picked it up and used it. Also the KDE System Settings -> Input Devices -> Joystick settings work wonderfully well including the calibration mode.
I did in fact spin up a seperate M5 install and found that to work equally well. In VirtualBox, M5, KDE, 64-bit Package(s) under test: fgrun flightgear flightgear-data simgear default install of fgrun, flightgear, flightgear-data & simgear [root@localhost wilcal]# urpmi fgrun Package fgrun-3.2.0-1.mga5.x86_64 is already installed [root@localhost wilcal]# urpmi flightgear Package flightgear-3.2.0-1.mga5.x86_64 is already installed [root@localhost wilcal]# urpmi flightgear-data Package flightgear-data-3.2.0-1.mga5.noarch is already installed [root@localhost wilcal]# urpmi simgear Package simgear-3.2.0-1.mga5.x86_64 is already installed All functions seem to work properly. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver Thrustmaster T.16000 joystick
In VirtualBox, M4, KDE, 32-bit Package(s) under test: fgrun flightgear flightgear-data simgear default install of fgrun, flightgear, flightgear-data & simgear [root@localhost wilcal]# urpmi fgrun Package fgrun-1.7.0-5.mga4.i586 is already installed [root@localhost wilcal]# urpmi flightgear Package flightgear-2.12.1-1.mga4.i586 is already installed [root@localhost wilcal]# urpmi flightgear-data Package flightgear-data-2.12.1-1.mga4.noarch is already installed [root@localhost wilcal]# urpmi simgear Package simgear-2.12.1-1.mga4.i586 is already installed Launch with fgrun, all basic functions seem to work properly. install fgrun, flightgear, flightgear-data & simgear from backports_testing [root@localhost wilcal]# urpmi fgrun Package fgrun-3.2.0-1.mga4.i586 is already installed [root@localhost wilcal]# urpmi flightgear Package flightgear-3.2.0-1.mga4.i586 is already installed [root@localhost wilcal]# urpmi flightgear-data Package flightgear-data-3.2.0-1.mga4.noarch is already installed [root@localhost wilcal]# urpmi simgear Package simgear-3.2.0-1.mga4.i586 is already installed Launch with fgrun, all basic functions seem to work properly. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver Thrustmaster T.16000 joystick
This thing's addictive :-) For me this backport works fine. Testing complete for mga4 32-bit & 64-bit Validating the backport. Could someone from the sysadmin team push this to updates. Thanks
CC: (none) => sysadmin-bugsKeywords: (none) => validated_updateWhiteboard: (none) => MGA4-32-OK MGA4-64-OK
Correction: push this to backports
We can't at the moment as sysadmins need to complete some changes first. We'll use a separate keyword for these too IIRC.
Keywords: validated_update => (none)
Adding feedback marker until we can progress
Whiteboard: MGA4-32-OK MGA4-64-OK => feedback MGA4-32-OK MGA4-64-OK
# /root/tmp/mgatools-new/mga-move-pkg --sync --backport 4/core/fgrun-3.2.0-1.mga4.src.rpm --backport 4/core/flightgear-3.2.0-1.mga4.src.rpm --backport 4/core/flightgear-data-3.2.0-1.mga4.src.rpm --backport 4/core/simgear-3.2.0-1.mga4.src.rpm The following SRPMs (and their corresponding binaries) will be moved: - fgrun-3.2.0-1.mga4.src.rpm - flightgear-3.2.0-1.mga4.src.rpm - flightgear-data-3.2.0-1.mga4.src.rpm - simgear-3.2.0-1.mga4.src.rpm Are you sure? [Y/n] Moving binary and source rpms: - i586: fgrun-3.2.0-1.mga4.i586.rpm fgrun-debuginfo-3.2.0-1.mga4.i586.rpm - x86_64: fgrun-3.2.0-1.mga4.x86_64.rpm fgrun-debuginfo-3.2.0-1.mga4.x86_64.rpm - source: fgrun-3.2.0-1.mga4.src.rpm Moving binary and source rpms: - i586: flightgear-3.2.0-1.mga4.i586.rpm flightgear-debuginfo-3.2.0-1.mga4.i586.rpm - x86_64: flightgear-3.2.0-1.mga4.x86_64.rpm flightgear-debuginfo-3.2.0-1.mga4.x86_64.rpm - source: flightgear-3.2.0-1.mga4.src.rpm Moving binary and source rpms: - i586: flightgear-data-3.2.0-1.mga4.noarch.rpm - x86_64: flightgear-data-3.2.0-1.mga4.noarch.rpm - source: flightgear-data-3.2.0-1.mga4.src.rpm Moving binary and source rpms: - i586: simgear-3.2.0-1.mga4.i586.rpm simgear-devel-3.2.0-1.mga4.i586.rpm simgear-debuginfo-3.2.0-1.mga4.i586.rpm - x86_64: simgear-3.2.0-1.mga4.x86_64.rpm simgear-devel-3.2.0-1.mga4.x86_64.rpm simgear-debuginfo-3.2.0-1.mga4.x86_64.rpm - source: simgear-3.2.0-1.mga4.src.rpm
Status: ASSIGNED => RESOLVEDCC: (none) => pterjanResolution: (none) => FIXED