Slic3r 1.33.4 hangup on start #136
Comments
|
I can confirm this. Same on my system. Windows 10 Home 64-bit Intel i5-2450M. Language English. Path is c:\3dprinting\Slicerp |
|
That's bad. I suspect the OpenGL drivers. I will try to provide a build, which will initialize the OpenGL shaders first after the Layer Editing button is pressed. |
There is not much to do about it right now. I believe the OpenGL driver hangs somewhere. To make Slic3r usable on computers with buggy OpeGL drivers, I have moved the initialization of OpenGL shaders to the first invocation of the Layer Editing button. I have also enabled the printout of the OpenGL shader compilation error. If the next Slic3r release hangs on you, I am most interested into the result of the shader compilation log, which you may get by running slic3r-console.exe --gui |
|
I am closing the issue now. Please reopen the issue if you can reproduce the problem with 1.33.5. In that case, please provide a long printed out by slic3r-console.exe |
|
@bubnikv thank you very much! New version (1.33.5) is able to start, but hungs up after I press Layer editing button with the following message in console:
|
|
@roboprint would you please provide information on your graphics card, driver, OpenGL capabilities? |
|
|
How did you generate the list? Slic3r relies on the following OpenGL ARB extensions: It looks like your driver does not offer any of those. Could you update your graphics driver? I bet your driver supports the required capabilities, only the OpenGL binding through Perl / wxWidgets supports the OpenGL 1.5 with ARB extensions. While OpenGL 1.5 is supported everywhere on modern computers, the ARB extensions likely not, though these ARB extensions are just another interface to OpenGL 2.0 capabilities. I will likely have to rewrite the OpenGL part to C++ to get access to OpenGL 2.0, but not in this release. |
I used program that you provided (gpu caps viewer), last tab contains button that produces this info as far as I remember.
Sorry, but it's impossible. The only way to upgrade drivers is to buy new hardware. Both Microsot and Intel abandoned driver development for such 'old' Intel G45 chipset. So I'm using default drivers provided by Win10. |
|
I see now. I overlooked, that you driver only supports opengl 1.1. This
looks like the Windows software only renderer. I think I will sleep better
now. There is not much anyone can do with such a graphics card.
I shall integrate some diagnostics though.
…On Feb 17, 2017 8:15 PM, "roboprint" ***@***.***> wrote:
How did you generate the list?
I used program that you provided (gpu caps viewer), last tab contains
button that produces this info as far as I remember.
Could you update your graphics driver?
Sorry, but it's impossible. The only way to upgrade drivers is to buy new
hardware. Both Microsot and Intel abandoned driver development for such
'old' Intel G45 chipset. So I'm using default drivers provided by Win10.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#136 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5I0THjltj6xHs449aTH121aBsAoZgks5rdfG8gaJpZM4MDgli>
.
|
|
I understand that. In any case I'm happy that I can at least run and use Slic3r 1.33.5 after your fix. Thank you for your support. |
|
Thanks for the quick response. You are correct, Slic3r will now start up but hangs on Layer Editing. I tried to update my graphics driver but there are no updates. GPU Shark v0.9.10
|
|
@OttoES Would you please run slic3r-console.exe from cmd.exe and send me the print-out? |
|
I did it as follows: open cmd, run slic3r-console.exe. The gui started up - nothing new on the console. Loaded a stl file - all fine. Pressed "Layer Editing" crash with the following on the console: c:\3Dprinting\Slicer133\Slic3r>slic3r-console.exe Once again thanks for your time and effort. Just a side comment that it does work on my other computer. |
|
@OttoES It seems your OpenGL does not support one of the following legacy OpenGL extensions: ARB_shader_objects Would you please send me the following statistics?
I will likely not be able to fix it, but at least I will be able to do a correct diagnostics on the target computer. Thanks |
|
I really appreciate all the trouble but if this is an isolated problem I will just live with it. Here is the report you asked for. Thanks ===================================================
|
|
@OttoES It really helps me immensely, if I get a reasonable information from someone, who has having issues with the software. Would you please do one more test for me? Would you please replace a file and then run slic3r-console.exe --gui , select the Layer Editing and send me, what Slic3r wrote into the console? Added some debugging information into the Perl module I have attached here. Thanks. |
|
I will help you as much as I can. Did the same as before. First without --gui and repeated it with --gui with the same result: c:\3Dprinting\Slicer133\Slic3r>slic3r-console.exe |
|
@OttoES this looks like a soft renderer has been instantiated, though you
are having a recent opengl installed.
Aren't you using slic3r over remote desktop?
Would any opengl 2.0 application run? I think an Adobe mesh mixer is a good
example, it will complain, if only opengl 1.x is available.
…On Feb 18, 2017 5:11 PM, "OttoES" ***@***.***> wrote:
I will help you as much as I can. Did the same as before. First without
--gui and repeated it with --gui with the same result:
c:\3Dprinting\Slicer133\Slic3r>slic3r-console.exe
Info about Body1.STL:
size: x=32.111 y=114.000 z=135.261
number of facets: 4922
number of shells: 1
volume: 18944.064
needed repair: yes
degenerate facets: 0
edges fixed: 34
facets removed: 0
facets added: 0
facets reversed: 0
backwards edges: 0
GL version: 1.1.0, vendor: Microsoft Corporation, renderer: GDI Generic,
GLSL version: , ARB:
Missing OpenGL extension: GL_ARB_shader_objects
Missing OpenGL extension: GL_ARB_fragment_shader
Missing OpenGL extension: GL_ARB_vertex_shader
Missing OpenGL extension: GL_ARB_shading_language_100
Shader version: 0
glCreateShaderObjectARB is not supported by this renderer at
c:/3Dprinting/Slicer133/Slic3r/lib/Slic3r/GUI/GLShader.pm line 82.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#136 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5IwTTliv1L-ZhkGNsHo-FGB8Putruks5rdxhKgaJpZM4MDgli>
.
|
|
I am not running it over a remote desktop. I will try Adobe mesh mixer - must just download and install it. |
|
I installed mesh maker and it runs without any warnings. It runs quit smooth so I would guess that it does use OpenGL or at least some hardware assistance to do the rendering |
|
@OttoES It will be rendered in a Windows 95 style without the manifest, but it may initialize the OpenGL driver correctly. Please send me the console log. It may be very likely the following issue: I am still looking on the web for another reasons why Slic3r does not get the right OpeGL context. |
|
@OttoES |
|
I tried it in both win 8 and win 7 compatibility mode but both crashed. Once again thanks for all the trouble but I think it is just one of those incompatibility things that we will have to live with. |
|
Implemented detection of OpenGL capabilities: |
Version
Slic3r-1.33.4-prusa3d-win64-full-201702151702
Operating system type + version
I'm using 64-bit Win10 version 1511 os build 10586.753, english user interface. Windows username contains only standard latin characters, windows user home directory also does not contain non-latin chars.
Behavior
Both new releases of Slic3r (1.33.4 and 1.33.3) and both (win32 and win64) versions just hangs up on startup with 100% cpu usage.
I have tried startup with previous version configs in user directory and without configs at all.
The same behavior from all disks/paths, including c:\Slic3r and orginal c:\Slic3r-1.33.4-prusa3d-win64-full-201702151702
Previous release of Slic3r (1.31.6) working great without any problems.
Call stack of main thread in debugger:
The text was updated successfully, but these errors were encountered: