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

[H2EK] Remote Command Views #134

Open
BenSteenson opened this issue Oct 20, 2021 · 1 comment
Open

[H2EK] Remote Command Views #134

BenSteenson opened this issue Oct 20, 2021 · 1 comment
Labels
content Written content required for the wiki

Comments

@BenSteenson
Copy link

BenSteenson commented Oct 20, 2021

In Halo 2 Guerilla (2021), you can see the Remote Command View button working when you have a Sound tag active. RCV is enabled by default and creates this section of the Sound tag properties:

image

If you click "Remote Command View" in the Edit dropdown menu, this section disappears. Clicking it again makes it reappear. The option only affects the selected tag.

Clicking the buttons (except for Stop) asks for the name of a Running Instance.

The purpose is likely to play audio in a running instance of the game, possibly other types of tags like objects could have been created as well. I have not figured out if it can be used with Standalone/tagtest, and if so what the valid name for the "Running Instance" would be (when running on the same PC).

EDIT:

You can also trigger the "Target Machine" dialog by opening a .model_animation_graph tag and scrolling to animations, which has a button to Play on player.

I spent a lot of time trying to put in various addresses and names, anything that should work threw a lot of network errors looking with WireShark.

@num0005
Copy link
Collaborator

num0005 commented Oct 22, 2021

Huh so it's actually trying to connect to something in the H2 MCC release? In H2VEK the code was stubbed out and didn't try to connect to anything. I believe it was meant to connect to a dev build of the game running on an Xbox so artists could see what their work looks or sounds like on the actual target system.

@csauve csauve added the content Written content required for the wiki label Oct 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Written content required for the wiki
Development

No branches or pull requests

3 participants