Doom 3 engine release and game code

[motorsep]

What is the target PC your are trying to boost performance for?

[revelator]

atm my own i7 950 +2x 560 gtx in sli and 24 gig system ram.
Yeah might seem like a lost cause with a monster like that but with all the eyecandy on + sikkmod even this rig crawls hehe.
So im not lying when i say that crysis has no beat on the doom3 engine in fact one might consider the crysis engine to be rather nicely optmized for the amount of detail its capable of.

[revelator]

Hmm spotted another bugger.

static bool R_ClipLineToLight( const idVec3 &a, const idVec3 &b, const idPlane frustum[4],
idVec3 &p1, idVec3 &p2 )

frustum[4] might lead to array owerflow the correct one is frustum[6] even if the function only uses 4 planes

[mikehayes85]

[revelator]

[revelator]

Atm uploading an installer for my engine with wrapper executables for starting the game with sikkmod by default.

Hang on to yer gfx and run for your life its seriously detailed.
Also seems i somehow got parallax occlusion mapping working by reordering a few things -> me.

Will be ready sometime tomorrow.

[revelator]

Ok one bug report for mh in regards to mapbufferrange. Seems it causes some problems on ATI cards got several reports of the engine dropping fps to 2 with that codebit.
strangely enough its actually sppeds up nvidia cards (not by alot but around 6 - 7 frames) well everything counts .

[mh]

I've a new chunk of code that handles that cleaner but it'll be a coupla days before I can post it.

[revelator]

No rush m8 atm im working like a dog on a new glsl backend but its a bitch to get running (ported from mc faddens engine but it uses opengl / ES arrrrrgh)
still no material shaders but his backend has some nifty things also it uses a strict uniforms in draw_common.cpp and tr_renderer.cpp (callbacks to the glsl renderer).

Some of the ES functions are quite a headache though :S

[mh]

Try this for size: http://pastebin.com/rHrwP0nA

It'll need some work to integrate into any other codebase, but it should be obvious what was done.

Currently in GLSL version hell.

[revelator]

[revelator]

Ok tested it and seems to work rather nicely one remark though the r_reuseVertexCacheSooner was set to the debug value which i guess was not intended ? so i changed it to 1.

[motorsep]

Any significant gain in performance?

[revelator]

a bit 10 or so frames with the heavy stuff on.

i toyed a bit with the constants and static const int FRAME_MEMORY_BYTES = 0x4000000; // upped to 64 mb from 2 mb
proved to gain me a massive speedup 60 fps with pom and ssao woaaa.

[r00k]

Is there a wiki for the doom3 gamecode? I really havent even looked at the source, but would like to tinker with a quake1 mod in doom3-land.
id Tech3 is fueling QuakeLive, but if one was to make a doom3 mod worthy and popular I think using Quake1 gameplay would beat QuakeLive, at the next level.
Kinda like making Quake%Redux backwards, by releasing the multiplayer 1st then work on singleplayer if acceptance is positive. Or if anything just to showcase a modded D3Engine.

Ack! now i need to learn c++

Wait ive had too much vitamin B, I should just use DP/FTE :O