THanks QuaziGNRLnose for clarifying timescale issue. For some vague reason I thought tickcount was timescale sensitive ( meaning ticks wouldn't count when timescale =0)...Could you please help me how can I translate the expression "cos(tickcount)" into something so that it becomes timescale sensitive?
Here is some list of things that I noticed while I am preparing my app for iPad - Your comments will be helpful
1. The Q3D inside mode is absolutely slow on iPad. I had to change this to Infront. But this came with a set of UI issues that I had to workaround...It will be good if inside mode can run faster as this is the most useful mode where the power of C2 and Q3D can together be leveraged to the fullest extent.
2. I could no longer use Scale/Position to Autofit mode because I had C2 UI elements that I had to show on the screen. And since Q3D mode is infront now, I had to leave top and bottom borders around Q3D area, to include these C2 UI elements.
3. For this reason, I had to change Q3D to Positioned. But in Positioned mode, though my Project window size was 640 by 480 ( as required for iPad), I had to somehow re-size the Q3D area to 1020 by 655 to make it fit the iPad screen!! I had to arrive at this by several trial and error...Somehow Q3D size as occupied in the editor doesnt scale up as it is onto the screen at run time. Added to that, it is scaling differently for different browsers in positioned mode! This had been a big problem for me...Please let me know.
4. Probably a WebGL issue - If the image size used in Q3D was large, then somehow it gives me a WebGL memory error and doesnt load that Q3D texture on iPad, although it works fine on a desktop.
I have lot of plans to use this plugin extensively for my apps. Your help will be appreciated.