Announcement

Collapse
No announcement yet.

Spawn Actor, replication of exposed on spawn variable values

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    [FEATURE REQUEST] Spawn Actor, replication of exposed on spawn variable values

    Hi,

    I think it would be really useful and also expected that Actors which are set to replicate and get spawned on the server, will start with the exposed on spawn variables fed by the server.
    Currently clients ignore the Values set on the Server, the desired functionality would be that Actors spawn with the same values as on the Server.

    #2
    Bump.This would be very useful.

    Comment


      #3
      Won't happen. The vars need to be replicated.

      Comment


        #4
        Originally posted by TheJamsh View Post
        Won't happen. The vars need to be replicated.
        I see a lot of these kind of posts from you, from time to time. You're not being very helpful. Maybe you should take a step back.
        Originally posted by soannoyed View Post
        Hi,

        I think it would be really useful and also expected that Actors which are set to replicate and get spawned on the server, will start with the exposed on spawn variables fed by the server.
        Currently clients ignore the Values set on the Server, the desired functionality would be that Actors spawn with the same values as on the Server.
        Expected maybe, but this would delay initial replication which is undesired for most use cases. What you could do however is to wait for the initial replication bunch to arrive before you show the actor. You could also implement a similar trick like in Unreal Tournament where you force replication to happen earlier (they do it for Projectiles) and minimize the time your object spends with less than its full state.

        Comment


          #5
          Exposed variables are set directly on the CDO, so to me this request doesn't make much sense..
          | Finite State Machine | Savior | USQLite | Object-Pool | Sound-Occlusion | Property Transfer | Magic Nodes | MORE |

          Comment


            #6
            Originally posted by Stefan Lundmark View Post
            I see a lot of these kind of posts from you, from time to time. You're not being very helpful. Maybe you should take a step back.
            Lot's of these threads are usually started out of frustration when the engine doesn't do something the user thinks it should (and usually, it shouldn't). Most of the time it's clear that the poster hasn't researched it and immediatelly comes here instead.

            But, fair enough - here's a full explanation:

            ---

            Any property that has to travel to the client has to be replicated - this is the defacto expectation made by the engine. If they only need to travel once, you can use the COND_InitialOnly flag.

            Having a new system which replicates all 'ExposeOnSpawn' properties by default, increases the cost for everybody.

            Comment

            Working...
            X