I've always found that if I get bored/demotivated with my project, I will take a break from whatever specific thing I am working on and do something else for a while.
For example, I am pretty new to scripting and it really takes some motivation to do such a tedious thing when you don't know functions and such off-hand.
So, I make a simple to-do list of things that need to get done and try to organize them in order of importance. Maybe I'll go ahead and make a few environmental meshes, or tweak some of my mesh placements in a map, or make a new material asset, and then I will go back to my design document (if you don't have one, you should) and make changes as needed.
I'll make sure to make notes on how certain scripts should be put together
I.E. - My "pickupfactory" for weapons is a crate that needs to do the following:
- Check to see if the player is close enough to "use" the factory...
- ...If so, Open The crate (play Animation).
- ...If not, Make sure the crate is closed.
- If the player isn't close enough and the crate is open, close it.
- Check to see if the weapon should spawn...
- ...If it should and the crate is closed, spawn the weapon inside the crate.
- ...If it should but the crate is open, don't spawn the weapon until the crate is closed again.
- Check to see what kind of weapon should spawn.
Etc.... You get the point. This way when I go back to scripting, I already have the basic layout of everything that script should do, so I can go about coding specific things one at a time.
So, pretty much like everyone else has said, set one small goal at a time.
Also, I want to add about you saying your work looks like **** to you: We are all our own worst critics, as are most artists. It really boils down to whether or not you love what you are doing. If you don't know the answer to that, then you may want to re-think things through.
For example, I am pretty new to scripting and it really takes some motivation to do such a tedious thing when you don't know functions and such off-hand.
So, I make a simple to-do list of things that need to get done and try to organize them in order of importance. Maybe I'll go ahead and make a few environmental meshes, or tweak some of my mesh placements in a map, or make a new material asset, and then I will go back to my design document (if you don't have one, you should) and make changes as needed.
I'll make sure to make notes on how certain scripts should be put together
I.E. - My "pickupfactory" for weapons is a crate that needs to do the following:
- Check to see if the player is close enough to "use" the factory...
- ...If so, Open The crate (play Animation).
- ...If not, Make sure the crate is closed.
- If the player isn't close enough and the crate is open, close it.
- Check to see if the weapon should spawn...
- ...If it should and the crate is closed, spawn the weapon inside the crate.
- ...If it should but the crate is open, don't spawn the weapon until the crate is closed again.
- Check to see what kind of weapon should spawn.
Etc.... You get the point. This way when I go back to scripting, I already have the basic layout of everything that script should do, so I can go about coding specific things one at a time.
So, pretty much like everyone else has said, set one small goal at a time.
Also, I want to add about you saying your work looks like **** to you: We are all our own worst critics, as are most artists. It really boils down to whether or not you love what you are doing. If you don't know the answer to that, then you may want to re-think things through.
Comment