Counter-Strike: Source Forum

I get white text on a black screen since the update from last week. Wondering if I am the only one or not. If this is a known issue, what is the fix?

[edit]
For the record, I have done a revalidate on my files.
I have also reset all settings to defaults.
No other game that used to work is malfunctional aside from other Source games. Hence my curiosity on what went sour here.
[/edit]

Thanks

Andrew.

Fedora 16 x64
nVIDIA 560 Ti

Hey Andrew!...

....what you describe, seems exactly the same as this...

http://www.codeweavers.com/compatibility/browse/name/?app_id=3379;forum=1;msg=115076

Cheers!

Well if it is the same problem, the solution didn't work.

I did create a new bottle and re-download CSS, and the same thing happened. So either the version of Wine is outdated (likely) or something is wrong with my system.

I am going to try vanilla wine and see what happens there.

...it certainly sounds like the same problem ... I've got a new
system build that I've been strangling some sense into, so I'll
have another look at it now that I have things convinced enough
to run CXG again ... (went too close to the edge and cut myself =)...

Update:

...you know, I was going to say it was a tad presumptuous to
think it was our dinosaured winecore to blame, however, it's
a good thing I bit my tongue and tested first - CS:S is broken
for us it seems -- it's still working (with issues) in wine-1.3.36
(seems like it's not updating server list) but, it doesn't crash
and burn and you can still connect to a server/play via either
your favorites or history lists...

..in linux, I'm getting an error about not being able to load
some file ; on the Mac with cxg 10.2.1 the game actually loads
up, but then you're presented with that 'Pinion' survey BS, which
you can work around, but upon joining a server it crashes with
an unable to load csmeshblablabla.... and it bails...

..so, the speculative among us always guessed and feared this
might happen (hoping it wouldn't) but it looks like it has. Mind
you, I'm of the mind it's all the xmas/holiday and other spamish
junk being piled onto the the game proper causing this, so maybe
another CS;S update to remove all that garbage -might- fix it
again... but I've just had a go at working around it, failed, and
turned to latest wine-devel instead. I suppose a check with a nightly
might be a keen idea...

Cheers!

Artist Formally Known as Dot wrote:

Update:

..so, the speculative among us always guessed and feared this
might happen (hoping it wouldn't) but it looks like it has. Mind
you, I'm of the mind it's all the xmas/holiday and other spamish
junk being piled onto the the game proper causing this, so maybe
another CS;S update to remove all that garbage -might- fix it
again... but I've just had a go at working around it, failed, and
turned to latest wine-devel instead. I suppose a check with a
nightly
might be a keen idea...

Cheers!

OK, Thanks for confirming what I kinda felt it was. Either that or a busted nVIDIA driver. Several fleetmates in STO told me to at least try a downgrade there. They assumed I was on Win7 like them, who are all having issues in more than one way with the new drivers. I politely thanked them, but never could truly dismiss it as a potential vector. That said Diablo 2, STO, DDO, LOTRO, Darkspore, and PWI all work fine. A few are installed in my Steam bottle too, with no issues. So my gut says definitely valves boo-boo, brain says ... drink more Monster ....

Thanks again bro.
Andrew.

..no prob... regarding nvidia drivers, an anecdotal note
here is that I found an apparent bug in an app a couple
of weeks back (characters not being drawn), and I was using
the last/latest of the nvidia 285.xx series, but the app wasn't
displaying the issue on the ati fitted rig here. I updated to
the 290.10 driver set ; problem solved. So while it's fairly
constant banter from the Windows camp about always checking
to see if they have the latest (video) drivers installed,
it would seem definitely the case that us linux users are
going to need do the same thing...{sigh}.. we're owned B)

Cheers!

OpenGL renderer string: GeForce GTX 560 Ti/PCI/SSE2 
OpenGL version string: 4.2.0 NVIDIA 290.10

Well thats what glxinfo has to say at least.

So, I can attest that I am at the latest that rpmfusion has packaged up. Dunno if that is THE latest and greatest, but its what the repo has to offer. But I am glad that I didn't have to fire up my crummy (gaming wise) laptop with OpenSUSE 12.1 on it to see if its a Fedora 16 issue. Wouldn't be the first time. If I wasn't such a Red Hat Whore (TM), I might just go the safe route and stick with a LAN of OpenSUSE workstations and RHEL geek/coder/sysadmin boxes.

Sigh. The fun of Wine-ing :P

...further, after the usual volley-ball match one has when
they haven't touched their macports for a time, I got the
wine-1.3.36 tree installed on the iMac as well. CS:S does
still run there as well...

We have tried this in-house on Mac & Linux machines this morning with the latest version of CrossOver Games (10.2.1) and we are unable to reproduce the black & white screens. We do not have a 560 in-house, but we did try it on a 460 GTX, not to mention two ATI machines.

If you are still seeing this, please submit a Support Ticket so we can further triage this issue.

Hey Caron!!...

...oh, you're too late to have had this fun -- I just rechecked
it now, and the problem is no longer apparent ... but then, neither
is the 'pinion' overlay thing nor the rest of the spam that -was-
appearing at launch (which I posited above may have been the actual
issue) ; now that valve have CS:S back to it's usual makeup, all's
good again ; btw, I did get a trace on the issue .. it was d3d9ex
stuffs being called which seemed to lead to the crashing (and the
-nod3d9ex switch had no effect)...but, all better now ; knowing
Andrew, he'll prolly check & confirm when he reads this =)

Cheers!

edit: 4am dyslexia

Caron Wills wrote:

We have tried this in-house on Mac & Linux machines this morning
with the latest version of CrossOver Games (10.2.1) and we are
unable to reproduce the black & white screens. We do not have a 560
in-house, but we did try it on a 460 GTX, not to mention two ATI
machines.

If you are still seeing this, please submit a Support Ticket so we
can further triage this issue.

I am still running into issues.

I have a log file I made.
http://www.schotty.com/storage/steam-diag-20120103

Let me know what more you all need.

What I did was run Steam.exe from the "Run File" option inside the bottle manager with the standard logging enabled.

I ran and logged into Steam.

I then launched CS:S, started a private server, got in to where if I wanted to gear up and game on I could proceed to do that, and then quit out of Steam and CS:S.

Here are some screenies to illustrate what I am getting at. Perhaps thru this we can narrow down the issue here:

Main Menu
Server started
Game started

[edit]
Ticket submitted:
http://www.codeweavers.com/support/tickets/browse/?ticket_id=872271;layout=user_tickets;sort%5Bstatus%5D=ASC
[/edit]

...you're right, so am I ... just scratching my head a bit,
it would seem my remark above was wrt MacOS. That'd be a
bit typical of me at a 3am wake-up seeing Caron's post above,
in that I tend to think in linux, one has a lot more latitude
to (easily) jump to another wine version, whereas in MacOS,
that's probably not the case and the user needs to do lots
more to achieve the same ends... so, if something like this
happens, if it comes good on the Mac I remark "Phew, not a
drama then" ... =)

...anyhow, on this linux build which is brand new and still
at the toddler stage, CS:S goes to start, I see the menu
background (in color) for a brief instant, then CS:S bails
and I'm left with a small window entitled 'Engine Error',
which displays the text 'Could not load client library' ;
I was seeing this on&off a few days back when this all began...

...so, I'm just currently installing it on the iMac hardware
running Deb6 for a comparo ; I know that hardware can do it
fine with MacOS at the helm, so we'll see what linux & ati
linux prop. drivers go...

..tbh though, I'm not particularly interested in a ticket
on this ; it's all working fine in 1.3.36 and that's where
a lot of my time is going now...

@Caron - feel free to add me to Andrew's ticket tho' if you
need some testing done ..(on any fix which imho is awot =)

Cheers!

Update: ...m'kay, it runs in deb6 on the imac hardware, which
has a hd5670. Halflife2 itself seems uneffected... I'm suspicious
about a (known bug) error I'm getting (system wise, not cxg/app wise)
and I'll have to install deb6 on this rig to crosscheck that..

@Andrew ... just curious, which libc version does your system have?

Update 2: ...and, in Deb6 on the same PC hardware with nv9800gt
& 290.10 nvidia drivers, it works fine as well. That is to say,
when I initially started it, I had a crash in gameoverlayrenderer
(starting a server), so I just disabled in steam and CS:S server
started fine. I even booted into my old (now deprecated) build,
and it's working fine there as well...

...so...{shrug}...while it would be very easy for me to blame
my new handrolled linux system (as I know there's a glibc/gcc
bug there that only seems to affect some 32bit binaries), if I
concede that point, I'm still left holding the situation wherein
CS:S works brill when using wine-1.3.36 (actually runs better
there compared to cxg 10.2.1)... ergo, I'm unfussed here...

...well, I can see the bug chatter, but can't reply there,
which is absolutely correct ; I choose my words carefully..

...however, I'm coming at this from a different angle ; I'm
going to install Debian testing (wheezy) on another partition
and check that. Good thing about (school) holidays here, is the
high-school 100metres away is closed, so we've got oodles of
BW right now =) In as much as I expected it to work in Deb6
AMD64 (and already see it working in Deb6 x86 on the iMac), if
my hunch is right, my gut feeling is it will fail in 'wheezy'
in some manner or form....

...I want to check wheezy anyhow related to something else...

...and it did =) About 7 out of 10 times it will start (a server)
cleanly ; when it fails, one or another scenario pans out...

*it bails with an error about steam application failing to start.
This, is actually akin to my 'failed to load library client' error
(above I got library & client arse about), but it happens to my
build -consistently- because I haven't gone back and jailed this
system (again) to recompile/reinstall gcc, after the last jailing
when I patched eglibc and recompiled it, so the linker bails pretty
early on for me, when cs:s does whatever it's doing...

*it starts, but, it's -really- 'clunky' and jerky as though there's
rocks in the gearbox - if somebody (poor soul ;) joins the server,
it gets weirder and the enemy has a sure advantage, as though only
you are being boxed by the clunkiness ...

*..a couple of times the server started, the menus were misdrawn,
and once the game loaded proper ... it was surreal, in that there
was no way up, I found myself walking/falling through walls/floors,
until suddenly being lost in a realm reminiscent of the 2nd of 'The
Cube' trilogy (HyperCube), before things crashed&burned on following
a pointer to an apparently bad memory address.. but, it was kewl while
it lasted =) ..what can I say, I like the surreal...

...good test tho', I found Wheezy to be spitting and coughing up blood
in exactly the same way my new build is in certain areas, and it's
always fun to see how the Deb folks fixed other things and adopt same
for my own purposes ... but I'll have to see if I can fix gcc first..

edit: no, I haven't futzed with -dxlevel settings - I refuse to! ;)

...and here I am perhaps one last time here, because I've
more or less satisfied myself that whatever it is that cs:s
is doing here in linux (seems fine on the mac), it's exposing
some bug(s) in eglibc-2.13 ; 12454 for one, but after a bit
of tuck&parry here wrt fixing the things mentioned before
with this build, it now behaves exactly like wheezy does with
cs:s currently wrt cxg-10.3.x...

...further, now that I have fixed my little build oversight,
cs:s and wine-1.3.36 are now getting along famously without
something getting stuck in the spokes, and it starts (and runs)
as reliably as it ever did... ergo, I'm just gunna sit stuum
and wait for crossover next (and if I convince myself to rebuild
things, I'll probably have at eglibc 2.14 where a lot of this
brouhaha is changelog fixed)...

Cheers!