Half-Life 2 Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

My HL-2 Experiences So Far...

Suprisingly good!

CW Version:
6.0 (6.0.0)

Rig:
MBP 2.33 15" 2G

Launch Options:
-console -heapsize 512000 -dxlevel 80 -width 1280 -height 800 -window -novid +cl_drawmonitors 0 +r_shadowrendertotexture 0 +r_WaterDrawReflection 0

Graphics Options:
Model detail: High
Texture detail: High
Shader detail: High
Water detail: Simple reflections
Shadow detail: Low
Antialiasing mode: None
Filtering mode: Trilinear
Wait for vertical snc: Disabled
HDR: None

Results:
You'll notice my launch options fire up in a window. This is due to the fact that I can't seem to play full screen. I've tried a slew of varied settings (including DX7) and full screen mode fires up with the dock area blackened which skews my where my pointer "thinks" it is -- and leaves a black bar accross the bottom of the screen the same size as my dock.

Playing in windowed mode works suprisingly well so far. I haven't had a chance to play into the game very far so I haven't pushed the engine very hard. But what I have played has been mostly flawless.

Sound is nice and clear and I haven't had any skips of just sound yet.

I have had what I assume to be disk access pauses, but they are minor annoyances at best (and I seem to recall having them from time to time on my PC anyway).

[And one more edit before anyone replies... I had iMail, Safari, a torrent of CentOS and iTerm all running during testing.]
Uploading screenshots...

Using the same settings as above, except full screen at 1440 x 900, on my Imac First Generation (core duo, ati x1600, 1GB ram)

Went through the movies (white screen, then black screen, audio but no picture) then into "Insertion point". Graphics were ok in game (on the train and at the station) , however upon loading second level, the game crashed. "Microsoft Visual C++ Runtime error, the program HL2.exe asked the runtime to stop it in an unusual way." From memory - sorry - then I had to exit crossover completely to get back to my desktop.

Occasional audio hiccups - sounds repeat themselves like a "stuck robot".

I don't have a screenshot of the crash, as the game had already halted. A dialog had popped up with the above message.

Of course, you can't actually play the game if it crashes like this...

You have to set your dock to auto-hide if you want to play in fullscreen. CrossOver hides the dock when an app switches to full screen mode, but macos still doesn't allow the game to draw on that area for some reason.

Right, that is an issue of with the aqua X window manger we use from the Apple installation CD. We have notified Apple about that bug, there is nothing we can do to fix it on our side.

Jim, those occasional audio hiccups you describe are a known issue on the Windows side, too. It's something with the Source engine.

One additional note:
I was noticing that on stretches of CLEAR water that I would get the skybox problem where it would obscure pertty much everything which, when trying to steer the airboat was nearly impossible.

When I added this to the launch properties
+r_waterdrawrefraction 0
to the end of the string mentioned above, it fixed the problem perfectly. I'm sure this lessens the impact of the game but I could care less, it still looks amazing so give it a try if there is a problem.

Kyle, are you using the ATI driver? We are using the GL auxiliary buffer for offscreen rendering, and the back buffer as a fallback. The ATI Linux driver doesn't do AUX buffers, so it is using the back buffer. Thus the offscreen texture rendering overwrites the data in there, in your case the skybox(the rest of the world is drawn after the offscreen textures, that's why it works).

This is in a certain way a bug in CrossOver. AUX buffers are a terrible thing, we shouldn't use them. We have an alternative codepath using frame buffer objects which does not support them. Unfortunately the FBO codepath has some bugs on its own, and triggers driver bugs on almost all drivers, so we default to the AUX buffer path, since we think the skybox issue is better than plain crashing.

Meanwhile, you can enable the FBO path by setting this registry key:

HKEY_CURRENT_USER/Software/Wine/Direct3D/OffscreenRenderingMode = "fbo"

Save your data before starting the game though. I don't know about any specific fglrx-fbo bugs, but I am not certain that it works fine either.

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzMxNDM1MjAzLCJjc3JmX3Rva2VuIjoic0VzeGd5aGQ4cjJzbVFiSiIsImdkcHIiOjB9