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

Add Spectator Mode #190

Open
Cheeseness opened this issue Mar 2, 2014 · 3 comments
Open

Add Spectator Mode #190

Cheeseness opened this issue Mar 2, 2014 · 3 comments

Comments

@Cheeseness
Copy link
Contributor

We'd like to allow late joiners to be able to watch an in-progress game.

@Cheeseness
Copy link
Contributor Author

Following some IRC discussion, it looks like we're considering some larger scale changes for spectator cameras than seem necessary.

I'm note sure that we need to bother with syncing spectator or player camera locations across the network (unless we want to make spectators visible to players/each other, but is there much value in that?)

My suggestion would be to allow spectators to control a freely moving camera with no synchronisation. It looks like this could be implemented without any significant networking changes.

If we did want to allow a spectator to follow a player, we could position the camera relative to already synced cart position/orientation and use HOTween to interpolate camera movement client side (we're already using it for other stuff, so we can quickly implement using that and see what kind of impact it has). We'll end up with a little camera lag, but that might end up looking pretty neat anyway.

@thegsm
Copy link
Contributor

thegsm commented Mar 3, 2014

I actually think this will make some things simpler for spectator view to sync it and the change may not prove to be that significant.
Anyway, at this stage I recommend delaying spectator view altogether until we have closed the other elements related to networking (but keep that in mind).

@Cheeseness
Copy link
Contributor Author

I actually think this will make some things simpler for spectator view to sync it

Can you expand some more on the value of camera/spectator positions here? Involving network synchronisation of that seems like it would make things less simple than not doing so. If we're already passing cart position orientation and orientation around the network, that's all we need for knowing where the cart's camera position is (that's what the cart's camera is positioned relative to in the first place).

Anyway, at this stage I recommend delaying spectator view altogether until we have closed the other elements related to networking (but keep that in mind).

Are you referring to a code tidy/refactoring of the networking system structure? If so, I think I agree. It'd be nicer to clean things up before potentially clouding them up more.

Right now, having unjoinable in-progress matches is costing us a little momentum and enthusiasm from people who're interested in testing though, and that's worth considering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants