zBlock 3.0.0 (Final) Released

JB · January 18, 2007, 08:31:02 AM

The minimum's actually 8.1 guys, anything below that is stopped.

Whitey · January 18, 2007, 08:32:04 AM

But isn't zBlock only checking what version of DirectX is running on your system and not what your card supports? :g:

I've done lots of reading and not found a definitive answer. It looks like older cards could have a drop in frame rate going from DirectX 8 to 9 though, but this shouldn't be an issue if you upgrade to 8.1.

I doubt many people could play source on a card that only supports DirectX 7, so this may not be an issue. Time for a poll in the main forum or do we just put up a post saying "Make sure your DirectX level is 8.1 or above"?

JB · January 18, 2007, 08:39:01 AM

Correct mr Whitey sir, also released yesterday at 10pm was a new version of zblock which supports dx level 8.0 and a few bug fixes.

Post in the CSs forums on ED about it.

Anonymous · January 18, 2007, 09:55:33 AM

k version 3.0.0 replaced by version 3.0.1

Can people please try this out?

Whitey · January 18, 2007, 08:19:37 PM

BK is running DirectX 9.0c according to dxdiag and he's not getting the DirectX error now but he is getting the one about cl_restrict_server. I've asked him to type in the console command to see if that works.

Blunt · January 18, 2007, 08:30:45 PM

I just tried and was kicked with the message

disconnect: kicked by console: zblock-'cl_restrict_server

running divx 9.0c

edit: just did console command cl_restrict_server_commands 0 and Im in

Anonymous · January 18, 2007, 08:34:45 PM

I've removed zBlock until we decide on a way forward. Whether the way forward is to forget zBlock, ask everyone who visits MH to add the necessary line to their configs (like that'll work yeah!) or do we setup a separate game server with zBlock so that MH and Boomer are unaffected by this crap!

Whitey · January 18, 2007, 08:48:15 PM

BK got in as well, after entering the command.

I'm not sure of the best way forward here but we need zBlock for matches on ED.
Can you put it back on Meathook for the match on Sunday?
The seperate match server sounds ideal but seems overkill for the amount that Meathook gets used.

Anonymous · January 18, 2007, 09:04:15 PM

Well I'm a great one for keeping things simple and the hardware has LOADS of horsepower so I've setup Baldric as a CSS Match Server with zBlock in it. We now have 3 CS:S Servers:

Meathook (Private, Custom Maps) - 87.240.138.21:27015
Baldric (Matches, Standard Maps) - 87.240.138.21:27017 - zBlock running
Boomer (Public, Standard maps) - 87.240.138.21:27019

NB, If you are going onto the match server you MUST have:

cl_restrict_server_commands 0

in EITHER your config.cfg, your autoexec.cfg or your userconfig.cfg. Wherever it is, it is best set BEFORE you connect to the server.

You might need to update ED pages with new IP details of baldric.

DuVeL · January 19, 2007, 07:09:18 AM

Quote from: BlueBall;173797Well I'm a great one for keeping things simple and the hardware has LOADS of horsepower so I've setup Baldric as a CSS Match Server with zBlock in it. We now have 3 CS:S Servers:

Meathook (Private, Custom Maps) - 87.240.138.21:27015
Baldric (Matches, Standard Maps) - 87.240.138.21:27017 - zBlock running
Boomer (Public, Standard maps) - 87.240.138.21:27019

NB, If you are going onto the match server you MUST have:

cl_restrict_server_commands 0

in EITHER your config.cfg, your autoexec.cfg or your userconfig.cfg. Wherever it is, it is best set BEFORE you connect to the server.

You might need to update ED pages with new IP details of baldric.

You can use console for it: start op Source, before the game press: ~
Then type: cl_restrict_server_commands 0

Anonymous · January 19, 2007, 07:59:24 AM

Quote from: DuVeL;173826You can use console for it: start op Source, before the game press: ~
Then type: cl_restrict_server_commands 0

but if its in your configs then you never have to worry about it again (until Valve change things :sideways:)