Open the-powl opened 2 months ago
Hi, please attach your system info to provide us with more data. It may help us. If you export the G-code and then open it in a G-code viewer, is the issue observed as well?
Hello, same problem. After opening G-code in G-code viewer, the problem is also observed. PrusaSlicer Version: 2.8.0+win64 Build: PrusaSlicer-2.8.0+win64-202406270929
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (сборка 19045), 64-бит редакция Total RAM size [MB]: 17,124MB OpenGL installation GL version: 3.3.0 (3.3.0) Profile: Core Vendor: NVIDIA Corporation Renderer: GeForce 8800 GT/PCIe/SSE2 GLSL version: 3.30.0 Textures compression: Enabled Mutisampling: Enabled (4 samples)
The same for me. Previous versions where good to use. The 2.8.0 is unusable in G-Code preview (I can't rotate the screen anymore for big models).
Specs:
PrusaSlicer
Version: 2.8.0+win64
Build: PrusaSlicer-2.8.0+win64-202406270929
Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 11 (build 22631), 64-bit edition
Total RAM size [MB]: 17,109MB
OpenGL installation
GL version: 3.3.0 (3.3 (Core Profile) Mesa 12.0.0-rc2)
Profile: Core
Vendor: VMware, Inc.
Renderer: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
GLSL version: 3.30.0
Textures compression: Disabled
Mutisampling: Disabled
Very, very, very slow response in Previewmode and G-Code Viewer.
PrusaSlicer Version: 2.8.0+1-lm-spe2411-MacOS-x64 Build: PrusaSlicer-2.8.0+1-lm-spe2411-MacOS-x64-g86e8e256a-202407171406
Operating System: Macintosh System Architecture: 64 bit System Version: macOS Mojave Version 10.14.6 (Build 18G103) Total RAM size [MB]: 8,590MB OpenGL installation GL version: 3.3.0 (3.3 NVIDIA-10.4.14 310.90.30.05b27) Profile: Core Vendor: NVIDIA Corporation Renderer: NVIDIA GeForce GT 330M OpenGL Engine GLSL version: 3.30.0 Textures compression: Enabled Mutisampling: Enabled (4 samples)
Same on my machine. Although I don't see any performance drops in the slicer, I see it affecting other graphics-heavy applications when the slicer is in the background, doing nothing and showing a static picture. Task manager shows the slicer running my GPU at 75% - and that's for an NVidia 4060.
Version: 2.8.0+win64
Build: PrusaSlicer-2.8.0+win64-202406270929
Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (сборка 19045), 64-бит редакция
Total RAM size [MB]: 16,781MB
OpenGL installation
GL version: 4.6.0 (4.6.0 NVIDIA 556.12)
Profile: Core
Vendor: NVIDIA Corporation
Renderer: NVIDIA GeForce RTX 4060 Laptop GPU/PCIe/SSE2
GLSL version: 4.60.0
Textures compression: Enabled
Mutisampling: Enabled (4 samples)
same here, Model view is working without any issue even with models over 1M tris, gcode view is barely usable.
PrusaSlicer
Version: 2.8.0+linux-x64-GTK3
Build: PrusaSlicer-2.8.0+linux-x64-GTK3-202406270929
Operating System: Unix
System Architecture: 64 bit
System Version: Linux 6.1.0-23-amd64 x86_64
Total RAM size [MB]: 7,202MB
OpenGL installation
GL version: 4.6.0 (4.6 (Core Profile) Mesa 22.3.6)
Profile: Core
Vendor: AMD
Renderer: AMD Radeon Vega 8 Graphics (raven, LLVM 15.0.6, DRM 3.49, 6.1.0-23-amd64)
GLSL version: 4.60.0
Textures compression: Enabled
Mutisampling: Enabled (4 samples)
Here's mine:
PrusaSlicer
Version: 2.8.0+win64
Build: PrusaSlicer-2.8.0+win64-202406270929
Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (build 19045), 64-bit edition
Total RAM size [MB]: 34,141MB
OpenGL installation
GL version: 4.6.0 (4.6.0 - Build 31.0.101.3959)
Profile: Core
Vendor: Intel
Renderer: Intel(R) UHD Graphics 770
GLSL version: 4.60.0
Textures compression: Enabled
Mutisampling: Enabled (4 samples)
I reverted back to PrusaSlicer 2.7.4 because 2.8.0 is not usable at all for me.
Over 90% GPU load when it is showing a static image. I hear fans on full blast.
UPD: Sometimes Edge WebView also adds random spikes of up to 30% (even though the physical printer tab is not even open), but I guess that's beyond our power to fix.
I'm seeing the exact same thing on MacOS Monterey, PrusaSlicer 2.8.0 is completely unusable when in the sliced gcode view, moving rotating the object, view layers and just clicking in the interface produces horrible lag. In addition to this here, I've relayed the same info in email to prusa. Version 2.7.4 was rock solid, no issues. Really need this working so I don't have to manually build profiles for the MK4S in version 2.7.4 - Here's the system info:
Version: 2.8.0+MacOS-x64 Build: PrusaSlicer-2.8.0+MacOS-x64-202406270936 Operating System: Macintosh System Architecture: 64 bit System Version: macOS Monterey Version 12.7.6 (Build 21H1320) Total RAM size [MB]: 17,180MB Resident memory: 456MB Peak memory usage: 918MB RAM size reserved for the Undo / Redo stack: 1,074MB RAM size occupied by the Undo / Redo stack: 0MB OpenGL installation GL version: 4.1.0 (4.1 INTEL-18.8.16) Profile: Core Vendor: Intel Inc. Renderer: Intel Iris Pro OpenGL Engine GLSL version: 4.10.0 Textures compression: Enabled Mutisampling: Enabled (4 samples) Installed extensions: GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_explicit_attrib_location GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_attrib_64bit GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ATI_texture_mirror_once GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_sRGB_decode GL_NV_texture_barrier Eigen vectorization supported: SSE, SSE2, SSE3, SSSE3, SSE4.1
Seems to be a duplicate of #12937
Seems to be a duplicate of #12937
U will find lots of similar complaints since 2.8 is avable. It´s performance bug still pending and unresolved. 2.7 was rocksolid even on weak/old Hardware. 2.8 Preview is a pain in tha and it feels like dev´s dont work it out.
@DerKameramann PrusaSlicer 2.7.4 is still avaliable for download. PrusaSlicer is Open Source, if you want to contribute a fix dont hesitate to do so.
its summer and vacation season, the devs have a life/family, please be patient.
no wonder OSS devs want to quit, suffer from bornout etc. when they have to deal with stuff like your comment. be patient and refrain from implying the devs dont care about this issue.
@DerKameramann PrusaSlicer 2.7.4 is still avaliable for download. no way ...
PrusaSlicer is Open Source, if you want to contribute a fix dont hesitate to do so. there is no need for another codenerd and I dont think you want me to teach how to fix such issues so dont call me up.
its summer and vacation season, the devs have a life/family, please be patient. well, a bunch of people, including me, are patient for 3 Months already i know they work on it - that´s why version 2.8.0 +1 is existent - but the problem persists and some say its parent is a major revision in the developer tool´s world dropping older hardware support. true? probably maybe. A statement like "nope, old hardware is not supported any longer" or forking a 2.7.x lts version dedicated to older hardware are possible moves.
no wonder OSS devs want to quit, suffer from bornout etc. when they have to deal with stuff like your comment. be patient and refrain from implying the devs dont care about this issue. did i say something like they dont care?
slow preview on my System too PrusaSlicer Version: 2.8.0+win64 Build: PrusaSlicer-2.8.0+win64-202406270929
Operating System: Windows System Architecture: 64 bit Windows Version: Windows 11 (Erzeugungsversion 22000), 64-bit Edition Total RAM size [MB]: 34,280MB OpenGL installation GL version: 3.3.0 (3.3 (Core Profile) Mesa 12.0.0-rc2) Profile: Core Vendor: VMware, Inc. Renderer: Gallium 0.4 on llvmpipe (LLVM 3.6, 256 bits) GLSL version: 3.30.0 Textures compression: Disabled Mutisampling: Disabled
How to enable the last 2 and how to update GLSL version ?
Greetings and THX
Description of the bug
The graphics performance of PrusaSlicer 2.8.0 seems to have largely declined on my machine. I'm using the internalt Intel UHD Graphics 770 of my Intel Core i5 Processor and that's usually sufficient. But with the newest version of PrusaSlicer when I want to rotate the view on a half decent model in the sliced Preview the framerate drops to below <1fps. For large prints this is not even usable any more.
Project file & How to reproduce
gdsgf
Checklist of files included above
Version of PrusaSlicer
2.8.0
Operating system
Windows 10
Printer model
irrelevant