Repository navigation
Replies: 2 comments
|
This is sadly a limitation of the simulator. It disables all Metal features that are not supported on the immediate-mode GPUs that Intel Macs use. For some reason, it does this even on Apple Silicon Macs. |
0 replies
|
Thank you, so would not rate HostVisible memory as DontDo in general? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We are creating an x-plat app for Windows/macOS desktop and iOS (iPhone/iPad) based on Avalonia. We have our own vk based 3D renderer that we integrated into the Avalonia 2D UI. We have made that work on Windows/macOS (MoltenVK for mac) and just recently as a PoC for iOS using MoltenVK which works.
One gap currently is the fact that we create HostVisible memory in the Vk-based renderer which works on iOS devices but not on iOS simulator. This HostVisible memory is used e.g. to efficiently copy image and other data into the vk items. My question: should we just live with the fact that this is not supported on iOS sim or should such HostVisible memory have been avoided (independent of the the iOS sim problem) in the first place.
Like: when using MoltenVK we noticed that geometry shaders would not work which made us understand that the task our geom shaders currently do, can be implemented even better without them. So, not only will that make the compatibility with MoltenVK better but it makes the entire thing better and simpler.
Hence, I would love to understand whether the HostVisible memory is a similar issue.
All reactions