I started using ASTAP recently - which is an AWESOME piece of software.
To begin with I had the platesolving working smoothly.
However, now I get an "Access Violation" when trying to Solve.
I have removed the software, database files and all configurations that I could find on my laptop and reinstalled again incl. the D50 star database.
Tried running the software as Admin makes no difference either.
I am running the latest version for M1 Mac.
Any input on what might be at play?
Or any information that I can provide to help debug this?
I am having the same problem. Just updated to the latest ASTAP executable and I installed the V50 database (since I'm doing photometry). I deleted the old V17 before installing V50.
Whenever I try to solve an image I get an "Access Violation" alert.
I'm on a non-M1 iMac.
It has been 10 days since Christian's original post and Han hasn't responded. I realize this is a labor of love (thanks), but it would be nice to get this fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey
I started using ASTAP recently - which is an AWESOME piece of software.
To begin with I had the platesolving working smoothly.
However, now I get an "Access Violation" when trying to Solve.
I have removed the software, database files and all configurations that I could find on my laptop and reinstalled again incl. the D50 star database.
Tried running the software as Admin makes no difference either.
I am running the latest version for M1 Mac.
Any input on what might be at play?
Or any information that I can provide to help debug this?
I am having the same problem. Just updated to the latest ASTAP executable and I installed the V50 database (since I'm doing photometry). I deleted the old V17 before installing V50.
Whenever I try to solve an image I get an "Access Violation" alert.
I'm on a non-M1 iMac.
It has been 10 days since Christian's original post and Han hasn't responded. I realize this is a labor of love (thanks), but it would be nice to get this fixed.
Hi Christian & Bill,
I missed the first post of Christian. I will check the Mac version and upload a fresh copy.
Han
Found the problem. Fixed in the new version 2023-.03.30.
Thanks Han. The new version works fine. Thanks for the quick support.