No, you are right, I expect the software to work OK, specially when using basic built-in functions. It is not like I was pushing it to extremes or using it in a way it was not designed to, cases in where a bug is much more acceptable. This kind of bug is no different as to having the circle tool fail.
On the other hand I never expected someone to be available 24/7, you can see this thread was already a day old before Pascal replied to it.
He did not, at all. If he had done that, I would not have had the need to ask for clarification multiple times. You can see just below his first reply I did that, and then I had to do that again at the end.
Seriously? This is poor support at it’s best. The easiest thing to say is “there is no solution”. Miraculously, against all odds, there was a course of action. Actually two at least: A custom script, a GH definition.
What is worst, both solutions did not come from McNeel. One from me, one from you. That is a disgrace.
Granted, the information about target distance that Pascal provided was useful. But because of you and me! Another user would have achieved nothing with said information. That information is only useful for the developers to fix the problem.
And this act of providing of information does not rule out the waste of time, at all. I don’t know how you arrive to that conclusion or how that logic of yours works, but that is simply not the case.
Seven comments were exchanged before arriving to that piece of information. Seven!
And then two additional ones where I asked for a possible workaround and was simply replied there was no workaround other than contacting the developers.
This is wrong on so many levels:
First, it should not be me the one asking for a workaround, that should be a given. The standard reply should be directed in solving my problem by providing workarounds in the form of. “You can try this, or that, rather than that you can also try creating a custom script if you know how to code, or try a GH script, there is a plug it that lets you control the camera”.
If I am not wrong @pascal knows how to code. If he does not have the time, I am sure another McNeel user could have done it, it would have been great if Pascal would have said hey @X can you hop in and try a custom scrip? But honestly, how long did it take you to write that code? 20 minutes?
Second it should not be me the one looking for workarounds. You see, not only did I have to “ask” for possible workarounds, I also had to “look” for them, google them, download a plug-in, create a GH definition, try stuff.
I made a bigger effort in solving McNeel’s flaw than McNeel itself.