Add explicit CMake output when Sentry.io is enabled/disabled
Fix Qt6 menu models for the Flight planner
Fix Qt6 menu models for the Flight planner
Add doxygen comments for StateMachine class
Fix ATC takeoff clearance messaging appearing at splash screen (#3068)
Update submodules to 'v2024.1' tag
Fix windows installer failure due to missing COPYING
Cleanup top-level directory documentation, convert to Markdown
Remove SimpleMarkdown
Remove f_parse_markdown()
Add bug report issue template
Update submodules to the v2024.1.1-rc4 tag
Remove deprecated documentation browser (fixes #20)
Make .gitignore not ignore .gitlab
Speculative fix for #9
Hey @octal450, do you still want these changes merged? If so, I think the easiest course of action would be to create a new Merge Request over on GitLab: https://gitlab.com/flightgear/fgdata.
Add bug report template
Replace *_list defs with explicit vector type
cleanup: Remove ancient/dead tests.
@lukas25 Just a heads up that we have migrated to GitLab, so all further discussion of tickets will happen there. I have replied to your issue over on GitLab and you can see it here: https://gitlab.com/flightgear/flightgear/-/issues/2955
Cleanup: Remove 20 year old Perl scripts
Cleanup: Remove very old Java example code
TICKETS HAVE BEEN MOVED TO GITLAB
[Launcher] Runway/Parking dropdowns empty until another dropdown is selected
Option to connect to Swift disabled in 2024.1
Tested with the 2024.1.1-rc3 AppImage and it's all working as expected now, woohoo.
Hey Fernando, I didn't reset the sim with Shift+ESC at any point.
I'm a complete Docker noob, I literraly run the commands in the Dockerfile comments and it's worked. I'm hosting Docker on macOS but I doubt that makes any difference? Hmm, the host OS shouldn't make a difference. I was once very in-tune with Docker a number of years back but need to clear the cobwebs in that part of my brain in order to sink my teeth into it. There's no doubt been been some changes in Docker conventions and best practices since the last time I did any real devops work. Let me know...
I would be happy to try except I'm actually blocked from building it due to this error in the Docker build (on fgmeta next). CMake Error: The source directory "/c-ares" is a file, not a directory. Specify --help for usage, or press the help button on the CMake GUI. Which is hurting my brain a little bit because the container works in GitLab CI, and I didn't touch c-ares at all. So there could be a mismatch between whats in git vs. whats pushed to the registry or I simply have a knowledge gap in terms...
Ah okay, perhaps I'm misunderstanding the workflow on fgmeta. I figured it would be best to merge to next and then we'd cherry-pick to release/2024.1 as this issue would presumably be present on next.
Ah okay, perhaps I'm misunderstanding the workflow on fgmeta. I figured it would be best to merge to next and then we'd herry-pick to release/2024.1 as this issue would presumably be present on next.
Ah okay, perhaps I'm misunderstanding the workflow on fgmeta. I figured it would be best to merge to next and then cherry-pick to release/2024.1 as this issue would presumably be present on next.
@jmturner PR is up on fgmeta: https://sourceforge.net/p/flightgear/fgmeta/merge-requests/47/.
Fix #2944 (add libevent-dev to Docker CI)
Add libevent-dev to Dockerfile
I'll take a look!
I can reproduce this using the 2024.1 rc2 AppImage. Reproduction Steps: Start FlightGear 2024.1 with any aircraft at any location Click Multiplayer from the menu bar Observe that the option "Swift Connection" is greyed out and disabled. From what I recall Swift support requires something like libevent or libdus, is it possible we aren't bundling that library with the AppImage, and it's another one of 'those' AppImage bugs, @jmturner?
Option to connect to Swift disabled in 2024.1
I can reproduce this using the 2024.1 rc2 AppImage. From what I recall Swift support requires something like libevent or libdus, is it possible we aren't bundling that library with the AppImage, and it's another one of 'those' AppImage bugs, @jmturner?
Graphical artifact (white rectangle) appearing on-screen in 2024.1
As well, it's worth noting that the white rectangle in the top-right screen is unrelated to this bug report. The user that passed along the screenshot happened to be lucky enough to capture two bugs at once. It has already been reported as #2943.
I haven't been able to determine how to reproduce it, but I have come across this bug (see the attached screenshot, disregard the glitched out scrollbar, I'm making a ticket for that issue shortly). It appears to be a new bug introduced in 2024.1.
This has been reproduced by myself and one other user. Both on Linux, but with different integrated graphics cards (one was Intel, the other AMD). As well, here is the .gpx route for ease of reproduction. You can also reproduce by simply adding several waypoints too.
Scrollbar in Route Manager broken in 2024.1
OpenXR is available through the official Ubuntu repositories as libopenxr-dev. After I installed it CMake picked it up and FG built with VR support. Unfortunately trying to setup a Quest 3 to work with Linux is a bit clunky so I can't speak to whether it works with the version of libopenxr provided by apt , but it certainly builds.
What platform are you using? Ubuntu 22.04 LTS + 2024.1.1 rc2. In principle the CI builds for 2024.1 and next should have working VR, but I think we might be missing some SDK pieces which allow osgXR to build. This is the build output for flightgear/flightgear for the commit that I created the v2024.1.1-rc2 tag (and then the release) from. Looks like it can't find osgXR: https://gitlab.com/flightgear/flightgear/-/jobs/8453467975#L86
Hi @portree_kid, I'm just clearing out old tickets and was wondering if this was something you ever fixed? Thanks!
Canvas setPixel() not working with DDS cache enabled
Launcher: readable state names not sync with auto selection logic.
Hide or clarify "View > VR Options" menu item on 2024.1 release builds
FlightGear freezes when holding keys that use Canvas tooltips
I wasn't able to reproduce with 2020.3.19, but I did get a crash on the 2024.1.1 RC 2 AppImage (Ubuntu 24.04). I actually wasn't able to get the release/2024.1 branch running at the moment interestingly enough, so I couldn't debug the issue because I'm getting this on startup: 13.24 [ALRT]:general Cannot find texture "Textures/buildings-lightmap.png 13.24 [ALRT]:general Cannot find texture "Textures/buildings.png 13.24 [ALRT]:general Cannot find texture "Textures/buildings-lightmap.png 13.24 [ALRT]:general...
I wasn't able to reproduce with 2020.3.19, but I did get a crash on the 2024.1.1 RC 2 AppImage (Ubuntu 24.04). I actually wasn't able to get the release/2024.1 branch running at the moment interestingly enough, so I couldn't debug the issue because I'm getting this on startup: 14.54 [WARN]:osg Cannot assign between Uniform types double and float 14.54 [WARN]:osg Cannot assign between Uniform types double and float 14.54 [WARN]:osg Cannot assign between Uniform types double and float 14.54 [WARN]:osg...
Crash enroute from EPWR -> LKPD: free(): invalid next size (normal)
Crash enroute from EPWR -> LKPD: free(): invalid next size (normal)
Hi @r-harrison, any chance you would be able to give an update on the status of this issue? Thanks! Joshua
[Request] Use Screenshot function from Phi instead of SimGear.
Hi @megaf, any chance you are able to reproduce this issue on the release/2024.1 branch?
Launcher fails to load using AppImage for 2024.1
Patches to add 'Custom' category to poi.dat and Marker Pins
Launcher fails to load using AppImage for 2024.1
Launcher fails to load using AppImage for 2024.1
Hi @antgel, are you still experiencing this issue? If so, please try the AppImage for the 2024.1.1 RC 1 and and see if it works? https://gitlab.com/flightgear/fgmeta/-/releases/v2024.1.1-rc1. Hopefully we can get this fixed for the upcoming release next month. Cheers, Joshua
Hi Stuart, I've actually noticed since that the issue is broader than just damage. In the Twin Otter for example, the sound of the doors closing is triggered every-time the cockpit view is selected. I've noticed engine start-up sounds triggering every-time the cockpit view is selected on the MD500 as well. With the Piper Cub, there's just a creaking sound everytime you switch to the cockpit view, and with the Cessna 172 you hear the engine start sound everytime you select a 'far away' view (i.e Tower...
Property access reportedly 3-4x slower in 2024.1 than in 2020.3
Hey @jmturner, we have two patches available to solve this ticket, do you have any preference on which one to go with? I can go ahead and make the MR if need be.
Thanks @shfsn, it is much appreciated :)
Hi @frougon, I'll let merspeiler and others speak to whether or not the bug has been verified. Assigning the ticket to the 2024.1 milestone is not an indication that the bug is verified in the release/2024.1 branch, it's to indicate that addressing this issue should be on the roadmap and be fixed as part of the 2024.1 milestone. If indeed it has already been fixed (which it is by the sounds of it) we can check it off our list once there's confirmation :) Cheers, Joshua
Taxiway markings make ground transparent at Terrain Quality level 'Low"
Hello, I know it's been quite a long time since you reported this issue, but would you be able to provide any information as to whether you're still experiencing it on newer builds of FlightGear? Thanks :)
FlightGear sends constant value of "hground"
Sounds like this issue has been resolved (hurray), so I think we are safe to mark this as closed :)
JSBSim pipe output to log
The fix on the JSBSim side has been merged, so I will mark this as closed :)
YASim PistonEngine Correction for EGT calculation
NasalSysTests::testCommands segmentation fault
FPNasalTests::testBasic and CanvasTests::testCanvasBasic segmentation fault without X11
Unable to use FG on PC with Widescreen monitor plugged in.
Hi Alex, based on the forum thread it looks like you were able to get this issue resolved - excellent! I'll mark this ticket as closed but feel free to get in touch if you experience this issue again in the future.
Hey @jmturner, did anything come of this afterwards? Is it something we may want to look at including in the 2024.1 release?
VSI instrument: excessive FPM at init and oscillation on ground
[Request] Add some metadata to saved jpg screenshots.
Hi Alex, would you be able to try one of the latest builds and confirm if the issue is still present? Thanks!
I can also confirm it works on therelease/2024.1 branch, it prints "f1" as expected. Should we update the status as Fixed? I would assume that because the 2024.1 release is right around the corner it is unlikely for this fix to be backported to 2020.3.x.
No font size setting
Building flightgear with LTO fails due to ODR violation
Multiplayer bug ?!
simgear 811f06 Add SPDX headers drops #ifndef
35 Buttons for Joysticks
Hi @alexey256, I know it's been quite some time since you started experiencing this issue. Have you been able to try one of the newer releases of FlightGear to see if the issue persists?
AI Wingman Issue
Hi @jmturner, just checking in to see if there was any update on this and whether we should include it in the 2024.1 release or hold off.
Patches to add 'Custom' category to poi.dat and Marker Pins
Nasal: See if plane is near runway
MirrorPropertyTreeWebsocket - Add commands addListener, set, get, and exec
Select Airport: UI bugs (patch available)
ATIS: weird chirping sound
I can reproduce this as well, on release/2024.1. I have attached a short video clip as well.
SIGSEGV std::_Rb_tree_insert_and_rebalance
SIGSEGV osgDB::SharedStateManager::share(osg::Node*, OpenThreads::Mutex*)