OrcaSlicer icon indicating copy to clipboard operation
OrcaSlicer copied to clipboard

Black build plates after adding different printer pack

Open axi0m89 opened this issue 2 years ago • 5 comments

Describe the bug On the Mecury one Zero G discord one of the members created a "pack" for the Zero G conversion. It contains printer images as well as the printer .json - This appears to be related to AMD drivers only and Prusa Slicer had the issue in 2022 but looks like the resovled it. https://github.com/prusa3d/PrusaSlicer/issues/8678 - This is affecting all build plates not just the ones used for the Zero G pack

To Reproduce AMD drivers and then copy the files from the Zero G pack and put them in the resources folder.

Expected behavior Build plates to remain normal

Screenshots image

Printer model Ender 5+ Converting to a Mecury one Zero G

Desktop (please complete the following information):

  • OS: Windows 11
  • Version: 22H2
  • AMD Graphics Driver 31.0.14057.2005 for the 6800XT

axi0m89 avatar May 29 '23 21:05 axi0m89

Looks like it is related to the dimensions of the used texture. A temporary fix is to set the dimensions to a power of 2, such as 512 x 512 or 1024 x 1024. See also the related comments for the Prusa Slicer issue.

landomando avatar Jun 10 '23 15:06 landomando

Looks like it is related to the dimensions of the used texture. A temporary fix is to set the dimensions to a power of 2, such as 512 x 512 or 1024 x 1024. See also the related comments for the Prusa Slicer issue.

Deleting the texture from the resources folder does fix the issue

axi0m89 avatar Jun 22 '23 17:06 axi0m89

Hi! I´ve found another solution that was the only way for my buildplate to look right again: I have a Sovol SV05, and I couldn´t find the file to delete in the resource-folder as mentioned here. Instead I deleted the file "sovol_sv05_buildplate_texture.png" located in "OrcaSlicer_Windows_portable\resources\profiles\Sovol" and was very pleased with myself when I managed to fixe the issue... I guess I just didn´t find it the first time I checked the resource-folder since the file is located 2 steps further into the foldertree, and that got me thinking that there may be other 3d-print owners out there that makes the same mistake I did, so I thought I post this as a suggestion on where to look for the file to delete... Naturally I deleted the one that was meant for my printermodel (Sovol), and others will obviously have to go in to the folder that is used for their printerbrand... Best regards VHelst

VHelst avatar Sep 10 '23 19:09 VHelst

I fixed this issue by replacing the PNG file with an SVG one AND pointing the "bed_texture" to it.

zsmbrvr avatar Sep 23 '23 17:09 zsmbrvr

GitHub bot: this issue is stale because it has been open for 90 days with no activity.

github-actions[bot] avatar Dec 23 '23 00:12 github-actions[bot]

GitHub bot: This issue was closed because it has been inactive for 7 days since being marked as stale.

github-actions[bot] avatar Dec 31 '23 00:12 github-actions[bot]