Reply 120 of 196, by DosFreak
- Rank
- l33t++
wrote:Tried it your way. Slightly less graphic distortion on Win98SE. Nothing for XP. Having said that, my version is 1.21 (One Whole Unit release).
Just checked your profile. GF3. Have you tried 640X480?
wrote:Tried it your way. Slightly less graphic distortion on Win98SE. Nothing for XP. Having said that, my version is 1.21 (One Whole Unit release).
Just checked your profile. GF3. Have you tried 640X480?
I take it that this pic is explains what a few of use are experiencing ?
I've sent Paul my copy of Blood, so hopefully (When the poor chap gets some time 😉 ) He'll have a look at it.
It's definately nothing to do with resolutions, as I've tried every combination possible.
Athlon 64 3000+ stock
MSI NForce 4 K8N Neo Platinum
2Gb RAM
nVidia Geforce 6800GT stock clocks
SBLive! Platinum + Audigy ZS2 Drivers
WinXP Pro SP2
Ok, I've found out how to make it use your Mouse in Windows, and in a window, NOT fullscreen.
Note, this is in Win9x. Not tested it in Win2k/XP.
2nd Note, DON'T use Paul's newer "mouse" fix. Use the original Blood glidos release.
What you need to do is
goto your Glidos directory
right click the Glidos PIF, and goto Properties
goto Font, and change to "Bitmap Only"
goto Memory, and make sure everything is set to Auto.
goto Screen, and make sure only - "Window", "Display Toolbar", and "Fast ROM emulation" is ticked
goto Misc, and make sure only "Exclusive mode", "Warn if still active", "PrtSc", "Alt+Enter" is ticked.
Now run "Setmain" in the Blood folder, goto Controller setup, Choose controller and make sure Key and mouse is set.
Goto Advanced and Advanced Mouse abd check
Mouse X Axis - analog turning
Mouse Y Axis 0 analog moving
exit, and save settings
Some of the above may already be set, but this worked for me and I now have full mouse control in a window.
Paul, is there anyway you could 'add' a tick box to Glidos, to stop the Glidos PIF from being copied ? One could then have different PIFs for different games.
Athlon 64 3000+ stock
MSI NForce 4 K8N Neo Platinum
2Gb RAM
nVidia Geforce 6800GT stock clocks
SBLive! Platinum + Audigy ZS2 Drivers
WinXP Pro SP2
wrote:Hmmm, my copy is v1.11. Have had it since 1997 but don't remember exactly where I got it from. I simply patched it with the 1.20 3dfx patch.
Then just follow the steps that I posted above....
That's what I thought. So it is highly likely that your copy and the standard Blood on whole unit have differences that would explain why you can run on W2K and lots of people can't.
If you could try out Blood - one whole unit, then probably it wont work for you either and comparisen of the two versions (the cfg files maybe) will show up what the problem is.
What do you mean it seems like it can't find the files? Can you run Blood without GliDos? heh. You know what your doing so I'm not gonna go through the basic troubleshooting checklist. 😉
It works for me only under W98. Under W2k it dies with an error about loading the .dem file headers (weird). If I delete the .dem files it gets a bit further. I get the background of the menus but not the menus themselves. Hitting <CR> the right number of times takes me into the game, but it crashes after dissplayign the "WAIT" screen.
wrote:I take it that this pic is explains what a few of use are experiencing ?
Can anybody confirm that this version of blood has these problems used with GLidos, but works okay with a real voodoo card? It looks like the game is plotting the wrong triangles.
A test with a voodoo card would want to use my blood.bat so as to get the same BUILD_XXXX settings.
wrote:The mouse seems inverted to me and the sensitivity is wrong, plus you really want left/right to strafe when you have a mouse.
That sounds like normal mouse operation in BLOOD. Like most 2.5D shooters, using a mouse-look function is kind of awkward in an environment that's not truly 3D. The game was designed back in the time when "DOOM" controls reigned (Ctrl, Alt, and the arrow keys), so it works best with that and the occasional mouse-shot.
While we're sort of on the subject, Glidos leaves the audio code alone any only affects the graphics right? With that being the case, if you were to get the 3Dfx Shadow Warrior working I'd still have the same stuttery sound as the regular, software SW, wouldn't I?
wrote:GF3. Have you tried 640X480?
Like I said before, yes, I am using 640x480. The only other mode that Voodoo1 would support is 800x600, and GliDOS doesn't match that (it uses 800x640...and yes, I tried that too).
Despite your assertion earlier, I think you having the earlier version is what's making the difference. This patch wasn't made for the "One Unit Whole Blood" version (v1.21). It was actually made for your version, not ours. Like I said, I'm amazed that it starts at all.
Hopefully when this all gets figured out, Shadow Warrior will be a drop-in addition. 😀
"I see a little silhouette-o of a man, Scaramouche, Scaramouche, will you
do the Fandango!" - Queen
Stiletto
wrote:Glidos leaves the audio code alone any only affects the graphics right?
Right. Paul uses VDMSound when running under NT/2000/XP, so you'll get the same results as when you run it normally. About the only thing that might be different is that Paul was able to access the "Tomb Raider" CD audio tracks. So, it might allow you to play the "Shadow Warrior" CD soundtrack.
Damn... Scratch that then...
This is getting ridiculous, just what is it that SW does differently to Duke3D, Blood and Redneck Rampage (although I've only tested demos of the last two but I highly doubt the full verisons would be much different) with the sound code?
Hmmm, Can you guys send me the executabe from v1.21 so I can try that?
wrote:Ok, I've found out how to make it use your Mouse in Windows, and in a window, NOT fullscreen.
Blimey! That works.
What's more if I disable all of Glidos's mouse support, then it works for Descent II.
It doesn't seem to work in W2K though. I'm almost glad it doesn't: the effort I went to putting mouse support into Glidos. If this worked in W2K then it would all have been a waste of time.
Anyway I'd still like to get the mouse buttons working in Blood. Does anybody know whether the source to blood or another build engine game is available? It needs to be the original DOS version. Blood is doing some thing wierd with int 33h. It is being called with ax = fffd, which makes no sense according to Ralf Brown.
Is this all a waste of time? I'm just downloading qblood. This looks like an OpenGL rewrite. Is that what it is, or have I misunderstood?
Nah, it's just Quake with some modified and imported graphics from Blood for multiplayer.
wrote:Nah, it's just Quake with some modified and imported graphics from Blood for multiplayer.
Actually, they worked quite hard on it, but it's still obviously Quake. They spent all that time trying to make 3d models for the 2d weapons and they still don't look as good.
What blood looks like on my winxp (still not sure why it even works?)
What my US version of blood looks like (got both versions):
What are your blood .cfg video settings?
Your glidos.ini settings?
Your openglide.ini settings?
Are you using Glidos v1.19?
Are you using the Openglide that comes with v1.19?
Have you used all of the blood updates that Paul has posted so far?
Which ver of blood are you using again? (Probably already posted but I wanna get it all in one post)
What kind of vid card do you own? Which driver ver are you using?
What does your blood.bat look like?
What does your glidos.bat look like?
Anyway I'd still like to get the mouse buttons working in Blood.
They *do* work, are you talking about in general, Paul ?
Look at this screen from the SETMAIN.EXE, then "Setup Mouse".
Athlon 64 3000+ stock
MSI NForce 4 K8N Neo Platinum
2Gb RAM
nVidia Geforce 6800GT stock clocks
SBLive! Platinum + Audigy ZS2 Drivers
WinXP Pro SP2