Work Post

12:44pm - So I've had an 'interesting' day, I got up around 6pm yesterday and I've been either sleeping or almost sleeping for most of the night afterwards. I'm tired now but I don't know hw much 'awake' I've been in the mean time.

Anyways I finally feel like trying to tackle the problem that's been nagging at me. I've got to do a test, or learning experiment, using the Unity Job System, to really get my hands in and figure out how to use it with my own project, if I'm going to use it.

So, what am I going to make?

I'm not entirely sure. My plan was to make a rotating box in the middle of the screen, and then do so much other junk (probably just delays) that the framerate drops. Then I'd set up the job system so that the delays are in there and see the frame rate go back to normal, or something.

I'm not sure that's a good test though.

I also need to do something with sending messages from the worker thread to the main thread, and test UI stuff...

So maybe I should make a UI in the main thread and have it get locked up by delays, and then move the delays to a job and have the job and main thread send messages to eachother.

That makes more sense. But now I'm getting really tired and Rob's up so I'm going to just save this here and maybe do some more later.