12-18-2015, 10:04 AM
One thing I've never understood is why the spawn initialization happens on the creating thread, and not the first act of the tick thread.
I suggest we get rid of CreateAndInitalizeWorld, and replace it with a method that inits the spawn asynchronously. We'll have to deal with interactions with uninitialized worlds, but thats probably the best way to fix this.
I suggest we get rid of CreateAndInitalizeWorld, and replace it with a method that inits the spawn asynchronously. We'll have to deal with interactions with uninitialized worlds, but thats probably the best way to fix this.