Doom 3 engine release and game code

[raynorpat]

I have my reservations about GLSL backend. It's been 5 month and it seems all projects are in a coma.

Working on quake is a lot more fun though.

There is no clear indication to why GLSL has to be implemented. I bet rewriting ARB shaders to replace the original ones would be way less work.

I think mainly it's because of GPL concerns, but this is a valid point. Rewriting the original ARB shaders would be nice and quick, maybe a few hours worth of someones time.

Looking towards the future though, it's GLSL all the way. Like mh said, ARB shaders are limited and a lot of people, especially on the Doom3World forums, want more. Imagine trying to do some of these: [url]http://renderwonk.com/publications/s2010-shading-course/[url] with ARB shaders, you'd be burnt out in no time.

[motorsep]

Aye, someone have already rewritten ARB shaders I just wish there was a way to get depth buffer without modifying the engine

Btw, are you planning in finishing your GLSL backport ?

[raynorpat]

Don't think I probably will finish it anytime soon unfortunately since it was more of a quick challenge when I was unemployed for a while.

Working on quake2 is more gratifying for me right now

[motorsep]

That's why I got these ARB shaders, cos I've had a feeling Doom 3 won't get GLSL any time soon

[mh]

ARB shaders aren't that difficult to write, but still not as nice/easy to work with as a real high-level language though. But still straightforward enough once you get over the initial "WTF is this?" reaction. The big stumbling block is GPL concerns though; the original shaders were part of the game content and the game content is still under it's original license, so you can't just rewrite the existing shaders and release them. What you could do is take the nv20 and/or r200 paths, which are shader-based but contained entirely in the GPL source, and translate those to a different shading language. You're still screwed on custom materials but at least you'd have the core interaction stuff.

mh, do you have a theory on why ARB to GLSL translator hasn't been implemented yet?

I had thought about doing one myself, but didn't bother in the end after I realised that I wasn't going to be working much on this code. The idea still interests me a little, but not sufficiently to actually break out the editor. I'm amazed that at least one of the GPU vendors doesn't provide something though.

[motorsep]

Eeh, yeah, I can learn from ARB shader that is proprietary and create my own. It's just a math and it will be the same for third-party shaders. There is no way the case could go to court and even if it does, it would be very hard to win it.

In other words, these shaders I have now are written from scratch, but are compatible with Doom 3 / RoE. So why wouldn't we be able to release them under whatever license we want to (or just use them for production) ?

[Spirit]

ARB -> GLSL can be done by http://icculus.org/mojoshader/ if I followed icculus' talk correctly.

[motorsep]

ARB -> GLSL can be done by http://icculus.org/mojoshader/ if I followed icculus' talk correctly.

Well, I wish I was a programmer

[motorsep]

Sent some pm's, please check

[revelator]

poking a bit on the mojoshader (hmm fails with mingw compilers cannot find libraries ouch) :/.

Got your pm motorsep ill make a diff of my current work.

[JasonX]

https://github.com/dhewm/dhewm3

[motorsep]

yeah, that's what we use, but there is no GLSL backend. Also the author created a patch for aggregated GLSL backend work (raynorpat's and logical error's put together), but it's still the same half-way done GLSL back end.

[revelator]

<not related to the above but i discovered a big whoops by the ID folks

#define ID_STATIC_TEMPLATE static was used as a template for __forceinline well you cannot do that as __forceinline is allready static by nature. msvc lets it pass but both mingw and intel refuses to compile this xD.

In regards to motorseps issue im still working on it but someone more used to shader code might have better luck adding the missing parts (two or so functions missing).

[motorsep]

Btw, has anyone started porting mfc stuff for the editors to qt or something similar ? Otherwise we will end up without tools because mfc only supported with commercial MSVC (not Express).

[revelator]

Havent looked into it myself but i remember earlier in this thread that the darkmod folks had created a working standalone editor for doom3
In case others need to convert MFC code to wxwidgets for crossplatform i do have a handy macro for visual studio that does a lot of the work.