OrcaSlicer
OrcaSlicer copied to clipboard
Support painting and seam painting
OrcaSlicer Version
1.9.0
OS version
Windows 10
Additional system information
No response
Printer
Sovol SV01
How to reproduce
Import file choose an object click Support painting or Seam painting
the object disappears
Actual results
no possibility to manipulate both paintings
Expected results
see the object
Project file & Debug log uploads
Checklist of files to include
- [ ] Log file
- [ ] Project file
Same Issue here.
I had the same problem. Rolled back to the previous version. Works on it.
I was having the same issue, with a notebook that has Nvidia card and AMD integrated graphics. Setting the OrcaSlicer to use the Nvidia card instead of the AMD IG made it work.
On windows 10/11, this is done in the Graphics settings (Settings>Display>Graphic settings link at the end), choosing the orca slicer executable (at Program Files/OrcaSlicer) and changing the options to use High Performance with the Nvidia Graphics.
There seems to be some compatibility issue with AMD Vega GPUs.
Same problem here on my laptop with an AMD Ryzen 5 4500U with Radeon Graphics. Previous Orca version had no issues. Windows 11.
No problems on my colleagues Intel processor, Nvidia graphics card system.
I have Nvidia dGPU and AMD integrated graphics. Forcing Orca-slicer to use either integrated or dGPU does not fix the issue of the model not appearing when support painting for me.
Edit: noisyfox's comment on using the windows display setting worked for me.
I have Nvidia dGPU and AMD integrated graphics. Forcing Orca-slicer to use either integrated or dGPU does not fix the issue of the model not appearing when support painting for me.
Make sure you force the dGPU from windows' own display settings, not from Nvidia control panel.
I just test ist on my notebook with Nvidia graphics - all is ok The desktop computer has AMD Radeon R7 graphics
I am experiencing the same problem. Win11, AMD Vega graphics card.
Forcing Orca to use the on-chip graphics card (Intel "something") did not change the behaviour. (But maybe changing that setting did not work as expected - I don't know.)
I had no problems with AMD Vega and previous versions.