About this blog
This journal may contain languages not suitable for minors and some occasional swearing.
Entries in this blog
Just signed up for the World of Warcraft stress test. I didn't get into the beta back when it started, and not being a real MMORPG fan I wasn't devastated. But from what I've heard, this one will be worth picking up, so I'm happy I get to play it in a couple of days, or whenever they open it for testing. It's downloading on my home computer as I write this.
On other news, I'm fucking starving, lunch won't be here for another 40 minutes...
What else? oh yea, I guess I'll finish this with another quick tip.
Never, EVER hardcode numbers, if you need to, use a const variable for it, this will describe what this number is being used for. Doing stuff like this:
float fAltitude = fCurrentAltitude * 0.304799f;
will just confuse the hell out of whoever tries to read your code, instead, do this:
const float fMetersToFeetRatio = 0.3040799f;
float fAltitude = fCurrentAltitude * fMetersToFeetRatio;
by doing it this way you don't have to guess what's going on, it's plain to see you're converting fCurrentAltitude from meters to feet.
And that concludes todays quick tip.
Found a cool site...
it's 3D graphics stuff with lots of code samples.
The past couple of days have not been as bad. Though progress has been somewhat slow, the progress I have made is good solid stuff. Just a few more things and I'll be able to switch gears from getting stuff working to just fixing bugs as they come up.
Always have a macro or function that converts from game units into other commonly used units, such as meters, feet, etc. In the long run it saves a bit of time, and there's no point in having to do these conversions as needed all over the place.
Man, it's 12:09 am... I shouldn't need to be here. I hate it when they ask for so much stuff in such short notice. This blows. I want to go home and sleep. Oh well, I'll be able to post a link to show what I've been slaving over once this is done... in the meantime, I think my build is done, so I'm going to test this and if all goes well go home.
Didn't write anything yesterday, it was quite a day, I was refactoring a bunch of script. My first idea didn't quite work as planned. But I was mentioning the problem to a friend and he suggested I try a point to line distance solution. Turns out that gave me a very nice, elegant and reliable solution to the problem. It took me all afternoon, but once the point to line stuff was working everything else just came naturally and started falling into place.
Today is one of those days in which I'll spend most of the day getting the level stable, playable and looking good. Then I'll add a feature and everything will go to hell, just like always.
I was just reading about LaMothe's new creation, the XGameStation. Here's what it says:
This sounds like something I would like to play with, it would be real interesting to write a 3D rasterizer for this system. See how far the cpu on it can be pushed.
I love it when they bring us beer for dinner.
Infinite loops result in some truly unpredicatble behavior. Especially when the infinite loops exists in a script rather than in code.
Basically I had a function (I'll call it FunctionA) that worked something like this...
while ( conditionA is false )
pause execution here
if we got here, then call FunctionB
then in FunctionB I had
while ( conditionA is true )
pause execution here
if we got here, then call FunctionA
So, this worked nice and didn't cause any problems... that is until a different bug somewhere else caused the object that was being tested for conditionA to be NULL.... so now, the while test would be undefined, and the scripts behavior in this case is to keep executing... that's where all hell broke loose and eventually resulted in a stack overflow.
It's a silly mistake, I should've thought about this problem a little longer before I implemented such a bad solution. Oh well, I refactored that piece of code and I'm about to test it.
Just got back from having dinner at the cafeteria, had a turkey sandwhich with swiss cheese and what felt like three pounds of icecream. Today is one of those days, I've been working most of the day on the same thing and yet at the end of the day I feel like I have accomplished nothing. I'm probably not staying very late tonight, I'm starting to feel fatigue affecting my work, so I'll go get some rest at home tonight.
Maybe tomorrow I'll have a more development oriented entry in this journal... but, who knows.
Now I got to get back to trying to figure out a damn bug that's really annoying the hell out of me.
So here I am at work, I just signed up for GDNet+, like many others my main motivation to sign up was to support GameDev which through the years has been a great source of information.
Not many people here know me, in fact, probably no one does. I've never been the kind of guy that spends a lot of time in forums, at least not writing in them, I do read a lot of posts that catch my eye on here, but usually people beat me to replying with a solution.
Also, the fact that the project I'm working on is getting close to being done doesn't give me much time to do anything, other than work. I haven't gone surfing (in the ocean, not the web) in months, I sure miss it. I might just say 'fuck it' on sunday and go, it'll be a good way to unwind and release some of the pressure.
Don't get me wrong, I love making games professionally, especially the project I'm on. But it sure is a lot of work, so much work in fact, that I no longer play as many games as I used to. And when the game I'm working on comes out, I wonder if I'll have time to play it. I'll have to make time because it's going to be an awesome game. And yes, I am biased, but it's not like I made the whole game, there are levels that I haven't even seen, or that I've only seen glimpses of and they just look amazing.
Ok, it's time to go grab some lunch. Damn, I didn't bring money to get a soda from the vending machine.