PursaSlicer 2.0.0 Not Responding
I'm attempting to start the PursaSlicer 2.0.0 but it gets stuck at not responding.
Oke here I have some update. The installer used is the 2.2.6 I could not download the 2.2.5 becouse it gave me a DNS error what I did attempt are the following things:
- Reboot off PC
- Run as admin
- Install as admin
I'm using Windows 10 I did succeed in running inital setup
Is there annyone who knows how to fix this problem?
I installed the 2.2.6 on a new windows 10 computer last night and it installed and runs fine so its not a global issue. I didnt install it admin either so I suspect its something about your pc it doesnt like. I would open an issue on github for it and hope one of the devs can give you some debug instructions so they can figure out what the issue is. https://github.com/prusa3d/PrusaSlicer/issues
Maybe try moving/clearing the PS configuration directory? Could be something got junked up in there and is making it crash.
Hey all thx for the replay I resolved the issue for now by removing leftovers in the %appdata% dir. I think something went rough
Hey all, Update. Again same problem. No cleu why
Usually it is a graphics card driver issue or incompatibility with PrusaSlicer. Sometimes an update of the graphics card driver helps.
As a workaround, you may try the software renderer by copyling the opengl.dll from the MESA directory next to the PrusaSlicer.exe, though the software renderer will be quite slow.
I am having the same issue what I have tried;
4x,. Uninstall, Reinstall, updated all drivers, uninstalled other slicer software, reinstalled PS 2.2.6. No help. Next is a HAMMER!
PS 2.2.6. You mean the driver package? P.Slicer is only at 2.0.0 released. 2.1.0-alpha (2.1.0-beta is seriously broken).
Thank you for the response. Yes the driver package. I have a new dell i7 gaming laptop with nvidia 1060 card and 16gb of ram. All drivers are up to date.
For grins, go into the slicer folder, copy the exe and rename the copy to remove the dash.
Then try running the renamed copy.
ps: Also - if you don't have a printer profile select (or installed) - that can give you grief.
And have you tried deleting the Prusa specific appdata folder - then reinstall ??
Hi, I did try taking the dash out, no help. I also deleted the app folder as well, no help. Thanks for the reply.
@tim-m30 I got it resolved. Seems it was a compilation of possible things that was causing it to lock up.
This was the sequence that cleared it, uninstalled completely, updated all video drivers, deleted the appdata folder, rebooted 2x, reinstalled the Driver pack and PS 2.0. I suspect you were correct in your assumption of the Appdata folder, there must have been a corrupt file in there.
Thanks for the help,
I just went through pretty much the whole process. What finished it for me, was removing ALL old files associated with PrusaSlicer from my %appdata% folder.
I did a full, 100% fresh re-install, and it immediately started up when I launched from the shortcut on the desktop.
Yeah.. If it's what I think it is, I posted on it in a few Redit forums.
There is a bug in the way the program closes when it is closed on a secondary or tertiary monitor. In the INI folder in C:\Users\[YOURNAME]\AppData\Roaming\PrusaSlicer contains a line that tells the slicer where it was on the monitor when it was closed last. If it was closed on a non-primary monitor, it writes a value that it cannot use and freezes half way through loading.
The line is: window_mainframe = 465; 30; 1455; 1020; 0
If you delete this line or just delete the INI file, it will start working again without losing your presets; though you will have to click your way through the setup again if you delete the INI.
Hope this helps.
You ever find yourself in the Baltimore/DC area, I'll buy you a drink. Strong work!
> There is a bug in the way the program closes when it is closed on a secondary or tertiary monitor.
This issue sounds like https://forum.prusaprinters.org/forum/prusaslicer/prusaslicer-no-longer-opens/
We tested that scenario, it shall work. I will ask our tester to re-test it.
You may want to check https://github.com/prusa3d/PrusaSlicer/issues/2522
The "Nahimic" driver that some manufacturers bundle with their laptops or motherboards seem to cause that issue. I am afraid we cannot do anything about it.
If you let me know where to find the specifics of that driver, I can check a couple of computers here to see if that jibes.
Look at this comment
Unfortunately I don't know more than that. I sent a complaint to the Nahimic company, but I did not receive any answer. You may try to do the same.