Adding to what Charlie said, this bug was present before the change to 3000 regions. I’ve noticed this since at least 2016.
People don’t trouble to complain I guess, I do remember, that at least a year ago, this bug was mentioned on forums…
Anyways, experience from last night, me and two of my friends had experienced this again…ver. 3.0.1.0 and 2.9.3.
Before running he sequence, I check the plate solve setting and make sure it set to 200 regions. Then I send mount to random place in the sky and do Solve and Sync. After it was completed I go back to plate solve setting to double check and find that that it set back to Max Regions by it self… Put it back to 200 and then it stick’s for the rest of the night.
But, If i do not check it and set it back for 200 and run sequence, it will be set at Max Regions on it’s own.
Jared:
Thanks for your concern, Yes, it is a problem, as you can see from the responses. Not fatal, just irritating. I have not yet upgraded to V3, perhaps its fixed in that version, to be purchased soon.
Ed
Hi, I am planning to get a NUC to be used next to my scope for SGP, PHD2, QSI660 and Mach1 mount and trying to figure out if an I5 based NUC will show any difference with an I3 NUC considering that nothing else will be running.
I am mostly interested in image download time so I will use an SSD disk.
I’ll appreciate any experience that can be shared.
Thanks,
Renan
Given our purposes, I doubt you’ll see any difference between an i3 and i5
processor. Certainly the processor doesn’t have much to do with
downloading an image. I’d go for the i3, SSD, and as much RAM as the NUC
will accept (or you can afford).
Thank you Joel,
I was planning to have 8 Gb RAM but may be I should consider 16Gb, and an I3 NUC.
Renan
8GB would be more than sufficient. Actually, I didn’t know that NUC’s
could have more than 8GB.
The just now available quad core, Pentium based NUC is more performance than you need to effectively run SGP and all its supporting software:
Put in two, 4 gig memory modules and a 2.5" SSD drive (Samsung 860 EVO).
I have the prior version with a quad core Celeron and it performs great – the Pentium version is about 40% faster.
Charlie
Good!, I will check this NUC
Thanks
Renan
I guess the good news for me is my plate solving problem after meridian flips is not all me. I’ve only flipped 3 times and was thrilled each time till the plate solve 2 attempted. Would someone share a screen shot of how they solved this. I created an equipment profile and never changed it. The last time I took a test frame/focus shot and saw my galaxy was still in the shot, just on the corner not the center. I was surprised it would not solve considering I was so close.
I’m using ver 3.0. Current settings I have are Search Max Regions, Binning 2x2, attempt to center 20 times, until error less than 50 pixel, use blind solve fallover is checked. Please tell me if I should change any of this.
Thank you, Amy
Has this been fixed yet? Same problem observed here. In my experience if PlateSolve 2 doesn’t finish after 200 regions, it rarely ever solves, so I waste a ton of time - would be better to just fail over to astrometry.net after 200.
But max regions in Plate Solve 2 seems to always revert to 3000, no matter what I try.
Rowland
Unfortunately no, it has not been fixed. It’s entirely random for me. Sometimes it will revert back to 3000, other times when I start SGP it will stick with my default of 100. No idea why this happens.
I have found that when I do my first solve and sync, it runs as supposed with 200 regions.
After it finishes I go back to settings and see that it has set back to 3000. I set it to 200 again and then run sequence and it sticks for the rest of the night.
But yes, I have to remember to do that each night.
It happened to me numerous times last night 
For the past year or more I have set Platesolve 2 max to 100 with fail over to astrometry.net. I have never ever seen this behavior. It always stays at 100. So clearly something random is going on here. I am running on an i7-3770 CPU @ 3.4ghz, with 8GB ram, 64 bit Windows 10 Pro, with an SSD for drive C. Have no idea if any of that matters.
I would suggest for those where this continues to happen regularly, just shift to astrometry.net as the only solver. For me it solves almost every target in less than 10 seconds, often around 6. Slightly slower than Platesolve 2 if it is able to solve. When it can’t, it takes FOREVER to get to 3000, and then you solve with astrometry.net anyway.
This is not random, it is repeatable. It happens when I do a manual solve and sync at the beginning of every session. I just go to the control panel plate solve tab and reset it to 100. After that it stays at 100. It’s only when dual a manual solve and sync that this occurs.
The same thing happens to me. Like Joel, I make sure to set the max to 100 each session. Otherwise it defaults to Max 3000. I have just made the decision to live with the glitch.
Thanks for the reproduction steps @joelshort. I’ll see if we can address this now that we have a manner to replicate it.
Jared
Resolved in version 3.1 (not in beta)