Forum Discussion
Issue with development.. (stalling)
Is it just me, or does anyone else have an issue with their development becoming stalled due to testing a change?
What I mean is that, when I make a change to something, I go to test it out and completely lose track of time and get way to immersed in the environment, usually for a couple hours or more. By that time, since I'm completely strapped for time, I have to shut it down for the night :cry: It sucks since this is taking up most all of the time I can afford for development :\
Anyone know of any good tricks to avoid this?
What I mean is that, when I make a change to something, I go to test it out and completely lose track of time and get way to immersed in the environment, usually for a couple hours or more. By that time, since I'm completely strapped for time, I have to shut it down for the night :cry: It sucks since this is taking up most all of the time I can afford for development :\
Anyone know of any good tricks to avoid this?
7 Replies
- Yes, this only happens every single time I test something. :lol:
I've found the best way to test basic functionality is by testing them in a non-VR mode. I execute the game without the rift wherever I can. I'll even go as far as avoiding things I need to test with the Rift until I have enough items that it's worth going in for. - If you're too immersed, maybe you can try adding some clocks or timers to your gameworld? It'll remind you of how long you've been in VR. Another idea would be to get webcam input and put it into your gameworld, so that you can see your IRL self from inside VR. That might be enough to break immersion, while still allowing you to test whatever it is you're testing.
- Yeah that sounds like you need to separate out how you test. If you are testing VR related issues or trying to come up with VR design related ideas, test your game in VR mode and try to focus on the goal that you went in for. If it is something else you are testing, anything else, try just going into the game without the Rift on. This will speed up your workflow and help you stay focused.
If you aim to succeed here focus is going to be critical. Keep up the good work, if you are getting lost into your own worlds already that is a great sign that you are doing well. ;) - Use automatic unit tests instead of "testing as you go."
1) The computer doesn't get lost in the fantasy.
2) The computer will remember to re-test everything every time. "jwatte" wrote:
Use automatic unit tests instead of "testing as you go."
1) The computer doesn't get lost in the fantasy.
2) The computer will remember to re-test everything every time.
This will depend heavily on what you are testing. I don't think computers can unit test immersion levels...
Totally valid point though. Anything that you can unit test, you should.- "You have been testing for three hours. Please take a break".
"diablosv21" wrote:
"jwatte" wrote:
I don't think computers can unit test immersion levels...
You just have to think out of the box, write a custom testrunner that dispatches a sms to your incredible unlucky test-guy.
Then you have a camera that measures how much his mouth is open.
Solved! ;)
A bit unrealistic, but I really think many "untestable" features get testable if we have got some dedicated test-guys.
A commit could trigger another cycle of human testing of the related modules.
