Common ShiVa3D Issues and Solutions

1. ShiVa3D Project Fails to Build

Developers may experience build failures when exporting a project for deployment on different platforms.

Root Causes:

• Incorrect platform settings in the export configuration.
• Missing or outdated SDK dependencies.
• Script errors preventing proper compilation.

Solution:

Verify the platform settings in the ShiVa editor:

Project > Export > Select Platform

Ensure the correct SDK versions are installed:

Android: Install latest NDK and SDKiOS: Ensure Xcode and required profiles are installed

Check the log output for script errors and resolve them before exporting.

2. Lua Script Errors and Runtime Crashes

Lua-based scripting errors may lead to unexpected crashes or incorrect game behavior.

Root Causes:

• Incorrect function calls or missing required arguments.
• Nil references causing runtime exceptions.
• Incorrectly loaded assets leading to script failures.

Solution:

Enable error logging to debug script issues:

application.setOption(application.kOptionLogLevel, 3)

Check for nil references before accessing variables:

if myObject then    myObject:doSomething()else    log.message("Object is nil!")end

Ensure assets are properly loaded before use:

if application.hasResource("myTexture") then    local texture = resource.get("myTexture")end

3. Performance Bottlenecks and Low FPS

ShiVa3D applications may experience performance issues due to excessive draw calls or inefficient scripting.

Root Causes:

• Too many active objects in the scene.
• Unoptimized textures and high-poly models.
• Excessive physics calculations in real-time updates.

Solution:

Reduce draw calls by batching objects:

scene.setBatchingEnabled(true)

Use lower resolution textures and optimize 3D models.

Limit physics calculations to only necessary objects:

if object.hasComponent("Physics") then    physics.applyForce(myObject, 0, 10, 0)end

4. Shader and Rendering Issues

Visual artifacts such as flickering textures or missing lighting may occur in ShiVa3D.

Root Causes:

• Incorrect material settings in the object properties.
• GPU driver incompatibilities causing rendering errors.
• Unsupported shaders used on mobile devices.

Solution:

Ensure proper material assignments:

object.setMaterial(myObject, "myMaterial")

Update GPU drivers and test on different devices.

Use mobile-friendly shaders for better compatibility:

material.setShader(myMaterial, "MobileOptimized")

5. Input Handling Not Responding

Touch or keyboard inputs may not work as expected in ShiVa3D.

Root Causes:

• Input bindings not correctly assigned.
• Incorrect event listeners in scripts.
• Conflicting input events overriding expected behavior.

Solution:

Verify input bindings in the ShiVa3D editor.

Use proper input event listeners:

function onKeyDown(k)    if k == input.kKeySpace then        log.message("Spacebar pressed")    endend

Ensure multiple inputs do not interfere with each other.

Best Practices for ShiVa3D Development

• Optimize scene objects and limit unnecessary draw calls.
• Debug Lua scripts with logging to catch errors early.
• Use mobile-friendly shaders for better rendering performance.
• Profile game performance and reduce excessive physics calculations.
• Test input handling on multiple platforms to ensure compatibility.

Conclusion

By troubleshooting build failures, script errors, performance bottlenecks, rendering issues, and input handling problems, developers can create stable and optimized games using ShiVa3D. Implementing best practices ensures a smooth development experience across multiple platforms.

FAQs

1. Why is my ShiVa3D project failing to build?

Ensure correct platform settings, verify SDK dependencies, and resolve script errors before exporting.

2. How do I fix Lua script runtime crashes?

Enable logging, check for nil references, and ensure assets are properly loaded before use.

3. Why is my ShiVa3D game running slowly?

Reduce draw calls, optimize textures and models, and limit real-time physics calculations.

4. How do I resolve rendering issues in ShiVa3D?

Verify material assignments, update GPU drivers, and use mobile-friendly shaders.

5. Why is my input handling not working?

Check input bindings, use correct event listeners, and ensure input events are not conflicting.