Thanks for the info.
I'll contact you if I need any help. :)

Sorry, the networking logic is outside of my domain. Perhaps other users here can help, or you might try the Android developer forums. I do suggest doing this part in Java using the Android APIs.

Once you work out the networking part, you'll want to integrate it with our sample code. For images (textures), you'll need to update our Texture.java class to load the texture from a different input stream (whatever you receive from the network). For models, you need float/short/byte arrays that you can send to native (via the JNI) and feed to OpenGL. I can help you with this part if you get stuck.

Another option is to send your models in a popular 3D format (e.g. obj) and integrate a parser on the mobile end to extract OpenGL-ready data.

- Kim

Thanks...

Can you provide me some sample code or guidance (if you can)?

Thanks a lot. :)

Sure, but this isn't a QCAR-specific problem. If you can write an Android application that can download a model file from a server and render it using OpenGL ES, then you can integrate this with QCAR. Our samples provide one possible pathway for loading 3D models and textures, but will work with any OpenGL ES solution.

- Kim

Thanks for the quick reply.

What about the 3D model (or image) to be rendered? Can I load it dynamically?

Thanks. :)

Currently the trackable data files (config.xml and qcar-resources.dat) must be present at compile-time. There is no way to download these and use them at runtime. This is a feature request we are considering, however.

- Kim