SnpM
commented
8 years ago Network sync is the reason. A saver is used because the order of object initiation isn't deterministic. I.e. if every object registered itself via Start (), they wouldn't register in the same order so things like the physics loop would run through the objects in a different order on 2 clients.
On Tue, Jul 5, 2016 at 2:04 PM, Jesse Fish notifications@github.com wrote:
I have been pulling the code apart for this project. I'd like to make a reasonable fighting game with it (using a different network structure than what is currently setup for rts). I am trying to make a simple scene as a prototype that is just a 2d world with a bouncing ball on a flat surface. There seems to be some system of registering objects in the scene with a saver object. I want to know why this is the preferred method. I don't understand why I can't edit objects in the scene and have the objects self register on wakeup and to set up their initial positions based on their transforms. Why is the default approach using a saver object and clicking save for the scene in the editor to load all the lsbodies into the saver, then on game start only acknowledging objects that were loaded from the saver and not any that are in the level at game start. The only reasons I can think of are for network synchronization or because the other manager objects aren't guaranteed to be initialized before the lsbody objects but those seem like solvable problems without using the saver mechanism.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SnpM/LockstepFramework/issues/79, or mute the thread https://github.com/notifications/unsubscribe/AHXqp2bqSv5gydbKYmg_03GfdKrdb_Dbks5qSriwgaJpZM4JFeff .
erebuswolf
I have been pulling the code apart for this project. I'd like to make a reasonable fighting game with it (using a different network structure than what is currently setup for rts). I am trying to make a simple scene as a prototype that is just a 2d world with a bouncing ball on a flat surface. There seems to be some system of registering objects in the scene with a saver object. I want to know why this is the preferred method. I don't understand why I can't edit objects in the scene and have the objects self register on wakeup and to set up their initial positions based on their transforms. Why is the default approach using a saver object and clicking save for the scene in the editor to load all the lsbodies into the saver, then on game start only acknowledging objects that were loaded from the saver and not any that are in the level at game start. The only reasons I can think of are for network synchronization or because the other manager objects aren't guaranteed to be initialized before the lsbody objects but those seem like solvable problems without using the saver mechanism.