…. is that on adding new events to the sequence, the “Event Order” keeps dropping back to ‘Rotate through Events’ instead of ‘Finish Entire Events First’, which I find really annoying, if I don’t spot it, as it takes ages to finish events…
I’ve also just noticed\query is the event exposure time, is now assumed to be in seconds ??
I am not seeing this. Look at “Tools->Options->Sequence Options” tab and make sure “Rotate through events” is not checked.
Peter
I am also not able to reproduce this behavior.
Nothing has changed here… it is the way it has always been. You may enter time in most formats… e.g. 5 or 5s for 5 seconds, 5m or 300 for 5 min. That said, SGPro only stores exposure times in seconds… This means that if you set exposure time as 10m, the next time you open the sequence, it will read 600.
I checked Options before posting (should have said) and ‘Finish entire events first’ is checked…
As an addendum, the initial target, on a new sequence, is created with Finish Entire, but any subsequent targets are created with Rotate…
Thx for the report, I misunderstood what you were getting at. This has been resolved… new beta out soon.
Thanks you Ken…
Hi,
I have installed this version on my post processing computer (Win7)) for testing purposes. It starts loading then gives an error. Then I installed it on another computer which runs W10 and it runs without any problems ? Is it correct to assume this has to do with Win 7 operating system ?
Below are the error message and the details (my apologies, it’s partly in Turkish but I guess you can figure out what it says
The details given are as follows:
Sorun imzası:
Sorunlu Olay Adı: CLR20r3
Sorun İmzası 01: Sequence Generator.exe
Sorun İmzası 02: 3.1.0.245
Sorun İmzası 03: 5d82b63f
Sorun İmzası 04: Sequence Generator
Sorun İmzası 05: 3.1.0.245
Sorun İmzası 06: 5d82b63f
Sorun İmzası 07: 3aa6
Sorun İmzası 08: 2a
Sorun İmzası 09: System.NullReferenceException
OS Sürümü: 6.1.7601.2.1.0.256.48
Yerel Kimlik: 1055
Ek Bilgiler 1: 0a9e
Ek Bilgiler 2: 0a9e372d3b4ad19135b953a78882e789
Ek Bilgiler 3: 0a9e
Ek Bilgiler 4: 0a9e372d3b4ad19135b953a78882e789
Log file is also in the attachment
Thanks
Sedat
sg_logfile_20190920214644.txt (942 Bytes)
Just noticed that beta 247 was out. Downloaded it and tried again but nothing has changed.
What version of SGPro were you using prior to 245? This seems like it might be an error migrating your settings to the new format… and then some regional issue blew SGPro up.
Ken, it was 169. Just reinstalled 169 and it works without a glitch.
This is a dummy installation where I check the betas prior to installing them to my observatory computer remotely. Once in a while, I work with MFW and that’s it…
I tested 245 and 247 once again after I have a successful session with 169 but still got the same error.
Cheers
Please attempt to install 3.1.0.249, it will not fix this issue but should provide more information on what’s happening.
Please find the files attached
sg_logfile_20190920231825.txt (25.6 KB)
sg_logfile_20190921071744.txt (2.8 KB)
Making progress… Could you please install this build? It will not function properly and, if it open, SGPro will look very odd… BUT I just want to see if it does open. Thx!
will do right now
Ok… sorry this is annoying. I just can’t recreate what you are seeing. Here is another build (252) that has as much debug information as I can jam into the general area that is crashing.
@bilgebay I have sent you a direct message in this forum in hopes you can check something out related to this issue. Thx!
I replied your DM.
Best
