I am working on a Xamarin.Forms project with a interactive 3D part that should run on UWP, Android and iOS. The most obvious and proposed solution for the 3D part seems to be UrhoSharp. However, we have encountered a number of serious issues in UWP that make us wonder whether UrhoSharp is production ready and a reliable solution for the future.
The issues include:
- AccessViolationException while loading models this part of the code is already invoked from main thread but once every 20 or so starts the error still occurs, can't be caught in our applications code and thus always leads to a crash.
- Erroneous pointer positions the calculation for the pointer position is wrong and it seems that the size of the window is being used instead of the frame. This error is known and described in issue 310 on github (can't post links yet) since March. We fixed it by calculating the offset but its really a hack instead of a solution.
- Navigation issues when navigating to the page containing the UrhoSurface using back button or PushAsync there are a bunch of different issues. This includes "application not ready" exceptions (which seems to be a racing conditions since putting in a delay seems to work), black screen when returning to a previous UrhoSurface and residue in memory despite calling all exit, dispose and destroy functions on the objects.
- No updates, low maintenance the last release is 4 months old and many questions on the forums have an open end.
Since our application is supposed to be used by technicians in a industry environment on a daily basis, these issues are really deal-breakers for UrhoSharp. Therefore my questions. Are we the only ones facing these problems? Is UrhoSharp under active development and if not what 3D Engine are we supposed to use with Xamarin.Forms?
Thanks and Best regards