New OMR WebGL Render Engine


New OMR WebGL Render Engine
#1
As some may know, we're in the process of switching the WebGL engine from brigl to Lasse's buildinginstructions.js (or, as I have dubbed it, LDBI).

Since that last thread became a bit of a monster, here's a summary:

Here's a link to the test page:
https://www.ldraw.org/hidden-content/omr-render.html

If you want to see it in action on the OMR simply find an OMR file page and add "_ldbi" after files in the URL
Example:
http://omr.ldraw.org/files/1182
would change to:
http://omr.ldraw.org/files_ldbi/1182

Here's Lasse's stated priorities:

(2019-09-04, 7:31)Lasse Deleuran Wrote: A progress bar would be a great idea, but my attempts to create one have failed as it has decreased the loading speed significantly. I will have to check StackOverflow for some pointers.

There may be an issue due to the depth buffer issue mentioned earlier. I have also observed it with other large models which are not on wheels.

How is the general feeling of prioritization? Right now my list is:

1) Fix rendering issues (this includes what you mention here, but also the UV calculation as you can see there are still many warnings generated in the log)
2) Stud logos (while studs can easily be enabled by setting a parameter, my experience is that the file size doubles and rendering time doubles as well. I am working on a light-weight alternative)
3) Control buttons to set up camera, lights, etc.
4) Progress bar
5) Better support of transparency.
6) Support of illumination parts (such as glow-in-the-dark ghosts, etc.)
7) Distance-based blur for a more realistic rendering
8) Textures
9) Geometry culling (such as removing studs that cannot be seen)


And of course, everyone is welcome to take up a task and create pull requests - it is all open source / license free
Reply
RE: New OMR WebGL Render Engine
#2
The result looks spectacular but I also vote for a progress bar ... it takes quite some time to load even a small model and in the meantime all I get is a black screen. I'm happy with the simplest hourglass if a progress bar is not doable. Everything telling me something's going on in the background is fine.

w.
LEGO ergo sum
Reply
RE: New OMR WebGL Render Engine
#3
(2019-09-05, 20:02)Willy Tschager Wrote: The result looks spectacular but I also vote for a progress bar ... it takes quite some time to load even a small model and in the meantime all I get is a black screen. I'm happy with the simplest hourglass if a progress bar is not doable. Everything telling me something's going on in the background is fine.

w.

Yes, I'm sure I can put a spinny loading widget in there until a progress bar is implemented.
Reply
RE: New OMR WebGL Render Engine
#4
(2019-09-05, 20:02)Willy Tschager Wrote: The result looks spectacular but I also vote for a progress bar ... it takes quite some time to load even a small model and in the meantime all I get is a black screen. I'm happy with the simplest hourglass if a progress bar is not doable. Everything telling me something's going on in the background is fine.

w.

I added a logarea that tells you what part the renderer is loading.
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)