![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
8:57am - Down at the McDonalds again today, but much later than usual. Slept a lot more last night than usual so naturally... Anyways the downside is my usual spot is already taken, and my backup spots, and so I'm in a less than ideal spot right now. The sun is beaming in hard and my screen is dim from low power mode. Alas.
Anyways I've got more multithreading research to do!
9:43am - *does lots of research* Still not sure about this. :/
I wonder if I ever will be?
Let's look at my own code again.
10:19am - Okay I've popped my function into a thread and it's got a runtime error that it's trying to reference Unity values it's not allowed to. I know about this sort of thing, so I need to figure out where it's doing that and pull it out.
10:32am - Looking at what the code, I've come to a realization; the problem I was trying to solve with multithreadding was that all of the Actors were being handled in the update method, all at once, and all that processing could take longer than a single frame, or lock the program if there were no player controlled actors.
However, the optimizations I constructed to allow for multithreading already solved those problems. It only processes one actor per frame now, and the processing for a single actor isn't enough to break out of a frame... yet.
When it does come time for threadding again, it's going to be because of things like routing, pathfinding, and goal finding... Those should be able to run in seperate threads in their own way. I might like to plan ahead some and figure out when they'll be needed, but I also should probably get back to making the actual game.
10:47am - Okay now I'm feeling kind of spent, which is bad since I'm only just settling in and I just got a cup of tea and some water and geez. I'm not sure what to do with myself, or with my project.
The last thing I was working on before I got distracted by this problem was developing brains with more advanced AI, senses and pathfinding.
So, I'm not sure if I should dive in and start coding blindly or plan it out ahead of time. Normally the latter would be the obvious choice, but sometimes planning to do something and then doing it can be more work than just doing it and figuring out how to do it as you go.
Anyways for now I'm going to rest, play a game or something, and come back to this after lunch.
12:02pm - Plans have changed. I was just sitting down to eat when I got a phone call from my Dad. He's in town and wants to do lunch. XD
I told him I'd meet him and have something light. Maybe I can bring something home? McDonalds food doesn't keep well so I'll eat that now. Anyways I'm going to cut this journal short now.
Anyways I've got more multithreading research to do!
9:43am - *does lots of research* Still not sure about this. :/
I wonder if I ever will be?
Let's look at my own code again.
10:19am - Okay I've popped my function into a thread and it's got a runtime error that it's trying to reference Unity values it's not allowed to. I know about this sort of thing, so I need to figure out where it's doing that and pull it out.
10:32am - Looking at what the code, I've come to a realization; the problem I was trying to solve with multithreadding was that all of the Actors were being handled in the update method, all at once, and all that processing could take longer than a single frame, or lock the program if there were no player controlled actors.
However, the optimizations I constructed to allow for multithreading already solved those problems. It only processes one actor per frame now, and the processing for a single actor isn't enough to break out of a frame... yet.
When it does come time for threadding again, it's going to be because of things like routing, pathfinding, and goal finding... Those should be able to run in seperate threads in their own way. I might like to plan ahead some and figure out when they'll be needed, but I also should probably get back to making the actual game.
10:47am - Okay now I'm feeling kind of spent, which is bad since I'm only just settling in and I just got a cup of tea and some water and geez. I'm not sure what to do with myself, or with my project.
The last thing I was working on before I got distracted by this problem was developing brains with more advanced AI, senses and pathfinding.
So, I'm not sure if I should dive in and start coding blindly or plan it out ahead of time. Normally the latter would be the obvious choice, but sometimes planning to do something and then doing it can be more work than just doing it and figuring out how to do it as you go.
Anyways for now I'm going to rest, play a game or something, and come back to this after lunch.
12:02pm - Plans have changed. I was just sitting down to eat when I got a phone call from my Dad. He's in town and wants to do lunch. XD
I told him I'd meet him and have something light. Maybe I can bring something home? McDonalds food doesn't keep well so I'll eat that now. Anyways I'm going to cut this journal short now.
