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

How To replicate the runtimemesh on server #283

Open
whcmn opened this issue Apr 23, 2024 · 1 comment
Open

How To replicate the runtimemesh on server #283

whcmn opened this issue Apr 23, 2024 · 1 comment

Comments

@whcmn
Copy link

whcmn commented Apr 23, 2024

We created a runtimemesh actor with runtimemeshcomponentstatic, and createsectionfromcomponent. But we can't spawn runtimemesh actor on client side unless we do the createsectionfromcomponent at BeginPlay stage.
we want to konw how to createsectionfromcomponent only once on server then replicate the actor to the client.
Can you kindly adivse.
Thank you very much!

@KamikazeXeX
Copy link
Contributor

We created a runtimemesh actor with runtimemeshcomponentstatic, and createsectionfromcomponent. But we can't spawn runtimemesh actor on client side unless we do the createsectionfromcomponent at BeginPlay stage. we want to konw how to createsectionfromcomponent only once on server then replicate the actor to the client. Can you kindly adivse. Thank you very much!

I'm not officially affiliated with RMC, but I am using it exclusively in multiplayer, currently RMC does not support direct replication, I.E you cannot create geometry on the server and it automatically get pushed out to clients, as it stands, you have to run the generation of your mesh both server side and client side separately.

What you can do is have your server side generate the data that can be used to construct the mesh from, then replicate that via a ReplicatedUsing/OnRep variable and then reconstruct the mesh on the client separately.

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

No branches or pull requests

2 participants