The Seestar S50 has trouble tracking at high altitudes (> 80 degrees). The Telescopius target search algorithm has a filter for > altitudes for a specified time period, it would be great to also have a filter for < altitudes over the same specified time period (the net result being to exclude all objects which do not satisfy both criteria). This can be figured out from the charts of course, but an automated feature would sure help!
In any case, Telescopius is brilliant, thank you!
That’s a good use case for adding the max altitude filter. I’ve just added it to the backlog, hoping to do it soon. Thanks for your suggestion 
While you’re at the max altitude enhancement…
…I am sure I’m not alone in having a more restricted horizon view in certain quadrants. So how about also enabling min altitude to be specified per quadrant? e.g. in my case I would specify a target search with a min altitude of 25 degrees for SE and SW, but 50 degrees for NE and NW. Of course, I could exclude the NE and NW quadrants completely, or specify an altitude of 50 degrees and all quadrants, but then in both cases the results would exclude targets which are visible. Enabling min altitude per quadrant would resolve this issue.
Thanks for your attention, and again, it’s a great tool just as it is!
I’ve always had the idea of being able to search using the custom horizon, but so far it’s been very computationally expensive. I like this idea of minimum altitudes per quadrant, I’ve just added it to the roadmap. Thank you
The quadrants are excellent - perhaps 8 sections for even better tuning?
The best I could do so far is 4 quadrants due to performance reasons. To narrow down the list further by using 8 quadrants, not only would I need to compute the rise, transit and set times for all 75,000 objects in the database, but 4 new values (at which time objects cross the NE, SE, SW and NW points), and then filter by that. I love the idea but I’m not sure if this would perform well. I’ll do some tests, maybe it’s better to have the feature even if it’s slow, than not having it at all.
I would love in fact to use the custom horizon for narrowing the results down perfectly, but that’s even more difficult because that requires custom computations for each object.
Please implement the low-hanging fruit first 
Ah I see - I sort of imagined all the data would already be calculated and it would be just extra filters. The quadrants is already such a benefit. Thanks