|
Ok, I ended up spending the weekend hanging out with my son and my nephew so I didn't do any coding. Today , aside from a couple hours this morning that are my daily exercise, eat, and shower routine and a few minutes to make this post, I'm pretty tied up.
Yesterday however, I finished writing the block management class and finished writing the block generation and placement for the game Barricade. Here's a screen shot.
Clicky For Bigger
It felt great to finally get this finished. Tomorrow I'll be starting on something new for the game. More later.
Ok, so I ended up scrapping the entire collision based block placement idea after a few more iterations of merking with it. Instead I decided to go with a basic grid placement system, that I will hopefully have finished by the end of the weekend. I just keep track of the space available, how many blocks of various sizes I have to place and update that information after each block placement. It's more of a simple system and actually makes sense, unlike my mad scientist ideas previously ventured. More later.
I was doing some more reading and I had a side thought about the last suggested block placement logic. The way it is currently set up the loop exits upon first collision, meaning that if the block were to intersect on the x axis while it was being placed, it would simply be projected away from the object it was colliding with and then the loop would exit leaving it possibly suspended in mid air, if the block was now no longer colliding with an object.
OOps, not what we want to happen. This is an easy fix though, we just have to continue to move the object through the main do loop until both an x and y collision has happened, so that the Object is at rest. So, this will change the logic structure too..
int collide=0 //Change collide to an integer value
do
{
if(collide==0)
{
Move block along negative x and y axises by -0.005
}
else
{
Move block along negative y axis by -0.005
}
if( collision with block placement area)
{
determine the projection by seeing which axis is the shortest distant to
non collision
move block to new position.
collide +=1; //ADD ONE TO COLLIDE
if(collide==2)
{
break; //(SIMPLE IF ENCLOSER OF BREAK STATEMENT)
}
}
else
{
do
{
subtract a number from the current block to work down the list of previously
generated blocks
if(the current block to check is out of bounds)
{
subtract one from the current row of blocks to check and make the last
block in the row the first to check
}
if(the row is out of bounds)
{
no collision happened, so break this loop
}
if(collision with current block to check)
{
determine the projection by seeing which axis is the shortest distant to
non collision
move block to new position.
collide +=2
break;
}
}
while(there's still blocks to check)
}
}while( collide<2)>
This seems to fix our problem, but upon closer inspection we run across one more. Using the current structure of logic the blocks at some point will begin to leave spaces due to the inability of the blocks to know about spaces between each other. This problem occurs no matter what point of origin is used for placing the blocks into the Block Placement area. This is due to the different sizes of the blocks and the random nature of their creation.
So.. Now what?? Well one solution is that through the use of reference counting, the blocks keeping track of the order in which they are created, that they should be able to share information with a management system. It will be the job of this management system to keep track of available space that needs to be filled as the blocks are generated. For example : The first row of blocks can be generated by keeping track of the translations of the blocks before them without running into the space problem. By simply knowing the boundaries of the block before it and knowing it's own boundaries the right origin for placing the block can be determined. Once the first row is filled, if we continued to rely on this system alone, the same problem would occur so an added element is needed. Because of the nature of the growing complexity of placing these blocks, this is where a quad tree does indeed come in handy. By Subdividing the space we can know which blocks the next block placed in the new row can come into contact with, without having to cycle through all of the blocks. It will be up to blocks to keep track of what sectors or branches of the subdivided space they are in so that when an initial collision occurs on the new row, by comparing sizes of the blocks, and knowing the dimensions of the each sizes bounding blocks, we can determine where the new block will fit without wasting space.  This sounds well and dandy in theory, and I'm glad that I took the time really analyze the problem before attempting to really code the solution again, even though this analysis took me a couple of hours, it probably ended up saving me a couple of days time. Following this model I will be structuring a new system for block placement. I will post screenshots of this implementation, even if it ends up that it doesn't work out. That will be available sometime later today. Further analysis will be required as well if this implementation fails.
I'm trying to get into a habit of continuously blogging with good content. Hopefully I make that become a reality. It has been a somewhat progressive week.
With the addition to the implementation of the bounding boxes for objects in the game engine, I also managed to add some simple AABB type collision to the system.
I'm still struggling with how I'm going to actually handle the collisions for the initial block placement in the game barricade however. So, because of this, tonight, I'm taking some time dedicated solely to research in that area.
Yesterday, I experimented with writing some simple functionality that took a block and moved it from the center of the world origin down the negative y axis and the negative x axis until it either came into contact with the block placement volume or another block. Once a collision happened, a test would take place to make sure that the block was not outside of the block placement area, if it was, we iterated small movements until it no longer was testing both the X and Y half-vectors of the bounding volumes. ( I realized that this wasn't the best approach as it eats up some time, but seeing as how there are only a maximum of 60 blocks currently being created, I figured it was at least worth experimenting with.) If it was intersecting with another block we did the same thing. Now feasibly this should work, except that you either A) have to at least divide areas into sub regions and check every block in that region, or B) check every single block in that has already been generated and placed. Seeing as how the game works with such a small number of objects, for simple block placement it didn't seem to make much sense to write a system to check for subdivision organization. My opinion on this may eventually change as I do some additional research this evening.
My problem with the sample implementation yesterday simply was a lack of accurate checking on the x axis for all boxes. I was simply trying to write something fast and was some what disoriented as I've been sick for the last week or so, again.. damn winter, At any rate, I only checked for a collision on the previously generated and placed block instead of with all
blocks. Essentially what I was supposed to have written was two separate main bodies of code for collision, one that checked for block 2 block collision and one that checked for block
to placement bounds collision. Inside each one I was supposed to have checks to see what the shortest path of projection for the objects to no longer be intersecting was and then move the objects appropriately to their resting places. But as I said I didn't check for every block on the x axis, and I didn't get the new translation position from projection, instead, I did small moving increments, which looking back caused extra checks to be made afterwards.
Writing this out has really allowed me to see where I went wrong with things yesterday. I had the right idea, but my actual implementation was wrong. My new structure should look something like the following.
bool collide=false
do
{
Move block along negative x and y axises by -0.005
if( collision with block placement area)
{
determine the projection by seeing which axis is the shortest distant to
non collision
move block to new position.
break;
}
else
{
do
{
subtract a number from the current block to work down the list of previously
generated blocks
if(the current block to check is out of bounds)
{
subtract one from the current row of blocks to check and make the last
block in the row the first to check
}
if(the row is out of bounds)
{
no collision happened, so break this loop
}
if(collision with current block to check)
{
determine the projection by seeing which axis is the shortest distant to
non collision
move block to new position.
collide = true
break;
}
}
while(there's still blocks to check)
}
}while( collide == false)
That should be all the code I need for proper placement of the blocks, at least that's what I'm thinking right now. Yesterdays implementation was something like 273 lines of code, so, if this works, it should speed the block placement up drastically. I'm still going to do some additional reading before trying to implement this in the actual game and make sure that there isn't a better approach to take that I haven't thought of yet. Hopefully, my next entry will include some screen shots of some neatly placed blocks.
Well, I spent the last few hours working on implementing bounding box collision detection. I would have gotten farther today, but I spent a lot of time looking for a simple bug in the wrong places, which sometimes happens. Essentially for the game barricade, I have it setup so that I can see the bounding boxes in debug mode for the game. Or, at least that was what I was trying to do. All I could get it to do was draw three boxes in the center of the screen though, one for each of the different sizes of blocks in the game. So, I went hunting to see if I could find the problem. I thought maybe I wasn't drawing it right, and tried different variations of using offsets from the quads the sprites are drawn on. It didn't work.
I then realized, after setting some break points, that the data stored in the structures for the sprites bounding boxes was still set to zero. You see, I had placed setting the bounding boxes translations in the same function that generated the sizes of the blocks. This wouldn't have been a problem, except that the bounding boxes are determined by an offset based on the dimensions of the textures and the translations of the quads for the sprites themselves. So, of course the size of the blocks would need to be generated before the placement of the blocks, so the data wasn't getting set correctly. I finally figured this out after looking around for a while. Simple, simple things can cause such chaos in a system.
So, I ended up re-building the system within it's own function and had it updated after the placement of every block. This worked out great. Here's a picture of it in action.
Clicky for bigger View
Next up tomorrow will be writing the actual collision detection for block to block collision. Then it will be on to finishing the bullets class, followed by bullet to block collision. Then bot to powerup collision.
After that the only things left to do will be to code the powerup effects, the scoring system, add sound effects, and the demo will be finished. I'm aiming to get this done by the end of the month.
It's been a while since I have blogged oh blog of interest oh mine. As a new year starts I am reminded of my own mortality, of the short time that I know I have to get things going, of the relationships that I have to remember to cherish and of all the good things that are to come.
Game development wise, things have still been moving forward, slowly but surely. I was even gracious enough to help start a local game development meeting that meets the second Tuesday of every month, which is very cool. It's good to find some kindred spirits in the area. Unfortunately life has been heck tick due to some bad decision making on my part, so I haven't really had the time to build those relationships as much as I would like, but that should change with time.
Engine progress is going well, editor is coming a long too. I'm entering a design phase again currently, making sure that things are going where I need them too and deciding on the functionality that I really need to concentrate on. Also, I'm shooting to have a playable Barricade demo complete by the end of this month. Short of adding collision detection to the game demo, it's pretty much complete.
I'll be shooting to journal more once again, as I gain some stability to my interest once more. I'll need to structure up some actual interesting things to write about for a change though. :P
Building an editor takes time. It has been taking me a while up until recently. I guess I really haven't spent that much time on it up to this point either, but it's becoming more pressing as the engine moves along. Design has been rather slow, but things will be picking up this week. I took some time off from game development, about a week, after having to drop out of said competition mentioned in the previous post.
It did give me some interesting ideas to continue to move things along however, so it was not all in waste. I think I'm going to continue to make the game I started developing resources for during the competition as I develop the editor as well. This way I can hopefully find any bugs that may come along and have something to keep me busy as I work on back end python scripting for the engine. I hope to have that and the editors GUI and menu's finished by the end of next weekend.
I haven't been working on Wrath of The Scarecrow the last week either and one of the books I ordered from amazon was canceled so I'm still waiting on some material. I'll start back to work designing WOTSC tomorrow as well.
It's been a little bit of time since I wrote anything in this blog, which is something that I should put an end to this week. I don't really have a lot of time though, and as such I've been blogging over at my GameDev.net Journal
a lot. In regards to the issue with the sprites, I fixed the issue the same week as my entry. Essentially it came down to texture filtering. So graphics look great now. For anyone who may not know. The game that I was working on, Barricade, with Phyersoft has essentially been indefinitely postponed due to the designer not having follow through with the project. So, I've been working on a little project that I like to call Wrath of the Scarecrow. Check out my other journal if intrigued I'll be posting some stuff in here about work on the engine soon as well.
I'll have to update this blog later in the week. In the meantime check out the Taming the Beast link to the right over there. You'll find information about the project I'm currently working on, if you're interested. Which if you're here reading this, you might just be. Barricade is on hold indefinitely as far as I know, but an equally, if not more exciting project is underway. More later.
Well, I was hoping to have already been working on the demo for the comic book convention by this point for Barricade, but time flows a lot faster then I would like in a day, or at least it'd be nice to
A. Have enough wealth so I wouldn't have to work to earn a pay check for the rest of my life, I could dedicate my time to that which I wanted(I'm working towards this one.)
B.Had more hours in a day.
C. Could manipulate time with my mind so that I could get more accomplished.(I'm working on this one also)
So, I'm not really that far behind schedule all things considered. Only a couple of weeks of what I was shooting for to get done in the month of march, but now I'm running into some other issues, that I recently had to solve, and are in the process of now being resolved.
The main issue, had to do with animations for my sprite class. I have no idea how other people handle this in their code. I haven't bothered to ask or do research, but the way I've been handling it is simply loading a sprite sheet into memory as one texture and then mapping the sections with the individual frames to be shown at the appropriate time.
Some pseudo code might look like
----------------------------------------------------------------------------------
LoadTexture
Sprite->Animate
Call to Animate Looks like
advance function hit count
get active frame
if enough hits have taken place advance the active frame number
MapTexture
for frame one show these texture coordinates
for frame two show these coordinates
ect..
---------------------------------------------------------------------------------
My actual codes a lot better structured and is organized object orientedly and works great. The problem is that when I go to manually map my textures in my current editor
(I'm concurrently building a new editor as these issues and the demo are being built)
I have to go in and manually manipulate the textures for the frames to show up correctly on the quads. This is where I'm sure it isn't the best approach, but I don't really know another one, (Aside from having the graphics artist create the sprite sheets very precisely, which seems to be as much trouble as I'm having on my end anyways.)There are slight shifts in the textures do to slight shifts in the textures when I'm going in to map them, and while the anomalies are small and would even possibly be unnoticeable to someone playing the game, they are pretty damn obvious to me.
The solution I've come up with thus far is to increase the precision of movement for mapping the textures and also come up with a more precise grid for aligning the texture on the quad. I'll be trying this out in the next couple of days when I have a little bit of time this weekend.
If anyone out there can make some suggestions or offer any similar experiences up, I would be thankful, although I'm not sure if anyone ever reads this anyways, but if you do thanks in advance for the comments.
The title of this post has nothing to do with anything specific. I just couldn't come up with an idea for a general direction for the content of this post, and thus no appropriate title, which kind of makes the title appropriate.
So.. it's another Sunday and it has been a while since my last update. I've been extremely busy the past few weeks with work and family and have gotten small amounts done on T3D. It's been hard for me to be motivated the few hours I have each day to do anything other then relax, but some days I have managed to push myself to get things done. This weekend has been the first weekend I've had free to work on things for almost a month, unfortunately today has been the only day that I've actually sat down to accomplish anything. At least there is today though.
So, I've finished up the animation class and sprite classes today as well as went back and fixed a few things in a few locations that needed to be cleaned up. I am hoping to get started on an external editor today for levels as well as completing some additional classes for the editor itself. These include a generic mouse event handler, a generic game state manager (ie.. menu's, levels, credits, ect..), and possibly a few other things that need to be done. Actual production of the game Demo should start by the end of this week if all things go well. I am essentially awaiting the arrival of a design doc and other resources for the demo, which is supposed to be completed by mid June, and if not started soon I have a feeling that deadline won't be met.
I really wish I had more time to work on the engine and the upcoming game, but that just doesn't seem like it's something that going to change for a long time. So I'm really going to have focus on time management again.
I am going to have to write another demo to test the sprite class out sometime this week, and when that's completed I'll upload a video of it. Until then, remember that the challenge isn't knowing what you think you want, but challenging what you want to think. That even though you may feel that you're doing all that you can, that there is usually a part that feels you can do all that you feel.
It's been a little while since my last update. I've been meaning to be more consitant at updates, but I usually end up being pretty short on time. Family, job, projects, and then blog updates in that order. The first two usually take up most of my time, which is fine, it's good to have both, but until things get out of march, which is a month full of birthdays and other things, it will be kind of hard to find the time to update.
T3D
Trodlodyte Version 0.2.0 was finished a couple of weeks ag0w When the sound was finished. I then took too documenting the code base which was taking me quite a while. I ended up being pointed too Doxygen which is a great piece of software that automatically write code docuemtation for you based on comments that you make in your code using specific character sequences. So my documentation process went from about a week to around three hours. I can't thank
Ravuya enough for inadvertly pointing me in that direction.
For the past couple of weeks I've been working on reorginizing my design and code process and coding an animation and a sprite class. It took me a few attempts to really get things designed correctly as first I was attempting to structure everything into one class, but after a while, I soon realized it would just be easier to break the animation features up into a serperate class.
The next few days, when I find sometime, I need to sit down and create a demo for the Sprite class, and also that will be a stress test for the engine itself. I'll really get to see how good my code structures are. The engine has seemed to run very well on all the systems I've tested it on so far, but the demo's I've made haven't really had a whole lot going on. I'll find out soon how things stack up.
There is still a lot to do before the demo needs to be ready for the comic book convention this June, but I think I'll have enough time to get it all completed.
So, a quick update. I ended up working on the engine quite a bit last week. I got the sound initialized for the engine using OpenAL. I just built a class to manage the audio context and listener device and one for sources and buffers. I started a new job last week as well, so time management is going to become more and more important. I have to catch up on documentation of the engine and then I'll really be concentrating on developing classes for the up coming game with PhyerSoft. More on that as it develops.
So, I have made some pretty decent progress the last day or so on the engine. I finally finished the in game command console keyboard input handling. I simply added a repeat feature for keys being held down as well as encapsulating the functionality into a class. This also got me thinking about how to structure the rest of the states.
Ideally, when the engine is complete, I want it to be able to be sort of a generic piece of software that the developer can use to extend things upon. Of course for my current level of skill this is very challenging for me to come up with concrete designs to actually implement. I have general ideas of how to accomplish certain design goals, but at the same time the more complete versions of certain features and the way things are handled with be an evolutionary development process. This also comes down to me wanting to start dealing with game objects, getting shit on the screen, as well as diving into data management and eventually developing into the engines scenegraph. All of which I have no experience with at this point.
On top of these issues I was finally able to get an understanding of side by side assemblies and packaged an application for deployment for the first time today. It was pretty educational. Up until this point in my coding career, most things I've written have been standalone console applications so I never really had need for a deployment system. Also prior to windows xp it wasn't a requirement to use such a distribution process.
Anyone out there having similar issues or wanting to learn more about the process in VS2005 should check out Deployment Walkthroughs
Looking a head over the next couple of days, I am going to be concentrating on finishing up some base object classes, after which, I will have to make a decision either to build a game prototype(demo) with the engine in it's current state or continue to add more functionality into the engine. I also still need to begin writing the interfaces for python scripting, write the camera classes, light classes, and a host of other things yet to be completed.
So, Happy not so New Year!
It is my resolution to actually journal in more of a technical standpoint in this blog from here on in. No more rantings and musings about being a twenty something looking to find their place in the world and understand the universe around them.(AFTER THIS POST ANYWAYS)
Instead I will be concentrating on the design process that I will be continuing to go through in regards to the game engine. Oh.. and the screen shot in the previous post was wiped out due to some hardware failures on my end of things, so just use your imagination there.
Later today I will be concentrating on bringing my design focuses back up to par. I will be mapping out a plan of attack and really be looking to get as much done as I can this year, in a consistent fashion.
Well hello gentle reader and thank you for stopping by my lonely blog. It has been a little while since my last entry as I have taken the time to write out my thoughts in a while. A lot has changed since my last entry. I am now living in an apartment all on my lonesome for the first time. Mind you not being away from my folks, as I grew up more away from home for long periods of time it seems, but this is the first place I've lived where I haven't had a roommate, fun stuff. It's better to know that when I come home from work, the apartments not going to be trashed, my food will still be there ready for me to eat, and no one will keep me up jaming until six oclock in the morning when I have to be to work at seven.
Also, I quit my job last Wednesday so I am no longer cleaning buses at nights, which is a good thing. If anyone were extremely bored or for some other reason inclined to read through all my previous posts you would notice a trend of complaint about that job. So, now instead, I will be landscaping, which sounds like a blast to me. Being out doors is something that I've always loved, and I don't even to take a pay cut, and it's a tipical 8 to 5 job, so no more nights. After a year and a couple of months of working nights, with little to no time off and being isolated all the time, this is a much welcomed change.
Ahhh.... what the hell, is this guy ever going to quit yapping and get on with the game stuff?......
Keep your shirt on, .. I'm getting there.
OOHHH, Picture.....
S0 here's the first screen shot ever of T3D. Not all that impressive I know, but there's a lot more going on then meets the eye. Currently I'm still working on finishing the console for the engine. Eventually I'll be writing python interfaces for the console to interact, but I'm still working on getting the input to show up correctly. I currently have three buffers that take in a string. Commands can be up to three strings, thus the three buffers, anyways, I was trying to write my own input handlers that only processed input ever 25milliseconds, but it's been hard to get the character presses to be drawn to the screen the way I want with the current subsystems in place. So , I'm currently looking into an input alterantive. I was trying to find one that is cross platform. I've looked at a few different api's out there that handle a vastly different amount of game functionality, but I haven't seen any that deal specifcally with input. I'll probably end up just using some type of wrapper for one of the api's I've already looked at, but I still have yet to decide. If anyone has any suggestions, drop me a comment. Umm... not really a lot more going on. Well back to work on the engine. Until next time....
So, with time sober comes... a chemcial imbalance from the chemicals attempting to blance themselves out from being out of balance from the mass alchohol consumption on an almost daily basis. Otherwise known as depression. I really have no urges to drink anymore though, which is good. I do however feel like the passion is being sucked out of me. I think I mostly use my current job as a scapegoat. It does suck, I was there a year last month, and no body even said thank you, or good job to me. I didn't get a raise and infact it seems as more time goes by the more I've been neglected there, or taken for granted, or however you want to put it, so I've been focusing all my negative feeling towards that. THis of course doesn't solve anything, nor does it effect my performance at work, it just makes more depressed. THen there's the search for jobs that don't pan out, mostly because all the places that I can think I'd like to work for, aren't hiring currently. So, I just try to think positive and relish in the fact that atleast I have a job, I'm a live, and there are people that do actually care about me in my life. This subdues some of that depression, and I know with time it will pass. It just make me sluggish.
So, due to this depression, who will now be called Mr. Carmikle, in an effort to master this ever annoying pest, I haven't been focusing on my engine for the last couple of days. Instead I've been playing games to try and get my mind off of Mr. Carmikle's antics. He keeps tapping me on the shoulder, and I keep trying to ignore him, but the only time he seems to leave me alone is when I sleep a lot. So, I did that yesterday. He kind of got the hint, but he keeps poking his head in my room today and reminding me he's still here.
So, I still haven't fixed the display problem for the console window and I still haven't got it take input or display output yet. I'm trying to decide whether or not I should instead concentrate on a base class that will incorporate some timers so that anything inherited from the base class will already have to logic to handle animations. This approach would make sense and it's probably what I'll end up doing. I just have to get Mr. Carmikle under control so I can concentrate.
I've kind of been at a lack of inspiration lately to work on things as I've felt like I'm not doing any work that really means anything to the world. Not in the sense that I inspire some girl to be obsessed with an older boy in her trailer park and get pregnant because she listens to my crappy boy band song, but more a long the lines of helping people in need, or creating culture that inspires people to actually help themselves. I think that this theme is also seeded in my depression, especially in regards to my job. I mean the world is so fucked up, yet day in and day out people are apathetic as hell to one another and to the world in general. I mean if people just realized that we are the universe, the world incarnate, that yes there is the illusion of seperatness, but we are still what we always have been, which is one, then maybe we would be nicer to our fellows, instead, people concentrate on the differnces, whether they be social, economical, spritiual beliefs, or whatever bias people choose to concentrate on, and we let that divide us even more. Thermodynamics states that energy can not be created or destroyed. Energy, which in term relates to matter. This means that matter can be changed, altered, reformed, but the underlying energy is always the same energy that has always been there. Recycled.. throughout the ages. This concept is in every religion, but closed minded people choose not to look at it that way, people are too interested in feeling superior, having power, to realize that anything that has true power, doesn't look to be in control, it looks to serve.
This has turned into another long non game development related post that may just look like a bunch of jibberish. I guess what I'm saying is that I really hope future generations can become aware of how to help, love, and respect one another, themselves, enough to see where it is the previous generations have gone wrong. It's fear that propogates the negativity in this world.
As an example, look at global warming. We are destroying our world, and yet the vast majority of people don't give a shit enough to stop doing it, I fall into this categorey as well. I do care, but not enough to stand firm on that conviction. Oh well what could we do, some may ask. Answer = STOP DRIVING CARS,&STOP BURNING COAL, &STOP PRODUCING GREEN HOUSE GAS!
Well, we couldn't do that how would we get to work? Answer = Provide public transportation for the masses, walk, ride a bike, come up with alternative fuel sources.
Oh but we don't want to do that, then we'd have to associate with people we don't want too. Or we 'd have to wake up fifteen minutes earlier, or we'd have to change our lifestyles.
These things are all issues that come out of fear.
THink about it. Would the world stop if the American way of life, the way we know it, suddenly changed? If people decided to go back to basics, not commute as much, be more niche associated, would the world stop? People are afraid of change, especially if they've done things a certain way their entire life. This seems to be a taught behavior that is accepted throughout our culture and yet it is this thing that will cause this construct of organismal life form, that we call human beings, to be erraticated from the bussom of the planet. Scary.. and a long rant. I should organize these ideas better, but to be truthful I'm not trying to convince anyone of anything. THis is stuff that if anyone is able to be truthful with ones self they already know. I'm just trying to get some passion back in my own life, maybe to have a fire burn to influence something for the better, someday.
Well, we have it four days sober, and the start of an in game console for T3D. It feels good to be hard at work, focused, and back on a path that I fell off of roughly four months ago. I'm currently familiarizing myself with the process of a timestep so that the animation for displaying the console window displays correctly. I really know squat about graphics programming. Up until this year, I've mainly focused on programming in general, seeing as the only things I've completed code wise were various example applications, a quarter of a completed text game(really only lacked content, all the subsystems and systems were complete), and my first game demo that I coded in Visual Basic three years ago. SO, needless to say I'm learning a lot this year, but it has gone slow up until this point due to neglect of effort, well consistantely anyways.
I have a feeling that I will have to end up doing a complete overhaul after a while on my entire code base, but I'll have to cross that bridge when I come to it. For now, I need to concentrate on completing some lower systems and then move on to constructing my first scene graph, from there I should be ready to start concentrating on scripting, geometry, physics, and a host of other shit that I'm sure it's going to take me another year or two to complete to a functional version. It's a long road, but you can only take it one step at a time.
I managed to change my template around today. It wasn't really that hard to figure out what all the tags were for, although it has been a while since I last dived into any net code at all. So, I'm sitting here, doing this, mainly to keep my mind occupied. I've given myself a rough week as of last and well, frightfully enough, all I seem to be able to do is to through myself into something, in order to get back on my feet. I'm being a bit criptic here, but I'll leave it at that, I don't really feel a need to clarify as I know what I mean.
So, I'm still working on researching and designing a scene graph for my game engine. I haven't really done much of anything this last month, but I'm at a point in the engine work and in my life, where focusing strictly on the things in my life that need to be done is top priority. It's pretty obvious too me, just from reading my previous entries that this blog has had little to do with my actual pursuit of game development and more of a ranting on my struggle with alchohol abuse, which tells me a lot about my life these last few months. I'd really like to see this blog deal more with game design, as with my life having to deal with no more alchohol abuse.
My Quote of the day : By Me
Plans are often only as good as the convictions of those who attempt to carry them out.
|
|
