Notifications
Clear all

Intel HD3000 once again  

  RSS
karl-herbert
(@karl-herbert)
Illustrious Member
Intel HD3000 once again

Hello community,

my Dell E5420 with i5-2520 CPU and internal graphics HD3000 supports only OpenGL 3.1 which is not compatible with PrusaScli3r 2.1.0. The laptop is a bussines model 2014. On earlier Slicer versions there was an option for older graphics cards. Why did Prusa remove this from V 2.1.0. The most of us printer enthusiasts have little budget and do not want to upgrade their computer because of an Slicer-Update. Intel is not interested in an HD3000 update. What does prusa say about that?

Does anyone have a solution?

wbr, Karl

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 03/10/2019 7:41 pm
--
 --
(@)
Illustrious Member
RE: Intel HD3000 once again

Best to post over at github where devs might actually respond. This is a peer-to-peer forum, and as such we have little ability to help change code. My notebook is probably in the same state: so I'll be stuck with 2.0 or older for slicing.  But I have a desktop.   

Have you tried running Plicer on a Rpi4 ?  I'm not even sure it's possible, but the Rpi4 I am playing with seems to do some amazing stuff, and only $50.

Posted : 03/10/2019 8:37 pm
--
 --
(@)
Illustrious Member
RE: Intel HD3000 once again

A quick attempt yielded failure on the Rpi ... seems the code needs to be compiled for ARM for that to work.  With all the Rpi/Octoprint users, you'd think that would be a default.

Posted : 03/10/2019 9:31 pm
karl-herbert
(@karl-herbert)
Illustrious Member
Topic starter answered:
RE: Intel HD3000 once again

@tim-m30

thanks for feedback. I'll open a ticket on GitHub. Maybe i can find there a solution without changing the hardware.

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 04/10/2019 8:15 am
karl-herbert
(@karl-herbert)
Illustrious Member
Topic starter answered:
RE: Intel HD3000 once again

https://github.com/prusa3d/PrusaSlicer/issues/3032

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 04/10/2019 10:53 am
karl-herbert
(@karl-herbert)
Illustrious Member
Topic starter answered:
RE: Intel HD3000 once again

Prusas answer (issue 3008):

2.1.0 implements texture compression for reduced graphics memory usage.
2.1.0 shall behave better than 2.0. We cannot rule out a bug on our side,
but until we collect enough data, we cannot do much. For now, you may try
to update your graphics driver.

I told them, that newest drivers are installed and Intel closed the support 2016. Now i have the choice:

change hardware, change system, change slicer....

My solution was: I installed Linux Ubuntu 18.04 on the same machine and Slicer 2.1.0 is running now without any problems.

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 05/10/2019 9:28 pm
bobstro
(@bobstro)
Illustrious Member
RE: Intel HD3000 once again
Posted by: @karl-herbert-g

[...] My solution was: I installed Linux Ubuntu 18.04 on the same machine and Slicer 2.1.0 is running now without any problems.

Installing Linux fixes myriad problems. Glad you found good hardware support for legacy hardware on a current OS! Cheaper than replacing a perfectly functional computer.

My notes and disclaimers on 3D printing

and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan

Posted : 05/10/2019 9:36 pm
jebtrix
(@jebtrix)
Active Member
RE: Intel HD3000 once again

You can test this latest git build to see if that recent commit resolves it for you (unless you blew away your Windows OS installation 😏 ):

2.1.0-git-snapshot-1

Posted : 06/10/2019 9:34 am
karl-herbert
(@karl-herbert)
Illustrious Member
Topic starter answered:
RE: Intel HD3000 once again

@jebtrix

i copied the data from zip file into my existing slicer2.1.0 folder (by overwriting existing files) and got following error:

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 06/10/2019 10:55 am
jebtrix
(@jebtrix)
Active Member
RE: Intel HD3000 once again

My bad. I'm so used to building full debug builds for myself. If you visit the same releases page you will see a revised version. It includes the latest Microsoft VC_redist.x64.exe  runtime installer. You should just extract the zip into its own folder (Desktop is fine) and run it from there since your just testing it.

Posted : 06/10/2019 7:56 pm
karl-herbert
(@karl-herbert)
Illustrious Member
Topic starter answered:
RE: Intel HD3000 once again

Uninstalled current version 2.1.0, installed VC_redist_x64 (VC++), systemrestart, tryed as user and admin, always the same issue, after one second slicer lost the texture mk3.svg on display.

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 07/10/2019 6:00 pm
jebtrix
(@jebtrix)
Active Member
RE: Intel HD3000 once again

It looks like the dev responsible for trying to fix is going thru the effort of providing git builds himself. Just keep watching that github issue. I'm sure the dev will keep posting builds himself as he tackles this problem. Since he may be compiling a special test branch just keep trying out his posted test builds. Keep the feedback going there when you do. 

Posted : 07/10/2019 10:27 pm
karl-herbert
(@karl-herbert)
Illustrious Member
Topic starter answered:
RE: Intel HD3000 once again

Thanks, if something has changed, I will report!

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 08/10/2019 8:32 pm
Share: