Wolfenstein for Doomsday Released (No support given)
Information:
This is a fragmented release of WolfTC, as is.
That means that there are loads of bugs in it and many texture names needs renaming to fit in and many still needs to done or redone.
Remember, no support will be given.
It only works with Doomsday 1.8.6 as of now.
The source code is lost, and I could only dig up these 2 builds so try and see if you can get it running.
I had issues running it but by running Doom 2 just once first I was able to run WolfTC.
Reason for release:
I am no longer a member of the team and haven't been for quite a while for various reasons I won't go into details with. Some time after I left the project it grinded to a complete halt. So why release a broken and unfinished project?
Well the ultimate reason why this is released is so that maybe the rest of the community could pick the pieces of this project which seems to have exploded and maybe be able to piece together something that might work, maybe even work in the latest Doomsday build, who knows. I and the rest of the team certainly hope to see someone being able to do something with the project so it wasn't developed in vain.
Downloads:
{EDIT DaniJ: link removed}
>>> WolfTC build from 12-01-2007
{EDIT DaniJ: link removed}
>>> WolfTC build from 05-04-2005
{EDIT DaniJ: link removed}
>>> High resolution textures and patches from 12-06-2009
{EDIT DaniJ: link removed}
>>> External music from 09-04-2005
Credits:
{EDIT DaniJ: link removed}
For the team I was a former member of:
I hope you guys wants to see this play out nicely as much as I do and I hope Batteryman, Doom Jedi and Vermil will release what they have so the community might pick it up and make it work, even though the source code is lost.
Most of all I hope there won't be any grudge or struggle between team members or ex-team members, so we can see this release as like planting a seed which will eventually grow into a new project.
Comments
Which is both builds you have posted
I am willing to permit discussion of addons that ultilize resources from other games in Doomsday here out our official forum. However I do not want to see such things released via this forum. Some may remember me "chastising" the Skulltag team for allowing such things on their official forum and it would be rather hypocritical of me to allow the same here, at our forum.
Btw I can't wait for the last 2 exams to be over so I can return to texturing for Doom..
My understanding is that the svn code wasn't as up to date as the packaged code - but svn "worked" with 1.9.x, while the packaged code was 1.8.6 only. It does look like a lot of work to get it running with current doomsday, as so much has changed.
Now with regards to source code and binaries - if a link to that was posted, I'm sure there would would be a lovely legal and ethical mindfield should it be removed. It does appear a link to the binary was posted, two in fact - and it appears that the binaries were distributed to Freelanzer in violation of the GPL as they did not receive the source code, nor any ability to receive such source.
Perhaps it is fortunate that WolfTC as distributed is based on a version of Doomsday that does not contain my code (1.8.6 waas before my time) otherwise I would be demanding very loudly for the license to be honoured. I would like to know the reasoning behind why the binaries were removed - and at Vermil's request is inconsistent with the license terms.
I sent all team members a new build of the TC about once a month. FL posted two of those builds that he received while on the team, without telling anyone. He had no right to release my work without my permission, hence my request to remove the links to my work; the TC itself.
FL's role when on the team was solely making hi-res textures, which, with my consent, he released ages ago completely separate from the TC.
Having recieved the binaries under the terms of the GPL, he is in fact quite entitled to release the binaries, and the source. By all means, feel free to seek legal advice on this, you will find that he can release the binaries and source. What he can not do is release any non-code content he does not own the copyright to - an example would be if you created a texture and he released that - he would be quite wrong to do so, and you could demand, quite rightly, a takedown of that asset.
Unless you had a contract drawn up, where it stipulated that he was creating those works for you, under a works for hire agreement, you'll find that he in fact owns the copyright on his textures, and does not need your consent to do whatever he wishes with them.
Stop twisting my words to say something they aren't.
Lol anyway, seriously.... I dunno what the big deal there is, but I thought that because WolfTC was never distributed no source was required to be included. Isn't releasing it with source as per GPL law a completely different thing to sending testing-builds to his own staff for their dev-work? I mean, it's not released, nor being distributed....
... can we move along now plz :clown:
So Vermil, Is this a dead project or do you think it'll get some progress again one day?
It's dead. It looks like the team tore itself apart, which is a shame, as it looked rather good from what I saw of it.
I stand by my comment, echoed by Joshua, that internal builds released to other members of a dev team do not have to include the source code.
That said, I don't see what you or I have to gain from this little argument about things that are in the past (i.e. whatever we say here, nothing can be done about it now).
Moving on from that, quite frankly, some aspects of the WolfTC files are incredibly dated now. By which I mean that I have since learnt far more effective, professional ways of achieving many things in WolfTC.
I do think that when I return to doing major work on WolfTC, that I will rip out large parts of it and redo them.
All these constant "public issues" (to put it nicely) with the "team" do erode my interest in working on the TC. I haven't worked on the TC in some time and currently have little interest in the very near future. But, as it stands, I personally would rather not publically release my work on WolfTC, rather than release it incomplete.
By comparison, everything is going great with Corr7TC, which as the name suggests is a non-src based Doomsday TC of Capstone's Wolf3D engine based Corridor: Alien Invasion, that I am working largely by myself; a couple of people are helping me with the audio. Makes me wonder if maybe WolfTC is cursed to put it light heartedly.
Certainly, WolfTC has taken on a mythical greatness of sort's to some Dday users that it will probably never achieve. None of the "team" that worked on it, myself included, would have been up to making a mod of such a level of greatness in my opinion.
I'm still planning on "porting" Wolfendoom to Doomsday regardless, kind of a different thing though (from what I read about WolfTC, it was designed to not be a 'remake' of Wolf3D was it - but rather a completely new 'inspired by' TC....?)
Something interesting I thought worth mentioning, even if it's only barely related:
http://www-personal.umich.edu/~jimw/Wolf3D/
EDIT: Wait... is this the same WolfTC found at http://wolftc.yaa.dk/ !?!? [But links to a missing forum thread]?
He actually introduced the site over at NewDoom a while before NewDoom was abandoned, but nothing has been heard from them since.
Indeed, I won't deny that I have wondered if you are the author of that site given some writing similarities?
....Nay, i'm a humble age-old Doom fan who's stayed silent i chose to join in finally since Doomsday has started to become pretty impressive, i've got a lot of spare time lately, and that Newdoom anal rape really pissed me off. The site was barely updated, poorly maintained, frequently offline and slow, yet somehow they bridged many gaps in the Doom community. Then they start demanding money from users AND developers.... Ok lets not dwell on that. I dunno what everyone else thinks, but i thought that was an epic bummer and obviously i'm not quite over it =(
Ah i've gone way off topic =/
...wait, what are you saying about my writing style?!?! Lol
I would disagree with you there.
I don't know why you guys never actually released anything - you shoot it down whenever it comes up. It motivates me to remind you that once you distribute a build you have obligations that come with it.
If doomsday had the same attitude - you would not have had an engine to work on in the first place!
It might be - or you might be one of those people that are better off developing in relative isolation. In anycase we'd love to see Corr7TC when you release it.
Unfortunately we'll never know.
Nice to play Wolf again even though it was the first mission only, but that is enough. I have the original also, with Spear of Destiny, and Both are bloody fucking BORING! Why are you guys even remaking this, and why the fuck are you fighting about it?
Wolf is a piece of ancient history, and will always be more like PacMan than Doom. If you really need to do something, then Commander Keen could sure use a remake.
Did you get that Vermin?
Sweet virgin Mary mother of Jesus, someone should make a Commander Keen FPS.
*glances at thread title* Hmmmm..... <:-P ........ ( <:-P ) :P [:)
Edit : I was up all night and still drunk ::party::
Yeah true, but I'd love to shoot big ol' one-eye green guy (whats his name again) with a blaster right in his stupid face
If the direction of this thread is any indication of how comfortable the authors are on talking about it/revealing details, we'll probably never know.
Still, though... That's a little bit of a tease, no? I thought there were enough resources available to scrap them together into a Wolfenstein 3D TC anyway, aren't there? If you're looking for hi-res sprites, there's the Jaguar version of Wolfenstein 3D with totally awesome ^2 versions! lol...
The pistol looks a lot like Doom's pistol, and the chaingun is almost EXACTLY the same as Doom's chaingun. It was a little ridiculous, but at least it was smoother than the old game.
Anyone here remember Blake Stone: Aliens of Gold? "MEDIC!" It was funny how everyone's head was just tall enough to be touching the ceiling it seemed like.