There are a few bugs that cause a CTD when using the script editor: 1. There
is a bug in the script editor that causes a CTD when you add or edit text in
‘ImagePath’. This happens on the ‘MissionBushTrip’ object and the ‘Objective’
child object, but not on the ‘Leg’ child object.
Doesn't cause a crash
Happens 100% of the time Steps to reproduce: Create mission project, open
script editor, add MissionBushTrip node, try to type in the ‘ImagePath’ box,
it will crash. This crash also happens when you try to edit this text, after
you added it manually in the .xml file. FS version: 220.127.116.11 2. Adding
certain nodes causes a CTD. Nodes that have this problem: Camera,
RequestTeleportAction, GateRacePoint, PylonRacePoint, and Flock. Happens 100%
of the time Steps to reproduce: Create mission project, open script editor,
add any of the mentioned nodes 3. Random crashes. Sometimes it crashes before
adding a new node or when deleting a node.
Hello @Mr_LiamT , Thank you for this very well written report and for your
Dump files, We are investigating this issue Regards, Boris
Hello @Mr_LiamT , We have investigated but unfortunately the script editor
should not be used at the moment. We plan to remove it temporarily from dev
mode as it is not usable in its current state. Regards, Boris
Hi Boris, I think it would be best to keep the script editor accessible, since
it is still really useful to have a visual overview of the mission script.
Editing the .xml file directly is much more convoluted. Right now I use the
script editor for most of the process, and when I come across a limitation or
ctd, I manually edit that part of the .xml and carry on in the script editor.
The script editor makes creating
and editing complex missions much easier, even if it isn’t fully functional
and bug-free. PS: I also found some other limitations of the script editor
that I will post on devsupport. You can use that for when the team has time to
improve the script editor.