http://bugs.winehq.org/show_bug.cgi?id=10206
Summary: Crysis has huge graphical errors on certain systems Product: Wine Version: 0.9.48. Platform: PC URL: http://www.fileplanet.com/168866/160000/fileinfo/Crysis- Demo-(Singleplayer) OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P3 Component: wine-directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: l_bratch@yahoo.co.uk
Created an attachment (id=8816) --> (http://bugs.winehq.org/attachment.cgi?id=8816) Screenshot from the start of the game
Crysis fails to render properly at all for me (see attachment), whereas on other systems, such as this user's (screenshot from the same section):
http://appdb.winehq.org/appimage.php?iId=14046
It looks fairly good.
The only difference is that that user is running a Geforce 8600 GT and I am running a 7900 GTX. Same Wine version and settings, and same driver version.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #1 from Luke Bratch l_bratch@yahoo.co.uk 2007-10-28 09:39:55 --- Created an attachment (id=8817) --> (http://bugs.winehq.org/attachment.cgi?id=8817) Screenshot from gpu benchmark
A handy tip for testing the game, it's much quicker to get to a place where it's trying to render by using the benchmark:
wine crysis.exe -DEVMODE +map island +exec benchmark_gpu
Attached is a screenshot from there.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #2 from Roderick Colenbrander thunderbird2k@gmx.net 2007-10-28 09:44:14 --- Watch the console for glsl warnings. The difference between a Geforce6/7 and a Geforce8 can be really big. In short the latest dx9 games stress the shader engine to the max capabilities of shader model 3.0. Lots of games consume about the maximum number of 'constants' (uniforms). To emulate differences between d3d and opengl we are 'eating' some of the constants. This causes less constants to be available to the game and if the game was nearing the limits this can cause serious problems. Quite a number of modern games are affected by this (including UT3). Not much can be done about this. Geforce8 cards offer a lot more constants (because SM4.0 requires this) and for that reason don't see these issues.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #3 from Luke Bratch l_bratch@yahoo.co.uk 2007-10-28 09:53:35 --- Created an attachment (id=8818) --> (http://bugs.winehq.org/attachment.cgi?id=8818) Console output
Are the kind of errors you described the kind that can be seen in the log there?
The err:d3d_draw:drawStridedInstanced error carrys on forever as long as the game is running.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #4 from Luke Bratch l_bratch@yahoo.co.uk 2007-10-28 10:51:13 --- Some discussion on this game's AppDB page suggests that 8 series cards are having the same problem, for instance this screenshot from an 8600GT:
http://appdb.winehq.org/appimage.php?iId=14067
http://bugs.winehq.org/show_bug.cgi?id=10206
Chris Spencer spencercw@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spencercw@googlemail.com
--- Comment #5 from Chris Spencer spencercw@googlemail.com 2007-10-28 10:54:55 --- (In reply to comment #4)
Some discussion on this game's AppDB page suggests that 8 series cards are having the same problem, for instance this screenshot from an 8600GT:
I get that same issue with a 6800XT.
http://bugs.winehq.org/show_bug.cgi?id=10206
Andras Kovacs andras@csevego.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andras@csevego.net
--- Comment #6 from Andras Kovacs andras@csevego.net 2007-10-28 13:06:46 --- set everything to high in graphics settings:
http://kukac.sth.sze.hu/~andras/wine/crysis
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #7 from Luke Bratch l_bratch@yahoo.co.uk 2007-10-28 13:44:35 --- Everything on high looks different, but is still uncomprehendable.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #8 from Luke Bratch l_bratch@yahoo.co.uk 2007-10-28 13:44:56 --- Created an attachment (id=8827) --> (http://bugs.winehq.org/attachment.cgi?id=8827) Graphics settings on high
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #9 from Luke Bratch l_bratch@yahoo.co.uk 2007-10-28 13:45:20 --- Created an attachment (id=8828) --> (http://bugs.winehq.org/attachment.cgi?id=8828) Graphics settings on medium
http://bugs.winehq.org/show_bug.cgi?id=10206
Jack Harra lukas.gorris@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lukas.gorris@gmx.de
--- Comment #10 from Jack Harra lukas.gorris@gmx.de 2007-11-10 08:43:00 --- (In reply to comment #6)
set everything to high in graphics settings:
Hi people. I get very similar behaviour with the graphical issues like Mr Kovacs: See appdb for my screenshots http://appdb.winehq.org/screenshots.php?iAppId=5880&iVersionId=
2-8 are from my system. Stuff set to low I get no objects and ntohing rendered corrrectly in the dark places. When light effects get into focus, screen is overbright 3/4 (see http://appdb.winehq.org/appimage.php?iId=14075). A good comarpision between high and low shader settings are last two shots: low: http://appdb.winehq.org/appimage.php?iId=14076 and high: http://appdb.winehq.org/appimage.php?iId=14077
Low looks like pile of poo and with high settings you see almost everything but extreme over hdr issues.
My vga is 8600 GT with 256megs
Playing on low I get a decent fps but on high it is unplayably slow. (well on low also not playable because of you see nothing. except of effects when you get hit by enemies ^^)
Hope I could help.
greetings, lukeg
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #11 from Jack Harra lukas.gorris@gmx.de 2007-11-10 08:54:14 --- wine crysis.exe -DEVMODE +map island +exec benchmark_gpu
everything set to low except of shaders to high.
4fps everything overbright / over hdr or whatever some textures drawn red some textures have moving stripes on them without those issues it would look great
I get this kind of output the whole benchmark
reams specify a different number of instances. Got 2, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 13, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 9, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 8, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 17, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 10, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 9, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 2, new is 0 err:d3d_draw:drawStridedInstanced Two streams specify a different number of instances. Got 9, new is 0
greetings, luke
http://bugs.winehq.org/show_bug.cgi?id=10206
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kgbricola@web.de
--- Comment #12 from Rico kgbricola@web.de 2007-11-24 14:25:19 --- Hi,
I got a lot of these errors: err:d3d_surface:surface_prepare_system_memory Surface without memory or pbo has SFLAG_INSYSMEM set!
I have always these graphic glitches (shadow on the upper half of the screen) http://appdb.winehq.org/appimage.php?iId=14076 This looks like the same error like this one: http://bugs.winehq.org/show_bug.cgi?id=9717
My system configuration: VGA: 8800GTS WINE: 0.9.49 VGA DRIVERS: 100.14.19
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #13 from Luke Bratch l_bratch@yahoo.co.uk 2007-11-29 10:46:52 --- It might be worth noting that the ultra low framerate only occurs when it isn't the first run.
On the first run, the framerate is very good (around 20 fps) but the graphical errors are still there.
On subsequent runs, the framerate drops to less than 1.
Deleting the ~/My\ Games/Crysis_SP_DEMO/ directory that the game creates resets it to its "first run" status.
That directory contains a /Shaders/Cache/D3D9/ directory, which is perhaps something to do with it.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #14 from Luke Bratch l_bratch@yahoo.co.uk 2007-12-25 15:55:05 --- I now have an 8800GTX, and this game runs _a lot_ better.
Slightly more stuff is rendered correctly, but still major issues. But the big thing is that the framerate of <1 is gone, and it is now very high (around 30 frames per second).
http://bugs.winehq.org/show_bug.cgi?id=10206
Travis Burtrum moparisthebest@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |moparisthebest@gmail.com
--- Comment #15 from Travis Burtrum moparisthebest@gmail.com 2008-01-17 17:02:48 --- I have found that crysis won't render correctly even under true windows XP unless the shader quality is turned to the highest possible option (this is with an 8800GTS) So this might not be a problem with WINE at all...
http://bugs.winehq.org/show_bug.cgi?id=10206
Ambro ambro@b4ever.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ambro@b4ever.net
http://bugs.winehq.org/show_bug.cgi?id=10206
Gregor Münch greg87@online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |greg87@online.de
--- Comment #16 from Gregor Münch greg87@online.de 2008-02-24 09:04:11 --- BTW dupe of bug 7991
http://bugs.winehq.org/show_bug.cgi?id=10206
Simetrical Simetrical+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #17 from Simetrical Simetrical+wine@gmail.com 2008-02-26 15:12:59 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=10206
Luke Bratch l_bratch@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #8816 is|0 |1 obsolete| | Attachment #8817 is|0 |1 obsolete| | Attachment #8827 is|0 |1 obsolete| | Attachment #8828 is|0 |1 obsolete| |
--- Comment #18 from Luke Bratch l_bratch@yahoo.co.uk 2008-02-26 15:52:11 --- Created an attachment (id=10991) --> (http://bugs.winehq.org/attachment.cgi?id=10991) Crysis settings on high
With the latest Wine, things looks significantly different, but it still suffers from the title of the bug.
Attached screenshot shows a scene from the start of the game, where you can see a map that overlays the whole screen. I have the feeling that the huge map actually belongs in the lower-left radar.
If you compare it with the screenshots that I've marked obsolete, you can see the significant changes.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #19 from Luke Bratch l_bratch@yahoo.co.uk 2008-04-23 13:59:10 --- Much the same in wine-0.9.60 - the map still overlays the whole screen.
http://bugs.winehq.org/show_bug.cgi?id=10206
haarp liquitsnake@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |liquitsnake@gmx.net
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #20 from haarp liquitsnake@gmx.net 2008-05-24 09:57:15 --- Map overlay is fixed in 1.0-rc2 However, severe graphical corruption remains
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #21 from haarp liquitsnake@gmx.net 2008-05-24 10:25:12 --- The worse corruption appeared between 0.9.58 and 0.9.59. I would regression-test, but Crysis won't even start at the first step of testing...
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #22 from haarp liquitsnake@gmx.net 2008-06-07 05:51:06 --- Created an attachment (id=13774) --> (http://bugs.winehq.org/attachment.cgi?id=13774) "shadows"
The ultra-low FPS are fixed in 1.0rc4 as long as the resolution doesn't get changed. The ugly stuff remains. I get tons of "shadows" on my screen that obscur it depending on where I look ( see screens )
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #23 from haarp liquitsnake@gmx.net 2008-06-07 05:53:44 --- Created an attachment (id=13775) --> (http://bugs.winehq.org/attachment.cgi?id=13775) "shadows" while looking elsewhere
Additionally, ultra-bright HDR glow remains. But it can be switched off from the console, so that shouldn't be the focus right now.
Ah, yes, and many objects seem to be invisible. Including your gun with some shader options, and vegetation/rocks.
All tests were made on Nvidia hardware (8600GT on 169.12 driver)
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #24 from Chris Spencer spencercw@googlemail.com 2008-06-07 07:49:04 --- I re-ran the benchmark on rc4, and while it is better, it is not significantly so (<1fps to ~3.7fps). There are also many graphical problems.
Still very much unplayable.
6800XT 173.14.05.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #25 from haarp liquitsnake@gmx.net 2008-06-07 07:50:57 --- Sorry, but you can't expect that video card to work properly, even on Windoze. Much less on Wine.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #26 from Chris Spencer spencercw@googlemail.com 2008-06-07 07:53:49 --- Why not? It plays perfectly well on Windows and I have completed the game on it.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #27 from haarp liquitsnake@gmx.net 2008-06-07 07:55:50 --- Well, it's too slow. maybe on Windoze it cna manage to keep the FPS up to a playable rate, but on Wine even I only get around 15 FPS with a 8600GT
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #28 from Luke Bratch l_bratch@yahoo.co.uk 2008-06-07 07:56:36 --- It may not run OK in Wine on that card for the reasons Roderick explained above.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #29 from Chris Spencer spencercw@googlemail.com 2008-06-07 08:00:11 --- haarp: Well that's the point, there are problems with Wine which means it is slower than Windows. Ultimately I should be able to play it on Wine at the same speed as on Windows.
Luke: Hm, missed that. That is unfortunate...
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #30 from haarp liquitsnake@gmx.net 2008-06-14 05:07:27 --- Looks like it's gotten worse in rc5. On high shader settings, at the start of the game, I can't see anything except the water. Like the shadows on my previos screens, but this time, they occupy the whole screen
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #31 from haarp liquitsnake@gmx.net 2008-06-28 17:55:17 --- Created an attachment (id=14435) --> (http://bugs.winehq.org/attachment.cgi?id=14435) Missing sprites
Since 1.1.0, it's gotten far better. On lower shader levels there still are problems (like overly done HDR lighting occupying the left half of the screen) On high shader level, it's as good as it was a few months before. Occasionally some over-HDR objects here and there, objects (like rocks) appearing at the wrong distance (too close), some sprites not working properly (see screen)
Also, the game won't slow down anymore when the resolution is changed. However, I can't choose my panel's native resolution (1920x1200) anymore. If I specify it manually in the config file, I encounter slowdowns to 1 FPS again. (8600GT)
So yea, 1.1.0 is actually playable again. Not that well, but possible. Keep up the good work!
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #32 from Austin English austinenglish@gmail.com 2008-12-29 10:52:26 --- Is this still an issue in current (1.1.11 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #33 from haarp liquitsnake@gmx.net 2008-12-29 10:55:48 --- Yes, and it'll probably take quite a while until this is completely fixed.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #34 from Rico kgbricola@web.de 2009-01-28 13:06:04 --- Setting the r_HDRRendering variable has a huge influence on the rendering result (sys_spec_Shading.cfg). Setting it to 2 (Shaders = High) the game looks fine (at least objects are rendered). But setting it to 0, you have problems to see the world. Also the generated shaders differ. So I guess there is a mistake in the shader generation.
Is there an easy way to dump the input for the shader and the generated shader and compare the results?
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #35 from H. Verbeet hverbeet@gmail.com 2009-01-29 03:37:13 --- Probably not easy, but running with +d3d_shader will dump both the d3d shader and the generated GL shader.
http://bugs.winehq.org/show_bug.cgi?id=10206
Athrun samurai_no_densetsu@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |samurai_no_densetsu@yahoo.es
--- Comment #36 from Athrun samurai_no_densetsu@yahoo.es 2009-02-14 10:59:31 --- This bug is still a duplicate of bug 7991
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #37 from Austin English austinenglish@gmail.com 2009-08-26 13:08:21 --- Is this still present in current (1.1.28 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #38 from Rico kgbricola@web.de 2009-08-26 13:56:42 --- Yes it is, but there is a regression ( bug 18799 ) which prevents further testing.
You could apply the patch from there and you still get a lot of rendering errors.
http://bugs.winehq.org/show_bug.cgi?id=10206
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |18799
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #39 from Rico kgbricola@web.de 2010-04-10 10:06:20 --- Created an attachment (id=27312) --> (http://bugs.winehq.org/attachment.cgi?id=27312) flickering pixels
Some progress here.
Patch e24473d53120f6edcabe9a367de5ef7fb765aefe seems to fix some of the rendering issues.
There are still some "flickering" pixels (see attachment).
You need this patch to get the game running http://bugs.winehq.org/attachment.cgi?id=27310 . See bug 18799 for reference.
http://bugs.winehq.org/show_bug.cgi?id=10206
Bug 10206 depends on bug 18799, which changed state.
Bug 18799 Summary: Crysis: Silent crash after first intro scene http://bugs.winehq.org/show_bug.cgi?id=18799
What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
http://bugs.winehq.org/show_bug.cgi?id=10206
Bug 10206 depends on bug 18799, which changed state.
Bug 18799 Summary: Crysis: Silent crash after first intro scene http://bugs.winehq.org/show_bug.cgi?id=18799
What |Old Value |New Value ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |
http://bugs.winehq.org/show_bug.cgi?id=10206
blaise mgavl69@juno.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mgavl69@juno.com
--- Comment #40 from blaise mgavl69@juno.com 2011-01-11 18:17:09 CST --- As of v1.3.11 Crysis runs perfectly on my GeForceGT220 system with no graphical errors except for no shadows. You still need to patch for double-buffering though.
http://bugs.winehq.org/show_bug.cgi?id=10206
Bug 10206 depends on bug 18799, which changed state.
Bug 18799 Summary: Crysis: Silent crash after first intro scene http://bugs.winehq.org/show_bug.cgi?id=18799
What |Old Value |New Value ---------------------------------------------------------------------------- Status|REOPENED |NEW Status|NEW |RESOLVED Resolution| |WONTFIX
http://bugs.winehq.org/show_bug.cgi?id=10206
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #41 from joaopa jeremielapuree@yahoo.fr 2011-08-03 14:14:00 CDT --- still a bug in current wine?
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #42 from Rico kgbricola@web.de 2011-09-19 03:36:50 CDT --- Created an attachment (id=36458) --> (http://bugs.winehq.org/attachment.cgi?id=36458) No shadows (settings = high)
There are still no shadows.
The flickering pixels are still there with shader settings low or medium. With shader settings high, the flickering seems to be gone.
The double buffering patch is still needed to run the game.
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #43 from Rico kgbricola@web.de 2011-12-17 07:42:37 CST --- Using "AlwaysOffscreen" = "enabled" removes the flickering for all shader levels for me.
The double buffer patch is still needed.
The shadows are still missing.
http://bugs.winehq.org/show_bug.cgi?id=10206
K1773R K1773R@darkgamex.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |K1773R@darkgamex.ch
--- Comment #44 from K1773R K1773R@darkgamex.ch 2012-02-10 18:19:30 CST --- (In reply to comment #43)
Using "AlwaysOffscreen" = "enabled" removes the flickering for all shader levels for me.
The double buffer patch is still needed.
The shadows are still missing.
works perfectly :) ty
http://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #45 from K1773R K1773R@darkgamex.ch 2012-02-13 21:24:20 CST --- the "hack" works well for crysis, but not crysis warhead :(
https://bugs.winehq.org/show_bug.cgi?id=10206
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
https://bugs.winehq.org/show_bug.cgi?id=10206
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned? Severity|major |normal
--- Comment #46 from Ken Sharp imwellcushtymelike@gmail.com --- Does this still occur in Wine 1.7.44 or later?
https://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #47 from Luke Bratch luke@bratch.co.uk --- The menu now has such severe graphics errors that I can't get into the game to test. That alone may mean that the bug is still valid as per the title.
I no longer have the original GPUs mentioned earlier in this thread (Nvidia 7900 GTX and Nvidia 8800 GTX) but instead now have a GTX 970, so the root cause *may* be different.
https://bugs.winehq.org/show_bug.cgi?id=10206
David Gámiz Jiménez david.gamiz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |david.gamiz@gmail.com
--- Comment #48 from David Gámiz Jiménez david.gamiz@gmail.com --- Hello comunnity!
I have affected by this bug.
Actually with my setup I have a problem with water. According to the inclination I have a problem viewing. Blue looks more opaque, and flickers. Could you know that you can be going on?
Other very long issue, the cascade shadows, in this case I have news:
Thanks to Roman Hargrave in your commentary find easy trick to show shadows maps perfectly.
"Read about this cvar in the cryengine docs.
0=use R16G16 texture format for depth map, 1=try to use R16 format if supported as render target 2=use R32F texture format for depth map 3=use ATI's DF24 texture format for depth map 4=use NVIDIA's D24S8 texture format for depth map 5=use NVIDIA's D16 texture format for depth map
Usage: r_ShadowTexFormat [0-5] I was toying with some cvars in crysis and managed to enable shadows by setting `r_ShadowTexFormat` to a value less than four."
I edit the config files whit this values, and yeah! Shadows! ;)
Path: ../drive_c/Program Files/Steam/steamapps/common/Crysis/Game/Config/CVarGroups/sys_spec_Shadows.cfg
Add this: r_ShadowTexFormat = 1
Path: ../drive_c/Program Files/Steam/steamapps/common/Crysis/Game/Config/singleplayer.cfg
r_ShadowTexFormat = "1"
By the way, I have also opened another similar but to another game, Bionic Commando. Could it be the same problem whit the format texture pixel used? The open bug: bugs.winehq.org/show_bug.cgi?id=37525
Thanks for this great work. Wine day by day and this last of couple of year improve incredibly!! :D
My Hardware: AMD Phenom(tm) II X6 1055T Processor × 6 8GB RAM Nvidia GeForce GTX 560 ti VRAM DDR5 1024 MB Driver Nvidia: 367.35 official graphics ppa
https://bugs.winehq.org/show_bug.cgi?id=10206
--- Comment #49 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with latest wine-rc6)?
https://bugs.winehq.org/show_bug.cgi?id=10206
Linards linards.liepins@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |linards.liepins@gmail.com
--- Comment #50 from Linards linards.liepins@gmail.com --- Is this bug still present on wine-staging 6.6 ?
https://bugs.winehq.org/show_bug.cgi?id=10206
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED Status|NEW |RESOLVED
--- Comment #51 from Ken Sharp imwellcushtymelike@gmail.com --- Abandoned
https://bugs.winehq.org/show_bug.cgi?id=10206
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #52 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla