When starting SharpCap

[sonata31]

Hello
Often when starting SharpCap I get this error

SharpCap_err1.png (325.9 KiB) Viewed 489 times

"A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. (No such host is known. (msdl.microsoft.com:443))"

SharpCap_err2.png (280.85 KiB) Viewed 489 times

Louis

[admin]

Hi Louis,

I think that this is related to the auto-update check not working in a way I hadn't anticipated. I have actually put a fix in for similar issues fairly recently (last couple of weeks), that I think will cure this problem too. However, there is currently an issue with focuser movement buttons becoming disabled in the latest update, so I won't recommend updatign to 4.1.11939 just yet (unless you do not use a motor focuser - then you are probably OK).

cheers,

Robin

[sonata31]

Hello
For the moment I am with version 4.1.11799
I use a focuser powered by Pegasus Astro FocusCube 2
Louis

[admin]

Hi,

you should now be OK to update to 4.1.11947, which fixes (hopefully) both the startup crash and the issue with the focuser buttons.

cheers,

Robin

[sonata31]

Hello
I will test when the battery is recharged
Louis

[sonata31]

Hello
At first glance this seems to be ok
Louis

[sonata31]

Hello
Finally there is always the problem
In <Scope Controls> I then have to connect the focuser manually, it works without problem
Louis

SharpCap-error4.png (277.08 KiB) Viewed 314 times

Louis

[admin]

Hi Louis,

what version of the Pegasus software are you using? Is it the 'Unity' combined software or the older separate ASCOM drivers? I have a couple of Pegasus focusers here that don't show the problem using the Unity software, so it may be worth updating to the latest version of that.

cheers,

Robin

[sonata31]

I use Unity v 1.15.2243.140

[admin]

Hi,

I have just checked and I can't make anything like that error happen here - please can you post the SharpCap log captured after the error has happened so that I can see if there is any more useful info in the log that might explain what is going on.

thanks,

Robin