Upon dissecting the HPL 1 Engine, Doom 3 Engine and looking back at my engine...As far as coding skills are consern I have a lot to learn! The whole entire framework is whacked. I am going back to read the Game Engine Architecture. It helped point out a lot about the design of an game engine.

In addiition, a API or SDK are just tools laid out for the developer to build a game. A house wouldn't be built without tools, right? Game is the house as in tools are the game engine's api or sdk.

What I've noticed is the Doom 3 engine uses a lot of macros definations and HPL 1 Engine uses a lot of macros. I thought you want to stay away from macro definations as best as you could?

Why in the world reading through someone's elses code so confusing? HPL1 uses a lot of interfacing; a lot of polymorphisms and don't forget the macro definations.

Remember that callback question that I asked about? Yeah I found out how that one works - never looked at the HPL Engine source code closely like today.

A lot of the time I was searching within the project how they co-relate to eachother. Callback function is all the way over to another header file, that gets used by a lowLevelSystem header file and then over the script header file.

It's like connect the dots - literally! Over here and over there and over there and over there!

Aren't any API or SDK suppose to make sense or do they literally have the whole "Connect The Dots"? Or do they purposly do that to prevent others from dissecting their code and making a better engine then theirs?

man: It's like here's a bunch of nails, screws, bolts, washer, a some wood and scrap metal - there you go! Have at it - now build a shed.

Builder: Where's the instructions?

man: There's no need for instructions just go with what you feel best!

Builder: Huh?!

How many revisions do a game engine undetake anyways? This is perhaps my fifth or so. I'm just venting - don't mind me! TIme for a smoke.

Thanks for the awesome feedback! I've been hitting pass those sluggish times where I want to take a coding vacation. Weirdly enough, the volumetric texturing had me do a lot more research than I ever did before! I think I actually learned a lot more than I had like two days. Back to the interconnecting of the engine - that's still undergoing it's way. Still working on the current issues. Today I cleaned up some code crude that I didn't need. I commeted the ones I can use later. I learned a hell alot more about memory allocation and provide better means. I kept on getting a stackoverflowexception than I figured out what I was doing wrong. I stopped that and sit back think why did that give me an exception.

A lot of the times it's just keeping the eye on the goal and never looking back. Hell, if my game doesn't sell nor work out as well I can always build an electronic equipment that uses 3D mapping like gdar - it sends radio waves through the grown when detecting hidden rooms or caves or some shat like that.

I wasn't thinking of Doom 3 as ideal goal - then again I think focusing on my own would be better than focusing on other people's engines.

What I've noticed is the Doom 3 engine uses a lot of macros definations and HPL 1 Engine uses a lot of macros. I thought you want to stay away from macro definations as best as you could?

Then again, a more "modern" version of that codebase is Doom 3 BFG's engine, I hear it was modernized a lot with ID Tech 5 code and its focused on multi threading. Its open source and uploaded to github if you want to take a look.

Wait I downloaded the Doom3 - BFG Source code along time apparently, it was in my github folder on my desk top. There was another ID Tech engine I think I looked at - not this one though.

I'll have a look at this one again. I still stand by this ideal - API \ SDK are just tools to allow the developer to develope the engine or game. As in in OpenGl, DirectX, BUllet Physics Api, Nvidia Physx and others. If I keep this in mind - it will help keep me on focus on what's important at hand. I'm still keeping my eye on the goal as I stated. Sometimes though; the burnt out feeling is from hitting blocks - like writers hit blocks when writing stories. Coders run in to the same thing. Especially when they have external bull crap like family in law related issues running rampant. I say Eventually the Hard Work Will Pay Off At the End. It's all a progress. Once the Engine and Creation Tools are out of the way then I can focus on the fun stuff like creating a masterpiece of a horror game.

About building an electronic device that maps out in 3D - I can even use my knowledge what I learned about 3D Graphics in that arena as well! I just wanted to point that out too.

The Chubu - I'll look at the source code. I'm on my second cup of coffee but I'll look at it. Thanks everyone for chipping in their wisdom.