[Bug 43995] New: Uplay - Assassin's Creed 4 Black Flag won't start
https://bugs.winehq.org/show_bug.cgi?id=43995 Bug ID: 43995 Summary: Uplay - Assassin's Creed 4 Black Flag won't start Product: Wine-staging Version: 2.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mi.bar.2001(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59652 --> https://bugs.winehq.org/attachment.cgi?id=59652 Terminal log from `wine AC4BFSP.exe` After clicking the "Play" button in Ubisoft Game Launcher (or launching `wine AC4BFSP.exe`), a window pops up informing, that the game is starting, but it disappears and the game doesn't launch. I don't have the Steam version, just the Uplay one. I've set Windows version to XP, wineprefix is 32-bit. Wine version will probably be visible when I post this, but I'm going to mention it just to be safe. Using Wine 2.20 staging -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 mi.bar.2001(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #1 from mi.bar.2001(a)gmail.com --- Created attachment 59775 --> https://bugs.winehq.org/attachment.cgi?id=59775 Wine 2.21 staging log from `wine AC4BFSP.exe` -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #2 from mi.bar.2001(a)gmail.com --- Still present in 2.21 staging -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #3 from debianxfce <fin4478(a)hotmail.com> --- UPlay crash reporter is launched in loop. Terminating the Black Flag process starts the game. When in the loop, you have the following in the terminal: fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll" fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffa, 0x33fdc4 err:heap:HEAP_GetPtr Invalid heap (nil)! fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll" fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffa, 0x33fdc4 err:heap:HEAP_GetPtr Invalid heap (nil)! fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll" fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffa, 0x33fdc4 err:heap:HEAP_GetPtr Invalid heap (nil)! Game works OK after terminating the Black Flag process, weird. I use win7 in winecfg. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #4 from debianxfce <fin4478(a)hotmail.com> --- Remove UplayCrashReporter.exe from the .wine/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/ directory to fix this bug. The game works fine without it. Backup your /home/xfce/Documents/Assassin's Creed IV Black Flag/Assassin4.ini file, some display setting can cause a black screen. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #5 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #4)
Remove UplayCrashReporter.exe from the .wine/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/ directory to fix this bug. The game works fine without it. Backup your /home/xfce/Documents/Assassin's Creed IV Black Flag/Assassin4.ini file, some display setting can cause a black screen.
Unfortunately this didn't help. The game still won't start. I attached a new log file (removedUplayCrashReporter.log) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #6 from mi.bar.2001(a)gmail.com --- Created attachment 59957 --> https://bugs.winehq.org/attachment.cgi?id=59957 Wine 2.21 staging log after removing UplayCrashReporter.exe from Uplay directory -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #7 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #5)
(In reply to debianxfce from comment #4)
Remove UplayCrashReporter.exe from the .wine/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/ directory to fix this bug. The game works fine without it. Backup your /home/xfce/Documents/Assassin's Creed IV Black Flag/Assassin4.ini file, some display setting can cause a black screen.
Unfortunately this didn't help. The game still won't start. I attached a new log file (removedUplayCrashReporter.log)
Use a clean .wine prefix and win7. From winecfg Graphics settings, disable Allow decorate the windows. Report your system, mine is: xfce(a)ryzen5pc:~$ inxi -bM System: Host: ryzen5pc Kernel: 4.15.0-rc2+ x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: N/A UEFI [Legacy]: American Megatrends v: 3401 date: 12/04/2017 CPU: Hexa core AMD Ryzen 5 1600 Six-Core (-HT-MCP-) speed/max: 2724/3691 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Polaris11] Display Server: x11 (X.Org 1.19.5 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 1920x1080(a)60.00hz OpenGL: renderer: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-rc2+, LLVM 5.0.1) version: 4.5 Mesa 17.4.0-devel Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 Drives: HDD Total Size: 256.1GB (65.4% used) Info: Processes: 252 Uptime: 40 min Memory: 2083.2/7985.9MB Client: Shell (bash) inxi: 2.3.45 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #8 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #7)
(In reply to mi.bar.2001 from comment #5)
(In reply to debianxfce from comment #4)
Remove UplayCrashReporter.exe from the .wine/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/ directory to fix this bug. The game works fine without it. Backup your /home/xfce/Documents/Assassin's Creed IV Black Flag/Assassin4.ini file, some display setting can cause a black screen.
Unfortunately this didn't help. The game still won't start. I attached a new log file (removedUplayCrashReporter.log)
Use a clean .wine prefix and win7. From winecfg Graphics settings, disable Allow decorate the windows. Report your system, mine is: xfce(a)ryzen5pc:~$ inxi -bM System: Host: ryzen5pc Kernel: 4.15.0-rc2+ x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: N/A UEFI [Legacy]: American Megatrends v: 3401 date: 12/04/2017 CPU: Hexa core AMD Ryzen 5 1600 Six-Core (-HT-MCP-) speed/max: 2724/3691 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Polaris11] Display Server: x11 (X.Org 1.19.5 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 1920x1080(a)60.00hz OpenGL: renderer: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-rc2+, LLVM 5.0.1) version: 4.5 Mesa 17.4.0-devel Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 Drives: HDD Total Size: 256.1GB (65.4% used) Info: Processes: 252 Uptime: 40 min Memory: 2083.2/7985.9MB Client: Shell (bash) inxi: 2.3.45
michal(a)PCMB:~$ inxi -bM System: Host: PCMB Kernel: 4.9.0-3-amd64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1) Distro: Debian GNU/Linux 9 (stretch) Machine: Device: desktop Mobo: MSI model: H110M PRO-VD (MS-7996) v: 1.0 UEFI: American Megatrends v: 2.C0 date: 04/20/2017 CPU: Quad core Intel Core i5-7400 (-MCP-) speed/max: 799/3500 MHz Graphics: Card: NVIDIA GM107 [GeForce GTX 750 Ti] Display Server: X.Org 1.19.2 drivers: nvidia (unloaded: modesetting,fbdev,vesa,nouveau) Resolution: 1440x900(a)59.89hz GLX Renderer: GeForce GTX 750 Ti/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 375.82 Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 Card-2: Atheros AR9271 802.11n driver: ath9k_htc Drives: HDD Total Size: 1250.3GB (7.5% used) Info: Processes: 155 Uptime: 3:21 Memory: 1156.8/7950.1MB Client: Shell (bash) inxi: 2.3.5 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #9 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #7)
(In reply to mi.bar.2001 from comment #5)
(In reply to debianxfce from comment #4)
Remove UplayCrashReporter.exe from the .wine/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/ directory to fix this bug. The game works fine without it. Backup your /home/xfce/Documents/Assassin's Creed IV Black Flag/Assassin4.ini file, some display setting can cause a black screen.
Unfortunately this didn't help. The game still won't start. I attached a new log file (removedUplayCrashReporter.log)
Use a clean .wine prefix and win7. From winecfg Graphics settings, disable Allow decorate the windows. Report your system, mine is: xfce(a)ryzen5pc:~$ inxi -bM System: Host: ryzen5pc Kernel: 4.15.0-rc2+ x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: N/A UEFI [Legacy]: American Megatrends v: 3401 date: 12/04/2017 CPU: Hexa core AMD Ryzen 5 1600 Six-Core (-HT-MCP-) speed/max: 2724/3691 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Polaris11] Display Server: x11 (X.Org 1.19.5 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 1920x1080(a)60.00hz OpenGL: renderer: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-rc2+, LLVM 5.0.1) version: 4.5 Mesa 17.4.0-devel Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 Drives: HDD Total Size: 256.1GB (65.4% used) Info: Processes: 252 Uptime: 40 min Memory: 2083.2/7985.9MB Client: Shell (bash) inxi: 2.3.45
Alright, the game launches and runs fine, but crashes during one mission. I'll provide the log when I'll be able to -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #10 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #9)
Alright, the game launches and runs fine, but crashes during one mission. I'll provide the log when I'll be able to
I have played 8% and had one crash. Now when I have sailing ship battles in Caribbean, main view freezes but mini map works. I restated the game and played forward and game works fine so far. It is difficult to trace these kind of problems so restart the game and do not make bug reports. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #11 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #10)
(In reply to mi.bar.2001 from comment #9)
Alright, the game launches and runs fine, but crashes during one mission. I'll provide the log when I'll be able to
I have played 8% and had one crash. Now when I have sailing ship battles in Caribbean, main view freezes but mini map works. I restated the game and played forward and game works fine so far. It is difficult to trace these kind of problems so restart the game and do not make bug reports.
I've completed the game to 31% and it crashes in the "Fireship" mission no matter how many times I restart it. I'm providing a log file of when the crash happens. It has a lot of those: * fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier * fixme:d3d11:shdr_handler Unhandled chunk "RDEF". fixme:d3d11:shdr_handler Unhandled chunk "STAT". * fixme:d3d:wined3d_buffer_create Ignoring access flags (pool). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #12 from mi.bar.2001(a)gmail.com --- Created attachment 59985 --> https://bugs.winehq.org/attachment.cgi?id=59985 Log after crash in the "Fireship" mission (loading screen after it) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #13 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #10)
(In reply to mi.bar.2001 from comment #9)
Alright, the game launches and runs fine, but crashes during one mission. I'll provide the log when I'll be able to
I have played 8% and had one crash. Now when I have sailing ship battles in Caribbean, main view freezes but mini map works. I restated the game and played forward and game works fine so far. It is difficult to trace these kind of problems so restart the game and do not make bug reports.
Also, in
I've completed the game to 31% and it crashes in the "Fireship" mission no matter how many times I restart it. I'm providing a log file of when the crash happens.
I meant restarting both the mission and the game -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #14 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #13)
I meant restarting both the mission and the game
Distribution kernels are slow and the 4.9 kernel very old. Make a non debug 1000Hz timer kernel from the 4.14.8 kernel at kernel.org. You have some threading problem and speeding up might help. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #15 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #14)
(In reply to mi.bar.2001 from comment #13)
I meant restarting both the mission and the game
Distribution kernels are slow and the 4.9 kernel very old. Make a non debug 1000Hz timer kernel from the 4.14.8 kernel at kernel.org. You have some threading problem and speeding up might help.
Okay, thank You for help. I think I'll just stick with what I have, I'm a Linux newb and I don't want to break my system while installing a new kernel. Thanks a lot! (Also, should I set the bug as resolved?) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #16 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #15)
(In reply to debianxfce from comment #14)
(In reply to mi.bar.2001 from comment #13)
I meant restarting both the mission and the game
Distribution kernels are slow and the 4.9 kernel very old. Make a non debug 1000Hz timer kernel from the 4.14.8 kernel at kernel.org. You have some threading problem and speeding up might help.
Okay, thank You for help. I think I'll just stick with what I have, I'm a Linux newb and I don't want to break my system while installing a new kernel. Thanks a lot! (Also, should I set the bug as resolved?)
Update your system to Debian testing. Debian stable is not stable, you break it with testing and unstable packages. Debian stable have years old buggy software. Distribution kernels are slow because of debugging code and 250 Hz timer. With Synaptic install gdebi. With Gdebi you can install downloaded .deb packages easily. Give the root password when asked. Install sudo, build-essential, kernel-package, qt5-default, qt5-qmake, qtbase5-dev, qtbase5-dev-tools and pkg-config packages too. Add yourself to sudoers: su adduser username sudo Logout and login to make sudo to work. The kernel configuration file of Debian Official kernel are available in /boot, named after the kernel release. Copy the .config file to the linux directory. Connect all your devices and run the command: make localmodconfig. You can use the command make defconfig too for creating initial .config file. Use the command: make xconfig and check that you have enabled: Reroute Broken IRQ, Amd IOMMU, Virtualization KVM and 1000Hz CPU timer. I also disabled Swap, Kernel Debug, CPU Freq scaling , Cpu handling in Acpi, Used Bios to control CPU and devices. In the drivers/graphics/amdgpu enable cik support for a gcn 1.1 gpu and si support for a gcn 1.0 gpu. Configuring wifi: https://wiki.gentoo.org/wiki/Wifi To prevent random kernel lock ups wit Ryzen cpus, enable RCU_NOCB_CPU and boot the kernel with the rcu_nocbs=0-X command line parameter. X is the cpu thread count -1. Create debian kernel package: export CONCURRENCY_LEVEL=2 or use -j 2 with make-kpkg (number of threads in your cpu) fakeroot make-kpkg --initrd kernel_image Add kernel_headers to the fakeroot command if you need headers. Install the kernel package with Gdebi. Reboot. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #17 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #16)
(In reply to mi.bar.2001 from comment #15)
(In reply to debianxfce from comment #14)
(In reply to mi.bar.2001 from comment #13)
I meant restarting both the mission and the game
Distribution kernels are slow and the 4.9 kernel very old. Make a non debug 1000Hz timer kernel from the 4.14.8 kernel at kernel.org. You have some threading problem and speeding up might help.
Okay, thank You for help. I think I'll just stick with what I have, I'm a Linux newb and I don't want to break my system while installing a new kernel. Thanks a lot! (Also, should I set the bug as resolved?)
Update your system to Debian testing. Debian stable is not stable, you break it with testing and unstable packages. Debian stable have years old buggy software. Distribution kernels are slow because of debugging code and 250 Hz timer.
With Synaptic install gdebi. With Gdebi you can install downloaded .deb packages easily. Give the root password when asked. Install sudo, build-essential, kernel-package, qt5-default, qt5-qmake, qtbase5-dev, qtbase5-dev-tools and pkg-config packages too. Add yourself to sudoers: su adduser username sudo Logout and login to make sudo to work.
The kernel configuration file of Debian Official kernel are available in /boot, named after the kernel release. Copy the .config file to the linux directory. Connect all your devices and run the command: make localmodconfig. You can use the command make defconfig too for creating initial .config file.
Use the command: make xconfig and check that you have enabled: Reroute Broken IRQ, Amd IOMMU, Virtualization KVM and 1000Hz CPU timer. I also disabled Swap, Kernel Debug, CPU Freq scaling , Cpu handling in Acpi, Used Bios to control CPU and devices. In the drivers/graphics/amdgpu enable cik support for a gcn 1.1 gpu and si support for a gcn 1.0 gpu.
Configuring wifi: https://wiki.gentoo.org/wiki/Wifi
To prevent random kernel lock ups wit Ryzen cpus, enable RCU_NOCB_CPU and boot the kernel with the rcu_nocbs=0-X command line parameter. X is the cpu thread count -1.
Create debian kernel package: export CONCURRENCY_LEVEL=2 or use -j 2 with make-kpkg (number of threads in your cpu) fakeroot make-kpkg --initrd kernel_image
Add kernel_headers to the fakeroot command if you need headers.
Install the kernel package with Gdebi. Reboot.
I've upgraded my system: michal(a)PCMB:~$ inxi -bM System: Host: PCMB Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: LXDE (Openbox 3.6.1) Distro: Debian GNU/Linux buster/sid Machine: Device: desktop Mobo: MSI model: H110M PRO-VD (MS-7996) v: 1.0 serial: N/A UEFI: American Megatrends v: 2.C0 date: 04/20/2017 CPU: Quad core Intel Core i5-7400 (-MCP-) speed/max: 3000/3500 MHz Graphics: Card: NVIDIA GM107 [GeForce GTX 750 Ti] Display Server: x11 (X.Org 1.19.5 ) drivers: nvidia (unloaded: modesetting,fbdev,vesa,nouveau) Resolution: 1440x900(a)59.89hz OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 version: 4.5.0 NVIDIA 384.98 Network: Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 Card-2: Atheros AR9271 802.11n driver: ath9k_htc Drives: HDD Total Size: 1250.3GB (9.8% used) Info: Processes: 150 Uptime: 13 min Memory: 795.7/7949.4MB Client: Shell (bash) inxi: 2.3.45 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #18 from mi.bar.2001(a)gmail.com --- The game still crashes at loading screen after the "Fireship" mission. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #19 from mi.bar.2001(a)gmail.com --- Created attachment 60014 --> https://bugs.winehq.org/attachment.cgi?id=60014 Log after upgrading to debian-testing from stable -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #20 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #18)
The game still crashes at loading screen after the "Fireship" mission.
I have played 19% without crashes. You could try the Nouveau driver and Oibaf ppa latest ubuntu version Mesa, do not forget to install firmware (if needed). Phoronix has tested 750 with the Nouveau driver and performance is good. https://www.phoronix.com/scan.php?page=article&item=nouveau-412-reclocked&nu... http://www.webupd8.org/2014/10/how-to-add-launchpad-ppas-in-debian-via.html -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #21 from debianxfce <fin4478(a)hotmail.com> --- AC4 crashes after the Fireship mission when the game is starting the next mission. Fix: add AC4BFSP.exe to winecfg applications and set the dll override for d3dx11_43 (builtin,native). I figured the solution from this crash trace: Modules: Module Address Debug info Name (226 modules) PE 340000- 37f000 Deferred d3dx11_43 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #22 from mi.bar.2001(a)gmail.com --- Unfortunately, the game still crashes in the same moment, but after the d3dx11_43 override there are some changes in the log file. There are a lot of these: * fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80000102. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. * fixme:d3d:wined3d_buffer_create Ignoring access flags (pool). * fixme:d3d11:shdr_handler Unhandled chunk "STAT". fixme:d3d11:shdr_handler Unhandled chunk "RDEF". -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #23 from mi.bar.2001(a)gmail.com --- Created attachment 60066 --> https://bugs.winehq.org/attachment.cgi?id=60066 Log after overriding d3dx11_43 as (builtin,native) for AC4BFSP.exe -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #24 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #23)
Created attachment 60066 [details] Log after overriding d3dx11_43 as (builtin,native) for AC4BFSP.exe
Override next dlls as builtin,native. Also nv driver has problems with IR code. Try Nouveau. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #25 from mi.bar.2001(a)gmail.com --- (In reply to debianxfce from comment #24)
(In reply to mi.bar.2001 from comment #23)
Created attachment 60066 [details] Log after overriding d3dx11_43 as (builtin,native) for AC4BFSP.exe
Override next dlls as builtin,native. Also nv driver has problems with IR code. Try Nouveau.
I have a noob question: by next dlls you mean dxd311_43, dxd311_44, dxd311_45, dxd311_...? Also, Nouveau drivers are installed in my system by default and they were terrible, I couldn't run anything, resolution was poor and unchangeable. It looked like this: Graphics: Card: NVIDIA GM107 [GeForce GTX 750 Ti] Display Server: x11 (X.Org 1.19.5 ) drivers: fbdev,nouveau (unloaded: modesetting,vesa) Resolution: 1024x768(a)76.00hz OpenGL: renderer: N/A version: N/A -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #26 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #25)
I have a noob question: by next dlls you mean dxd311_43, dxd311_44, dxd311_45, dxd311_...?
Read your log files, here is the list what you can ovveride: Modules: Module Address Debug info Name (214 modules) PE 340000- 36a000 Deferred gfsdk_ssao_win32 PE 370000- 39a000 Deferred gfsdk_godrayslib.win32 PE 3a0000- 3aa000 Deferred gfsdk_multires.win32 PE 3b0000- 3c3000 Deferred gfsdk_psm.win32 PE 3d0000- 3f8000 Deferred gfsdk_gsa.win32 PE 400000- 5290000 Export ac4bfsp PE 5290000- 56ff000 Deferred gfsdk_shadowlib.win32
OpenGL: renderer: N/A version: N/A
You did not have Mesa installed correctly. You did not remove nvidia driver packages correctly and reinstalled Mesa. You are using old and buggy Debian packaged nvidia drivers, they all must be removed and Mesa packages installed. Install the nvidia driver from nvidia site, current version is much newer than Debian has: http://www.nvidia.com/Download/driverResults.aspx/126577/en-us -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #27 from debianxfce <fin4478(a)hotmail.com> --- I have played many hours after the Fireship mission, so the Fireship mission freeze problem is caused by not Mesa, old or buggy nvidia drivers. Here is a video for a proof: http://www.filehosting.org/file/details/716995/2018-01-03%2008-42-00.flv -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #28 from mi.bar.2001(a)gmail.com --- I couldn't get to work the latest nvidia drivers from their website. I'll have to stick with the repo ones -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #29 from debianxfce <fin4478(a)hotmail.com> --- (In reply to mi.bar.2001 from comment #28)
I couldn't get to work the latest nvidia drivers from their website. I'll have to stick with the repo ones
It is difficult remove Debian nvidia packages, there are many. But it is possible to remove them and boot with the nouveau or vesa driver. You need to install nvidia drivers withou X running, so download the .run file and boot to the linux kernel rescue mode with grub. You must have make, C compiler and kernel headers installed but maybe you have them because you can compile dkms driver. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #30 from mi.bar.2001(a)gmail.com --- I've recently noticed another bug - the sound is stuttering. It increases the longer I play, it happens every time. I'll attach a recording file probably tomorrow, when I'll figure out how to capture system sound -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Wine Severity|major |normal Component|-unknown |-unknown -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #31 from mi.bar.2001(a)gmail.com --- I've tried to record the stuttering, but the video was laggy and the sound disruption was just inaudible -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #32 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-6.4? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 Maxime <berillions(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |berillions(a)gmail.com --- Comment #33 from Maxime <berillions(a)gmail.com> --- (In reply to joaopa from comment #32)
Does the bug still occur with wine-6.4?
Wine-7.7 / Mesa 22.0.2 / AMD 6700XT - Some people complain for two different things : - Unable to launch the game from UPlay - The game crashes after the mission "Fireship" during the loading screen. In the both case, i don't have these issues anymore. Tried with the attachment 60008 from bug 43208 (Fireship mission ending before the loading screen) --> This BR can be closed i think. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 Erich E. Hoover <erich.e.hoover(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #34 from Erich E. Hoover <erich.e.hoover(a)gmail.com> --- Per comment #33. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43995 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #35 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 7.8. -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla