-
Notifications
You must be signed in to change notification settings - Fork 21
Slow performance setting VertexData
properties with large arrays
#34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can see having a binary transfer abstraction might work here, I would have to do some testing see for sure. I will create an issue in the other project to track it. |
I'm also a little curious if there's a way to make the "default" number type be a double or float instead of a decimal. I haven't dived too deeply into it but using decimal makes the arrays twice as big when they don't need to be. I'm still exploring some of the options for your generator. Regardless, this is a great project! Thanks |
It has to be decimal sadly, it was not my first choice. I have spent many hours on this and it is a headache. |
This hack seems to be a decent workaround to loading large arrays into BabylonJS. And it works with float arrays, too :)
Typescript:
|
There is a huge bottleneck for me right now when I try setting decimal arrays of length > 100,000 on the
VertexData
object. It's probably due to the JSInterop layer. I took a look at your other project and it seems you useIJSUnmarshalledRuntime
only for certain getter scenarios.I wonder if it would make sense to include a new set function that has an option to use
IJSUnmarshalledRuntime
to transfer binary data. Maybe this belongs on your other project...The text was updated successfully, but these errors were encountered: