@unknownuser said:
I agree 100% with kwistenbiebel's calls for a 3d engine that works much better with a massive polygon count. Any BIM type development is definitely going to need it!
It's always been my understanding is that SU was developed to be a simple, intuitive and quick application to create 3D models with a somewhat limited poly count. Why create a subdivided cube when a plain 6 sided cube will suffice? Quick is predicated on models that don't have a massive polygon count. So far, SU has been just that ... Take away the simple, intuitive and quick aspects and we might as well use 3DMax, Zbrush or Blender to name a few ...
So, if I were Trimble and I wanted to integrate the SU engine into "field applications" I sure wouldn't morph it into something that would handle high poly counts or an "advanced" 3D engine. There's no need. Consider this: a guy in the field is doing some geo work and needs a model of a particular building for site he's at. He's on 3G/4G for connectivity. Someone at Trimble, for instance, has already whipped up a SU low poly model of the building and made it accessible for downloading to the field. The SU object doesn't need massive polys, or UV mapping or even texture mapping. It needs to occupy a physical space on a plot in a field device. I would expect downloading a SU file under 1meg for instance, would be preferable to something larger.
Another aspect, if the SU engine is integrated into field equipment, we're possibly talking about mobile devices like glorified smartphones with limited processor or memory capacity. So again, handling a high poly count is not useful.
Speculation is so much fun. Just my spin on it ... cheers.