(2020-07-01, 16:22)Orion Pobursky Wrote: A model viewer has been added to the LDraw.org website. This new tool will allow you to upload a model and view it in your browser. It's fairly basic at the moment but functionality will continue to be added.

It can be found in the Tools menu on the LDraw.org main site (click the red brick logo above) or directly here:
https://www.ldraw.org/tools/ldraw-model-viewer.html

This new feature is a continuation of an effort started with the LDCad PBG Generator to bring a series of useful tools to the LDraw.org website. Future plans include an model OMRizer and a part error checker.

As always, feature requests and improvements can be posted in the Website Suggestions forums.

(2020-07-01, 18:01)Jaco van der Molen Wrote: What happens to the files you submit? Are they kept or temporary and deleted after viewing?

(2020-07-01, 19:27)Orion Pobursky Wrote: Nothing. Everything is handled in browser and it never leaves your computer.

This may change slightly in the future. For the PT, I send the part number to be displayed to the server and it sends back a list of the parts and primitives used in the file. This helps speed the processing of the file since the viewer doesn't need to ping 2/3/4 separate address to figure out where the part data is (official/unofficial parts/p/textures). For models, the script used will get the model data but it won't be saved anywhere, only used internally by the script.

(2020-07-01, 20:30)Gerald Lasser Wrote: But is it loading unofficial Parts properly? I tried a model using part 24121 (unoff), it did not show this part.

(2020-07-01, 19:27)Orion Pobursky Wrote: This may change slightly in the future. For the PT, I send the part number to be displayed to the server and it sends back a list of the parts and primitives used in the file. This helps speed the processing of the file since the viewer doesn't need to ping 2/3/4 separate address to figure out where the part data is (official/unofficial parts/p/textures). For models, the script used will get the model data but it won't be saved anywhere, only used internally by the script.

(2020-07-01, 22:08)Lasse Deleuran Wrote: You can get stud logos if you include the texture loading..

(2020-07-01, 22:35)Orion Pobursky Wrote: I basically copied your sample code so if that doesn't load textures then the model viewer won't either. 
As for logos, this is the bug I reported. When I do stud logos, the loader want 3-4disc but never actually tries to load it.

(2020-07-01, 16:22)Orion Pobursky Wrote: A model viewer has been added to the LDraw.org website. This new tool will allow you to upload a model and view it in your browser. It's fairly basic at the moment but functionality will continue to be added.

It can be found in the Tools menu on the LDraw.org main site (click the red brick logo above) or directly here:
https://www.ldraw.org/tools/ldraw-model-viewer.html

This new feature is a continuation of an effort started with the LDCad PBG Generator to bring a series of useful tools to the LDraw.org website. Future plans include an model OMRizer and a part error checker.

As always, feature requests and improvements can be posted in the Website Suggestions forums.

(2021-06-03, 10:52)Jaco van der Molen Wrote: I am trying to submit and view a model that does not load.
The process stalls at loading 3-16cyls.dat?
Another model that has kind of the same bricks does load.
At least, I think it also has 3-16cyls.dat in a brick somewhere, because I briefly see it loading.

What could cause this?

(2021-06-07, 23:27)Orion Pobursky Wrote: Sorry for the delay.  Can you post or PM the model  in question so can test it?

(2021-06-08, 5:45)Jaco van der Molen Wrote: Np

I have PMd you.

(2021-06-09, 15:43)Orion Pobursky Wrote: This report has uncovered a much deeper bug. Some models load, others don't.  There doesn't seem to be any discernible pattern. Apparently all my test files didn't have whatever problem is causing buildinginstructions.js to crash but figuring out what that is will take some more digging.

(2021-06-09, 18:06)Jaco van der Molen Wrote: OK, strange. But good luck bughunting. I'm afraid I cannot help you with that, but if you need any testing done, let me know!

(2021-06-11, 3:01)Orion Pobursky Wrote: I think I've fixed the issue. I'm still not sure what the problem was but my fix bypasses all the issues (I think) by totally regenerating the model object. I did find another bug involving changing background color but that doesn't affect the rendering of the model.

(2023-10-09, 14:30)Eduard Wrote: Hey @Orion Pobursky,

I would like to use the Viewer for a small university webpage for a lego lab (a lego lab made with school children, only for educational purpose).

We have a few own models (as .ldr files, converted from Lego Studio .io) and we would only need a basic simple viewer to show/zoom/rotate the 3D models as a motivation for the kids how the final model looks like.

Is there a copyright?

Or did you just used the ldraw viewer docs from ThreeJS for building it ?

Any code you would like to share (basic functionality around ldraw viewer) ?

(2021-06-11, 3:01)Orion Pobursky Wrote: I think I've fixed the issue.

(2024-10-18, 10:29)Rene Rechthaler Wrote: something i noticed: edgelines in inside corners are hard to see...
(which then sometimes looks like a missed one)

(2024-10-18, 16:13)Orion Pobursky Wrote: This is a known problem with lines in WebGL. I vaguely remember a discussion here on the forums if you want to dig for it.

• https://forums.ldraw.org/thread-26372-post-55313.html#pid55313
  

(2024-10-18, 21:47)Orion Pobursky Wrote: This is a rendering software issue (transparency can be tricky).

Open an issue with buildinginstructions.js:
https://github.com/LasseD/buildinginstructions.js/

Edit: I take this back for now as the 3D preview for the tracker doesn't do this.

(2024-10-18, 19:10)Orion Pobursky Wrote: I made a few tweaks to the part fetch routine. Using your model, I'm not seeing the problem you mention. Is it fixed on your end?

(2024-10-18, 23:19)Orion Pobursky Wrote: Also, FWIW, LDCad renders the boat motor test file with no obvious problems.

(2024-10-19, 0:52)Eugen Wrote: Confirms, in LDCad all looks good.

(2024-10-18, 22:44)Franklin W. Cain Wrote: Sorry, they still show.  :-(  

FWIW, you are probably using a previous version of my model, where those parts were still color-72, Dark Grey, which is why you won't see this problem. Here is the relevant segment of DAT code, updated: 

Code:

0 FILE joint.ldr
1  71    0    0    0  0  0 -1  0 -1  0 -1  0  0 32016.dat
0 STEP
1   4    0    0  -10  0  0  1  0  1  0 -1  0  0 89678.dat
0 STEP
1  16    0    0    0  1  0  0  0  1  0  0  0  1 joint-pt01.ldr
0 //
1  16    0    0    0 -0.924 -0.383  0  0.383 -0.924  0  0  0  1 joint-pt01.ldr
0 STEP
1  16    0    0  -10  0.981  0  0.195 -0.195  0  0.981  0  1  0 joint-pt02.ldr
0 NOFILE

0 FILE joint-pt01.ldr
1   1   30    0    0 -1  0  0  0  1  0  0  0 -1 43093.dat
0 NOFILE

0 FILE joint-pt02.ldr
1  72    0    8  -20  1  0  0  0  1  0  0  0  1 85861.dat
0 STEP
1  71    0    0  -20  0  0  1  0  1  0 -1  0  0 15712.dat
0 STEP
1  72    0   -8    0  1  0  0  0  1  0  0  0  1 26047.dat
0 STEP
1  71    0  -16    0  0  0 -1  0  1  0  1  0  0 32828.dat
0 NOFILE

Thanks! 
Franklin

(2024-10-19, 3:15)Orion Pobursky Wrote: This leads me to believe this some sort of external graphics issue and beyond my ability to fix.

(2024-10-19, 3:32)Orion Pobursky Wrote: You're using a mirrored matrix on this line:

Code:

1  16    0    0  -10  0.981  0  0.195 -0.195  0  0.981  0  1  0 joint-pt02.ldr

It causes problem in LDCad as well.

(2024-10-19, 4:09)Orion Pobursky Wrote: It's not worth the trouble since the problem will lie with WebGL render package which I didn't write and don't have the knowledge, skills, or time to try to fix.

(2024-10-19, 4:50)Eugen Wrote: OK, lets leave external graphics issues to its software developers.

But why there is a difference between shortcut and the manually assembled model from subparts?

This difference looks like LDraw-specific issue, as it appears more or less in all the programs and in online viewer too.