![]() Howto:Add new features to the route manager system.Autopilot PID controller tuning resources.If in doubt, please get in touch via the mailing list or the forum first. įor details on exposing these C++ systems to Nasal, please refer to Nasal/CppBind. Technically, this is also the correct approach, as it allows us to easily reuse existing code that is known to be stable and working correctly. For example, this would enable Scripted AI Objects to use full FDM implementations and/or built-in route manager systems. The FlightGear/ SimGear code base already contains fairly generic and efficient systems and helpers, implemented in C++, that merely need to be better generalized and exposed to Nasal so that they can be used elsewhere. It will also help to unify duplicated code. This is primarily to help reduce Nasal overhead (especially GC overhead). Sent from sourceforge.Note Whenever possible, please refrain from modeling complex systems, like an FDM, autopilot or Route Manager with Nasal. The a/c loaded is the Citation X+ from Patten's Hangar. Screenshot, together with the ILS28 approach (relevant XML snippet only). Are you able to test the same issue withįlightgear freezes and uses 100% CPU time as soon as i click 'Activate' Of course 2 minutes after hitting 'Send' i discovered git tags. To unsubscribe from further messages, please visit Sent from because you indicated interest in flightgear_next/bin/fgfs -launcher Let me know if any further information is needed. SIGPIPE nostop' -ex r -ex 'thread apply all bt' -ex where -args 'handle SIGCONT nostop' -ex 'handle SIGHUP nostop nopass' -ex 'handle Gdb cmd line used: gdb -q -n -batch -ex 'handle SIGTSTP nostop' -ex home/sfr/src/fgfs/flightgear/src/Autopilot/route_mgr.cxx:866: route home/sfr/flightgear/share/fgdata/Nasal/route_manager.nas:207: flightplan "/home/sfr/fgfs_addons/FMS/Airports/E/D/T/" home/sfr/src/fgfs/flightgear/src/Airports/airport.cxx:591: EDTY: loading home/sfr/flightgear/share/fgdata/Nasal/route_manager.nas:126: saw active home/sfr/flightgear/share/fgdata/Nasal/route_manager.nas:36: saw Loaded is the Citation X+ from Patten's Hangar. Together with the ILS28 approach (relevant XML snippet only). The flightplan is shown in the attached screenshot, next_routemanager_edds_edty_28_ils28_stuck_on_activate.pngįlightgear freezes and uses 100% CPU time as soon as i click 'Activate' in. ![]() Are you able to test the same issue withĬreated: Sat 02:35 PM UTC by Stefan Frank On Tue, at 9:45 AM James Turner Stefan, will take a look. Your branch is up to date with cat version Has 'version' just not git checkout release/2020.3 But which branch should I use? release/2020.3.9 does not existĪnd release/2020.3 has version set to 2020.3.7. Let me know if any further information is needed. Gdb cmd line used: gdb -q -n -batch -ex 'handle SIGTSTP nostop' -ex 'handle SIGCONT nostop' -ex 'handle SIGHUP nostop nopass' -ex 'handle SIGPIPE nostop' -ex r -ex 'thread apply all bt' -ex where -args. I've also attached the gdb log (taken after killing the fgfs process). home/sfr/flightgear/share/fgdata/Nasal/route_manager.nas:36: saw departure changedĦ8.48 :nasal /home/sfr/flightgear/share/fgdata/Nasal/route_manager.nas:126: saw active flightplan cleared, deactivatingħ9.55 :general /home/sfr/src/fgfs/flightgear/src/Airports/airport.cxx:591: EDTY: loading procedures from Path "/home/sfr/fgfs_addons/FMS/Airports/E/D/T/"ġ86.37 :nasal /home/sfr/flightgear/share/fgdata/Nasal/route_manager.nas:207: flightplan activated, default GPS to LEG modeġ86.37 :autopilot /home/sfr/src/fgfs/flightgear/src/Autopilot/route_mgr.cxx:866: route manager, current-wp is now 0 The flightplan is shown in the attached screenshot, together with the ILS28 approach (relevant XML snippet only). Flightgear freezes and uses 100% CPU time as soon as i click 'Activate' in the Route Manager GUI. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |