Predicted object callbacks delayed on a clientHost #377
Closed
Hukha
started this conversation in
Feature Request
Replies: 2 comments 1 reply
-
What is the feature request here? What is behaving different? |
Beta Was this translation helpful? Give feedback.
1 reply
-
When the object is spawned as clientHost the server is spawning it because
predicted spawning isn't needed. You should be using OnStartNetwork to
check if owner is local client if you are planning to code for clientHost.
IsOwner will become true when the client end receives the spawn packet.
Perhaps I can look into using predicted spawning as clientHost if the
object is configured to.
…On Mon, May 22, 2023, 5:09 AM Santiago ***@***.***> wrote:
Well, as I said:
A predicted objects spawned in a clientHost has delay in it's callbacks
(Also in the setting of IsOwner ofc) while normal clients (not host) have
none.
This creates different behaviours between clients and can cause problems
like the one described with the bullet.
—
Reply to this email directly, view it on GitHub
<#377 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGPJC3WHLWJF23VZIBGQVMTXHMUK3ANCNFSM6AAAAAAYIGLQKE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Basically what the title says.
When you spawn a Predicted Object in a clientHost, the callbacks (OnStartClient, OnNetworkStart...) for those objects are delayed. This does not happen in normal clients AFAIK.
This has two problems imho:
In case someone has this issue, what I did is basically create a layer in-between where my created objects know if they were created "locally" to start the movement even before receiving the network callbacks
Beta Was this translation helpful? Give feedback.
All reactions