![]() In your case, you are still getting issues with software rendering This has obviously happened in the past, since SharpCap detects this failure the first time and tries to resolve the issue by switching from graphics card accelerated rendering to software rendering. I can see that what is happening is the graphics rendering system (a Windows component used by SharpCap) has failed during the resolution change. OK, I have found the bug report now, thank you. In your situation, I would suggest trying the wired connection to see if it does work reliably - that would at least confirm or refute the theory that the problem is coming from an unreliable wifi connection. However, in your case, since you are using WIFI there is no serial port involved. In both cases, SharpCap will request that the ASCOM driver connects to the mount hardware, and that will fail.ĭon't worry about the 'serial port' message - that is just something that SharpCap adds, since the that is one of the common causes of this failure. The same applies when you open a camera and the 'auto connect' option is turned on. The error you posted above is coming from SharpCap first connecting to the mount and quizzing it on what functionality it has.Īlso, seeing an error when you try to tick the connected box and the mount isn't actually there is expected. An incomplete uninstallation of a program may cause problems, which is why thorough removal of programs is recommended.I suppose that it is possible that Stellarium is either not asking the same questions, or is ignoring any errors or possibly retrying on an error. There could be other causes why users may not be able to uninstall Stellarium. ![]()
0 Comments
Leave a Reply. |