I intend on writing an engine (for an FPS) and want to know a few things, please:
*1 - Is Quake 1 the simplest code to wade through? (I'm okay at C)
*2 - Since I'm going to be heavily modfying the code (say, Valve) then do you think I'm going to need a copy of Quake along the way? I know you need Quake to mod the engine. But I'm not modding. If not, then I'll have to write my own program to utilize the engine?
*3 - If 1 is a "no" then which id engine should I use?
I'm also using Bloodshed's awesome Dev-C IDE. Is that good for Q1 engine programming?
Quake 1 Engine Coding
Re: Quake 1 Engine Coding
Mentioning Valve on this forum is considered vulgarflockhound wrote:I intend on writing an engine (for an FPS) and want to know a few things, please:
*1 - Is Quake 1 the simplest code to wade through? (I'm okay at C)
*2 - Since I'm going to be heavily modfying the code (say, Valve) then do you think I'm going to need a copy of Quake along the way? I know you need Quake to mod the engine. But I'm not modding. If not, then I'll have to write my own program to utilize the engine?
*3 - If 1 is a "no" then which id engine should I use?
Quake 1 engine code is pretty easy to read, and the id1 gamecode is very easy to read.
Quake 2 engine code is easy to read, but the baseq2 gamecode is pretty bad.
Quake 3 engine code is a bit challenging, and the baseq3 gamecode is pretty bad.
If I may ask, why base on an id engine, and for that matter why make a new engine? Why not use an existing enhanced engine like DarkPlaces if considering Quake1?
Sorry to say I don't understand your goals.
-
- Posts: 3
- Joined: Fri Aug 04, 2006 9:00 pm
- Location: Earth
Ooo, sorry 'bout the...uh..."V" word.
I'd just like to develop my own engine (with a cousin actually). I don't know much about making an engine, and since the Quake 1 engine is open source, why not? As I develop the better engine I'll learn a lot about engine programming. Stuff on hierarchies and BSP stuff (Quake 1 uses BSP, right?) Either way, I'm a fan of Quake 2's solid game design.
I'm not using an enhanced engine for some of the reasons above. Now, I'll probably look and see how they made their modifications (no, I'm not copying) but I won't use them. It's sort of a "It's my baby and I programmed it" situation...
I'd just like to develop my own engine (with a cousin actually). I don't know much about making an engine, and since the Quake 1 engine is open source, why not? As I develop the better engine I'll learn a lot about engine programming. Stuff on hierarchies and BSP stuff (Quake 1 uses BSP, right?) Either way, I'm a fan of Quake 2's solid game design.
I'm not using an enhanced engine for some of the reasons above. Now, I'll probably look and see how they made their modifications (no, I'm not copying) but I won't use them. It's sort of a "It's my baby and I programmed it" situation...
Same boat a lot of Quake engine coders are inflockhound wrote:Ooo, sorry 'bout the...uh..."V" word.
I'd just like to develop my own engine (with a cousin actually). I don't know much about making an engine, and since the Quake 1 engine is open source, why not? As I develop the better engine I'll learn a lot about engine programming. Stuff on hierarchies and BSP stuff (Quake 1 uses BSP, right?) Either way, I'm a fan of Quake 2's solid game design.
I'm not using an enhanced engine for some of the reasons above. Now, I'll probably look and see how they made their modifications (no, I'm not copying) but I won't use them. It's sort of a "It's my baby and I programmed it" situation...
Have fun with it
A tip: besides these forums you can also usually get some meaningful discussion going in the channels #quakedev and #venr2 (Entar's Vengeance r2 engine channel) on irc.anynet.org, and #darkplaces also but that's a bit more modder oriented, a little less engine discussion (except when I'm talkative, I guess).
-
- Posts: 3
- Joined: Fri Aug 04, 2006 9:00 pm
- Location: Earth