IntRenderer Error reproducible in my system. Attached log for details.
Tested with default settings from user_settings.py file enabled and Beta V2.0 version of the game.
After running I see an Error message: InitRenderer
OS: Ubuntu 18.04
Proton 3.16-6 Beta
Video drivers is updated.
70828.830:0024:0025:fixme:d3d9:d3d9_device_CreateRenderTargetEx iface 0x1f60b8, width 1920, height 1152, format 0x15, multisample_type 0, multisample_quality 0, lockable 0, surface 0x92580c, shared_handle (nil), usage 0 stub!
Blazblue Central Fiction now goes all over until the intro tries to play, after ArcSystem Works logo with Proton 4.11.1(with D9VK OFF), then crashes to desktop. Im glad we got over the initrenderer error but now it seems to crash at the intro movie. AWWW....
D9VK causes the old issue about initrenderer window.
I really like to see improvements, we need that extra mile to make it work. Thanks.
Attaching debug log file.
steam-586140.log
Update: Installed Quartz thru winetricks, still crash to desktop.
steam-586140.log
Thanks to user Z0z0z, the game is playable, even Online and lobbies tested and working fine. Still no intro video or videos on story mode but everything else is fine.
<Link removed by moderator>
Hello @Orochikyocr, the link you posted is legally problematic and has been removed.
System Information
Compatibility Report
Unplayable out of the box, game crashes before getting to the main menu. With mfplat workaround it is playable but with these issues:
Another game for issue #1464
Video codecs are:
WMV, WMV2 + WMA
GPU: RX 5600 XT
Driver: mesa 22.0.3
Kernel: 5.17.7-arch1-2
Distro: Archlinux
Proton: 7.0-2, Experimental, GoldenEggroll
Compatibility Report
Unplayable out of the box, game freezes before getting to the main menu. I haven't tested the mfplat workaround.
Sometimes after half an hour the game starts after playing the video.
Proton 6.3-8 works like a charm btw.
Proton 6.3-8 works on my machine, but there's no way to get controllers to work, no matter if Steam Input is on or off. Tested Dualshock 4 (wired) and Dualsense (wired).
Artix Linux on Linux 5.18.6-artix1-1; Mesa 22.1.2 on AMD Radeon RX 580
It works with all my controllers. Steam and everything elses works for you except blazblue?
Thats a bit odd.
Steam and everything elses works for you except blazblue? Thats a bit odd.
Yep. This is the only game that does not accept any input from my trusty Dualsense.
Log file:
steam-586140.log
Picking Mai Natsume in the character select screen causes the game to crash.
Additional information:
It seems like Proton 7.0-5 and versions below (I've this and 6.3-8) don't seem to be experiencing this issue but there appears to be a number of reports of instabilities on ProtonDB.
I can confirm that selecting Mai in Proton experimental crashes the game. It's really strange because no other character causes this crash (but I couldn't test Juubei because I don't have the dlc). I tried with GE-Proton7-43 too and it also crashed.
This isn't an issue with the beta Proton 7.0-6 Release Candidate.
@Yemi-1020 @luni3359 Thank you for reporting! This is indeed a regression, and turns out to be a regression in dxvk. I went ahead and filed an issue in the dxvk tracker (see mention above). For now, please feel free to continue using Proton 7.0-6 which has a different dxvk branch that does not include this commit :)
Blazblue Central Fiction: Game crashes when selecting a specific character
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6771.
@360nocompilesegfault posted on 2023-05-13T06:48:20:
The game crashes when choosing a specific character (Mai Natsume) in training/challenge mode. I have yet to try other modes but it seems to only occur when the person (on Linux) chooses her.
When online, opponents can choose her (presumably on windows) but the person on Linux will experience a crash.
I would like to note that this seems to occur with Proton 8.0_2. Proton 7.0_6 does not have this issue (I was able to switch back to this version and see that it works fine)
I can confirm this too. Same behaviour. Full AMD hardware running with current Archlinux and vulkan-radeon.
@360nocompilesegfault @pseiler Could you please try current Proton Experimental just to be sure this issue hasn't already been fixed? If you see the same crash on experimental-8, could you try dropping in dxvk from 7.0-6 into 8.0-2 to test if the bug is still in dxvk or if you are now running into a different bug? To test this:
cp ~/.steam/steam/steamapps/common/Proton 7.0/dist/lib/wine/dxvk/* ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/dxvk/.
cp ~/.steam/steam/steamapps/common/Proton 7.0/dist/lib64/wine/dxvk/* ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib64/wine/dxvk/.
When you are done testing, you can undo this by deleting the entire Proton 8.0/dist folder and it will recreate itself.
@alasky17
The crash still happens in experimental-8
I can confirm, however, that copying dxvk 7.0-6 over to 8.0-2 fixes the problem
@360nocompilesegfault could you provide a proton log from current experimental without moved dll's?
Edit: also @pseiler
Edit 2: nvm i see the mistake i made with the crash workaround :no_mouth:
@Blisto91 not sure if you still need it but just in case. I've attached the log when trying with proton experimental
steam-586140.log
@360nocompilesegfault Thanks for the log. The issue should now be worked around properly in Experimental Bleeding Edge. And will get pulled in to regular Experimental when ever dxvk is updated there.
I hadn't time to test it yet. But it seems that it's already located and will be fixed. Thank you very much @Blisto91
In the latest Proton experimental, the game opens to a black screen with a broken loading symbol in the bottom right corner. Proton 8.0-2 opens the game normally, selecting the character Mai Natsume still crashes the game as before.
Here are two logs, the first is the experimental problem and the second is the character select crash:
steam-586140-experimental.log
steam-586140-8.0-2-mai.log
Has proton Experimental updated dxvk yet or does the fix not actually fix the mai crash?
It includes the crash workaround yes. I will see if i can reproduce the black screen broken loading symbol issue.
The black screen issue is a dxvk regression that has already been fixed upstream but isn't included in regular Experimental yet. Only Bleeding Edge.
proton experimentalx5 2023-05proton 8.0-2x1 2023-05proton 7.0x1 2023-05proton 8.0x1 2023-05proton 7.0-6x2 2022-12ge-proton7-43x1 2022-12proton 7.0-5x1 2022-12proton 6.3-8x2 2022-06proton 4.11x2 2019-08proton 3.16-6x1 2019-01PULSE_LATENCY_MSEC=60 %command%x1 2020-03
Game doesnt start. Gives initrenderer error. I heard this problem sometimes happens on Windows too to a few people.
SteamOS Brewmaster Beta.
Both Proton Stable and Beta.
Amd A10 6410 with Radeon R5.
Update: Progress
The game now goes until the ASW logo, then blackscreen and crash to desktop with Proton 4.11.1