Any news on a Doom 3 DK2?

"danielmguk" wrote:
http://en.wikipedia.org/wiki/Oculus_VR#Conflicts_with_ZeniMax_Media

A very sad state of affairs. It didn't have to be like this. Very sad that people decide on conflict rather than cooperation. They decided to bicker about some trivial matters, instead of saying "Oh well, they borrowed some stuff from us, but that's OK, we're a believer in VR and we're glad to help make it come real! And now here's DOOM 3 IN VR!". No, they hired lawyers instead, and have placed themselves firmly in the trenches. Sadly, if VR takes off and becomes the primary medium for consuming games, it will be difficult for them to move on.

Hi

I too am pretty gutted about this, right back at the start Doom3 VR was so exciting.

has anyone "unofficially" considered working on it?

There's someone who worked on perfecting the DK1 version (forum name 2eyeguy) but I have no idea if he could replicate his work for DK2, I bet a lot of stuff for DK1 was already pre cooked in Doom 3 BFG edition.

I share your desire to try DK2 in this game though, since it was already awesome in DK1!

I would give my left nut to be able to try this out in the DK2 (with proper support). Zenimax shot themselves in the foot big time. :roll:

Here's a project on Github that has SDK v0.3 support:

https://github.com/tmek/DOOM-3-BFG-VR

....may not be too difficult to get it working with SDK v0.4.

Ignoring the whole zenimax thing, the public release of Doom 3's source code is under the GPL license. The rift sdk is not GPL compatible. Unless you are careful how you integrate them, adding rift support to Doom 3 is a license violation.

"kojack" wrote:
Ignoring the whole zenimax thing, the public release of Doom 3's source code is under the GPL license. The rift sdk is not GPL compatible. Unless you are careful how you integrate them, adding rift support to Doom 3 is a license violation.

yay FOSS FUD FTW! :lol:
Just use GPL for any file containing doom3 code and use any licence you want for anything else.
Also you can just fork doom3 into a library release it under gpl and use that.

If you are not redistributing anything, but are compiling from source on your own machine then there's no issue with licence violation, as the conditions of the GPL only apply to distribution.

If you are planning to redistribute the whole thing it's a problem, because the SDK needs to be statically linked. That does create a conflict with the GPL since you are creating a derivative work and according to the GPL, that entire work must have a GPL-compatible licence, which the OVR licence is not.

This means that source code distributions designed to work with (but which do not include) the 0.4 SDK are fine, but it would be a licence violation to compile the game and distribute the binary: anyone that wants the game would need to get the SDK on their own and compile everything from source because you don't have a licence to distribute them together.

That interpretation of GPL licence shenanigans is simply wrong. You aren't creating derivative work as long as you don't release parts of the GPL'ed software under a different licence.

You can use GPLed code as long as you keep it under GPL. That's it. That is essentially what Android does, mid you just because RMS says something doesn't necessarily mean the Law agrees with him...
Again in practice this works like this: Fork Doom 3, modify it so that it compiles into doom3.dll or doom3.so release that under GPL. Then do whatever you want, in any licence you want.

The LGPL/GPL shenanigans are essentially bogus because what RMS wants and the reality are two different things. Proof: almost a billion android phones. If you are now posting "Well Android is essentially illegal." - get out.