-
Notifications
You must be signed in to change notification settings - Fork 1.9k
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PrusaSlicer 2.1.1 locks up when opening on 2nd monitor in windows 10 #3689
Comments
I have the same/similar issue, only exacerbated since my original main display broke (thanks VR...) so I can no longer move PrusaSlicer back to that display to get it working again. Win 10, 64 Additionally, I do not have sonic studio installed, and add/remove programs has nothing when I search for Nahimic or sonic. I do, however have the Nahimic service. But even when I stopped the service my display driver crashes. It seems like whatever PrusaSlicer is doing also causes nvlddmkm to crash, with the Nahimic service running and not. While PrusaSlicer does not crash for me since updating to 2.2.0, any attempt to rotate the build plate or click within the application causes the application to lag heavily (mouse cursor jumps from position to position) and eventually the display driver crashes again. I seem to recall the last time I encountered this issue there was a file that could be deleted from the AppData/path/to/prusa that reset the application settings, which also fixes the issue. |
Hello. I would like to ask users having troubles with Nahimic libraries to try this build. It should display warning dialog about NahimicOSD.dll linked. We know that this is just a warning rather than a solution, but currently we have no way to stop loading this library as it comes linked statically when we start our process. Also if you are aware of another libraries of same source please let us know their names. You can find it with ProcessExplorer tool. |
There was no response. We believe the issue is the dreaded Nahimic driver injection. Warning about the Nahimic DLL being injected into PrusaSlicer will be rolled out with PrusaSlicer 2.4.0-alpha1. It is not a "fix" for the nahimic issue, but at least the user will be informed. |
Version
2.1.1
Use
About->About PrusaSlicer
for release versionsFor -dev versions, use
git describe --tag
or get the hash value for the version you downloaded orgit rev-parse HEAD
Operating system type + version: Windows 10 Pro 64bit
What OS are you using, and state any version #s
In case of 3D rendering issues, please attach the content of menu Help -> System Info dialog
3D printer brand / version + firmware version (if known)
What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s
Behavior
PrusaSlicer opens fine on main monitor #1. If moved to Monitor #2, closed, and restarting Prusaslicer defaults to Monitor #2 it will hang and be nonresponsive. Had to duplicate display to move opening location of program to Monitor #1 and works again.
Is this a new feature request?
Project File (.3MF) where problem occurs
Upload a PrusaSlicer Project File (.3MF) (
Plater -> Export plate as 3MF
for Slic3r PE 1.41.2 and older,File -> Save
/Save Project
for PrusaSlicer, Slic3r PE 1.42.0-alpha and newer)Images (PNG, GIF, JPEG), PDFs or text files could be drag & dropped to the issue directly, while all other files need to be zipped first (.zip, .gz)
The text was updated successfully, but these errors were encountered: