I often use the Script AI Manager along with Replay Mode to record paths for vehicles while creating scenarios for Youtube car crash compilations and have encountered a number of problems while doing so, including the software simply being disorganized and hard to navigate. My main issues are listed below: 1) The paths that the vehicles follow are inconsistent with the original route you recorded, loosely following your path and having difficulty maintaining the same speeds, braking at the same times, and recreating the same angles of steering which may have caused the vehicle to lose traction/tip over. Suggested Solution: Create higher number of nodes while recording a path using the Script AI Manager; also, a more realistic AI. 2) The Script AI manager does not record electronics and other components (horns, parking brakes). Suggested Solution: Record electronics and other components. 3) THERE IS NO AUTOSAVE. The Script AI Manager is almost always as a means of content creation and I therefore think an autosave, or at least a simplified save system which is contained within the game should be created (similar to replays). This is in replacement of one which creates individual files in the desktop system (which are very difficult to load and often freeze that game). There have been multiple occasions where my Beam.NG has crashed and hours of work perfecting the paths involved in my scenario were lost all as a result of, first of all: the volume of aspect present in the game which can lead to screen freezes and crashes (replay mode bugs, bugs within the Script AI Manager; specifically with the 2X speed feature, lack of optimization in general), or the simple lack of autosave. Suggested Solution: Create and autosave or simplified save system which keeps files readily available within the Beam.NG application.
