European AstroFest 2023 - 3 & 4 February 2023 - Kensington Conference and Events Centre, London.
Please come all to AstroFest in London to ask us (Mabula & Vincent) questions and to see live demos of APP!
Please note our new Downloads page here
2023-01-19: APP 2.0.0-beta13 has been released !
!!! Big performance increase due to optimizations in integration !!!
and upgraded development platform to GraalVM 22.3 based on openJDK19
We are very close now to releasing APP 2.0.0 stable with a complete printable manual...
Astro Pixel Processor Windows 64-bit
Astro Pixel Processor macOS Intel 64-bit
Astro Pixel Processor macOS Apple M Silicon 64-bit
Astro Pixel Processor Linux DEB 64-bit
Astro Pixel Processor Linux RPM 64-bit
Mabula -congratulations on the new release. I have noted only one issue regarding the image viewer on Windows 11. If I have OpenGL4 (It shows Green in APP), the maximum size that can be displayed in the image viewer appears to be 1/4 of the image viewer screen - displayed on the lower left. (image attached) If I try to expand beyond this size, sliders are enabled on the right and bottom to move through the imaged like it was filling the entire image viewer area. I noticed that if I turn off OpenGL4 the image will correctly fill the entire image screen. Please note that I did not have this issue with using OpenGL4 on any previse version of APP.
Again, my thanks for an excellent software product. And my hope is that a correction can be found to continue to use OpenGL4.
Paul
@wvreeven Thanks for the quick response and I will be watching for the next release
@wvreeven Thanks for the quick response and I will be watching for the next release
@assafh That's not possible as those are not movable. We are of course taking suggestions with a beta, the moving of those parts of the window is a bit more complicated though with the current UI system.
Interesting! What location did you install APP? Maybe it needs admin rights there?
@vincent-mod Hi Vincent - it installed in what I think is the default path:
C:\Users\cswin\AppData\Local\AstroPixelProcessor
I have other installs in a separate folder in same location ie AstroPixelProcessor2 - no issues with those.
Have checked the Security settings and they all look the same. I'll uninstall and reinstall and see if that fixes the problem. Aside from this am enjoying the new version! Thanks for all the hard work.
Very odd then, yes if you can completely uninstall it and try again, that would be helpful. Any virus scanners you're running that may cause issues?
@vincent-mod hi - sadly performing an uninstall and reinstall has broken it. I can't get it to stably open the file dialogue, even as administrator anymore.
That is very strange, never heard that before. Is there any chance there is something going on with your system, disk wise perhaps?
@vincent-mod nope - I ran a full scan this morning to be sure there was nothing wrong with the machine (its only 15 months old but things can go wrong I know). I see no strange behaviour with any other apps. I'll keep digging but right now I only have a data point of one which is the behaviour of the beta. Are there any logs it generates that might point to clues?
You can try to start APP via a terminal, but I don't think that will reveal much more. It starts to sound like a system issue to be honest, something with the rights are getting mixed up or something. Did you upgrade from 10 to 11 and I guess you're starting app as user cswin?
I upgraded from Win10 to Win11 around 6-7 months ago. I'm starting it as user cswin. The strange thing is sometimes if you leave it for 10 mins the Open file dialogue can open and it may allow browsing to a location and loading files or it may not. I suppose if it was a permission issue it would be binary. Either way its the only programme showing this behaviour. I did notice on the original install it installed over an existing APP installation leaving a hybrid folder. So maybe that messed things up. However I removed all my installs of APP - manually running the uninstall routine from the respective folders as only one instance of APP showed up in the Programs list depending on which had been installed last - and then reinstalled. I did find that the uninstall didn't remove registry settings. Not sure what else it may have left behind that may be confusing things. The current production version of APP is working fine though.
Thanks for the further report. I'll share this with Mabula and we may have to investigate further.
@vincent-mod I checked the Windows Error Reports and there are a series of Critical reports that state the javaw.exe program hung - not sure if it helps:
The program javaw.exe version 17.0.1.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1a9c
Start Time: 01d86908247ba55e
Termination Time: 4294967295
Application Path: C:\Users\cswin\AppData\Local\AstroPixelProcessor2\jre\bin\javaw.exe
Report Id: 72f2886c-80a2-43ce-bc5e-4509b993ed48
Faulting package full name:
Faulting package-relative application ID:
Hang type: Top level window is idle
One other thing, Mabula noticed you installed in a folder called AstroPixelProcessor2, is the older version installed in AstroPixelProcessor? Could that, by whatever reason, be the problem?
@vincent-mod hi Vincent - no I've tried completely removing the older version and only installing the beta so there was only one astropixelprocessor directory. No luck. I've also updated my nvidia graphics drivers as I read that could cause issues with javaw.exe. Since I did the latter I have managed to add a dataset and process it using my account rather than as admin. However clicking on buttons that open file dialogue boxes ranged from instantaneous to 10 mins to respond. So it is working but for some reason it is incredibly slow. This only pertains to anything to do with adding lights, flats etc or setting the working directory. Once data is loaded everything works fine. Its just the hour it took me waiting for the app to respond that was the problem while loading data.
So strange. It seems like it's a very local issue, let me send you a pm for an idea.
Seems solved because of a network related issue.