Apology and Update on Version 2.4 Issues - Stable Version 2.3.3 Available: Page 2

Apology and Update on Version 2.4 Issues - Stable Version 2.3.3 Available

bobpowell@northstate

deans 100% agree! You could easily repackage 2.3.3 and call it 2.4.1 and maybe 2.4.0 would just go in the dustbin of history. This has been SO much trouble.

falconer

Corsair This worked perfectly. Thank you, sir.

PMTeam@ZWO

azskyguy Freezes during auto run where sequence just stops on 'loading'.

This may be because the state of this area is not clear when trying to expose it again. We will optimize it in the next iteration.

azskyguy Guiding exposure drops to zero and can't be changed back. Camera needs to be rebooted. This is on an 'air' camera.

Regarding this issue, can you resubmit a log after the problem occurred? We have not received other similar feedback and need to know what happened

azskyguy The new plate solve method designed for NB filters no longer works.

If you use a filter, it is recommended that you increase the exposure time

azskyguy WiFi continuously drops out with computer close to the telescope.

Are you using a PC? Please submit the log for analysis

azskyguy The directory of targets has been made too complex and requires more clicks than it used to need.

At present, this catalog is more professional. In the next iteration, we will consider supporting two modes. The current one is list mode, and a new celestial body thumbnail mode will be added, which will focus more on celestial body pictures.

azskyguy

PMTeam@ZWO
I'll try to respond to these.. thanks for following up.
Believe I sent logs on many of these issues.
As far as longer exposure for plate solves, they always worked in the past with the same filter and exposure. That's not the problem. Plate solves in general are a mess. Saw that again tonight. Manual plate solves work, but in acquiring a target they take so long (90 seconds or so) that I give up. With the same filters and previous versions of the software plate solves took about 4 seconds.
I use a Mac running ASIAIR. Used to work great. Each new version of the software it got worse.
It's not the size of the pictures, it's that there are more clicks to accomplish what took one click before. There's nothing professional about having to click more. It's simply bad GUI design.

Tonight I switched back to 2.33 and these problems went away. Plate solves were broken in 2.4.. many others have reported this.

R0k9pZfT

azskyguy I did some imaging tonight on 2.3.3 and plate solve was so snappy! I quit trying the new plate solve because it is usually slow or never returns before I abort it after waiting a good 30 seconds, even under dark skies.

PMTeam@ZWO

azskyguy As far as longer exposure for plate solves, they always worked in the past with the same filter and exposure. That's not the problem. Plate solves in general are a mess. Saw that again tonight. Manual plate solves work, but in acquiring a target they take so long (90 seconds or so) that I give up. With the same filters and previous versions of the software plate solves took about 4 seconds.

What function triggers the poor plate solve effect? PA?

R0k9pZfT

Again I say, I haven't seen a single positive comment about the new object list interface. It seems universally disliked. The old one looks more refined, is cleaner, easier to use, easier to understand. Seems like you're trying to fix something that was never broken. Again. The new interface looks dated and clunky.

Are you addressing the apparent stacking or histogram problem in live mode? Several of us have mentioned it and I don't recall that you have acknowledged it. Perhaps I missed it.

Also, I reiterate my observation of autofocus in live mode aborting the current image capture in progress and threw it away rather than waiting for it to finish. That seems like a waste of minutes of exposure just because of parameter hit suddenly. Let the current exposure complete!

Also a method to manually trigger autofocus in live mode would be nice so that we don't have to exit live mode. Why not let us pause, trigger an auto focus if we want to, and then resume?

It's exhausting repeating myself over and over only for it all to be ignored or at least not acknowledged. I think this is how we got into this situation in general.

PMTeam@ZWO

R0k9pZfT Also, I reiterate my observation of autofocus in live mode aborting the current image capture in progress and threw it away rather than waiting for it to finish. That seems like a waste of minutes of exposure just because of parameter hit suddenly. Let the current exposure complete!

Also a method to manually trigger autofocus in live mode would be nice so that we don't have to exit live mode. Why not let us pause, trigger an auto focus if we want to, and then resume?

Thank you very much for your suggestion, we will optimize this part later.

In addition, we have optimized the histogram in the repair version. If possible, would you like to use it to see if it solves your problem? Thank you

PMTeam@ZWO

6h3g399i Hello. You can refer to the following post.
https://www.facebook.com/groups/ASIAIR/posts/3300730050090195

PMTeam@ZWO

DJCummins99 We have fixed the MF anomaly issue, but unfortunately we don't have the actual conditions to test it right now. If you are willing, would you be willing to help test whether the fix solves your problem? Thank you

PMTeam@ZWO

Ceejay 2.4.9 is 2.3.3

PMTeam@ZWO

tyco Hello. Are you using iOS or Android? We have optimized the histogram in the repaired version and are currently testing it. Would you like to help see if the repaired version solves your problem? Thank you.

Pinguru

I have observed another bug with the 2.4 during polar alignment:
After the initial three pictures are taken, the calculated misalignment is plausible in the range of some arcminutes. When another picture is taken, the calculated misalignment jumps up to something like 1-2° and does not return back to plausible values unless I abort the process and start over again.
Then the first misalignment is plausible again...

I have spent half an hour to align my mount, still not convinced whether its correctly aligned or not.

PMTeam@ZWO

Pinguru Hello. Are you using the full sky polar align method?

PMTeam@ZWO

R0k9pZfT Thank you for reporting these bugs to us. We are actively fixing the bugs reported by everyone. Regarding the problem that you can't plate solve the images in the album, can you send us the original image for analysis? This way we can analyze and find the cause faster. Thank you

In addition, regarding the histogram problem, we have fixed and optimized it. The fixed version is currently being tested. Would you like to help test whether the fixed version can solve your problem? Thank you

PMTeam@ZWO

R0k9pZfT Will keep this link

PMTeam@ZWO

4H29wipq Hello. Does this happen after GoTo?

azskyguy

PMTeam@ZWO

Plate solves fail during polar alignment, and on a goto a target. They work if you are in preview and tap the solve button. In that mode plate solves are usually under 4 seconds. On the same field of stars if I try a polar alignment or move the scope very slightly and do a goto no plate solves work. Logs have been sent multiple times.

shamrock

PMTeam@ZWO

This problem has been reported several times over the past couple of years by Southern Hemisphere users.
The 'drift' occurs even if you don't adjust the mount RA/DEC – just keep hitting "Refresh" and the error increases.

But ZWO has not addressed the problem in all that time.

The only work around is to adjust the mount and then restart the alignment from scratch; and, of course, repeat that process until the target is reached.
Tedious, but you eventually get there!

sferlix

PMTeam@ZWO
Not sure it's a bug or not:

during PA, the sensor size and FOV size are reported as 0 x 0
filtering objects list on FOV returns zero objects.

bye

frank

PMTeam@ZWO

sferlix Hello. If possible, please take a screenshot of your celestial library filter conditions. It is not necessarily a bug, it may be that no celestial body meets these conditions.

In addition, the FOV size during PA is 0×0, which seems to be caused by parsing failure. What PA method do you use?

magore

Suggestion. For the object catalog. Have larger objects preview thumbnail taking 50% of the full page width. Next to it have equal size plot of the objects path in the sky vs time like this but with hour markers next to the dots
Alternatively have it display detail when clicked on.
This method of display lets an observer to easily plan around tress and obstructions
Stellarium Pro uses this when selecting "visualize objects path".
The advantage is you can just glance at the chart and instantly see everything as it takes less time to interpret then your recently updated graph.
You current updated graph has only arrows but the observer has to integrate the path in their mind. My suggestion shows the path as elevation vs azimuth vs time on a compass face.

Of course you might want to make swapping East on the right and West on the left as an option

PMTeam@ZWO

magore Thank you for your suggestion, we will consider the following version

« Previous Page Next Page »