xeon

Here is a simple example of a health bar using Shape Keys.
https://cdn.soft8soft.com/AROAJSY2GOEHMOFUVPIOE:f2f27a4091/x3l_healthbar.zip
Blend file included.

There are two cubes – left and right. Clicking on the left cube simulates something that would deduct from health…..the right cube simulates and input that would add to the health.

Hope this helps.

Hi there…after reviewing the file you will find the problem in your shader nodes.
Although the Voronoi Texture is supported its really only has limited support. You happen to be using two things within that node that are not supported. You are using “4D” and “W” you will have to change to settings to 3D which will eliminate the “W”. You can read more about this here: https://www.soft8soft.com/docs/manual/en/blender/Shader-Nodes-Reference.html#Voronoi_Texture

With respect to uploading zip files. The V3D App Manager supports uploading zip files to the soft8soft CDN. You can find more info on this here: https://www.soft8soft.com/docs/manual/en/introduction/App-Manager.html#exporting_applications

Can you provide your project file wit the texture….or at least the shader nodes that we can look at?

Sounds like your problem is isolated to iOS is this correct? Are you using XRviewer to test or something else?

If you scene is optimized and your puzzle logic is clean and memory controlled (no infinite loops) your use of procedures will not affect your FPS in any meaningful way. However if your puzzle structure is created with a lot of open or free floating puzzles, then grouping them would be helpful. I personally do not let any puzzles exist outside of a procedure except for my initialization set of puzzles. This ensures I am controlling the flow of execution vs letting the position of the puzzles determine the execution order. In doing this I have always been able to get FPS of 60 after loading in to memory. Based on your code examples for your project you are going to have a tough time keeping a high FPS because you are using more than one “every frame” puzzles and its questionable whether all the things being requested can be completed in less than 1/60 of a second. It probably takes longer….thus limiting your FPS.

You will need to validate that the conditions of your logic are actually occurring?

I suggest adding some simple print to console statements for each condition so you can validate if the conditions you are testing are firing as expected.

Values from the getmorph puzzle is a “number” so you can do what ever math you want to it and stick it back into a setmorph puzzle.

I try to provide information when I can at xeons3dlab.com

There are tutorial links in the forum that may also be helpful.