Here is an article that describes the motivation behind Babylon Native.
cmake displays such error:
C:>cmake -D CMAKE_SYSTEM_NAME=WindowsStore -D CMAKE_SYSTEM_VERSION=10.0 -A arm64 ..
-- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.
CMake Error at CMakeLists.txt:5 (project):
Failed to run MSBuild command:
C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/MSBuild/Current/Bin/MSBuild.exe
Check you have installed MSVC for arm64.
In VisualStudio, go to menu Tools -> Get Tools and Features. Then check for arm64
A detailed page is avaible here.
The JavaScript virtual machines (JavaScriptCore, V8, Chakra, ...) that we have so far all support WebAssembly automatically.
In VisualStudio, select Script in the Local Windows Debugger. Then, run your app in debug mode (F5). You can put breakpoints, watch variable, ... in your JS scripts.
With Safari tools, it's possible to hook any JavaScriptCore instance running locally on your Mac or on your device and simulator. Follow this steps to set it up. Then you can debug from Safari just like you would debug standard JS.
First, if you get rendering issues in Babylon Native but you don't reproduce in BabylonJS (in Playground), please consider posting the issue on BabylonJS forum.
Download and use RenderDoc. You can find a guide to debug graphics on Android device at this location.
The tool of choice on Apple device is Xcode. It contains tools to capture and inspect shaders, textures and more. A more detailed documentation is available here.
A complete callstack along system information can be retrieved with this command after your app has crashed on your device:
adb bugreport ./bugreport.zip
It will create a zip that can be linked to an issue to help debugging. More details can be found at this link : https://developer.android.com/studio/debug/bug-report