Share:
Notifications
Clear all

June 24 2026 APP 2.0.0-beta46 has been released !

Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.

May 27 2026 APP 2.0.0-beta45 has been released !

Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

[Solved] A very weird repeatable result

6 Posts
3 Users
1 Reactions
953 Views
(@favalessa)
White Dwarf
Joined: 6 years ago
Posts: 21
Topic starter  

I imaged two galaxy targets 3 nights ago; same optics, filter, etc.  One integrates beautifully; the other gives me a circular image.  I've Blinked the subs in Pix and don't see any abnormalities.   I've reset all the parameters from 0 to 6...same weird result. 

I was able to image same again 2 nights ago.  It integrated perfectly.  Then I combined the data from the night before and got a circular image again.  I then started integrating 2 subs at a time from the weird dataset and got the circular image no matter what I integrated...guess I'll just throw out the set. 🤪 -john

10407 M63 QUAD 1

 



   
ReplyQuote
(@michel82)
Neutron Star
Joined: 9 years ago
Posts: 90
 

oh boy, did you use a round telescope instead of a square one? 😂

No kidding: I have had the same in 1 occasion. It was solved by either switching off dynamic distortion correction or same camera and optics. Don’t know why, but it worked….



   
ReplyQuote
(@favalessa)
White Dwarf
Joined: 6 years ago
Posts: 21
Topic starter  

@michel82

switching off dynamic distortion correction worked!!!  thanks you so much Michel!  this was driving me nuts 🤪  -john



   
Michel Sw reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5363
 

Hi John @favalessa,

Ah I already answered in the duplicate topic, I will delete the other one. Indeed, dynamic distortion correction needs to be disabled here. Thanks @michel82 for helping out here.

"This problem can occur if you enable dynamic distortion correction in 4) Register, if your data really does not need it. So please disable it in 4) Register and try again and let me know if all is okay now 😉

On our issue list, this issue is noted to be fixed as well."

Mabula



   
ReplyQuote
(@favalessa)
White Dwarf
Joined: 6 years ago
Posts: 21
Topic starter  

@mabula-admin Yes all is well when I disabled dynamic distortion correction.  I did reset all 1 to 6 to defaults in my testing, but that must have not been disabled.  I just checked and it does get disabled when I reset 1 to 6.  not sure why it didn't before...I don't remember ever enabling it.  I so appreciate your efforts and that I took your time with this.  I did create a duplicate of my post as it wasn't showing up after a day...I think I didn't "confirm" soon enough via the confirmation email.  -john



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5363
 

Hi John @favalessa,

No problem, I am glad all is okay now 😉 we will fix the issue going forward with dynamic distortion correction.

Mabula



   
ReplyQuote
Share: