2024-02-18, 05:17 PM
(This post was last modified: 2024-02-18, 05:20 PM by theskyhound.)
Dude. Think about it. Why am I doing an EAA version? I don't think you really understand.
You are currently using the Visual version and it makes calculations for your eyepiece instead of your camera. We have talked at length about how this will not always give appropriate results. It can be useful in many circumstances if kludged properly, but not all. When the moon is up, bright, and/or nearby to your object, you literally can't see many objects visually. Its like being in the center of New York City doing visual astronomy. That's not some generic, the moon is up so Greg will penalize people for the moon being up thing, its an accurate simulation. The actual impact of the moon is calculated for each object.
So why an EAA version? Its not just about putting an FOV rectangle on a chart. The reason for an EAA version is to make the computations for your camera, to calculate the signal on your detector of both the object and the sky, under varying conditions such as moonlight. I am very good at that. There is a whole imaging version of the software. The moon impacts your camera differently. Sometimes that will mean you can't get a decent image of something with the moon up, and other times it means you can. The idea is to be able to know the difference and plan accordingly. That is not a limitation that you will need to work around.
The is the second time you have asked me to make changes to SkyTools in the EAA version. But you only need them to get around the fact that you are currently using the version for visual observing. This is obvious to me. How can I help you understand that your complaints will not apply to the EAA version? All you will need is the EAA version to be happy. You will not have these issues once you have that. I don't know how to explain this more clearly. What you see as limitations of the software are limitations entirely due to the mismatch of your camera to an eyepiece.
In the meantime, please stop accusing SkyTools of being limiting. It is not. Your issue is with using the visual version. Your frustrations come about from using the visual version. Please, for goodness sake do not be telling people that SkyTools is limiting! That would be super unfair of you! You were informed going in that you need the EAA features for it to work properly. To hold that against me and my product is wrong.
Goldilocks walks into the SkyTools store with a camera on her telescope and a desire to do EAA. She tries SkyTools Imaging. But its designed to support long exposure photography and does not work for her. "Why do I have to create an Imaging Project for everything," she cries in annoyance. She tries SkyTools Visual, but that has problems too. "Why is it telling me I can't take images of a galaxy in broad moonlight?" SkyTools is broken! SkyTools is limiting! Then Greg rolls out the shiny new SkyTools Visual with EAA support, and she tries that. "It accurately tells me which objects I can see on the screen and how long I'll need to stack to make them visible or look good", she says. "It tells me if the moon is too bright to detect that faint galaxy. I use it to be sure that I help people on my youtube channel understand that EAA is still astronomy, still bound by issues like atmospheric extinction and moonlight, only differently", she says. SkyTools Visual with EAA is just right.
Dude. Trust me.
You are currently using the Visual version and it makes calculations for your eyepiece instead of your camera. We have talked at length about how this will not always give appropriate results. It can be useful in many circumstances if kludged properly, but not all. When the moon is up, bright, and/or nearby to your object, you literally can't see many objects visually. Its like being in the center of New York City doing visual astronomy. That's not some generic, the moon is up so Greg will penalize people for the moon being up thing, its an accurate simulation. The actual impact of the moon is calculated for each object.
So why an EAA version? Its not just about putting an FOV rectangle on a chart. The reason for an EAA version is to make the computations for your camera, to calculate the signal on your detector of both the object and the sky, under varying conditions such as moonlight. I am very good at that. There is a whole imaging version of the software. The moon impacts your camera differently. Sometimes that will mean you can't get a decent image of something with the moon up, and other times it means you can. The idea is to be able to know the difference and plan accordingly. That is not a limitation that you will need to work around.
The is the second time you have asked me to make changes to SkyTools in the EAA version. But you only need them to get around the fact that you are currently using the version for visual observing. This is obvious to me. How can I help you understand that your complaints will not apply to the EAA version? All you will need is the EAA version to be happy. You will not have these issues once you have that. I don't know how to explain this more clearly. What you see as limitations of the software are limitations entirely due to the mismatch of your camera to an eyepiece.
In the meantime, please stop accusing SkyTools of being limiting. It is not. Your issue is with using the visual version. Your frustrations come about from using the visual version. Please, for goodness sake do not be telling people that SkyTools is limiting! That would be super unfair of you! You were informed going in that you need the EAA features for it to work properly. To hold that against me and my product is wrong.
Goldilocks walks into the SkyTools store with a camera on her telescope and a desire to do EAA. She tries SkyTools Imaging. But its designed to support long exposure photography and does not work for her. "Why do I have to create an Imaging Project for everything," she cries in annoyance. She tries SkyTools Visual, but that has problems too. "Why is it telling me I can't take images of a galaxy in broad moonlight?" SkyTools is broken! SkyTools is limiting! Then Greg rolls out the shiny new SkyTools Visual with EAA support, and she tries that. "It accurately tells me which objects I can see on the screen and how long I'll need to stack to make them visible or look good", she says. "It tells me if the moon is too bright to detect that faint galaxy. I use it to be sure that I help people on my youtube channel understand that EAA is still astronomy, still bound by issues like atmospheric extinction and moonlight, only differently", she says. SkyTools Visual with EAA is just right.
Dude. Trust me.
Clear skies,
Greg
Head Dude at Skyhound
Greg
Head Dude at Skyhound