not responding in 3D TAB #672
Comments
|
I have to add my voice to this as well. I've been using the latest stable version (1.38.5) and the 3D tab will simply lock for the most part. I've used Intel's Driver and Support Assistant and just updated my graphics driver (HD 4000) today (Jan. 26, 2018). Still the same issue. I've not seen anyone with a clear answer as to how to resolve this reliably. I have an MK3 on order and hoped to use Slic3r - I'd rather not resort to another slicer if possible. Additional detail: Windows 10 Creators update (version 1709, build 16299.192) 64-bit |
|
You can try an older driver (+restart). There are no rule for this graphic driver bug. One time, i had to do this 5 times. |
|
I'll try that. If I find a version that works, I'll post it here. Thank you. |
|
Well, that was surprisingly easy. There are only three versions of the Intel HD 4000 driver for Win 10 64-bit. Two I've already tried (the version I installed just yesterday and a version I had installed earlier in the month). The third is the earliest driver for Windows 10: 15.33.43.4425 (found here). Once I installed this and restarted the computer, Slic3r works beautifully. I hope this can be of some use to others. |
|
Thanks PlacidCat! That worked for me too. thanks for link much appreciated. |
|
Odd. When I started Slic3r this morning, the 3D view is once again slow. No updates or reboots happened in between. I'd be curious if others, once they update their driver, notice things getting bad again. |
|
|
I'm guessing it might be 2. Intel still reports my drivers as being the same version as what I reported above. I might try rebooting and seeing what happens, just in case. I half wonder if there are conflicting libraries. |
|
Rebooted. Slic3r works again. I can live with that, even if it is inconvenient. I do hope that Intel/MS sit down together and resolve this or, in the mean time, for there to be some way for the Perl libraries to work around it. |
|
Guys, I am sorry to hear about the reappearing Intel HD Graphics issue. I am developing Slic3r on a laptop with the same class of an integrated graphics and I never had such issues. Would you please provide as much as possible information about your hardware? What computer is that, what mark, what year, what exact setup etc. We may try to buy one of those to be able to find some workaround. Thanks |
|
Sorry for the delay. I've attached the dump from Intel's DSA software. Please let me know if you need any additional information. I appreciate your willingness to investigate this. I really feel the fault lies with the driver manufacturers and you are stuck with the mess. This is an old laptop. The HD 4000 graphics alone is a sign of that. Also, the image of Windows 10 is fresh - I had a drive crash and had to re-install Win10. As such, there isn't the usual associated bloat with this laptop. |
|
On a side note, can you believe that even though Chrome is my default browser Windows decides to falsely claim IE is the default? :-) |
|
Good pc : M-5Y51 (HD 5300) windows 10 |
|
Same issue here with HD 4000. Is there any way to just disable the 3D tab in the absence of a fix? I would even settle for showing a different tab by default so I can at least get the software started. |
|
@justinvoelker - When I had the issue, I generally found that I can click one of the other tabs and hold the mouse button for a few seconds to ensure it registers and eventually that tab will appear. I often would select the Preview tab. After adding an object, a slicing of the model would, of course, cause it to appear. If you have the time, try the link to the drivers I mention in a few posts back. It has worked well for me aside from a quirky instance where things slowed down again. I haven't seen that issue since, though and now I'm happily using the 3D tab. |
|
There is a parameter --no-plater for opening Slic3r just for editing the
parameters. This settings is used by the Repetier Host, but I doubt it will
be of much use to you.
I tried to work around this issue by providing an option to disable
anti-aliasing and OpenGL 2.0 features through a new "Use legacy OpenGL 1.1
rendering" checkbox at the preferences dialog. Would you please try this
option? Thanks.
…On Tue, Jan 30, 2018 at 4:41 AM, PlacidCat ***@***.***> wrote:
@justinvoelker <https://github.com/justinvoelker> - When I had the issue,
I generally found that I can click one of the other tabs and hold the mouse
button for a few seconds to ensure it registers and eventually that tab
will appear. I often would select the Preview tab. After adding an object,
a slicing of the model would, of course, cause it to appear.
If you have the time, try the link to the drivers I mention in a few posts
back. It has worked well for me aside from a quirky instance where things
slowed down again. I haven't seen that issue since, though and now I'm
happily using the 3D tab.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#672 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5I2J8zKCBXHeYKcPBASyF33Y_WknHks5tPo9dgaJpZM4RVdHv>
.
|
|
@PlacidCat Thanks for the report. Is it this laptop?
What exact brand and type of a laptop is it? I am trying to find something we can actually buy and I can debug on it. |
|
My pc is the hp pavilion g6. Intel hd graphics 4000 driver. |
|
@bubnikv Yep! That's it. I got mine for under $400 re-purposed. (Ex-business machine.) I would hope there are better deals out there. I should mention I tried the legacy mode in my search for results and had no luck. I read somewhere about the issue perhaps being due to frames not being "committed" at certain points (sorry, I don't remember the address or the specifics). I don't know if the rendering on the 3D tab and the slicing preview tab has a different pipeline but I certainly never had issues on the latter. Thanks for looking into this. |
|
It's an asus taichi 21 (ultrabook). |
|
Thanks @PlacidCat. I actually updated to the newest HD 4000 drivers here trying to fix an issue in with OpenGL 2.0 in OpenSCAD but it appears that the new drivers actually fixed this issue in Slic3rPE. So, I guess that's a possible fix others may want to try as well. |
|
That's somewhat funny, @justinvoelker - those drivers didn't fix my issues with Slic3rPE. This, and the fact I had odd behavior even on my current drivers, really makes me wonder if there are two competing libraries on my computer. We have other machines in the house though, so I have a backup in case I can't get things working on mine. :-) |
|
We'll it wouldn't be any fun if the problem were consistent! For the record, I'm on an ASUS S56CA-DH51. |
|
Anybody willing to part with his laptop configured to hang with Slic3r due to the Intel HD Graphics driver issues? Anybody to sell the laptop to Prusa Research for a reasonable price? |
|
Not saying I wouldn't possibly part with my machine, but, is it really worth it to PR to buy my 5 year old laptop to debug an issue that is, at best, extremely sporadic? |
|
Not saying I wouldn't possibly part with my machine, but, is it really
worth it to PR to buy my 5 year old laptop to debug an issue that is, at
best, extremely sporadic?
Unfortunately yes, it seems to be worth, as the issue happens too often to
be ignored, and without a way to reproduce the issue we will likely burn
much more money on developers trying to work around it blindly.
…On Wed, Jan 31, 2018 at 11:43 PM, Justin Voelker ***@***.***> wrote:
Not saying I wouldn't possibly part with my machine, but, is it really
worth it to PR to buy my 5 year old laptop to debug an issue that is, at
best, extremely sporadic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#672 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5Ixj-E7hU3g22xIN0UXkNClkfV9DAks5tQOx3gaJpZM4RVdHv>
.
|
|
Ah, I see. Well @bubnikv, send me an email and we'll see if we can work something out. The reason I say that is that this is my primary machine so I'd have to buy a replacement before getting rid of this one. |
|
Same issue here. I'm running Windows 10 Pro on my Lenovo X1 Carbon 1st gen, Slicer for my brand new MK3 is useless, same as the MK2 version. What's funny is that the Prusa Control slicer works well. And just like for @PlacidCat, when I installed the old driver version, it works. But this is obviously an ugly workaround and I need my drivers current for other reasons. Not to mention never knowing when Windows Update will update me to the latest without me knowing. Technical details: PC: Lenovo X1 Carbon 34447MG (I'm also based in Prague so if there's any help I (or my laptop) could offer in person, let me know.) |
|
Seems like it's happening on the HD4000 only. |
|
It is very much Intel HD4000 related. It even sounds like different driver versions may or may not help. Drivers that did not work for others have worked for me and vice versa. |
|
@roesel It would help us immensely, if you could stop by with your laptop, so we could do couple of experiments. It would be great, if we could borrow your laptop for a day or two. We will happily compensate you with printing filament :-) |
|
@bubnikv I should be able to survive parting with my laptop for a few days. I could probably stop by your headquarters with the laptop and charger tomorrow morning on my way to work. Feel free to hit me up at [email protected] (in Czech if you want ;) ) and let me know if that works for you or if you want me to stop by a different day. |
|
Thanks to @roesel for lending his laptop to us for a day, I was able to investigate the issue and I believe I have a workaround for at least this particular laptop. We will release an updated beta today and we will hope for the best. For the technical folks out there, the OpenGL driver hangs on the call of glFlush(). |
on the laptop of @roesel. fixes #672 The Intel HD Graphics hangs on the glFinish() call for some reason with one particular graphics driver revision. Also the glFinish() call was superfluous and it only may have had negative effect over the performance. Both glFinish() and glFlush() were removed for performance reasons where they were not needed, see https://www.khronos.org/opengl/wiki/Common_Mistakes
|
By the way, my installation has decided to randomly act up again (no driver update - just stopped working) so I will test the commit as soon as I download the updated files and place them in my installation. I will test after updating drivers as well. Thanks everyone! |
|
OK, I downloaded the two files and updated them locally. Works like a dream - immediately after updating the files, things started to work. I will update my drivers later and try again. |
|
If you have this issue, would you please re-test with the latest beta build and report the results? Thank you. https://github.com/prusa3d/Slic3r/releases/tag/version_1.39.1-beta1 The fix consists of removing the OpenGL glFlush() calls. The glFlush() call was superfluous, but it certainly should not lead to such adverse effects. Removal of glFlush() calls certainly solved the issue on one laptop, so let's hope it will fix all the other issues or at least most of them. Thanks @roesel for providing a laptop for testing, it was a blessing to us. |
|
Worked with older drivers. Works with new drivers. I think we might have a winner! |
|
GREAT! it worked for me too. Thank you very much for sorting this issue. Thank you @roesel for the use of your laptop. im very happy now |
|
Fixed issue for me. |
Version
Version of Slic3r used goes here
1.37.2 prusa3d. win64, I use multi material version and Mk3 prusa version. both versions respond the same
Use
About->About Slic3rfor release versionsFor -dev versions, use
git describe --tagor get the hash value for the version you downloaded orgit rev-parse HEADOperating system type + version
What OS are you using, and state any version #s
Windows 10 home, V1709 OS build 16299.192 64bit
Behavior
not responding when in 3D TAB, works fine in 2D and preview. i have the latest Intel HD graphic driver - Installed Version: x.x.x.4653.
Is this a new feature request?
STL/Config (.ZIP) where problem occurs
Upload a zipped copy of an STL and your config (
File -> Export Config)The text was updated successfully, but these errors were encountered: