Shadow Warrior betas released!
#92 Posted 20 May 2017 - 08:53 AM
This post has been edited by Nancsi: 20 May 2017 - 08:53 AM
#93 Posted 20 May 2017 - 09:05 AM
Nancsi, on 20 May 2017 - 08:53 AM, said:
I use D-Fend Reloaded , it does not matter then if it (dos game) uses dos4gw or not. If all fails, you can get the improved version here
#94 Posted 20 May 2017 - 09:18 AM
Robman, on 19 May 2017 - 09:35 PM, said:
What have you ever done for SW, Myhouse? or are you just a cool guy mouth piece?
#95 Posted 20 May 2017 - 11:01 AM
icecoldduke, on 19 May 2017 - 12:08 PM, said:
nice thread about shadow warrior - then someone has to start this shit up again. Like one entire thread dedicated to it wasn't enough. Good job.
Hendicks: "I sent in betas" - crowd commences ass sucking
Rob "I got the ball rolling by contacting the people needed to get authorization for the alpha/betas to be released" - crowd commences to throw rocks. "Don't take credit!"
This post has been edited by Forge: 20 May 2017 - 11:02 AM
#96 Posted 20 May 2017 - 11:17 AM
Forge, on 20 May 2017 - 11:01 AM, said:
Hendicks: "I sent in betas" - crowd commences ass sucking
Rob "I got the ball rolling by contacting the people needed to get authorization for the alpha/betas to be released" - crowd commences to throw rocks. "Don't take credit!"
Lol so true, not to mention being fought every step of the way by some people in here.
Oh well, mission accomplished - Give your appreciation to Fred, Nigel, Termit and the fine folks who made the game.
#97 Posted 20 May 2017 - 11:52 AM
Hank, on 20 May 2017 - 09:05 AM, said:
Thanks, I'll try it later.
#99 Posted 20 May 2017 - 12:05 PM
Lunick, on 20 May 2017 - 02:35 AM, said:
Can you give more detailed info on how to do this please?
Edit:Nevernind,figured it out.Some of the maps where they test various effects are really interesting.
This post has been edited by KareBear: 20 May 2017 - 01:26 PM
#100 Posted 20 May 2017 - 12:09 PM
Sledgehammer, on 20 May 2017 - 11:58 AM, said:
If you join us, we can make a wonder-bread sushi roll.
I'm having issues with this dosbox. It doesn't like running in full screen - I have limited keyboard and no mouse input until it's windowed.
Probably follow the advice given earlier since I already have D-Fend Reloaded installed - just have to make the profiles.
This post has been edited by Forge: 20 May 2017 - 12:09 PM
#101 Posted 20 May 2017 - 12:23 PM
This post has been edited by Sledgehammer: 20 May 2017 - 12:25 PM
#102 Posted 20 May 2017 - 12:34 PM
I did a 4 hour stream of it yesterday but OBS (I fucking HATE OBS, god I miss FMLE) didn't record, as usual, and for some reason YouTube has no archive of it. If I find it, I'll post it, but I think it's gone for whatever reason.
Movement works better if you get rid of those alien keybinds that some noob set up.
Edit:
Why does this show up on YouTube if I search, but I cannot see it in the creator studio / dashboard? Who cares, I'll fix it.
Anyway, I'd jump forwards by 10 minutes or something unless you want to watch me struggle with a completely untested machine for a while.
Sound setup may crash from time to time, but you should be able to copy-paste the sound setup section of the CFG from a build where it works (i.e. the final) and just start the game. This doesn't always dodge it, my K6 still crashes if I do that, so yeah, prototypes, what did you expect.
This post has been edited by High Treason: 20 May 2017 - 12:38 PM
#103 Posted 20 May 2017 - 12:39 PM
This applies to both d-fend reloded & the version provided with steam
This post has been edited by Forge: 20 May 2017 - 12:41 PM
#106 Posted 20 May 2017 - 12:54 PM
#107 Posted 20 May 2017 - 01:45 PM
Robman, on 20 May 2017 - 12:43 PM, said:
If you're talking about the fix I think you're talking about, I highly doubt it.
#108 Posted 20 May 2017 - 01:58 PM
Forge, on 20 May 2017 - 12:39 PM, said:
This applies to both d-fend reloded & the version provided with steam
I am not sure if the issue is related to this:
Some DOS games may encounter problems if they are run directly in DOSBox. By "directly" I mean dragging the game's executable onto DOSBOX.EXE or starting a D-Fend Reloaded profile where the game is basically added to the autoexec.bat (or the DOSBox equivalent of it). This means the game is started before any key was pressed. Under these circumstances, reading the keyboard port returns a 0. The game's keyboard handler might not handle this properly because normally you'd never get to read a 0 from the keyboard port unless you edit your autoexec.bat to run the game directly after booting. 0 is a strange value to read from the keyboard port because this indicates that a key is currently held down. This may cause some issues, depending on how the keyboard handling is implemented in the game.
A fine example of this issue is Cosmo's Cosmic Adventure. If the game is started AFTER a key was pressed, it will show the episode's title screen, then switch to the credits screen and eventually start the demo playback. If you start Cosmo WITHOUT hitting any key and let it run for a while, it will show the episode's titlescreen, but it will not switch to the credits screen or the demo playback. It will keep showing you the title screen until you press a key. In this example, Cosmo *thinks* you are holding down a key and waits for you to release that key.
#109 Posted 20 May 2017 - 03:07 PM
Forge, on 20 May 2017 - 12:39 PM, said:
I'm still on Win 7 .... long shot, what about ProAsm ? Hendricks266 updated the windows detection a while ago, maybe all it needs now is to include Windows 10?
#110 Posted 20 May 2017 - 03:15 PM
K1n9_Duk3, on 20 May 2017 - 01:58 PM, said:
Could be - but in my case it's the mouse.
Regardless if I hit the mouse key or just let the game go hands off - SW will go through all the load screens until it gets to the game menu. Once I get to the menu, that's when the fun begins. If I let the game go hands free - I can scroll through the menu with the keyboard normally. If I hit a mouse button any time during the game loading process - I get one arrow press down from my keyboard - (which makes it jump down to the 'save game' selection) then nothing. No more input response until I window the game.
If I let it load hands free until the menu and hit a mouse button - the selection goes to "play it on ten" then no more input response
I think it's just windows 10 being a piece of shit because I never had this problem with dosbox on windows 7
This post has been edited by Forge: 20 May 2017 - 03:25 PM
#111 Posted 20 May 2017 - 03:18 PM
If dosbox freezes, chances are that the emulation failed.
I think the newer build refused to boot with SB pro and needed 8bit DMA instead of 16bit. Selecting 1.0 for SFX will do.
With dosbox, I tend to use 486_slow, fixed 90k ~ 150k ~200k cycles depending on years and et_4000 (but using s3 optimized or buffered if et4000 from setup flickers).
#112 Posted 20 May 2017 - 03:21 PM
Hank, on 20 May 2017 - 03:07 PM, said:
Isn't that what shadow warrior classic redux on steam uses?
I've played the steam redux version and it runs fine, but I don't recall ever specifically downloading and using that port straight from his site.
#113 Posted 20 May 2017 - 03:33 PM
Went to the game's d-fend profile and unchecked "auto lock mouse" - problem gone & now I can use my mouse on the menu screen
dosbox_swarrior.conf
[ sdl ]
autolock=false
This post has been edited by Forge: 20 May 2017 - 03:38 PM
#114 Posted 20 May 2017 - 04:27 PM
http://i.imgur.com/YvetgSu.gifv
- Apparently GIFs aren't allowed... Hell yeah!!!
#117 Posted 20 May 2017 - 08:33 PM
icecoldduke, on 20 May 2017 - 05:01 PM, said:
Given that both the retail release and the betas are freely available, I don't see why you couldn't.
#118 Posted 20 May 2017 - 08:59 PM
K1n9_Duk3, on 20 May 2017 - 01:58 PM, said:
Some DOS games may encounter problems if they are run directly in DOSBox. By "directly" I mean dragging the game's executable onto DOSBOX.EXE or starting a D-Fend Reloaded profile where the game is basically added to the autoexec.bat (or the DOSBox equivalent of it). This means the game is started before any key was pressed. Under these circumstances, reading the keyboard port returns a 0. The game's keyboard handler might not handle this properly because normally you'd never get to read a 0 from the keyboard port unless you edit your autoexec.bat to run the game directly after booting. 0 is a strange value to read from the keyboard port because this indicates that a key is currently held down. This may cause some issues, depending on how the keyboard handling is implemented in the game.
A fine example of this issue is Cosmo's Cosmic Adventure. If the game is started AFTER a key was pressed, it will show the episode's title screen, then switch to the credits screen and eventually start the demo playback. If you start Cosmo WITHOUT hitting any key and let it run for a while, it will show the episode's titlescreen, but it will not switch to the credits screen or the demo playback. It will keep showing you the title screen until you press a key. In this example, Cosmo *thinks* you are holding down a key and waits for you to release that key.
When it comes to DOSBox I'd much rather use custom config files for each game... In Build games for example it's a good idea to use fixed cycles because there's major sprite clipping if you use unlimited cycles, but you need a high amount of cycles to get good fps (100k at least, with a beefy machine of course, especially for Blood and Shadow Warrior).
#119 Posted 20 May 2017 - 10:23 PM
icecoldduke, on 20 May 2017 - 05:01 PM, said:
Doom64hunter, on 20 May 2017 - 08:33 PM, said:
Even though the game is free, don't redistribute the game or full GRP file on your own. And of course, you can use resources from the game and betas for your mods and projects that comply with fair use doctrine.
This post has been edited by termit: 20 May 2017 - 10:23 PM