You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2020. It is now read-only.
To my knowledge, Three.js is a veneer over browser canvas/WebGL that allows for 3D graphics. Considering UO isn't 3D, what are you hoping to gain from using a 3D rendering library that you couldn't get using standard WebGL?
The text was updated successfully, but these errors were encountered:
I'm considering using it because the land is rendered in isometric 3D on the original client. Three.js has an isometric camera which would be ideal for rendering it. Trying to emulate that with 2D rendering isn't really easy and tends to have several bugs.
We can then overlay sprites (which constantly face the camera) for framed animations and items on top of the orthogonal projected map. :)
Using webgl by itself without a wrapper would be a bit too complex for me. Perhaps down the line, it could be switched to use webgl alone.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To my knowledge, Three.js is a veneer over browser canvas/WebGL that allows for 3D graphics. Considering UO isn't 3D, what are you hoping to gain from using a 3D rendering library that you couldn't get using standard WebGL?
The text was updated successfully, but these errors were encountered: