Also… I’m being annoying now, but I have a working theory about what is causing this issue. If you have a moment, can you install 272 and open that same sequence. After you open it, in the lower left corner of SGPro you will see a status about background loading the sequence. Don’t touch SGPro at all until that thing reads that the sequence is done. I’m curious to know if the issue is still there or if everything seems to behave normally at this point. Either way, it’s an important data point.
@Ken I already have 272 installed, I hit the same issue with 272 hence my 2nd screenshot, it was the “Launch SGPro Now” that loaded up my sequence by default as this was the last sequence that was loaded, and it erased most of the information from it
Im not 100% following that. Do you mean that the very first target in the list had been reset? The screenshot above shows that the third target in the list had been clicked and loaded. What Im asking for is two things:
- Was the first target in the list (Crescent Nebula) ok or was that one reset also?
- Before you clicked on Dark Shark Nebula, was the sequence 100% done background loading?
@Ken I am seeing what you are referring to now, the “Loading Target” in the lower left, wow this takes much longer to load than it did previously. It was Dark Shark Nebula-1 onwards that had been reset (I have corrected some of them in the file uploaded).
Might be worthwhile preventing anything being done until the sequence has been loaded.
Why does it take so long to load in comparison to the current GA release?
Well, no… the whole point is that the sequence loads in the background. Once SGPro becomes visible you can use it as normal. I am not implying that you should wait, I was asking if you could just one time so you could answer a question.
So the question still remains… Can you, just one time, load that sequence and wait for the background load to complete. Then click on dark shark and see what happens?
Let me do a test
I will fully populate the sequence details, make a backup of the file first 
- Load it and wait for the sequence to fully load, check to see if all info is there
- Load it and start to modify sequence, and see if it changes
Thanks! This is very helpful. It is frustrating when I am not able to recreate a big issue like this.
Always a good idea in the beta.
The test should be like this:
- Load the sequence and wait maybe up to 5 minutes for it to load… the background load is slow (purposely). Don’t touch SGPro during this time.
- When loading is complete, click on “Dark Shark Nebula” and others further down in the list. Do those events display with the proper values? Or are they still reset?
Either way, this will narrow the number of possible places the issue could be.
OK I can trigger it at will
Load up the sequence, make a change (I just unticked a target), save the sequence before it has fully loaded, everything that it has not yet loaded will be Reduced, filter information removed, exposure time removed as it continues to load
Oh… I see. This is making more sense now. I never have auto save on and I bet you do. Dark Shark and below, at the 30 second mark, had not been loaded and your sequence saved. This is probably why I could not reproduce… Awesome. Thx so much!
@Ken No Problem, glad to be of help
SGPro 3.1.0.275 addresses this issue.
1 Like
Thank you @Ken
I released the wrong version… it will be 3.1.0.276
1 Like
Verified two ways
-
Re-enabled Auto-Save, loaded SGPro, during the sequence load process, I enabled two targets, this would have triggered an auto save…All targets retained their information…success
-
Loaded SGPro, during the load cycle, I enabled two targets and saved the sequence manually before sequence was fully loaded…success.
So we no longer have the race condition, thanks for getting that fixed so quickly
Noticed that the loading process is quicker also
Thx for checking. There is still an issue… not harmful, just annoying where trying to toggle the active state of a target before it has fully loaded takes FOREVER. This has also been fixed, but not released.
Oh I noticed that too, only the first time though, I thought I was just being impatient! 