Why the KEX engine?

[Wicked]

I mean yeah, KEX is good, but what makes it better than EDuke32 or ZDoom/GZDoom?

[>M@tEo$<]

It's their engine, made to run other engines, so they can run anything with it, I guess

[Steven Seagull]

Because the doors won't squish you? I don't know other reasons... That could have been fixed in BUILD (EDuke32) too I think.

[₦₣Đ]

Originally posted by ConseQuence:

I mean yeah, KEX is good, but what makes it better than EDuke32 or ZDoom/GZDoom?

Why don't you ask the devs themselves?

[Supa]

I got mouse problems in the old engines. If I moved my mouse very slowly it would not move AT ALL in the game. Theres also option for real 3D now so the game doesnt look weird when aiming up and down.

[Steven Seagull]

Originally posted by Supa:

I got mouse problems in the old engines. If I moved my mouse very slowly it would not move AT ALL in the game. Theres also option for real 3D now so the game doesnt look weird when aiming up and down.

EDuke32 doesn't have these problems for me and it is the BUILD engine. The OpenGL mode for EDuke32 is what you call "real 3D", it knows this feature since more than 10 years.

[Supa]

Originally posted by Steven Seagull:

Originally posted by Supa:

I got mouse problems in the old engines. If I moved my mouse very slowly it would not move AT ALL in the game. Theres also option for real 3D now so the game doesnt look weird when aiming up and down.

EDuke32 doesn't have these problems for me and it is the BUILD engine. The OpenGL mode for EDuke32 is what you call "real 3D", it knows this feature since more than 10 years.

I have the Steam version of Duke Nukem Megaton edition and Shadow Warrior Redux. Do they use EDuke32 or what? Both games had this problem.

[Steven Seagull]

Originally posted by Supa:

Originally posted by Steven Seagull:

EDuke32 doesn't have these problems for me and it is the BUILD engine. The OpenGL mode for EDuke32 is what you call "real 3D", it knows this feature since more than 10 years.

I have the Steam version of Duke Nukem Megaton edition and Shadow Warrior Redux. Do they use EDuke32 or what? Both games had this problem.

Duke Nukem Megaton is using EDuke32, I'm not sure about Shadow Warrior Redux (but I think it is using that too, because what else?). Make sure you turn v-sync off (if you only have a 60Hz monitor) and raw mouse input is on.

[Steven Seagull]

OK, just forget what I said. I tried DN Megaton edition and I have the same issue too. I tried the World Tour edition and it is the same. That sucks...

But I tried NBlood, which is using EDuke32, and there I can aim normally, I mean even if I move the mouse very little, it will react to it. So, this is not something what couldn't be fixed. Maybe the Megaton and World Tour are using a very old version of EDuke32 or I don't know. But BUILD itself is capable of "normal" mouse aiming (because it is just fine in NBlood).

[Steven Seagull]

Maybe NDS is using the KEX engine because this way they don't have to make the source code of their product public. EDuke32 is GPL so if they used that and modified that they would need to publish the source if anybody requests it.

[>M@tEo$<]

Megaton got some EDuke32 code here and there (polymost, ...)
They were some talk back when the dev was active between General Arcade and EDuke32 devs
Then GearBox took it down to release their shiny thingy

[Magmarock]

Because the best engine for the job is always what the devs are most comfortable with. Engines don't work like most people think.