I’m not certain. It depends on what version you were using prior, what version of ASCOM you are running and what drivers you have installed. It’s entirely possible that 1413 works better with different combinations of those things.
it seems so strange that after a couple of years it suddenly stopped working as before? Gut feel is a recent Windows update but would have thought others were seeing this effect?
Hoping older version is more stable - will report back
very interesting as that could be the link - there have been 2 more updates to Pegasus Unity 3 (bug fixes?) - and last night on the rig all was working fine? Fingers crossed it is a Unity issue not SGPro
That’s interesting. I don’t have any Pegasus gear handy, but I do wonder if maybe there is an issue with Unity 3 only when Unity 2 was first installed? Has anyone attempted to fully uninstall Unity 2 and then install Unity 3 after a Windows restart?
I too have been having issues which appear to be linked to Pegaus and unity.
I have been plagued by RPC not found errors, to the extent that the equipment profile manager ceased to function and sequences were not saving when manually saved. ( I have automatic saving turned off).
Reinstalling SGP made no difference. However, installing Unity 3 update moments ago did restore SGP to launch without RPC error codes.
I have fed this back to Pegasus support that there are multiple users impacted - I think there was a Unity 3 “patch” released recently - my rig with Unity 3seems to be running ok now
Interesting thing about Unity……If you update ASCOM at any point then you are supposed to fully uninstall Unity and reinstall it after the ASCOM update to ensure correct registration of unity products to the new version of ASCOM, even small incrimental updates.