SW as a base for a Blood "Port"

Stroggos · 09-13-2010, 04:37 PM

I know this is old news another Blood reverse engineering job but just about every port out there is either using Duke3D or building straight onto Build. My question as a programmer is why not use SW as a base for Blood. It has the same and even more features then Blood?

GrimWoman · 09-13-2010, 05:21 PM

Because no one seems to think about these things.

Stroggos · 09-14-2010, 02:41 AM

Really? It just seems so obvious to me.

GrimWoman · 09-14-2010, 07:17 AM

Actually, i believe its because SW is hard to mod and the fact that not alot of people own it would be the reason why there is no Blood TC for SW. Although i'm sure that a SW Blood TC would be the most accurate TC to blood created.

Hendricks266 · 10-08-2010, 05:13 PM

Because it would be just as hard to mod SW as Duke.

IceColdDuke · 10-09-2010, 12:14 PM

Back when I was porting blood I looked at using SW for a blood port but it won't help you out in the long run. The room over room implementation in blood is completely different than the implementation in SW.

my source code is still on sourceforge if you wanted to look at it, I think I stopped when I half way implemented the room over room(or sos what ever it was called).

It wouldn't be easy as drag and dropping the blood maps into SW. There are new structs in the blood maps(xsector, xsprite, etc), that you need to figure out. It's still amazing to me that who ever owns the IP to blood hasn't released the code for it yet.

Damien_Azreal · 10-09-2010, 06:39 PM

Quote:

Originally Posted by Hendricks266

Because it would be just as hard to mod SW as Duke.

This.
SW's engine is just a different from Blood as Duke3D's is. It would be the same amount of work.

Nacho · 10-09-2010, 10:38 PM

To be honest... I think it would be far easier to get a hold of the actual Blood source code then to make one from scratch.

Hendricks266 · 10-10-2010, 01:40 PM

I've tried a couple of avenues to get the Blood source, but I've been met with a brick wall. The most surefire way to get it honestly would be to buy the Blood IP and tell Matt Saettler that you want it released.

Stroggos · 10-11-2010, 03:41 PM

While on the Lith website I have made a small discovery: BLOOD™ Warner Bros. Entertainment Inc.

Josey · 05-15-2011, 02:58 PM

Blood intellectual proprety and legal rights were co-owned by GT Interactive, now Atari (known for a while as Infogrames), and by Monolith, now Warner Bros Interactive... so the rights were left in a kind of legal limbo. This was a very old topic on the blood forum... (now defunct also).

Darkman 4 · 05-15-2011, 10:22 PM

Then why are Blood 1 and 2 being sold on GoG with Atari as it's publisher?

Josey · 05-16-2011, 12:10 PM

Atari owns the distribution rights.

filipetolhuizen · 05-20-2011, 07:45 AM

Let's see how BloodXL performs when it's done. It looks very promising. The XLEngine is quite stable for an Alpha.

09-13-2010, 04:37 PM	#1
Stroggos	SW as a base for a Blood "Port" I know this is old news another Blood reverse engineering job but just about every port out there is either using Duke3D or building straight onto Build. My question as a programmer is why not use SW as a base for Blood. It has the same and even more features then Blood?

09-13-2010, 05:21 PM	#2
GrimWoman	Re: SW as a base for a Blood "Port" Because no one seems to think about these things.

09-14-2010, 02:41 AM	#3
Stroggos	Re: SW as a base for a Blood "Port" Really? It just seems so obvious to me.

09-14-2010, 07:17 AM	#4
GrimWoman	Re: SW as a base for a Blood "Port" Actually, i believe its because SW is hard to mod and the fact that not alot of people own it would be the reason why there is no Blood TC for SW. Although i'm sure that a SW Blood TC would be the most accurate TC to blood created.

10-08-2010, 05:13 PM	#5
Hendricks266	Re: SW as a base for a Blood "Port" Because it would be just as hard to mod SW as Duke.

10-09-2010, 12:14 PM	#6
IceColdDuke	Re: SW as a base for a Blood "Port" Back when I was porting blood I looked at using SW for a blood port but it won't help you out in the long run. The room over room implementation in blood is completely different than the implementation in SW. my source code is still on sourceforge if you wanted to look at it, I think I stopped when I half way implemented the room over room(or sos what ever it was called). It wouldn't be easy as drag and dropping the blood maps into SW. There are new structs in the blood maps(xsector, xsprite, etc), that you need to figure out. It's still amazing to me that who ever owns the IP to blood hasn't released the code for it yet. Last edited by IceColdDuke; 10-09-2010 at 12:20 PM.

10-09-2010, 10:38 PM	#8
Nacho	Re: SW as a base for a Blood "Port" To be honest... I think it would be far easier to get a hold of the actual Blood source code then to make one from scratch.

10-10-2010, 01:40 PM	#9
Hendricks266	Re: SW as a base for a Blood "Port" I've tried a couple of avenues to get the Blood source, but I've been met with a brick wall. The most surefire way to get it honestly would be to buy the Blood IP and tell Matt Saettler that you want it released.

10-11-2010, 03:41 PM	#10
Stroggos	Re: SW as a base for a Blood "Port" While on the Lith website I have made a small discovery: BLOOD™ Warner Bros. Entertainment Inc.

05-15-2011, 02:58 PM	#11
Josey	Re: SW as a base for a Blood "Port" Blood intellectual proprety and legal rights were co-owned by GT Interactive, now Atari (known for a while as Infogrames), and by Monolith, now Warner Bros Interactive... so the rights were left in a kind of legal limbo. This was a very old topic on the blood forum... (now defunct also).

05-15-2011, 10:22 PM	#12
Darkman 4	Re: SW as a base for a Blood "Port" Then why are Blood 1 and 2 being sold on GoG with Atari as it's publisher?

05-16-2011, 12:10 PM	#13
Josey	Re: SW as a base for a Blood "Port" Atari owns the distribution rights.

05-20-2011, 07:45 AM	#14
filipetolhuizen	Re: SW as a base for a Blood "Port" Let's see how BloodXL performs when it's done. It looks very promising. The XLEngine is quite stable for an Alpha.