VR Expansion Plugin

[mordentral]

@ctpeepee

Hi again. I previously had been using the button actor from the template on a map and noticed that some times the button could become out of sync between client/server. I’d assumed at the time it might not be configured properly to work in multiplayer as was only example. Have come back to it now and working with my own actor that has a VRButton component I have the same issue. If you happen to push the button in a certain way (quite easy to replicate if you just press the button lots of times from different angles) the hit can be registered on the server but not the client (and vice versa). Can acheive it with a vr pawn as well as an fps one.

If I authority guard the OnButtonStateChanged event in blueprint I can ensure my code (changing colour of button eg) is always synced which is fine for a toggle return button but as the internal bButtonState is out of sync the toggle stay button doesn’t work correctly. It seems to me its because the collision can sometimes only be considered a hit on either the server or client and as bButtonState is only replicated initially it can become out of sync. Or I’m doing something wrong of course!

You should never depend on collision being 1:1 on server / client (network data is compressed and rounded off to save bandwidth), choose one and run your events off of it. As far as the button syncing, currently it would be up to your to sync the button state when your chosen authority detects the change, that actually goes for all of the interactibles, I leave it up to the end user to choose a sync method, whether to automate had been something I haven’t made a solid choice on yet, its been at the back of my list to think about for some time now.

You can SetButtonState to sync if you need too, normally for it to be perfect you actually wouldn’t want anything but your chosen authority even running the button logic. So usually would mean that you would want it server auth and not toggle-able on clients.

If you want it server auth a decently quick fix would be to override the IsValidOverlap function and return false if not on an authority connection, and return parent if it is. Then sync button state when it changes and set the button to replicate position (or not).

Edit I could see a use case for a CanSetState function or boolean that would allow the button to follow but not state change locally though.

@ctpeepee

Was just searching in thread for an answer to something else and came across the answer in post. Sure enough the level I had the problem I was using a scene capture, and after disabling it the problem went away. Any idea why that is? I had noticed before that when the static mesh components weren’t late updating correctly for me, in the scene capture things were locked together correctly.

I remember that being brought up recently as a newish issue, but I haven’t actually had a scene capture do it for me.