http://bugs.winehq.org/show_bug.cgi?id=22588
Summary: Starcraft 2 Editor doesn't render anything on the terrain view Product: Wine Version: 1.1.43 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: ape@ape3000.com
Created an attachment (id=27717) --> (http://bugs.winehq.org/attachment.cgi?id=27717) Output after starting the terrain view
I can start Starcraft 2 Editor if I set "HKEY_CURRENT_USER\Software\Blizzard Entertainment\StarCraft II Editor Beta\Preferences\StartupModules" to 0. The editor seems to be working generally, but the most important feature is unusable.
When I enter the terrain view the editor freezes and I have to kill it.
The output I get hints that the problem is probably in directx-d3d.
http://bugs.winehq.org/show_bug.cgi?id=22588
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |-unknown
http://bugs.winehq.org/show_bug.cgi?id=22588
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=22588
Roderick Colenbrander thunderbird2k@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |thunderbird2k@gmail.com
--- Comment #1 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-07 09:59:43 --- What GPU + display drivers are you using? Based on the output you showed it, I would guess it is a GPU with DRI drivers. Do you see anything in the 3D view except for garbage? It might be that your drivers don't support the functionality we need for windowed 3d rendering.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #2 from Lauri Niskanen ape@ape3000.com 2010-05-07 10:11:52 --- I use proprietary nvidia drivers. The version is 195.36.15. I can play many 3d-games in window. For example SC2 works fine in windowed mode.
If I start the terrain view directly when I start the editor, I see my wallpaper through it or sometimes some textures from the game. If I start the terrain editor from other editor windows I just keep seeing the window as it was just before I changed the view mode. In any case the editor completely freezes.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #3 from Lauri Niskanen ape@ape3000.com 2010-05-07 10:12:31 --- I forgot to mention that my graphics card is GeForce GTX 285.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #4 from Austin English austinenglish@gmail.com 2010-05-08 17:28:51 --- Created an attachment (id=27817) --> (http://bugs.winehq.org/attachment.cgi?id=27817) screenshot in 1.1.44
Seems fine for me in 1.1.44 with an nvidia 9800 gtx+ and 195.36.15.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #5 from Lauri Niskanen ape@ape3000.com 2010-05-09 00:11:52 --- I updated to 1.1.44 and retested. It still happens both with my gaming prefix and with a clean prefix.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #6 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-09 03:04:58 --- Could you have a look at http://wiki.winehq.org/3DDriverIssues? I really suspect that your 32-bit 3D drivers haven't been set up correctly. When this is the case 3D can still work (though not at full speed and with all 3d features).
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #7 from Lauri Niskanen ape@ape3000.com 2010-05-09 04:13:49 --- I have 64-bit Arch Linux here, but I installed 32-bit Ubuntu 10.04. I have the same issue with it, so it's not about the 64-bit system or my specific software configurations. It's generally in wine, nvidia drivers or my hardware.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #8 from Florian florian@fkoeberle.de 2010-05-09 12:08:07 --- Created an attachment (id=27826) --> (http://bugs.winehq.org/attachment.cgi?id=27826) +wgl Log when opening the terrain module with wine 1.1.43 using a proprietary NVIDIA driver
The editor crash for me too when I open the Terrain module. The text and trigger modules work. I use like Lauri Niskanen version 195.36.15 of the proprietary Nvidia drivers. For me the attached +wgl trace looks like hardware acceleration works properly. I use Kubuntu 10.04.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #9 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-09 12:14:01 --- I believe Austin is using Ubuntu 9.10 or 10.04 as well. I really wonder what is different. If you are using compiz try to disable it. Further no weird registry keys are set? What happens if you use a wine desktop?
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #10 from Lauri Niskanen ape@ape3000.com 2010-05-09 13:17:57 --- (In reply to comment #9)
I believe Austin is using Ubuntu 9.10 or 10.04 as well. I really wonder what is different. If you are using compiz try to disable it. Further no weird registry keys are set? What happens if you use a wine desktop?
I already tried multiple wine prefixes including a clean prefix on my both operating systems. I also tried it with and without compiz and xcompmgr with no change. Also wine desktop didn't make it work.
http://bugs.winehq.org/show_bug.cgi?id=22588
Florian florian@fkoeberle.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |florian@fkoeberle.de
--- Comment #11 from Florian florian@fkoeberle.de 2010-05-09 14:23:17 --- I have tried the setting "Emulate a virtual Desktop" but it didn't help. I previously used the word "crash" which doesn't describe it correctly.
Test 1.) I start the editor with the StartupModules key set to 0 and click on the terrain module in the module selector: No window gets displayed but the process continues.
Test 2.) I start the editor with the StartupModules key set to 0 and open first the "Overview Manager" and then the "Terrain Manager": Once I open the terrain manager the "Sandclock"-icon gets dispalyed and the UI of the "Overview Manager" doesn't react to mouse and key input.
Test 3.) I start the editor with no StartupModules key set(default). The terrain editor even opens and starts loading itself. Sometimes I can use the editors menu, but then suddenly a few seconds later the UI of the editor becomes unresponsive. If I have a menu open it stays open and does no longer react to input. Sometimes everything gets displayed correctly when the UI freezes. I will attach a screenshot of a case where it froze while I had a menu open.
http://bugs.winehq.org/show_bug.cgi?id=22588
Florian florian@fkoeberle.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #12 from Florian florian@fkoeberle.de 2010-05-09 14:23:44 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #13 from Florian florian@fkoeberle.de 2010-05-09 14:25:59 --- Created an attachment (id=27830) --> (http://bugs.winehq.org/attachment.cgi?id=27830) Screenshot of a frozen terrain editor with correct 3d view and open menu.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #14 from Florian florian@fkoeberle.de 2010-05-09 14:29:01 --- Created an attachment (id=27831) --> (http://bugs.winehq.org/attachment.cgi?id=27831) Screenshot of a frozen terrain editor with broken 3d view.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #15 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-09 14:36:26 --- Can you look at the console in case the menu becomes unresponsive? Perhaps there is a threading related issue. I suspect that you will see some deadlock information in the console but it might take a minute or two to appear.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #16 from Florian florian@fkoeberle.de 2010-05-09 14:53:55 --- I tried again to activate the menu before it finishes loading and this time the loading seemed to have stopped while the menu was open. I closed the menu and the loading continued. I opened the menu again and this time the UI froze while the menu was open and the 3d view was broken too. I waited two minutes but no additional messages appeared in the console. While the menu window remains above all windows (even this browser window) the complete terrain editor window does no longer redraw itself.
Now after about 5 minutes I have checked the window again, still no additional messages.
The last log lines are: fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub 6 times: fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats () fixme:d3d9:Direct3DShaderValidatorCreate9 stub
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #17 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-09 15:02:27 --- I plan to reinstall StarCraft II on my laptop anyway, so I might be able to take a look at it then. I have an idea where the issue could be and I can add some hacks to figure out if it is indeed the problem.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #18 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-10 08:56:23 --- I tried the editor on my ATI based laptop on Ubuntu 9.10 and it works fine (I'm using Wine 1.1.44). My other laptop uses an Nvidia GPU and runs 10.04 perhaps I can reproduce the issues there. What I do notice is that the interface itself flickers so now and then (especially during loading) and I can't seem to exit the editor using the menu. The only way I can quit the app is by force (wineserver -k).
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #19 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-11 06:36:50 --- I just tried the editor on Ubuntu 10.04 x86 using a Nvidia Geforce GTS360M GPU and the 195.36.15 drivers. In all cases with and without compiz the editor comes up fine and I have no issues. I wonder what is different.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #20 from Florian florian@fkoeberle.de 2010-05-11 07:48:21 --- Thanks for investigating in this bug Roderick.
In order to find the difference I tried the following: a.) Use wine 1.1.44 instead of a patched wine 1.1.43 b.) I enabled the library mmdevapi again (It broke Starcraft 2 in 1.1.43) c.) I changed some nvidia settings about anti aliasing and flipping and tested again.
None helped me to work around the bug.
Maybe note worth is that the process takes 100% CPU time of one of my two cores when the editor is frozen.
I also tried to send a SIGV signal to a frozen editor which caused a blizzard error report dialog to popup. It contains debug information but they are encrypted so that you would need special tools to see the stacktraces.
Maybe we could do some traces to find out what is going on. Do you know some good channels to trace?
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #21 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-11 08:52:06 --- Initially I expected that this issue is perhaps related to some locking we perform before each opengl call in wined3d. In our winex11 code we also perform these locks. Recently I noticed (but didn't look at it thoroughly yet) that wined3d is again behaving not that nice with the locks (double locking which can cause issues for some calls being made).
You could try what happens if you disable the locking from the wined3d side. To do so open dlls/wined3d/wined3d_main.c. Somewhere you'll see: mod = GetModuleHandleA( "winex11.drv" ); if (mod) { wine_tsx11_lock_ptr = (void *)GetProcAddress( mod, "wine_tsx11_lock" ); wine_tsx11_unlock_ptr = (void *)GetProcAddress( mod, "wine_tsx11_unlock" ); } else /* We are most likely on Windows */ { wine_tsx11_lock_ptr = wined3d_do_nothing; wine_tsx11_unlock_ptr = wined3d_do_nothing; }
The easiest way is just to comment the GetModuleHandleA line.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #22 from Florian florian@fkoeberle.de 2010-05-11 12:27:17 --- I tried the following change at the position you told me: - mod = GetModuleHandleA( "winex11.drv" ); + mod = 0;//GetModuleHandleA( "winex11.drv" ); + ERR("Don't call ModuleHandleA\n");
It prints me my added error message before everything else, but the bug is still there.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #23 from Florian florian@fkoeberle.de 2010-05-12 15:21:49 --- Ubuntu 10.04 offers me to install two old versions of nvidia drivers.
Version 173 shows the same editor behavior like the most current version.
With version 96 however the terrain editor does not freeze: Instead it shows a ton of shader related error messages in the console and the 3d area of the terrain editor is black.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #24 from Florian florian@fkoeberle.de 2010-05-15 05:58:23 --- Created an attachment (id=27976) --> (http://bugs.winehq.org/attachment.cgi?id=27976) Warnings, Errors and Fixmes when starting the Starcraft 2 Editor
Wine (current trunk) prints some interesting errors, fixmes and warnings when starting the editor:
warn:wgl:X11DRV_wglGetPixelFormatAttribivARB Unable to convert iPixelFormat 0 to a GLX one!
fixme:d3d:debug_d3dformat Unrecognized 875710020 (as fourcc: DF24) WINED3DFORMAT! fixme:d3d:getFormatDescEntry Can't find format unrecognized(875710020) in the format lookup table
warn:d3d:IWineD3DDeviceImpl_Clear Clearing depth and/or stencil without a depth stencil buffer attached, returning WINED3DERR_INVALIDCALL
warn:d3d:IWineD3DDeviceImpl_GetDeviceCaps (0x1b61b8) : stub, calling idirect3d for now
err:heap:HEAP_ValidateInUseArena Heap 0x110000: block 0x96711b8 tail overwritten at 0x96711ba (byte 0/14 == 0x01)
warn:gdi:GDI_GetObjPtr Invalid handle 0xcfa0 warn:gdi:GDI_GetObjPtr Invalid handle (nil)
warn:d3d:IWineD3DBaseSwapChainImpl_QueryInterface {3c2aebf6-6f30-11d9-c687-00046142c14f} not implemented, returning E_NOINTERFACE.
The editor was displaying a broken 3d view when the UI became unresponsive.
The attached log does not contain the following warnings as the file would be otherwise over one MB huge: warn:dsalsa:IDsDriverBufferImpl_Lock warn:ntdll:NtQueryAttributesFile
http://bugs.winehq.org/show_bug.cgi?id=22588
DJ Kehoe dj_kehoe@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dj_kehoe@yahoo.com
--- Comment #25 from DJ Kehoe dj_kehoe@yahoo.com 2010-05-15 09:32:58 --- I have the same issues with the terrain editor freezing. Additionally the object editor causes an immediate program shutdown. I am using ubuntu 9.04. wine-1.1.43-564-g1af1784 I am using a Vaio Laptop with intel centrino duo 2.4 Ghz / core. Graphics card is GeForce Go 7600 I am using the envy installed driver 180.44-0ubuntu1.
http://bugs.winehq.org/show_bug.cgi?id=22588
Roderick Colenbrander thunderbird2k@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |s_kracker@web.de
--- Comment #26 from Roderick Colenbrander thunderbird2k@gmail.com 2010-05-17 07:37:42 --- *** Bug 22519 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #27 from Florian florian@fkoeberle.de 2010-05-24 11:07:48 --- I have filled in bug 22857 about the issue with the data editor crash. Might not be related.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #28 from Florian florian@fkoeberle.de 2010-06-24 16:09:19 --- I found out that the editor crash while opening the terrain view if I open and close the previewer first. The good thing is that I could get a nice backtrace for that case. See bug 23362 for more information.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #29 from Florian florian@fkoeberle.de 2010-07-03 12:46:53 --- I have got the terrain editor working for me:
I set the registry key HKEY_CURRENT_USER/Software/Wine/Direct3D/OffscreenRenderingMode to backbuffer and started the editor and opened at first the terrain module. The editor froze as before but was still printing the following two lines every second:
fixme:d3d_surface:fb_copy_to_texture_direct Doing a pixel by pixel copy from the framebuffer to a texture, expect major performance issues err:d3d_surface:fb_copy_to_texture_direct Texture filtering not supported in direct blit
Then after about 10 or 20 seconds the editor became responsible again, but the ground texture was broken in the area which is visible at start. Moving around the view fixes the ground. It is possible to place stuff on the wrongly drawn ground.
Afterwards I tried it again with the registry key set to fbo and with strangely it didn't freeze and the ground was correct from start on.
I tried it multiple times again without that registry key set and it continued to work. In other words: I can't reproduce this bug anymore even with my old setting...
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #30 from Florian florian@fkoeberle.de 2010-07-03 12:50:36 --- Created an attachment (id=29320) --> (http://bugs.winehq.org/attachment.cgi?id=29320) Starcraft 2 Terrain Editor started with OffscreenRenderingMode=backbuffer
This is how it look like if I set OffscreenRenderingMode to backbuffer and scroll a little bit around in the Terrain Editor to fix some ground tiles.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #31 from Florian florian@fkoeberle.de 2010-07-03 13:17:59 --- I found out why it started to work for me since my initial try with the OffscreenRenderingMode=backbuffer setting. It looks like the Terrain editor remembers which layer you had active. It stores the setting in: HKEY_CURRENT_USER/Software/Blizzard Entertainment/Starcraft II Editor beta/Preferences/TerrainActiveLayer
If this setting is 0 (= Terrain Layer) then the editor freezes at start. If it's 1 the terrain editor starts up fine. When you choose then the terrain layer via menu the editor crashes.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #32 from Florian florian@fkoeberle.de 2010-07-03 13:22:31 --- Created an attachment (id=29321) --> (http://bugs.winehq.org/attachment.cgi?id=29321) Crash backtrace when switch to the terrain layer when OffscreenRenderingMode=fbo
Crash backtrace, more or less identical to the backtrace of bug 23362 (which isn't as complete as this one).
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #33 from Florian florian@fkoeberle.de 2010-07-03 13:34:49 --- Created an attachment (id=29322) --> (http://bugs.winehq.org/attachment.cgi?id=29322) Hack of bug 23362 to convert the crash into a freeze.
This hack converts the terrain editor crash of bug 23362 into a freeze. It also converts the crash which happens when you switch to the Terrain Layer into the a freeze.
http://bugs.winehq.org/show_bug.cgi?id=22588
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #34 from joaopa jeremielapuree@yahoo.fr 2011-07-09 23:46:31 CDT --- still a bug in current wine?
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #35 from Florian florian@fkoeberle.de 2011-07-11 08:19:50 CDT --- I can't reproduce the bug with my new system and wine 1.3.24. So it could be that either: a.) the bug got fixed b.) the Starcraft 2 Editor no longer triggers the bug c.) my new system doesn't trigger the bug
I tried to evaluate that it is indeed a bug fix but I can't get wine 1.1.43 running. It compiles but gives a instant segmentation fault, even if I only try to run notepad.
http://bugs.winehq.org/show_bug.cgi?id=22588
--- Comment #36 from Florian florian@fkoeberle.de 2013-06-30 09:30:16 CDT --- I tried to reproduce it again with wine-1.5.29: The bug is gone.
http://bugs.winehq.org/show_bug.cgi?id=22588
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #37 from Austin English austinenglish@gmail.com 2013-06-30 17:19:44 CDT --- (In reply to comment #36)
I tried to reproduce it again with wine-1.5.29: The bug is gone.
Thanks.
http://bugs.winehq.org/show_bug.cgi?id=22588
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #38 from Alexandre Julliard julliard@winehq.org 2013-07-12 13:48:13 CDT --- Closing bugs fixed in 1.6-rc5.