LDraw.org Discussion Forums

Full Version: New OMR WebGL Render Engine
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
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
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.
(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.
(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.
It looks nice, but I personally prefer the lined style (as it currently is) more. It makes the parts much clearer instead of it looking like a giant blob of plastic.
But, that's just personal preference.
(2019-09-24, 17:46)Merlijn Wissink Wrote: [ -> ]It looks nice, but I personally prefer the lined style (as it currently is) more. It makes the parts much clearer instead of it looking like a giant blob of plastic.
But, that's just personal preference.

It’s getting there but not quite yet. There is a lined style that you like and I think we should offer both options. Also Lasse is actively working on this software as opposed to Brigl which isn’t actively developed.
(2019-09-24, 17:46)Merlijn Wissink Wrote: [ -> ]It looks nice, but I personally prefer the lined style (as it currently is) more. It makes the parts much clearer instead of it looking like a giant blob of plastic.
But, that's just personal preference.
Do you have a screenshot of where it looks bad? I am aware of issues with black and transparent parts, but if you see other things that do not look right, then please highlight it and I can look into it. And don’t hold back. I don’t always see the mistakes that others discover.
I have made a change to the materials used for the various colors. Standard (ABS) colors are now using MeshPhong material from three.js and I am adding some reflection to black parts. Rendering of a normal LEGO model with some black now looks like this:

[Image: 492.png]

The loading screen has now also been minimized by introducing animated construction similar to how you see it in LDD and Studio. Check it out here: https://brickhub.org/i/492 by clicking "3D". Hopefully this gets to the OMR render soon as well. 

I am still working on all the other topics. This was just a post to show you that I am not lying dormant on this.
Quote:Check it out here: https://brickhub.org/i/492 by clicking "3D".
...all I get is an infinite "loading..." (Chrome).
Quote:This was just a post to show you that I am not lying dormant on this.
I'm sure you don't Wink
(2019-10-05, 15:32)Philippe Hurbain Wrote: [ -> ]...all I get is an infinite "loading..." (Chrome).
I'm sure you don't Wink
That's no good! I think you might have been unlucky and hit the server right as I was having an epic battle with FileZilla. However. Just to be sure, I have bumped the .js file revisions so that this should happen now.
Pages: 1 2 3