HELP! I Broke It
 
Share:
Notifications
Clear all

Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.

It did take a long time to have the work finished on this and it  will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...

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.

 

HELP! I Broke It

5 Posts
2 Users
2 Reactions
2,713 Views
(@simon_rl)
White Dwarf
Joined: 9 years ago
Posts: 8
Topic starter  
Posted by: Simon

Hi All,

Could i please get some help with the attached file. It is a stack of M42 luminance data. Once the stack had finished I got a very weird pattern in the background. I realised I had too many luminance frames so I cut it back to 40frames from 125 to see if this would help with the background pattern. I tweaked some of the setting and went through the whole process again from star analyse to integration. The attached image is the result. Has anyone see this before and have any suggestions on what I could have done wrong.

St avg 810.0s SC 1 3.0 x 1.0 LZ3 NS full eq add sc BWMV nor AA RL MBB5 St

Thanks,

Simon.

Hi Simon,

Welcome to the forum 😉 !

Luckily, you didn't broke it I think. But it is a bug that I need to solve.

This will happen if you enable optical distortion correction in 4) register in a case were you most likely don't need it.

So my advice for now, is to register your images with dynamic distortion correction disabled.

I would assume that you didn't dither between your exposures or only very minor dithering and that all of your frames have nearly identical field of views?

Let me know if things work out fine without dynamical distortion correction 😉

Kind regards,

Mabula

 



   
ReplyQuote
(@simon_rl)
White Dwarf
Joined: 9 years ago
Posts: 8
Topic starter  

Hi Mabula,

 

That is so funny, I have been tearing my hair out trying to fix this problem and all it was, was one little check box 😀 .

 

Thanks heaps mate all working fine now. Hopefully I will be able to post my first LRGB image soon.

Cheers,

Simon.



   
Mabula-Admin reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Excellent Simon 😉

I'll work on removing this bug though !

Mabula



   
ReplyQuote
(@simon_rl)
White Dwarf
Joined: 9 years ago
Posts: 8
Topic starter  
Posted by: Mabula Haverkamp - Admin

Excellent Simon 😉

I'll work on removing this bug though !

Mabula

Hey Mabula, hope you had a great Xmas. Thanks heaps for the ongoing support of this fantastic product.

All the best for the new year.

Cheers,

Simon.



   
Mabula-Admin reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Thank Simon,

Best wishes for 2018 !

Cheers,

Mabula



   
ReplyQuote
Share: