Entering a mech while in a holopad as an AI causes it to de-tach your camera.

[TravisAngeI]

Exploit Reports

• I confirm this issue is not an exploit. (Required)

BYOND Version

515.1647

Issue Description

When in a holopad as an AI, entering an AI-beaconed mech exosuit causes the camera to de-tach from the mech, leaving the mech seemingly controlled by you, but your camera is detached and you can't move the mech.

What did you expect to happen?

To be able to seamlessly transfer from the holopad to the mech.

What happened instead?

My camera detached from the mech, and I had to use the eject button on my HUD to fix it.

Why is this bad/What are the consequences?

AIs should be able to seamlessly enter mechs without wonky camera stuff.

Steps to reproduce the issue.

1. Be AI
2. Have mech with AI-control beacon
3. Enter a holopad
4. Try to enter mech
5. Move around
6. Issue happens

When did the problem start happening?

If I had to guess, this is probably caused by #25078

Extra information

No response

Relevant log output/runtime error

[TravisAngeI]

Video for example. Won't let me attach files, so I had to get it in a link.

https://gyazo.com/e4c774d0d3e205b83e21f2f9fbb520db

[TravisAngeI]

You can also enter holopads while inside the mech, but this has really no issues and is more of an unintended feature.

[TravisAngeI]

Okay, yeah. There's quite a few issues related to AIs and mechs recently. Will list them out here.

If you try to double-click anywhere on your screen while in a mech, it moves your camera and unsticks you from the mech, causing the same issue of having to eject and re-enter.

Ejecting from a mech now sends you back to where you entered the mech, rather than where the mech actually is.

Also, while in a holopad, you can hear both normal and Relayed Speech, which shouldn't happen. (see image below)