http://bugs.winehq.org/show_bug.cgi?id=7644
jordanstudios2934(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Objects apear bright in Half|Objects apear bright in Half
|life 2 except when being |life 2 except when being
|acted upon (being moved (by |acted upon.
|user or by ai), having a |
|flash light aimed at the |
|object) |
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7644
Summary: Objects apear bright in Half life 2 except when being
acted upon (being moved (by user or by ai), having a
flash light aimed at the object)
Product: Wine
Version: 0.9.32.
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jordanstudios2934(a)gmail.com
All the objects that can be interacted with in Half life 2 appear very bright
(washed out) unless I am currently pushing or holding them or if an AI is
holding or pushing the item or when I shine a flashlight on them.
Also, some rocks and building parts have the problem too, but not all of them.
I have tried the following combos in attempting to fix the bug.
Pixel shader: Hardware mode - bug exists
Pixel shader: Emulator - bug exists - game slower
Pixel shader with "UseGLSL"="enabled": bug exists
Pixel shader with "UseGLSL"="enabled" and Pbuffer: bug still exists.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7615
------- Additional Comments From leffeman(a)gmail.com 2007-05-03 15:02 -------
This regression also affects Imperishable Night (verified through bisecting),
causing everything except the playing area to be cleared by black.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7641
------- Additional Comments From dank(a)kegel.com 2007-05-03 14:58 -------
The "bad class name" would be expected if the app
fails to call InitCommonControlsEx with ICC_DATE_CLASSES.
Maybe native doesn't require that anymore, though.
We should probably add a conformance test to see.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7584
------- Additional Comments From stefandoesinger(a)gmx.at 2007-05-03 14:30 -------
Interesting
I don't think something overwrites EndScene's address because it is written in
read only memory. Anything changing it would cause an exception.
But check the d3d? -> d3d7 thunks. They can mess things up
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7615
liquitsnake(a)gmx.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Platform|Other |PC
Resolution|DUPLICATE |
------- Additional Comments From liquitsnake(a)gmx.net 2007-05-03 14:19 -------
Enverex, these are not the same bugs.
I did some regression-testing:
e935600ebc7892bdd48993ecf2455cf10c0d2b1d is first bad commit
commit e935600ebc7892bdd48993ecf2455cf10c0d2b1d
Author: Stefan Dösinger <stefan(a)codeweavers.com>
Date: Tue Feb 20 22:44:12 2007 +0100
wined3d: IWineD3DDevice::Clear fixes.
Fix the use of the scissor test in Clear. The rectangle is only set if
a clearing rectangle is used, otherwise the scissor test is disabled
(the pixel ownsership test should take care of the window
boarders). To get the scissor test back to the value the app set up
Clear dirtifies the state(s).
:040000 040000 3f4fd41874050d0812e4e5629dead3ea7945240d
dd2315ad64125a043e29bc19213eb3b3fa7d045c M dlls
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7643
Summary: Supreme Commander crashes during play
Product: Wine
Version: CVS
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: viriiboxen(a)gmail.com
The game crashes with the following error message:
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 5 0x63db20
0x63db28
If I have the xactaudio DLLs loaded while running the game in order to enable
sound, the crashes happen consistently just as entering gameplay, at the end
of the load animation, whereas without them & thus without sound, the game
manages to load, but later crashes with the same error, usually when trying to
build structures in-game.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3551
------- Additional Comments From kris(a)pcbsd.com 2007-05-03 13:42 -------
Just an update, ran the test on 0.9.32, and it still failed:
../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p
kernel32_test.exe.so thread.c
thread.c:273: Test failed: CreateRemoteThread failed, err=5
thread.c:275: Test failed: waiting for thread failed, ret=4294967295
thread.c:282: Test failed: CreateRemoteThread failed, err=5
thread.c:290: Test failed: GetExitCodeThread failed, err=87
err:seh:setup_exception nested exception on signal stack in thread 0009 eip
9c192c53 esp 00113c30 stack 0x241000-0x350000
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.