Bug 42025

Summary: [RADEON:KMS:R600] wine, Halo Trial: glPointSize error = INVALID_VALUE
Product: Mesa Reporter: Brian Paterni <bpaterni>
Component: Drivers/Gallium/r600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: sa
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Brian Paterni 2011-10-19 20:31:53 UTC 
I'm trying to get the Halo: Combat Evolved Trial to launch on my machine and I'm thinking this may be a mesa bug rather than a wine bug. So I'm posting here first.

The game looks like it launches okay, but as soon as the menu pops up, the game screen starts to flicker different solid colors. I can hear the halo theme in the background so I know the application hasn't crashed entirely.

I've tried mesa's software renderer (llvmpipe). It does not experience the same solid color flickering as r600g does. Although another (unrelated) exception occurs if I do use llvmpipe.

An apitrace of what I'm experiencing should be located here:

http://bayfiles.com/file/18s1/EWVVJ9/halo-trial.trace.gz

You should be able to find the halo trial install/executable online for free somewhere with a google search. I don't think Bungie or Microsoft host the file themselves anymore, but you should be able to find it on one of the many free hosting sites available.

environment info:

Debian unstable/experimental with distro provided kernel 3.0.0-2-amd644
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 7.12-devel (git-3560027)
wine-1.3.30-293-g7fa15c5
Comment 1 Sven Arvidsson 2011-10-20 11:24:08 UTC 
I have played through Halo with Mesa drivers, but this was a while back and with Intel, not Radeon hardware. Still, it's probably worth trying older releases of both Wine and Mesa to rule out regressions.
Comment 2 GitLab Migration User 2019-09-18 18:58:53 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/401.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.