No hardware acceleration and for now limited to it seems 8gb ram allocated to the VM but for the sake of me being bored, it works.
5 Likes
Cool! But it’s not really useable as I understand, right?
If you have pen or touch input on your PC like I do, it’s useable but not fast.
Remeshing takes a long time, subdividing takes a long long time.
More ram means more total vertexes, but if I could get my GPU to provide HW acceleration it would be fast.
Maybe as the platform develops it might get better, or if you have a really really high end CPU (I’m running a Ryzen 3400g 4c8t 4ghz 32gb ram) it might be as fast as the New iPads maybe?
I’ll see if I can get more ram in the VM and HW acceleration to work.
It’s also a long process to get it working though, custom kernels and stuff, so it’s certainly not something I would recommend trying.
I am out 
I would not install win 11 on my workstation anyway the next year. But if everything is accelerated it would be interesting with a RTX3090, i9 10900K and 64 Gig Ram. But my Cintiq has no touch, though.
You can just install an Android emulator like bluestack.
2 Likes
You can, but the overhead in the emulator means much worse performance than the near bare metal solution for the wsa.
At the moment there’s no vulkan API support, so once that’s running it will be interesting. Everything is CPU based right now and even that is able to handle a few million vertex sculpt.
1 Like
It’s not cpu based, it supports OpenGL (not sure if it supports 100% of i thought).
Nomad simply uses OpenGL, Vulkan wouldn’t make much difference anyway.
If anything, the bottleneck is probably more on the CPU (overhead of VM? multithread? simd?, etc)
It’s definitely bottlenecking in the CPU as it’s using 0 GPU (even by nomads debug and log it’s using 0 GPU) it might be a configuration issue on my end as technically the subsystem should allow a vGPU with openGL and openCL support
I managed to get 16gb of ram Allocated and got stable 41M vertex models to sculpt with only 20gb system RAM used lol.
It doesn’t use the GPU.
The GPU is only used for rendering.
These logs don’t work, it always shows 0.
If your GPU is not used and if you have millions of face, it should run at <1fps.
CPU-optimized renderer are very rare (zbrush being the exception).
Blue stack, that sounds like a Great idea. Is it useable on blue stack or is it slow as well?:):):)
1 Like
Blue stacks didn’t support multitouch screen nor stylus, Windows subsystem for Android supports both. GPU is definitely used in WSA for rendering (Device reports as Vendor: Microsoft, Renderer: Subsystem OpenGL ES Translator).
CPU operations, including regular sculpting, are annoyingly slow though… Oh, the potential… If only…
Any chance of a native unsupported unofficial Windows build? I don’t care about keyboard at all (laptop is HP Envy x360, so keyboard will be folded away anyways). Stylus also isn’t super important, and maybe I could monkey patch it in myself via dll injection.
Yes, I know there are alternatives out there, many of them free, none of them however were made from the ground up for touch screens, which is an edge Nomad has over all of them. Nomad’s interface is just so clean, natural and an absolute joy to work with.
1 Like
How did you get it to work i tried using wsa but nomad kept closing when i tried to open it