First post, by Unregistered
I have been trying to run blood 3dfx using glidos,
I can get the start screen to come up but its all distorted and that annoying "glidos" logo come up and crashes!
Is it the logo that crashes the game or the game itself?
I have been trying to run blood 3dfx using glidos,
I can get the start screen to come up but its all distorted and that annoying "glidos" logo come up and crashes!
Is it the logo that crashes the game or the game itself?
Also, blood uses the BUILD engine. (same technology as Duke Nukem 3d)
Originally posted by Unregistered I have been trying to run blood 3dfx using glidos,
You have not given any description of your system; it's OS, processor, memory, video, audio,etc...
Those are needed for almost all troubleshooting.
Also, the 3dfx patched BLOOD is quite buggy and unstable.
Is it the logo that crashes the game or the game itself?
The logo is annoying because it's not free. You pay, it goes away. It's fairly safe to say that the logo does not cause the crash. Almost certainly the reason it crashes is that was originally created for one specific purpose, for one specific game(DOS Glide for Tomb Raider).
Paul has expanded it substantially to cover other games and expanded it's purpose as well. He lists what works on his site.
The 3dfx-patched BLOOD isn't one of them. Why did you think it would work?
As Nicht Sehr Gut says the log can't crash the game. The crashes could be because of Glidos not supporting some part of Glide that the game uses, but it could equally well be instability in the game, especially if it uses both Glide and VESA. Worth a try though. I'll see if I can get a copy.
I bet the problem is in the Build Engine in itself.
It was always too unstable on more recent computers.
I was never able to play it fairly in any Windows version.
Both Blood, Duke Nukem or ShadowWarrior crashed sooner or later, even without 3dfx.
The 3dfx patch for Blood is a joke. It never worked right.
I would disagree with that.
Blood worked well for me, in single and multiplayer.
And I even completed the game in the Glide version.
The reason that it doesn't work is that it needs pure dos, not emulated dos like WinME and WinXP provides. And I think GliDOS doesn't support it properly, anyway.
If you dual boot with Wion98, then at least the game runs without problems.
Craig.
It is worth trying both with and without Glidos's VESA support, although I expect Craig has done that experiment.
I can get the non-3dfx version to work, and I'm geting closer with 3dfx blood everytime I run it but its just really slow, I hope the next version of glidos works fine.
Maybe u should get the build engine souce cod and muck around with it until glidos works on it.
Blood source code was never released...
That´s one of it´s bigger problems.
wrote:I can get the non-3dfx version to work, and I'm geting closer with 3dfx blood everytime I run it but its just really slow, I hope the next version of glidos works fine.
Do you get lots of messages in capitals in the Glidos control window?
Ok, I've got Blood working in WinME now, and I have a feeling a lot more games will now work.
Basically, you have to patch WinME to work with DOS.
There are many around that 'Claim' to do this, but I've only found one that really worked.
It will modify "IO.SYS", "COMMAND.COM" and "REGENV32.EXE"
The filename is MFDDME13.zip
I can now use xmsdsk to create a 128Mb RAM disk for Temp, Temp Internet, and other log/temp files. Which all drastically speeds up WinME beyond any OS I've used.
I will now work on a lot of DOS games that didn't work before.
I didnt mean the blood source code they never released that , I meant the BUILD engine source code.
Its located here:
http://www.planetblood.com/bloodsource/files.shtml
u need watcom C or something to modify it
I have checked the glidos control and glidos has stoped getting messages while the SFX of the game is still playing.
wrote:I didnt mean the blood source code they never released that , I meant the BUILD engine source code. Its located here: http://www […]
I didnt mean the blood source code they never released that , I meant the BUILD engine source code.
Its located here:
http://www.planetblood.com/bloodsource/files.shtml
u need watcom C or something to modify it
Cool.
I did´nt knew that the Build source was out.
Thanx;)
Dream on...😉
I wish it could, too!
The Build Engine does´nt support hardware acceleration...
There was this guys, some time ago, who tried to make GLDuke, never finished it... 🙁
It never worked for me...
wrote:Dream on...;) […]
Dream on...😉
I wish it could, too!
The Build Engine does´nt support hardware acceleration...
There was this guys, some time ago, who tried to make GLDuke, never finished it... 🙁
It never worked for me...
Neither did the Doom engine originally but there are still plenty of accelerated source ports out there for it all because id release the source to pretty much all their engines at some point.
Still, it doesn't really matter to me, all I want is to be able to play Shadow Warrior again, I don't give a toss if its hardware accelerated or not.
Yes, of course, because, beside the Doom Engine source code there are available the Doom game source code, the Heretic source code and the Hexen source code, which are all diferent.
Strife never saw its source code available, and theré is´nt a single port for it, and it uses the Doom Engine too, but extract the sounds from the Strife voice wad is a work for a life time:)
And Blood Source Code is not available!
Do a search on the VOGONS forums. There's some major progress being made on GLDuke.
Yes, it’s my fault.
Screw Duke Nukem, I'm happy enough to play that without any OpenGL eyecandy, anyone know of any decent ports for Shadow Warrior (hardware 3D support isn't a prerequisite)?