Glock has somewhat missing texture (pink/black blocks)
.357 has missing texture
stationary “toxic waste” (that green stuff) has missing textures
There’s a constant wireframe over my view, even at the main menu
In some bodies of water (for example the one beneath the green 3 headed thing) if i go underwater i cant see anything aside from a pink/black checkerboard pattern[list]
[]NPC’s eyes replaced with pink/black squares
[/:m][/list:u]
I have checked to make sure everything is under “…sourcemods/BMS” and i used the .exe installer. Below i have attached a screenshot of the Glock/wireframe issue
Have you tabbed out recently? Source has a weird missing texture glitch for normals and cubemaps when you tab. Usually solved by tabbing out and back in again.
Ok so i tried lowering the graphics settings a bit, checked to make sure i did have directx 9.0c, still having the same problems, and a lot of lag. my specs are:
Pentium 4 w/ hyperthreading @2.8GHz
Nvidia GeForce FX 5200 Ultra video card
2 GB RAM (from what i remember im not at my computer)
It never had any trouble running Source games before…
same issue here. I am running in linux, though. The game says Hardware: directx8.0 Software:directx 9.0
I have installed directx9.42 using winetricks.
The erros I see are:
The whites of peoples eyes.
Some sewage/waste that you see in the opening sequence while you are riding the trolly
when you fill the sewer with water and you go underwater the entire screen becomes the pink/purple squares
Here is a screenshot
You’re not an experienced Linux user obviously :-).
Details DO MATTER. What is the distro you’re using? What’s your hardware, most importantly - what GPU do you have? If that’s nVIDIA or AMD/ATI - do you use binary-blob drivers supplied by the GPU vendors or not? If not - first thing to do is to disable kernel mode switching and install binary blob drivers from your GPU vendor. If you’re on Ubuntu or its derivate (like Mint) you could get by using xorg-edjers ppa and installing nvidia-current package from there. For other distros like Fedora driver installation procedure would be a bit different (and possibly harder).
Then, what Wine version do you use? I highly recommend sticking with latest 1.4.x release or - if you feel adventurous - with latest 1.5.x version from development branch. I prefeur to compile Wine myself but it’s not something that everyone would want to do. There are a lot of PPA’s for ubuntu and debian with latest Wine binaries.
Next, you would have to force the game into using non-HDR dxlevel90 renderpath. Add -dxlevel 90 to the command line parameters of the Black Mesa, start it up, navigate to the advanced video settings dialog and disable HRD (i.e. set it to “None”). Then quit the game and remove “-dxlevel 90” from the game startup commandline.
What else you might want to install into your Wine prefix using winetricks: is a “d3d9x d3dcompiler_33 d3dcompiler_34 d3dcompiler_35 d3dcompiler_36 d3dcompiler_37 d3dcompiler_38 d3dcompiler_39 d3dcompiler_40 d3dcompiler_41 d3dcompiler_42 d3dcompiler_43”.
I hadn’t checked if any of these are really required by BM but it won’t hurt to have them in place.
Last but not least: use a separate wine prefix for BMS. If you have any other games installed/used with the same wineprefix you try to play BMS with - make sure to create a new one for BMS. If you’re in doubt about what the wineprefix is - google for it and make sure to read Wine users guide docs.
The FX 5200 does not officially support Direct X 9.0, the rest of the 5xxx series do, but the 5200 was too cut down to make it cheap, anyway that card was old in 2007 when Vista came out, you had to use a trick just to enable Aero glass, why the heck are you still using that card? Get yourself a Geforce 8400 for 40$ and enjoy way more performance.
judging by some of the steps I took it must be my graphics card. Granted I only bought this PC for web/graphic development. Just figured I’d check out this game since I was a big HL fan.
Here are my stats
Intel® Ivybridge Mobile x86/MMX/SSE2
8gb ram
quad 2.5
game runs smooth with almost everything up full blast, until I hit those few problem areas.
If decyphering that means that you’re on a laptop equipped with quad-core Intel Core i7 CPU and you don’t have any dedicated GPU from AMD or nVIDIA in it and coupled with the fact that you’re on linux (opening up terminal, executing “lspci” and “cat /proc/cpuinfo” pasting here the output could be helpful) makes me believe that you’re generally out of luck playing this game flawlessly. Intel’s GPU drivers for linux are one of the best among OSS drivers but they are far from perfect WRT API support. OpenGL 3.0 support had been achived about two months ago and you have to manually rebuild from scratch half of the system (including libdrm, kernel, xserver and xserver-intel-ddx) and you would have to use third-party lib to get s3tc support (which is illegal to use in some countries due to patents concerns). It’s something that is too much to be handled by and an average PC user really so I’d suggest you to temporarily install trial version of the Windows 7 and play the game with it - you’d have ~30 days of the Windows “Activation period” which you could use to happily play BMS all the ways through.
thanks for trying to help. I am on a laptop. I5 actually, but its showing as a quad, could be a mistake… I have a copy of windows installed too, just hate booting into it (actually I don’t think I’ve booted into it since I bought the computer) Here is the output from lspci
and from cat /proc/cpuinfo
thanks for trying, I did try all of the directx installs from winetricks also. Game is still showing up as directx9.0 but same errors. Doesn’t matter what the graphic’s settings are.
Well, you’d better went on with booting into it to be able to play the BMS more-or-less normally (to the extent it’s possible with the low-power laptop CPU and integrated in CPU GPU, Intel HD Graphics 4000 in your case). Linux support for Intel GPUs isn’t that perfect yet especially if you isn’t a an engineer who is capable of rebuilding kernel and all other Mesa-related stuff from the bleeding edge git branches.
Actually you shouldn’t install any parts of the native DirectX under Wine unless it is absolutely necessary and you really know what are you doing and why. Most “magic” behind the DirectX on Windows in really implemented in GPU drivers with the DirectX redistributable being mostly a simple “bridge” beetween drivers and applications. On linux Wine pretends to be Windows and implements most parts of the DirectX and GPU-driver-Dirext-X-emulation stuff by itself (in form of wined3d library which essentially is a D3D->OpenGL translator). So for the worst case the only parts of the native DirectX you might need to use (and install using winetricks) are d3d9x_XX.dll utility libs and d3dcompiler_XX.dll HLSL compilers which are not (yet) implemented in Wine to be in functional parity with the native DirectX counterparts.
Well, that’s enough offtopic info for this thread though, so let’s summarize: for your case it’s better to boot into Windows to play the game. And don’t expect it to perform amazingly well on your hardware as Intel HD 4000 isn’t a really great GPU for this game. Expect frequent FPS slowdowns.
Founded in 2004, Leakfree.org became one of the first online communities dedicated to Valve’s Source engine development. It is more famously known for the formation of Black Mesa: Source under the 'Leakfree Modification Team' handle in September 2004.
