I have updated the AutoIntegrate repository and there is a new V8 JavaScript engine version available.
The changes in the V8 version of AutoIntegrate script are huge, so I expect a few bugs there.
Jarmo
Hello Jarmo.
I’m running Pixinsight 1.9.4 build 1693 with Auto v1.86.3 on Windows 11 25H2
Quite a few times when it comes to the end of the integration process it just locks up and says not responding along with Pixinsight..It just goes white..
Once I have closed it and Pixinsight.. AutoIntegrate v1.86.3 isn’t showing in Script menu upon re loading Pixinsight.
I have removed AutoIntegrate PixInsight repository from registry. Closed down and reloaded. Put it back into the registry. Ran update. It is being updated and it isn’t in Scripts.. The only way to run it is to use Execute Script and go to parent directory.
I’ve tried everything I can think of except reinstall Pixinsight.
I am not sure if this is a AutoIntegrate problem or a Pixinsight problem with Java 8. I think its a Pixinsight problem.
I wanted to bring it to your attention.
All the best.
Peter
Hi Peter,
Sorry to hear for the problems.
For the disappearing script, I do not really any idea at the moment. There is a way to reset repository by Resources / Updates / Reset updates. But maybe you have tried that already. One thing to try, if you get the scripts correct, is to make sure you exit PixInsight cleanly after that. Then everything should be saved properly.
For the lock up, I have seen something similar. When I run my large test set, it may take a really long time before PixInsight responds again. I mean, it may take tens of minutes sometimes. I should report this to PixInsight, but reproducing it in my case is not trivial because of the amount of data needed.
Regards,
Jarmo
Good morning Jarmo.
My data sets are very large now the Scope is up and running again. I’m looking at 3.2Gb per master.
I have gone back to 1.9.3 build 1646 and AutoIntegrate v 1.85. I don’t have a problem with this build at all with these size masters.
So from my standpoint its definitely a Pixinsight Java 8 problem not yours.
The forum is a bit light on recognised faults and people are bringing up quite a few issues that are being classed as cannot reproduce or not a bug. Repository issues seem to be a hot topic at the moment.
Have a happy day.
Peter