Isadora freeze on startup (Windows 10)
-
Inspired by @dgaddy 's comment I had a look into my AMD graphics driver again and found a solution that works for me so far.
After an update of my Radeon driver from 18.3.1 to 18.3.3 one setting now solves the problem: Switching "Wait for Vertical Refresh" from the default "Off, Unless Application Specifies" to "Always Off". I think there must be a conflict in handling OpenGL.
Thanks for everyone's input in this thread, I can now go on and actually test Isadora. :)
-
hello,
i have the same problem on my new laptop when I launch Isadora with external monitor or videoprojector on windows10 with a gtx 1060 and an intel graphic card. (displaying "Cycles 999.9 FPS 99.9").
best
Pascal
-
@pascal
Have you gone to your NVidia control panel, under 3d settings / manage 3d settings / program settings tab, and set Isadora.exe to only use the dedicated/high performance graphics card?
This setting solves problems with Spout video sharing, and may be required on laptops that have NVidia optimus or the equivalent AMD power saving feature. -
@DusX .....Done and it seems to resolve the problem : Un grand merci à toi pour tes conseils et ta générosité.
Best,
Pascal
-
@pascal said:
unch Isadora with external monitor or videoprojector on windows10 with a gtx 1060 and an intel graphic card. (displaying "Cycles 999.9 FPS 99.9").
I am having the same problems, testing my Laptop Win10 + GTX960.
If I start Isadorra with external monitor connected, it hangs with a white screen on both monitors.
I've tried all possible solutions mentioned here, no luck.
-
-
SOLVED
I had several problems with other software too, when playing video on the external HDMI output.
The problem is a process installed by MSI software: "NahimicMSISvc32.exe"
Just kill this process and Isadora opens flawlessly, opening the Stage fullscreen on the second monitor.
Thanks Ryan Webber for your advice. It was "a shot in the dark", but it worked!
Now I've rememebered I used to have a "clean.bat" batch file in my previous laptop, just for performing live with Isadora.
So I made a new one, killing most of the unnecessary processes (for live acts).
Here it is, in case someone finds it useful:
echo on
title LIVE setup: spring cleaning
echo
echo Live SETUP
echo
echo Killing nasty processes
echo
taskkill /f /im "Dragon Gaming Center.exe"
taskkill /f /im "NahimicMSIUILauncher.exe"
taskkill /f /im "SCM.exe"
taskkill /f /im "Silent Option.exe"
taskkill /f /im "XMouseButtonControl.exe"
taskkill /f /im "MSIService.exe"
taskkill /f /im "NahimicMSISvc64.exe"
taskkill /f /im "NahimicMSISvc32.exe"
taskkill /f /im "QMxNetworkSync.exe"
taskkill /f /im "mic_mute.exe"
taskkill /f /im "SteelSeriesEngine3.exe"
taskkill /f /im "AGSService.exe"
taskkill /f /im "ShareX.exe"
pauseI am so HAPPY !
-
I have this problem on my laptop every time W10 get a mayor udpate (anniversaty, creative and so on) only way found is to uninstall through DDU all video drivers and then install newest. This solve every time this bug on my laptop
-
Hello,
I just bought a windows laptop (MSI GS65 stealth with GTX1070) and I had the same problems: Isadora crashing with white screen, DaVinci resolve crashing, TouchDesigner crashing I have searched ruring 5 days and the solution of killing Nahimi is working perfectly, thanks to everibody. All is tipTop now.Jacques
-
@jhoepffner
I had a user recently with a MSI, same problem, and same solution (he posted to the forum somewhere to document it). -
Hello,
Here is the updated batch app for killing msi nahimic (the main culprit of white screen)
echo on
title LIVE setup: spring cleaning
echo echo Live SETUP
echo
echo Killing nasty processes
echo
taskkill /f /im "NahimicService.exe"
taskkill /f /im "NahimicSvc32.exe"
taskkill /f /im "NahimicSvc64.exe"
taskkill /f /im "MSIService.exe"
taskkill /f /im "AGSService.exe"
taskkill /f /im "ShareX.exe"
pauseHope that helps
-
It's happening again. Isadora 2.6.1 worked fine all day and tonight won't initialize. I get the same freeze on startup: 999.9 cycles, etc. I don't have Nahimic, optimized my NVidia graphics months ago. Any other solutions?
-
If Isadora was working in the morning it is very unlikely the new problem is with Isadora.
The application folder doesn't have any thing that changes, so it could really only be something external.Have you installed anything today?
Have you tried clearing your preference file?
Move your Freeframe, GLSL files, and Global User Actors? (so that they do not load on startup)