You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Desc: The A.I. module that the roboticist can make in the exosuit fabricator, which, when installed into a mech, should give the A.I. the ability to control the mech/exosuit in the same way as a remote drone, does currently not work.
Clicking on the Odysseus simply opens and closes the mech hatch (changes between occupied and unoccupied sprite), but doesn't allow for movement of the Odysseus or usage of its abilities. The A.I. camera focus simply locked on to the Odysseus, and would only detach from the Odysseus, when the "Tab"-button was pressed twice. The camera wouldn't change focus when prompted to by other means. Furthermore, when the roboticist entered and tried to eject the module, it wouldn't eject either, leaving it bricked inside the Odysseus.
Occurrence: Only tested and observed once for the Odysseus.
Planned future testing: To be tested for the Ripley, Ivan and if possible the Gygax/Durand, if not disruptive to the shift.
The text was updated successfully, but these errors were encountered:
How to reproduce:
Have a mech, print A.I. mech module, insert into mech, test with A. I. for wanted functionality, and test to see if the A.I. module will eject from the mech.
this has been a issue for a long time. You wont have any luck trying the other mechs it's just a broken unloved pile of code sadly.
if I recall it's suppose less like a drone but more like a machine your controlling though cams only functioning on said cams.
Without knowing .dm code very well, could adoption of the A.I. drone control code be a possible solution? The A.I. being able to control the mech, the mech giving camera feed, and the icons for opening op control panels for the mech and all that available to the A.I., while it's controlling the mech?
(sorry if this is incoherrent, it was written in a hurry. Will format later for easier readability.)
The reason this entire issue exists is because Baystation (Which eris is a downstream of) mecha code is utterly fucked, to the point eris just pulled it all out and threw it away.
Bay doesn't even touch their own mecha code
Blackbox testing of the A.I. mech module.
Desc: The A.I. module that the roboticist can make in the exosuit fabricator, which, when installed into a mech, should give the A.I. the ability to control the mech/exosuit in the same way as a remote drone, does currently not work.
Clicking on the Odysseus simply opens and closes the mech hatch (changes between occupied and unoccupied sprite), but doesn't allow for movement of the Odysseus or usage of its abilities. The A.I. camera focus simply locked on to the Odysseus, and would only detach from the Odysseus, when the "Tab"-button was pressed twice. The camera wouldn't change focus when prompted to by other means. Furthermore, when the roboticist entered and tried to eject the module, it wouldn't eject either, leaving it bricked inside the Odysseus.
Occurrence: Only tested and observed once for the Odysseus.
Planned future testing: To be tested for the Ripley, Ivan and if possible the Gygax/Durand, if not disruptive to the shift.
The text was updated successfully, but these errors were encountered: