Closed TheMrCaveman closed 2 years ago
I am on the latest amd gpu driver, have a 6950xt and the only way I can solve this is removing textures. Due note I am in the beta driver testing thing so might also pass this onto amd.
@TheMrCaveman can you please try a different version of drivers? When did this start happening? Can you send us the System info from the Help menu?
same problem newest amd drivers can confirm it was functional with older amd drivers
system info is here ` PrusaSlicer Version: 2.5.0-alpha3+win64 Build: PrusaSlicer-2.5.0-alpha3+win64-202207151230
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 22000), 64-bit edition Total RAM size [MB]: 17,102MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.7.1.220725 Vendor: ATI Technologies Inc. Renderer: Radeon RX 5500 XT GLSL version: 4.60
`
Same problem here. but the bed svg renders correctly with software render switch. It started to happen with AMD 22.7.1 version of Radeon drivers. To be noted, I have no other issues what so ever with any other software UI render. For some reason the OpenGL driver new version does not seem to be supported by PrusaSlicer.
PrusaSlicer Version: 2.4.2+win64 Build: PrusaSlicer-2.4.2+win64-202204251110
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 19044), 64-bit edition Total RAM size [MB]: 34,261MB OpenGL installation GL version: 3.0 Mesa 12.0.0-rc2 Vendor: VMware, Inc. Renderer: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits) GLSL version: 1.30
Same problem.
PrusaSlicer Version: 2.4.2+win64 Build: PrusaSlicer-2.4.2+win64-202204251110
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (Erzeugungsversion 22000), 64-bit Edition Total RAM size [MB]: 51,435MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.7.1.220725 Vendor: ATI Technologies Inc. Renderer: AMD Radeon RX 6700 XT GLSL version: 4.60
I have just started to get this problem. It happens in v2.4.x and 2.5.x Unfortunately I updated my AMD 5700X Win10 64 drivers and the PrusaSlicer configuration on the same day so cannot be sure which caused this error. I deleted the config files from under AppData/Roaming and let PS create new ones but it didn't resolve the problem.
When PS loads the correct texture is shown for a second or 2 then it turns black just as in TheMrCaveman's screenshot.
PrusaSlicer 2.5.0 Beta 1 Windows 10 Pro x64 AMD 5700 XT AMD Driver v22.7.1
PS System Info attached: SysInfo.txt
UPDATE: Latest AMD drivers now installed 22.8.1 (12 Aug) problem still exists...
I also updated to AMD Driver 22.8.1 and tried PrusaSlicer Version 2.5.0-beta1+win64. No luck = build plate is black. The initial start of the new beta shows the grid but after closing the dialog its black again.
BTW: Ultimaker Cura 5.1.0 has no problem with the AMD Driver 22.8.1 but I want of course use PrusaSlicer.
Rolling my AMD GPU drivers back to version 22.6.1 (June 2022) fixed the problem for now...
We tried to investigate this issue, and it seems that the two latest AMD GPU drivers, 22.8.1 and 22.7.1, probably contain some bug that is causing missing bed texture. For some reason, those new drivers have an issue when mipmaps are generated manually on CPU sides combined with texture compression.
We generate mipmaps manually on the CPU side because we previously had issues on some GPUs with generating mipmaps on the GPU side. And for some reason, those new drivers stopped accepting texture mipmaps generated on the CPU side.
So we made a workaround that for AMD GPUs with drivers newer than 22.6.1 (the latest working driver), we generate mipmaps on the GPU side, which seems to work correctly now. This workaround will be part of the upcoming PrusaSlicer 2.5.0-rc1, so the texture of the bed should start showing again.
For older PrusaSlicer versions, the only way (at the moment) to get texture showing is to downgrade the AMD driver to 22.6.1 or 22.5.1 (WHQL).
Please try with PrusaSlicer 2.5.0-rc1. The issue should be resolved.
In the end generating textures on the GPU side should be preferable. Not only because of the possible bug but also for better performance. Right?
We cannot know how the driver works. If we ask the driver to create mipmap, we don't know whether the mipmap will be constructed on CPU or GPU. It is driver's responsibility.
pá 19. 8. 2022 v 18:44 odesílatel Michael Klengel @.***> napsal:
In the end generating textures on the GPU side should be preferable. Not only because of the possible bug but also for better performance. Right?
— Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/8508#issuecomment-1220881521, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSIZZ4FKLGIHE3BIPKJLVZ62V5ANCNFSM53VDHOYQ . You are receiving this because you commented.Message ID: @.***>
I can confirm PrusaSlicer 2.5.0-rc1 shows the texture again.
Fixed my problem can comfirm thank you for your hard work.
Ok guys, thanks for confirmation of bugfix. I am closing the issue.
I do have the problem again with prusaslicer 2.5.0 and the latest driver AMD-PRO-Edition 22 Q3 I'm not using the adrenalin edition but the pro edition.
I'm a little confused why the bugfix is not working here.
PrusaSlicer Version: 2.5.0+win64 Build: PrusaSlicer-2.5.0+win64-202209060714
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (Erzeugungsversion 22000), 64-bit Edition Total RAM size [MB]: 33,689MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context .220823 Vendor: ATI Technologies Inc. Renderer: AMD Radeon RX 6600 XT GLSL version: 4.60
I too, have the 22.Q3 release for my Radeon RX 580. It's been working fine up to the update, when it went black. Using the '--sw-renderer' work around does allow it work, but it's not a fix.
I have the same issue with an RX 570, although as mentioned this its pretty clearly a bug on AMD's side. It seems that with every new driver release they break things in a new and interesting way. Credit to Prusa for trying to work around it, however at some point AMD needs to fix this issue on their end.
I'm having the same issue. WX 3200 series video card. Installed the latest drivers, problem still persists.
Running latest Radeon PRO drivers, 2022Q4, still the same issue.
I am running a Radeon RX 5700 on driver ver 22.11.1 and am now experiencing the same issue on PS 2.5.0.
I am also having this issue, with a RX5700XT and the 22.11.1 drivers, using PS 2.5.0. It's certainly annoying.
I am also having this issue, with a RX5700XT and the 22.11.1 drivers, using PS 2.5.0. It's certainly annoying.
running the program with "--sw-renderer" parameter It worked for me , RX5700xt 22.11.2 driver
Description of the bug
Prusaslicer should have bed textures. Most of them are vissible for a blink then turn black.
Project file & How to reproduce
open prusaslicer and select any printer r
Checklist of files included above
Version of PrusaSlicer
2.4.2, 2.5.0 alpha 2
Operating system
windows 11
Printer model
mk3s+