People often email me to ask what type of feedback are we looking for with our technology previews. As these previews are early in their life cycles, we are interested in knowing if the concept itself is a good idea, did it work correctly for you, and how was the performance. We like hearing the good, the bad, and the ugly. Here are some examples of the types of feedback we receive.
"I loaded an STL Model made in Rhino [into Project Falcon] and set the resolution at 200% which wound up being 3,300,000 voxels. It took a few tries and a little time, but I did run a 3d model and got a cd of .37. Since the model had no wheels or cutouts I was hoping for a cd under .3. For comparison, I made a quick model of an Airstream. There has been a lot of research on that type of body, and the results were probably a little lower than it should be .41. I expanded the virtual wind tunnel and tried another model (a teardrop h*2.5=L then sliced in half) that I knew would be under .2 but returned a cd of .51. None of the models had wheels or cutouts, just the shell. I must be doing something wrong?"
"Instead of playing the Project Chronicle video in our full web page or in an embedded web page, I want video playback to be in a small footprint window so that users can see both (app and video) at the same time and switch back and forth easily."
"Regarding the [DesignScript] 'create a collection via a collection of indices,' I really got stuck trying to find the correct Graph Node in the Libraries. So I had to resort to a code block. Also the section on generating a collection of numbers was extremely labored in trying to get a simple result with the nodes that I selected, maybe there is a better more efficient way with Graph nodes while still avoiding a code block script. Any ideas?"
"The [Design Checker for Inventor] is a great tool, I'm finding it very useful. However, the hole accessibility check for holes doesn't work properly."
I would like a workflow that starts with a Faro scanner and ReCap Pro, progresses to Project Memento and ends in Revit.
Please keep the email messages, discussion forum posts, Facebook comments, tweets, blog comments, and video comments coming in.
Feedback is alive in the lab.