Scott--thanks for testing the terrain feature. I guess, on the bright side, since you had an artificial horizon already there, it was easier to set your azimuth correction. I have set a keyboard shortcut to turning that artificial horizon on/off.

The terrain downsampling is mandatory if you're using a slower CPU, like an Raspberry Pi, which is why I defaulted it to 4, but I guess if you're using a fast MacBook, it could work with less. The real issue is that the KStars display code doesn't use the GPU. That apparently is a big project, and not something I'm familiar with.

I have also reworked the artificial horizon feature to get it ready for scheduler integration. The nice thing is now you can now edit your artificial horizon by clicking on the skymap while viewing your terrain image. E.g. see invent.kde.org/education/kstars/-/merge_requests/263   That work should also be in the release you're testing. I even have some artificial horizon / scheduler integration working in my private code. However, releasing the scheduler integration is on hold until the scheduler folks and I add more testing to the scheduler to make sure nothing breaks when new features are added. I'd like to add it in the next release, but want to make sure I work with them to make sure nothing regresses.

Hy

Read More...