Wow! Oh Wow! 3D for C2?! Me interest max!! Not sure why, but I can't test out the tinytank demo. I see the instructions but get a blank black screen. Really want to see what this baby is capable of doing!

Hi guys,

I am trying to learn and understand how the alpha, beta and gamma in touch orientation work. I did a test where three text objects display the values for each at every tick. I rotate my phone in every type of axis to test it out and get a better understanding of how it works. Problem is I really don't understand the results.

For example: When I hold it standing up straight on a table, the gamma which I read is in charge of right to left tilt, was somewhere in 80s. I thought that it was reading it close to 90 degrees. But when I tilt it roughly 30 degrees to either side, the numbers jumped a lot. It even went until the 10s. Another thing, I just tilt my phone to the left or right, but all three values changed a lot. I tried various axis movement and all three values moved around a lot. And also sometimes the numbers jump from negative to positive. For example, holding it in my slightly shaking hands, the value could jump from +80s to -80s. That was really confusing to me.

I apologize if I am missing something obvious here, but I really do hope that someone would be able to shed some light on this. For your reference, I tested it out on my HTC One using Crosswalk in the Intel XDK debugger test. Would really appreciate any info and guidance on this. Thanks.

Not sure if I understand correctly, but you have an object that rotates and you want to know what number or information is at the top when it stops?

I think the easiest would be to set up a condition, using the angle of the wheel. For example, check the angle of the wheel once it stops. If it is between angles 1-30 it is number 1, if it is between angles 31-60 it is number 2 and so on.

Wow! Nice! Going to download and try it out alextro!

guangzhen, thanks, it is good to know that the issue is being looked and and going to be updated soon.

It might take a while before I am able to test the solution and the "Android" option right now, as my computer had some problems and is now being fixed. Will try it out once I can. Thanks again!

guangzhen thanks for that. That sounds like a reasonable solution. Any news on the half black and half white screen when we change the phone's orientation during the splashscreen being displayed? I think that is a more obvious worry.

alextro, wow! The movement is really smooth, and the special effect of showing you which direction you are moving the blocks in is really nice! This should be a fantastic template for those that want to learn how to do swipe style puzzles! Thanks for sharing alextro!

Glad to see you have your solution Scottydoes3d.

Whiteclaws and blackhornet, thanks for that as well. I learnt something new

I've edited the capx so that now it will fade visible and invisible using opacity each time you flip the switch. I didn't do the 50% opacity if the switch is halfway, but if you study the capx, you should be able to easily do it as well.

https://www.dropbox.com/s/xp2l3oggmgk1y2s/Lighting%20TestModified.capx

quadonx, that looks right. So what is your issue? The music doesn't loop? It plays only once?

It is straight forward actually, just place it on Start of layout, and set it to loop. That's all.

Can you post a picture of your event sheet? I am sure everyone will be able to determine what is wrong.

Hi Ran, haha as a fellow graphic artist with absolutely 0 skill in programming, I can understand your feelings!

For my case, I try to use as little invert as possible. I think in your case you are using too much inverts that you have gotten confused. To be honest, I am quite confused with what you are trying to do in the first picture. You should try to keep your triggers as simple and as little as possible.

For most of your images, your problem is that you didn't have a trigger once while true, so it will for every tick run those actions and wait for that amount of seconds, which is it waits forever. For example, the second image of waiting 4.2 seconds, it does that for every tick, so it will never end.