Log in or register to post comments

Supported features/ 3D design guidelines

November 15, 2010 - 10:22am #3

Is there a master list of design criteria and limitations of the QCAR and Unity 3D combination?

Examples:

Texture image formats? Alpha channels supported?
Polygon/Triangle limitations?
Animation limitations? Position/ Scale/ Rotations supported?
Limit to number of objects?
Reflection mapping supported? (the Unity Asset store shows a reflective car)
Limitations on the number of reflection maps?

Would love to see some guidelines!

Cheers,
Eric

Re: Supported features/ 3D design guidelines

November 15, 2010 - 11:35am #2

This doesn't exist at this time. Currently we're still in the beta process with the Unity extension, and are focused on bringing its feature set to the level of the base QCAR SDK and making it more stable. For most of the metrics you mention, it's going to depend a lot on the particular device and its capabilities. It's probably going to take some trial and error on your part to see how far you can push things while maintaining a good framerate on all the devices you wish to support. I think that's an issue with Android development in general though, and isn't QCAR-specific.

In general, we would like any graphical feature that works with Unity Android to work with the AR extension, so let us know if something isn't behaving as expected!

- Kim

Re: Supported features/ 3D design guidelines

November 16, 2010 - 2:10pm #1

Great, so it's pretty much whatever Unity can handle.

Log in or register to post comments