FGAddon Illuminator GUI dialogs not working
I confirm that issues 2 only happen when using Xwayland. I can't reproduce issue 3.
I confirm that issues 2 and 3 only happen when using Xwayland
Fix build issue (gdal path)
Ok, will try and report... thanks!
Fix typo (stairs-300.xml referenced as Stairs-300.xml)
Fix Pushback warning light position
I'm getting this crash also with 777-300ER above north-east of Canada (I was flying from EGLL to KLAX). I also enabled ARPT view on NAV display at maximum range. Don't know if it can be related... I also have Navigraph SID and STARS data installed
Still getting this problem... Does anyone is going to fix this? I read the code in order to fix it by myself but unfortunately this task is above my knowledge. Is there any workaround in order to bypass FG crash?
Again... After 8:07 hours into flight.... :-(
Again... After 8:07 hours in flight.... :-(
Again... After 8:07 hours of flight.... :-(
FG Crash - Illegal character '7' at start of leaf of property path:/airports[0]/7622
typo fix (for case sensitive systems)
typo fix (jsbsim output's in thrust_lb property instead of thrust-lbs)
same problem for me here...
Thanks for your help... Deleting ~/.fgfs/autosave_*.xml solved my problems... anyway my OS is: Fedora 30 x86_64 and AFAIK, the terminal output didn't show any Nasal errors.
fgdata: $ git log commit 24553feb57254155520ce587cefd333a64f275da (HEAD -> next, origin/next) flightgear: $ git log commit 6ce33fcb5c483254be1c05a13a27dfa33dca731e (HEAD -> next, origin/next-gen/vulkan, origin/next, origin/HEAD)
view manager not working as expected
Hi Trevor, nice to here that you are back to this project!
Pushback warning lights position fix
can't read apt.dat.gz (new format?) - FG 3.0