Closed powersshell closed 1 year ago
Hi @powersshell, can you please provide us with the system info? Help -> System Info -> Copy to Clipboard
Here is the system info - 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 22621), 64-bit edition Total RAM size [MB]: 33,738MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.20.00.20.220516 Vendor: ATI Technologies Inc. Renderer: AMD Radeon(TM) Graphics GLSL version: 4.60
Thank you, can you please try the following?
@stepikovo - Updating the GPU driver resolved the issue. I did not need to follow steps 2 or 3. Thank you for your assistance and this issue is resolved for me.
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.
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 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.
Yup, same for me. I've try 2.5.0 Alpha3, same behaviour
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 (version 22000), édition 64-bit Total RAM size [MB]: 68,626MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.7.1.220725 Vendor: ATI Technologies Inc. Renderer: AMD Radeon RX 5700 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.
Same thing for me. Since the latest AMD driver update, it's like that
I revert back to the last WHQL and it's working now.
The same issue exists with the 22.8.1 driver as well. Reverting to the WHQL 22.6.1 driver seems to be the fix. To note, this issue also occurs with Superslicer, same driver versions impacted. Strange. I suppose this is going to be a ticket for AMD's driver team, or is this something that can be fixed on the Prusaslicer side?
same problem here, using --sw-renderer flag seems to resolve it. The performance is unusable with that flag set though.
System info (latest optional AMD driver as of today. system info reports Windows 10, but I'm using Windows 11)
PrusaSlicer Version: 2.5.0-beta1+win64 Build: PrusaSlicer-2.5.0-beta1+win64-202208151053
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 22000), 64-bit edition Total RAM size [MB]: 34,200MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.8.1.220810 Vendor: ATI Technologies Inc. Renderer: AMD Radeon RX 6800 GLSL version: 4.60
This issue seems to be caused by recent AMD driver rework / optimization. @hejllukas is able to reproduce the issue on his computer, he will try to work around the AMD driver issue. It seems the issue is due to texture compression incompatibility.
Rolling my AMD GPU drivers back to version 22.6.1 (June 2022) fixed the problem for now...
I figured as much. Some games and applications have had issues with AMD's most recent performance 'optimizations' . Such is life.
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 AMD GPU driver issue should be resolved.
I'm still having this issue with PS 2.5.0. I am running a RX5700XT with AMD drivers 2.11.2.
I'm still having this issue with PS 2.5.0. I am running a RX5700XT with AMD drivers 2.11.2.
Same graphics cars, also having the problem. Already tried with the r1 and r2 version, problem remains.
I am having the same problem. Black bed texture. Kinda important since i use the bed texture to mark areas of my printbed that have bubbles/rips/defects so i can avoid printing on those areas.
Graphics card: ATI Radeon RX 580 running on driver 22.11.2
System Information: PrusaSlicer Version: 2.5.0+win64 Build: PrusaSlicer-2.5.0+win64-202209060714
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 19044), 64-bit edition Total RAM size [MB]: 17,119MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.11.2.221130 Vendor: ATI Technologies Inc. Renderer: Radeon RX 580 Series GLSL version: 4.60
RX 580 is based on Polaris/GCN, the RX 5700 series that is a sort of hybrid of GCN and RDNA1. I wonder if AMD changed something with the alpha 22.11.2 drivers? I have a 6900XT and a 6700XT in 2 separate workstations, based on RDNA2 both recently upgraded to 22.11.2 and neither has the black bedplate issue in PS since it was fixed a few months prior. Have you reverted to 22.11.1 for now?
RX 580 is based on Polaris/GCN, the RX 5700 series that is a sort of hybrid of GCN and RDNA1. I wonder if AMD changed something with the alpha 22.11.2 drivers? I have a 6900XT and a 6700XT in 2 separate workstations, based on RDNA2 both recently upgraded to 22.11.2 and neither has the black bedplate issue in PS since it was fixed a few months prior. Have you reverted to 22.11.1 for now?
I actually just updated from 22.11.1, because I was having the same problem with that driver, and I wanted to see if updating would fix it, but it didn't.
Issue is still there. RX 6700XT, latest driver (22.11.2). PrusaSlicer 2.5.0. The correct texture appears briefly then is replaced by a black rectangle.
running the program with "--sw-renderer" parameter It worked for me , RX5700xt 22.11.2 driver
I am still having this issue, but only on one of my printer configurations. Voron 2 350 will show the proper bed texture until I mouseover the 3D view and then revert to a black surface. OS is Windows 11 fully patched every time, GPU is AMD RX 5500 XT and happens with every update of AMD drivers since PrusaSlicer 2.5.0 was released.
I made a clean %AppData%\PrusaSlicer
folder and added every default printer configuration to test.
Artillery Genius, Hornet, Sidewinder flash the correct bed texture with brand logo and immediately revert to black.
Voron 1 300, Voron 2 300, 350 show the correct bed texture but revert to black on mouseover of the 3D view.
These two brands are the only ones that have PNG files as bed textures. All others have SVG files.
I think I have reduced my issue to PNG texture dimensions. Textures up to 2048×2048 work correctly at any dimension, and larger ones work correctly only for each exact doubling of dimensions (4096×4096, 8192×8192, 16384×16384).
Replacing the three (because of reuse, and Voron 1 and 2 files are identical) bed textures that have irregular sizes with 4096×4096 resampled files seems good enough for now. If the original textures were created as vector graphics maybe the authors could export to SVG and harmonize all printer profiles.
I'm attaching resampled files so that other users with the issue can confirm it.
PrusaSlicer Version: 2.5.0+win64 Build: PrusaSlicer-2.5.0+win64-202209060714
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 22621), 64-bit edition Total RAM size [MB]: 34,210MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.11.2.221130 Vendor: ATI Technologies Inc. Renderer: Radeon RX 5500 XT GLSL version: 4.60
I am still having this issue, but only on one of my printer configurations. Voron 2 350 will show the proper bed texture until I mouseover the 3D view and then revert to a black surface. OS is Windows 11 fully patched every time, GPU is AMD RX 5500 XT and happens with every update of AMD drivers since PrusaSlicer 2.5.0 was released.
I made a clean
%AppData%\PrusaSlicer
folder and added every default printer configuration to test. Artillery Genius, Hornet, Sidewinder flash the correct bed texture with brand logo and immediately revert to black. Voron 1 300, Voron 2 300, 350 show the correct bed texture but revert to black on mouseover of the 3D view. These two brands are the only ones that have PNG files as bed textures. All others have SVG files.I think I have reduced my issue to PNG texture dimensions. Textures up to 2048×2048 work correctly at any dimension, and larger ones work correctly only for each exact doubling of dimensions (4096×4096, 8192×8192, 16384×16384).
Replacing the three (because of reuse, and Voron 1 and 2 files are identical) bed textures that have irregular sizes with 4096×4096 resampled files seems good enough for now. If the original textures were created as vector graphics maybe the authors could export to SVG and harmonize all printer profiles.
I'm attaching resampled files so that other users with the issue can confirm it.
Resampled files: PrusaSlicer Version: 2.5.0+win64 Build: PrusaSlicer-2.5.0+win64-202209060714
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 22621), 64-bit edition Total RAM size [MB]: 34,210MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.11.2.221130 Vendor: ATI Technologies Inc. Renderer: Radeon RX 5500 XT GLSL version: 4.60
Installed extensions:
Thanks for this!!!! I managed to get my bed texture to stay displayed using the files you attached, and I did some experiments on my computer: 1) the texture does indeed only go black on mouseover. 2) for me, the png must be square and a multiple of 1024px by 1024px Notably the png must be square. I use my bed texture to demark areas of the print bed that have scratches and bubbles. First I scale my bed photo to be square, then add it in prusaslicer, which automatically stretches it back to the correct 250mmx210mm aspect ratio. Any multiple of 1024 px works but non-multiples do not, even if they are square. 3) if anybody wants to experiment on their own, simply loading a different printer profile without a bed texture and then loading the profile with the bed texture will update the rendering. There is no need to remove and reselect the png in the bed shape dialogue box.
Yes! A 1024px by 1024px png indeed works correctly with an AMD 6700XT GPU, as does a 512px by 512px. My original bitmap, which was briefly rendered before reverting to a black surface was square too, but not a multiple of 512. Problem solved, thank you!
(This should perhaps be added to future release notes, unless a solution for arbitrary png sizes is implemented that works with AMD GPUs)
running the program with "--sw-renderer" parameter It worked for me , RX5700xt 22.11.2 driver
Yes, this also works (thank you), but the use of square png's with a size that is a multiple of 512px by 512px might be preferable as it probably makes better use of the hardware and is also a more general solution, e.g. it also works as it should when opening a .3mf or .stl from the file explorer with a double click if PrusaSlicer has been associated to the file types
On further testing, I have the following results: 512x512 works 256x256 works 64x64 works 10x10 fails 9x9 fails 9x8 fails 8x8 works 8x7 works 8x5 works 5x3 works 2x2 works 1x1 works
Maybe someone smarter than me can make sense of this and hopefully use it to nail down this bug. System info as follows:
PrusaSlicer Version: 2.5.0+win64 Build: PrusaSlicer-2.5.0+win64-202209060714
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 19044), 64-bit edition Total RAM size [MB]: 17,119MB OpenGL installation GL version: 4.6.0 Compatibility Profile Context 22.11.2.221130 Vendor: ATI Technologies Inc. Renderer: Radeon RX 580 Series GLSL version: 4.60
I resized my Voron image to 4096x4096 and that worked as well.
Can you guys please test with 2.6.0-alpha3? Thanks.
Apparently no issues. I tried a lot of random PNG files as bed texture, all worked correctly. Windows 11, AMD RX5500XT, 22.11.2 drivers.
PrusaSlicer Version: 2.6.0-alpha3+win64 Build: PrusaSlicer-2.6.0-alpha3+win64-202302031521
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 11 (build 22621), 64-bit edition Total RAM size [MB]: 34,210MB OpenGL installation GL version: 4.6.0 Profile: Core Vendor: ATI Technologies Inc. Renderer: Radeon RX 5500 XT GLSL version: 4.60.0 Textures compression: Enabled
@dimitrisch Thanks for getting back to us. Closing the issue.
Just loaded Prusa Slic3r 2.6 on my new computer and I have the same issue with the all black platter. And I am running Ubuntu 20.04 with an AMD Radeon 6900 XT with the latest drivers for Ubuntu 20.04. I'm also using the PrusaSlicer-2.6.0+linux-x64-GTK3-202306191220.AppImage, so I can't delete the mk2.svg file.
Description of the bug
The printer build plate flashes correctly on application start up, then goes black. When importing a model you cannot review the model from underneath the build plate any longer after slicing it. I have tried multiple printer profiles as well as creating new physical printers.
Project file & How to reproduce
Open the Prusa Slicer 2.4.2 test.zip
Checklist of files included above
Version of PrusaSlicer
2.4.2+win64
Operating system
Windows 11 version 22621.160
Printer model
Prusa i3 MK3S with MMU2S