Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A.I. Role / Mech module Issue - A.I. module for mechs doesn't work and won't be removed. #3871

Open
OorthianEmissary opened this issue Aug 19, 2022 · 4 comments
Labels
Good Issue Report A issue that is properly documented and requesting to be fixed.

Comments

@OorthianEmissary
Copy link

OorthianEmissary commented Aug 19, 2022

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.

@OorthianEmissary
Copy link
Author

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.

@Trilbyspaceclone Trilbyspaceclone added the Good Issue Report A issue that is properly documented and requesting to be fixed. label Aug 19, 2022
@benj8560
Copy link
Contributor

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.

@OorthianEmissary
Copy link
Author

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.)

@Yatiyaya
Copy link
Contributor

Yatiyaya commented Oct 9, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good Issue Report A issue that is properly documented and requesting to be fixed.
Projects
None yet
Development

No branches or pull requests

4 participants