[Bug 34871] New: Wine 1.7 DirectX Issues On Ubuntu 13.10

Bug #: 34871 Summary: Wine 1.7 DirectX Issues On Ubuntu 13.10 Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: shatteredlites@gmail.com Classification: Unclassified

Ok I've upgraded to Saucy Salamander and now Wine is going crazy again I've reinstalled and all but come up with problems when using games that require directX. these are the issues so far-

-Visualboyadvance-M ~Crashes upon starting if set to directX renderer.

-DeSmuMe ~Extremely slow app start due to performance issues ever since Wine 1.6 and beyond. once game is selected and loaded it crashes with windows bug window up not being able to find a problem.

-Sonic CD HD ~Upon starting either screen goes black with no sound or Desktop distorts and Closes or Freezes until CPU is forced into shutdown.

-Silent Hill 3 Retail ~ Game crashes bringing the desktop into a 860x680 resolution making it impossible to have the area or space to change res back.

-ePSXe ~ Crashes upon starting a game if its set to directX renderer.

-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

Show replies by date

wine-bugs＠winehq.org

7 Nov 7 Nov

9:03 p.m.

New subject: [Bug 34871] Wine 1.7 DirectX Issues On Ubuntu 13.10

--- Comment #1 from shatteredlites@gmail.com 2013-11-07 15:03:29 CST --- Update - I updated to 1.7.5 and DeSmuMe works fine now performance is great but all other apps still fail

wine-bugs＠winehq.org

8 Nov 8 Nov

12:24 a.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

Austin English austinenglish@gmail.com changed:

--- Comment #2 from Austin English austinenglish@gmail.com 2013-11-07 18:24:52 CST --- Not major. Please only one issue per bug. Please attach the terminal output.

wine-bugs＠winehq.org

3:35 a.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #3 from shatteredlites@gmail.com 2013-11-07 21:35:36 CST --- fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:win:EnumDisplayDevicesW ((null),0,0x32f7b8,0x00000000), stub! fixme:win:RegisterDeviceNotificationA (hwnd=0x1004a, filter=0x32fc84,flags=0x00000000) returns a fake device notification handle! fixme:win:UnregisterDeviceNotification (handle=0xcafecafe), STUB!

wine-bugs＠winehq.org

3:42 a.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #4 from shatteredlites@gmail.com 2013-11-07 21:42:20 CST --- this is from silent hill 3

fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:win:EnumDisplayDevicesW ((null),0,0x32f7b8,0x00000000), stub! fixme:win:RegisterDeviceNotificationA (hwnd=0x1004a, filter=0x32fc84,flags=0x00000000) returns a fake device notification handle! fixme:win:UnregisterDeviceNotification (handle=0xcafecafe), STUB!

this is from vbam i think i see a patern? fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:win:EnumDisplayDevicesW ((null),0,0x32f108,0x00000000), stub! fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. wine: Unhandled page fault on write access to 0x00000001 at address 0x7de838e6 (thread 0009), starting debugger... Unhandled exception: page fault on write access to 0x00000001 in 32-bit code (0x7de838e6). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:7de838e6 ESP:0032f050 EBP:0032f088 EFLAGS:00210206( R- -- I - -P- ) EAX:00000001 EBX:7dee5000 ECX:0032f0a0 EDX:ffffffff ESI:00000001 EDI:00000000 Stack dump: 0x0032f050: 0015fd44 00168930 0032f0e8 7defe7b5 0x0032f060: 00000002 00000010 7defbe41 7defe7b5 0x0032f070: 0016be08 0032f0a8 0032f0a0 7dee5000 0x0032f080: 001100b8 00000000 0032f0d8 7de7c037 0x0032f090: 00000550 00000300 001e7e88 7de7c037 0x0032f0a0: 00000001 00000000 00000003 00000073 Backtrace: =>0 0x7de838e6 wined3d_texture_decref+0x26(texture=<couldn't compute location>) [/home/seal/wine-1.7.5/dlls/wined3d/../../include/winbase.h:2587] in wined3d (0x0032f088) 1 0x7de7c037 wined3d_surface_decref+0x56() in wined3d (0x0032f0d8) 2 0x7de7f06d wined3d_swapchain_create+0x38c(device=<couldn't compute location>, desc=<couldn't compute location>, parent=<couldn't compute location>, parent_ops=<couldn't compute location>, swapchain=<couldn't compute location>) [/home/seal/wine-1.7.5/dlls/wined3d/swapchain.c:1027] in wined3d (0x0032f1b8) 3 0x7df0d5c0 d3d9_swapchain_create+0x7f(device=0x15fd40, desc=0x1605e8, swapchain=0x32f23c) [/home/seal/wine-1.7.5/dlls/d3d9/swapchain.c:333] in d3d9 (0x0032f208) 4 0x7defe3ba device_parent_create_swapchain+0x49(device_parent=<couldn't compute location>, desc=<couldn't compute location>, swapchain=<couldn't compute location>) [/home/seal/wine-1.7.5/dlls/d3d9/device.c:3437] in d3d9 (0x0032f258) 5 0x7ddfbff9 wined3d_device_init_3d+0xe8(device=<couldn't compute location>, swapchain_desc=<couldn't compute location>) [/home/seal/wine-1.7.5/dlls/wined3d/device.c:885] in wined3d (0x0032f2f8) 6 0x7df07b96 device_init+0x1f5(device=0x15fd40, parent=0x15ffb8, wined3d=0x164df8, adapter=0, device_type=D3DDEVTYPE_HAL, focus_window=0x100aa, flags=0x22, parameters=0xb005e0, mode=(nil)) [/home/seal/wine-1.7.5/dlls/d3d9/device.c:3554] in d3d9 (0x0032f4d8) 7 0x7df08484 d3d9_CreateDevice+0xbe(iface=<couldn't compute location>, adapter=<couldn't compute location>, device_type=<couldn't compute location>, focus_window=<couldn't compute location>, flags=<couldn't compute location>, parameters=<couldn't compute location>, device=<couldn't compute location>) [/home/seal/wine-1.7.5/dlls/d3d9/directx.c:461] in d3d9 (0x0032f548) 8 0x0047f04c in visualboyadvance-m (+0x7f04b) (0x00899028) 9 0x00000001 (0x006b292c) 10 0x0048cc70 in visualboyadvance-m (+0x8cc6f) (0x00562409) 0x7de838e6 wined3d_texture_decref+0x26 [/home/seal/wine-1.7.5/dlls/wined3d/../../include/winbase.h:2587] in wined3d: lock xaddl %edx,0x0(%esi) 2587 __asm__ __volatile__( "lock; xaddl %0,(%1)" Modules: Module Address Debug info Name (111 modules) PE 400000- 9eb000 Export visualboyadvance-m ELF 7bf00000-7bf04000 Deferred <wine-loader> ELF 7cc23000-7cc57000 Deferred libtxc_dxtn.so ELF 7cc57000-7cc62000 Deferred libpciaccess.so.0 ELF 7cc62000-7cc7f000 Deferred libgcc_s.so.1 ELF 7cd68000-7cd8a000 Deferred libdrm_intel.so.1 ELF 7cd8a000-7d172000 Deferred libdricore9.2.1.so.1 ELF 7d172000-7d1c4000 Deferred i915_dri.so ELF 7d1c4000-7d1d1000 Deferred libdrm.so.2 ELF 7d1d1000-7d1d7000 Deferred libxcb-dri2.so.0 ELF 7d1d7000-7d1ef000 Deferred libxcb-glx.so.0 ELF 7d1ef000-7d1f2000 Deferred libx11-xcb.so.1 ELF 7d1f2000-7d208000 Deferred libglapi.so.0 ELF 7d208000-7d261000 Deferred libgl.so.1 ELF 7d3ac000-7d3e3000 Deferred uxtheme<elf> -PE 7d3b0000-7d3e3000 \ uxtheme ELF 7d3e3000-7d3e9000 Deferred libxfixes.so.3 ELF 7d3e9000-7d3f4000 Deferred libxcursor.so.1 ELF 7d3f4000-7d405000 Deferred libxi.so.6 ELF 7d405000-7d409000 Deferred libxcomposite.so.1 ELF 7d409000-7d414000 Deferred libxrandr.so.2 ELF 7d414000-7d41f000 Deferred libxrender.so.1 ELF 7d41f000-7d425000 Deferred libxxf86vm.so.1 ELF 7d425000-7d429000 Deferred libxinerama.so.1 ELF 7d429000-7d430000 Deferred libxdmcp.so.6 ELF 7d430000-7d434000 Deferred libxau.so.6 ELF 7d434000-7d455000 Deferred libxcb.so.1 ELF 7d455000-7d58a000 Deferred libx11.so.6 ELF 7d58a000-7d59d000 Deferred libxext.so.6 ELF 7d59d000-7d5a1000 Deferred libxdamage.so.1 ELF 7d5a1000-7d5b7000 Deferred dwmapi<elf> -PE 7d5b0000-7d5b7000 \ dwmapi ELF 7d5b9000-7d64c000 Deferred winex11<elf> -PE 7d5c0000-7d64c000 \ winex11 ELF 7d64c000-7d671000 Deferred imm32<elf> -PE 7d650000-7d671000 \ imm32 ELF 7d671000-7d6fc000 Deferred gdiplus<elf> -PE 7d680000-7d6fc000 \ gdiplus ELF 7d6fc000-7d720000 Deferred oleacc<elf> -PE 7d700000-7d720000 \ oleacc ELF 7d720000-7d74c000 Deferred msvfw32<elf> -PE 7d730000-7d74c000 \ msvfw32 ELF 7d74c000-7d804000 Deferred winmm<elf> -PE 7d750000-7d804000 \ winmm ELF 7d804000-7d82f000 Deferred msacm32<elf> -PE 7d810000-7d82f000 \ msacm32 ELF 7d82f000-7d876000 Deferred avifil32<elf> -PE 7d840000-7d876000 \ avifil32 ELF 7d876000-7d892000 Deferred dinput8<elf> -PE 7d880000-7d892000 \ dinput8 ELF 7da04000-7da3e000 Deferred libfontconfig.so.1 ELF 7da3e000-7dadd000 Deferred libfreetype.so.6 ELF 7db06000-7db2f000 Deferred libexpat.so.1 ELF 7db2f000-7db49000 Deferred libz.so.1 ELF 7db65000-7db8d000 Deferred d3dxof<elf> -PE 7db70000-7db8d000 \ d3dxof ELF 7db8d000-7dc03000 Deferred d3dcompiler_43<elf> -PE 7dba0000-7dc03000 \ d3dcompiler_43 ELF 7dc03000-7dc90000 Deferred d3dx9_36<elf> -PE 7dc10000-7dc90000 \ d3dx9_36 ELF 7dc90000-7dcaa000 Deferred d3dx9_43<elf> -PE 7dca0000-7dcaa000 \ d3dx9_43 ELF 7dcaa000-7dda7000 Deferred opengl32<elf> -PE 7dcc0000-7dda7000 \ opengl32 ELF 7dda7000-7dee9000 Dwarf wined3d<elf> -PE 7ddb0000-7dee9000 \ wined3d ELF 7dee9000-7df27000 Dwarf d3d9<elf> -PE 7def0000-7df27000 \ d3d9 ELF 7df27000-7df3b000 Deferred msimg32<elf> -PE 7df30000-7df3b000 \ msimg32 ELF 7df3b000-7df72000 Deferred ws2_32<elf> -PE 7df40000-7df72000 \ ws2_32 ELF 7df72000-7e0a8000 Deferred oleaut32<elf> -PE 7df90000-7e0a8000 \ oleaut32 ELF 7e0a8000-7e12b000 Deferred rpcrt4<elf> -PE 7e0b0000-7e12b000 \ rpcrt4 ELF 7e12b000-7e269000 Deferred ole32<elf> -PE 7e140000-7e269000 \ ole32 ELF 7e269000-7e370000 Deferred comctl32<elf> -PE 7e270000-7e370000 \ comctl32 ELF 7e370000-7e3ea000 Deferred shlwapi<elf> -PE 7e380000-7e3ea000 \ shlwapi ELF 7e3ea000-7e61d000 Deferred shell32<elf> -PE 7e400000-7e61d000 \ shell32 ELF 7e61d000-7e708000 Deferred comdlg32<elf> -PE 7e620000-7e708000 \ comdlg32 ELF 7e708000-7e749000 Deferred winspool<elf> -PE 7e710000-7e749000 \ winspool ELF 7e749000-7e7bb000 Deferred advapi32<elf> -PE 7e760000-7e7bb000 \ advapi32 ELF 7e7bb000-7e8d2000 Deferred gdi32<elf> -PE 7e7d0000-7e8d2000 \ gdi32 ELF 7e8d2000-7ea2c000 Deferred user32<elf> -PE 7e8e0000-7ea2c000 \ user32 ELF 7ec2c000-7ee86000 Deferred kernel32<elf> -PE 7ec40000-7ee86000 \ kernel32 ELF 7ee86000-7ee93000 Deferred libnss_files.so.2 ELF 7ee93000-7ee9f000 Deferred libnss_nis.so.2 ELF 7ee9f000-7eeb8000 Deferred libnsl.so.1 ELF 7eeb8000-7eec1000 Deferred libnss_compat.so.2 ELF 7eec1000-7ef04000 Deferred libm.so.6 ELF 7ef06000-7ef20000 Deferred version<elf> -PE 7ef10000-7ef20000 \ version ELF 7ef20000-7f000000 Deferred ntdll<elf> -PE 7ef30000-7f000000 \ ntdll ELF b7376000-b737b000 Deferred libdl.so.2 ELF b737b000-b752f000 Deferred libc.so.6 ELF b7530000-b754b000 Deferred libpthread.so.0 ELF b7567000-b771c000 Dwarf libwine.so.1 ELF b771e000-b7740000 Deferred ld-linux.so.2 ELF b7740000-b7741000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 00000008 (D) E:\VisualBoy Advance\VisualBoyAdvance-M.exe 00000009 2 <== 0000000e services.exe 0000001e 0 0000001d 0 00000018 0 00000016 0 00000014 0 00000010 0 0000000f 0 00000012 winedevice.exe 0000001c 0 00000019 0 00000017 0 00000013 0 0000001a plugplay.exe 00000020 0 0000001f 0 0000001b 0 00000021 explorer.exe 00000022 0

wine-bugs＠winehq.org

6:26 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

joaopa jeremielapuree@yahoo.fr changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr

--- Comment #5 from joaopa jeremielapuree@yahoo.fr 2013-11-08 12:26:50 CST ---

Additional Comments: Please do not PASTE logs and back traces (attach them instead).

wine-bugs＠winehq.org

8:18 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #6 from shatteredlites@gmail.com 2013-11-08 14:18:01 CST --- Created attachment 46483 --> http://bugs.winehq.org/attachment.cgi?id=46483 Silent Hill 3's Error log Similar to VBAM

wine-bugs＠winehq.org

8:19 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #7 from shatteredlites@gmail.com 2013-11-08 14:19:37 CST --- Created attachment 46484 --> http://bugs.winehq.org/attachment.cgi?id=46484 VBAM Error log

wine-bugs＠winehq.org

8:20 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #8 from shatteredlites@gmail.com 2013-11-08 14:20:29 CST --- (In reply to comment #5)

...
Additional Comments: Please do not PASTE logs and back traces (attach them instead).

sry here the logs i got them both up because they seem to be affected by the same issue

wine-bugs＠winehq.org

14 Feb 14 Feb

3:47 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #9 from shatteredlites@gmail.com --- is there any update on this it still dosnt work at all

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

9:37 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

William Panlener wpanlener@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |wpanlener@gmail.com

--- Comment #10 from William Panlener wpanlener@gmail.com --- Which CPU/GPU do you use? These logs look very similar to another bug that I've been seeing, and I am trying to establish a pattern.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

9:55 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #11 from shatteredlites@gmail.com --- Ubuntu 13.10 Memory 1.5 GiB Processor Intel® Pentium(R) 4 CPU 2.80GHz × 2 Graphics Intel® 915G x86/MMX/SSE2

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

10:10 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #12 from William Panlener wpanlener@gmail.com --- This is the third case I have seen of Pentium 4 era machines with intel graphics chipsets crashing directx applications with terminal output containing strings of "fixme:d3d:check_fbo_compat...". See http://forum.winehq.org/viewtopic.php?f=8&t=20494 and http://bugs.winehq.org/show_bug.cgi?id=35582#c11.

Also, I was unable to reproduce the bug with Visualboyadvance-m on 1.7.12 with an i7-3770k/580 GTX with proprietary drivers.

I suspect this bug has to do with missing rendering features in graphics drivers for very old intel chipsets. Suggesting all future occurences of this pattern as a duplicate of this bug.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

10:29 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #13 from shatteredlites@gmail.com --- so this can be fixed right?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

10:33 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #14 from shatteredlites@gmail.com --- im sure the VBAM bug is related to that bug you mentioned. if this is fixed whatever is wrong with VBAM will be fixed as well im sure

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

20 Feb 20 Feb

6:21 a.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #15 from shatteredlites@gmail.com --- is there a fix coming?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

25 Feb 25 Feb

12:30 p.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #16 from shatteredlites@gmail.com --- the error is still present in the update i got yesterday.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

18 Mar 18 Mar

10:18 a.m.

New subject: [Bug 34871] Visualboyadvance-M crashes with directx renderer

--- Comment #17 from shatteredlites@gmail.com --- So the issue is still present. any news on this bug?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

2 May 2 May

11:56 a.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

http://www.romulation.net/roms/GBA/

Anastasius Focht focht@gmx.net changed:

--- Comment #18 from Anastasius Focht focht@gmx.net --- Hello folks,

same as comment #12 - no graphics problem here, the emulator works very nicely with NVIDIA graphics.

I tested with some GBA ROMs downloaded here:

Example: http://www.romulation.net/roms/GBA/2810-Hikaru-no-Go-%28J%29%28iND%29%28v1.1... ("Hikaru no Go")

As indicated by comment #12 this might be an Intel graphics chipset/driver related thing (obvious fix: get better graphics hardware or switch vendor).

Tidbit: the emulator starts with XAudio2 backend by default (subject to other bugs)

$ sha1sum VisualBoyAdvanceM1229.7z 40e5d0f16f54e7d019092d2a972d4423acc707b0 VisualBoyAdvanceM1229.7z

$ du -sh VisualBoyAdvanceM1229.7z 972K VisualBoyAdvanceM1229.7z

$ wine --version wine-1.7.17-175-gc1bf61e

Regards

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

11:15 p.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

--- Comment #19 from Bruno Jesus 00cpxxx@gmail.com --- I have an intel graphics board but I don't think it's old enough to reproduce this bug, it works for me even in wine 1.3.22.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

3 May 3 May

7:12 a.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

--- Comment #20 from shatteredlites@gmail.com --- the latest public release has not fixed the issue. it worked fine in 1.4 but after that its been all crappy.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

8 May 8 May

12:12 a.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

--- Comment #21 from shatteredlites@gmail.com --- I cant get ANYTHING USING DirectX to run at all Wine simply wont even try to run them anymore after them not working so many times. this worked fine back in 1.4 so why is this happening? was there some code change that just broke compatibility or what? I'm so stressed out that i cant get Project64, VBA-M, Snes9x, ePSXe, Silent hill 3, Sonic CD, Sonic adventure, etc NOTHING WILL RUN as a middle class citizen i cant afford a new computer or any of that luxury so getting a new chip is simply out of the question.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

12:13 a.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

shatteredlites@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Version|1.7.4 |1.7.18

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

12:16 a.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

--- Comment #22 from Austin English austinenglish@gmail.com --- (In reply to shatteredlites from comment #20)

the latest public release has not fixed the issue. it worked fine in 1.4 but after that its been all crappy.

Please run a regression test: http://wiki.winehq.org/RegressionTesting

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

12:12 p.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

--- Comment #23 from shatteredlites@gmail.com --- oh god not that i couldn't get that to run last time i was requested to do that :(

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

2 Aug 2 Aug

7:39 a.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

--- Comment #24 from shatteredlites@gmail.com --- ok i give up i want to revert back to Wine 1.4.0 but its not there anymore what happened I cant play anything without it. theres nothing that yall can do to fix this so how do i go back without using playon linux

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

7:41 a.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

shatteredlites@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

12:43 p.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

--- Comment #25 from shatteredlites@gmail.com --- *** Bug 37020 has been marked as a duplicate of this bug. ***

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

12:43 p.m.

New subject: [Bug 34871] VisualBoyAdvance-M (VBA-M, Game Boy emulator)crashes with old Intel graphics chipset/drivers

shatteredlites@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Version|1.7.18 |1.7.22

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

12:44 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

shatteredlites@gmail.com changed:

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

23 Aug 23 Aug

3:01 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

super_man@post.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com

--- Comment #26 from super_man@post.com --- Bugs should be opened against development version so the bug and regressions fixes can be found in next stable release. You have reverted back to 1.4. It basically makes this bug report invalid.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

9 Apr 9 Apr

1:21 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #27 from joaopa jeremielapuree@yahoo.fr --- INVALID BUG?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

27 Jun 27 Jun

1:13 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #28 from lahmbi5675@gmx.de ---

A similar issue has been discussed in the user forum recently. This issue probably arises, because some of the older intel chipsets were advertised as DX 9.0c compatible, but the hardware wasn't capable of Shader Model 3.0, so the Windows drivers emulated the missing functionality.

for more information about the capabilites of intel chipsets see https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units

A proper solution would imo require emulating the missing hardware functions in the intel linux driver, though I doubt, that intel will be willing to make that effort.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

11 Dec 11 Dec

12:46 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

mintos@discard.email mintos@discard.email changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |mintos@discard.email

--- Comment #29 from mintos@discard.email mintos@discard.email --- is there a chance that the Gallium llvmpipe driver or an opengl implementation could do the job of the missing hardware?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

16 Dec 16 Dec

1:19 a.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #30 from Matteo Bruni matteo.mystral@gmail.com --- Actually this might be a duplicate of bug 41052. Can someone try attachment 55929 (probably on top of Wine 1.9.21 / 1.9.22 if it doesn't apply anymore) and see if it helps?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

4 Feb 4 Feb

9:19 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

winetest@luukku.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com

--- Comment #31 from winetest@luukku.com --- (In reply to Matteo Bruni from comment #30)

Actually this might be a duplicate of bug 41052. Can someone try attachment 55929 [details] (probably on top of Wine 1.9.21 / 1.9.22 if it doesn't apply anymore) and see if it helps?

It was marked fixed in wine 2.1. No need to try any patches anymore. Just recent wine would do.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

12 Feb 12 Feb

8:20 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #32 from mintos@discard.email mintos@discard.email --- can confirm. it launches now with my 945gm gpu. however i now get the white screen bug that other people also reported.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

8:21 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #33 from mintos@discard.email mintos@discard.email --- can confirm. it launches now with my 945gm gpu. however i now get the white screen bug that other people also reported.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

9:28 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

Andrea Crescentini ac@andreacrescentini.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |ac@andreacrescentini.com

--- Comment #34 from Andrea Crescentini ac@andreacrescentini.com --- Probabily a duplicate of https://bugs.winehq.org/show_bug.cgi?id=34871 ? Seems related to older Intel iGPU and Directx too.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

9:28 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #35 from Andrea Crescentini ac@andreacrescentini.com --- (In reply to Andrea Crescentini from comment #34)

Probabily a duplicate of https://bugs.winehq.org/show_bug.cgi?id=34871 ? Seems related to older Intel iGPU and Directx too.

Sorry i've posted on the wrong bug.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

9:28 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #36 from Andrea Crescentini ac@andreacrescentini.com --- (In reply to Andrea Crescentini from comment #34)

Probabily a duplicate of https://bugs.winehq.org/show_bug.cgi?id=34871 ? Seems related to older Intel iGPU and Directx too.

Sorry i've posted on the wrong bug.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

13 Feb 13 Feb

2:33 p.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

--- Comment #37 from mintos@discard.email mintos@discard.email --- please close

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

17 Feb 17 Feb

midnight

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers

Matteo Bruni matteo.mystral@gmail.com changed:

--- Comment #38 from Matteo Bruni matteo.mystral@gmail.com --- Let's call this a duplicate of bug 41052.

*** This bug has been marked as a duplicate of bug 41052 ***

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

10 Mar 10 Mar

5:54 a.m.

New subject: [Bug 34871] Unable to Use Directx with old Intel graphics chipset/drivers