|
I totally agree, however that isn't my point or situation!
1. I spend hundreds of dollars on multiple products from Software Bisque - but first I always confirm if certain functionality is provided both directly and under ASCOM
2. I find the functionality is not provided by the ASCOM path (or its severely restricted) - even though they've never mentioned that before purchase
3. I query this isn't working the way you told me it would - is it your side of the equation or ASCOM or both that is limiting things? (this they should definitely reveal up front)
4. Bisque (over and over and over) take days to answer (or don't) then obfuscate and eventually you find out they provide very limited support for open source development. They never come out and say this - ASCOM folk do. When confronted with this they finally fess up yep - that's the way it has to be. You then challenge them but I asked before I bought and you said - in writing XYZ, they then say - but we intrepreted you'd want to use predominantly our stack, lovely you say but I asked X and you said Y - no wiggle room there...
This has happened to me multiple times. They promise, you buy, you find its not what they said - though you specifically ask in advance, you call them on it, they ignore, other folk jump in, etc... generally ASCOM folk do something brilliant and you get what you want, then Bisque say we'd still suggest you do it our way.
Their software is great, but I don't know how to socialise it well with the rest of my software stack - PEMpro, CDC, Stellarium, MaximDL - all will share the telescopes resources under ASCOM brilliantly; Bisque doesn't play on a level field well.
|