Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DoD:S] Server using sv_pure 2 or sv_pure 1 causes client crash on mapchange. #343

Closed
f64 opened this issue Apr 27, 2013 · 3 comments
Closed

Comments

@f64
Copy link

f64 commented Apr 27, 2013

No description provided.

@f64 f64 closed this as completed Apr 28, 2013
@f64
Copy link
Author

f64 commented Apr 28, 2013

For server's using +sv_pure 1 or +sv_pure 2 in the startup command line, clients will see many CMaterial::PrecacheVars: errors on a mapchange and will crash once an offending texture is shot.

I've only observed this behavior when changing to the same map.

Processor Information:
Vendor:  GenuineIntel
Speed: 4013 Mhz
4 logical processors
4 physical processors
HyperThreading:  Unsupported
FCMOV:  Supported
SSE2:  Supported
SSE3:  Supported
SSSE3:  Supported
SSE4a:  Unsupported
SSE41:  Supported
SSE42:  Supported 

Operating System Version:
Windows 7 (64 bit)
NTFS:  Supported
Crypto Provider Codes:  Supported 311 0x0 0x0 0x0

Video Card:
Driver:  NVIDIA GeForce GTX 470
DirectX Driver Name:  nvd3dum.dll
Driver Version:  9.18.13.1422
DirectX Driver Version:  9.18.13.1422
Driver Date: 14 Mar 2013
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 59 Hz
DirectX Card: NVIDIA GeForce GTX 470
VendorID:  0x10de
DeviceID:  0x6cd
Number of Monitors:  1
Number of Logical Video Cards:  1
No SLI or Crossfire Detected
Primary Display Resolution:  1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 26.65" x 15.00"  (30.55" diag)
                                        67.7cm x 38.1cm  (77.6cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 1279 MB
Supported MSAA Modes:  2x 4x 8x    
Sound card:
Audio device: Speakers (VIA High Definition A

Memory:
RAM:  8190 Mb

@f64 f64 reopened this Apr 28, 2013
@ghost ghost assigned zpostfacto Apr 30, 2013
@zpostfacto
Copy link

Fix is going to be released in a prerelease build today. If no major problems, will ship to main branch tomorrow.

@zpostfacto
Copy link

Fix has been released several days ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants