you can't build Doom 3 on the Half-Life engine, for example, because Doom 3 requires some things (like per-pixel lighting) that the Half-Life engine simply doesn't provide.

quote:

---

Original post by Leffe

you can't build Doom 3 on the Half-Life engine, for example, because Doom 3 requires some things (like per-pixel lighting) that the Half-Life engine simply doesn't provide.

Wrong! You can write a custom renderer. Somply disable client drawing and render everything with OpenGL or DirectX.

---

quote:

---

Original post by voodoo_john
We should petition Dave, cause its all very well throtling article release so that there's a backlog, but the amount of time that passed between days where the same thing sat there.........

---

quote:

---

What do you mean? There have been 4-6 new articles posted consistently every week since, oh, March or so.

In any case, assuming I get the articles from superpig in time, I'll be posting them every one to two weeks (probably more like two to give him enough time to keep up with me).

---

quote:

---

Original post by Myopic Rhino
What do you mean? There have been 4-6 new articles posted consistently every week since, oh, March or so.

---

quote:

---

Original post by pan narrans
Enginuity? ENGINUITY???

HANG YOUR HEAD IN SHAME

---

quote:

---

Original post by Houdini
Dave, I've noticed it and I can't tell you how great it is to see a new article every day or two!

Keep up the good work!

---

quote:

---

Original post by superpig
But Dave, you messed up my title! It was meant to be called "Enginuity, part 1; or How I'm Going to Lose the Next Few Weeks."

---

quote:

---

Original post by voodoo_john
Not to get anyone's back up.....

But I'm talking about thourough, in-depth articles such as The Direct-X GUI series ans SuperPig's etc, and not the "lite" ones like CRC Checking or a sample chapter from a book or sweet snippets, which while fine in themselves aren't meaty enough reading IMHO. The terrain geomorphing article recently was excellent, about the length and detail I personally like to see in an article.

---

quote:

---

Put it this way: If you can work out what a 'templated class that inherits from multiple virtual base classes and overloads the pointer-to-member operator' is, then you're ready. If not, then sorry, but you simply won't understand some of the code and design techniques I'm going to use in the series

---

 
class V1
{
public:
	V1()
		: miSum1(0)
	{}

	virtual void Once() = 0;
	int Sum1() const { return miSum1; }

protected:
	int miSum1;
};


class V2
{
public:
	V2()
		: miSum2(0)
	{}

	virtual void Twice() = 0;
	int Sum2() const { return miSum2; }

protected:
	int miSum2;
};


template<class T0> class WTF : public V1, public V2
{
	struct Stats
	{
		T0 tNumTeeth;
	} mStat;

public:

	WTF( T0 val )
	{
		mStat.tNumTeeth = ( (int)&miSum2 - (int)&miSum1 ) / val;
	}

	void Once() { miSum1 += mStat.tNumTeeth; }
	void Twice() { miSum2 -= mStat.tNumTeeth; }

	Stats* operator -> () { return &mStat; }
};        

quote:

---

Original post by IFooBar
Why in 's name would you want something like that?...anyway...I was bored so...

<complex source code demonstrating the concept>

I dunno what the hell it can be used for though. Will I understand your series now?

---