Trevor,

As you are aware, I've been working on trying to improve the quality of the POV-Ray rendering in LPub3D.  The first step was to implement customized lighting.  That resulted in a major improvement, but I was still running into an issue that I felt needed to be fixed: many images had dark gray artifacts on curved surfaces that I couldn't get rid of simply by changing the light definitions.

I think I have finally figured out source of the problem.

When LPub3D invokes L3P, it specifies a camera angle (field of view) of 0.01 degrees (-ca0.01).  I assume that you work backward from there to determine the camera distance (-cg0,0,{large number}) in order to end up with a properly-sized image.  My guess is that you are using a small field of view and a long distance to minimize apparent distortion caused by different parts of the model being different distances from the camera.  I think -ca0.01 is quite a bit of overkill and is leading to the artifacts I mentioned.

I have modified my program that inserts custom lighting to also modify the -ca and -cg parameters.  I am currently using a 10-degree FOV and calculating the corrected camera distance.  I'm quite pleased with the results.  The resulting renders are much closer to the quality I get when using LDView to manually generate the POV file.

Can I suggest that you try larger FOV values to when calling L3P to improve the quality of the resulting render while still minimizing apparent distortion?  Perhaps this could be a value set by the user in Preferences.

I've also been working on a way to have LPub3D use LDView for exporting POV files.  I've had some moderate success, but it's pretty klugey.  Since I figured out the L3P issue, there is no longer the same level of urgency to pursuing this route.

Thank you.

Kevin

Hi everyone,

I have created a virtual reality editor for ldraw.

https://github.com/baxterai/ldrawVR

ldrawVR currently supports Oculus Rift with Oculus Touch (although it could be easily upgraded to support Vive, considering that it is built using the Unreal Engine VR Template).

The C++ source is currently licensed under AGPLv3, which means that compiled/built versions of the project can't be distributed (due to Unreal Engine licensing restrictions), but you are welcome to test it out.

Custom parts are currently experimental (which use UE procedurally generated mesh objects), but it contains a full snapshot of the ldraw.org parts library (stored as UE static meshes). dat->fbx->uasset conversion of the parts library was achieved using the Blender Ldraw Importer add-on (along with some other tools to hack the fbx binaries).

I added some videos last year when I first tested it out (after around 4-5 weeks of development), a few days after the touch system arrived;

https://vimeo.com/196450456
https://vimeo.com/196450376
https://vimeo.com/196450270

Richard

Hi all!

I'm Miriana, I'm a lego fan aholic enthusiasitc...^^

I use mlcad, now I'm making "millenium falcon" from star wars (mod. 7778) and I need help with a part.

I need to "curve" Corrugated Pipe 112Mm as flexible part to put on model (as shown on attached image).

Can you help me?

Thanks in advance.

Attached Files

Thumbnail(s)
   

An updated version of the LDraw All-In-One-Installer, in short AIOI, has been released.

The AIOI supports Windows XP (Home and Pro), Windows Vista or higher (all versions). On 64-Bit Operating Systems it will install in the "Program files (x86)" folder. The Installer will NOT run on Windows 95, 98, ME, NT Ver 4, 2000, or XP below SP2.

It contains the following changes:

* Update to Parts Library 2016-01 (published 31.12.2016)
* Update to MLCad.ini 2016-01
* Update to LDView 4.2
* Update to LPub3D 2.0.19.877.2
* Update to LeoCAD 0.83.2 - 9306
* Update to LDCad 1.6 beta 1a
* Update to Offline Parts Catalog 2016-01
* Addition of LICreator 3.0

You can download the AIOI from:

Home > Help > Get Started > LDraw All-In-One-Installer

Many thanks to all the programmers who contributed to this release.


Willy Tschager
(LDraw.org Content Manager)

Per the LDraw.org Bylaws at [color=black]http://www.ldraw.org/article/268.html[/color], Subsection
6.03(a), the 2016/2017 Steering Committee hereby calls for the community to
nominate individuals as candidates for the 2017/2018 Steering Committee[1].

Please post nominations in response to this message. Nominations will only be
recognized if they are in response to this message.

Per ss.6.03(a), you must specify the name of the person you are nominating,
along with your name. Another member of the community must second the nomination
in a reply, and the nominee must publicly accept the nomination in the same
channel (direct reply to the nomination or second) in order to be valid. If the
nominee does not accept, it will be assumed that he or she has declined, and
they will not be placed on the ballot.

Nominations will close at 11:59 PM GMT on 28 February 2017. This means that to
be listed on the ballot, a candidate must have been nominated, seconded and must
have formally stated acceptance by that time.

The Steering Committee will give sufficient notice of the election and election
procedures per ss.6.03(b).

NOTE: subsection 6.03(b) states that elections should take place before March 1.
We interpret this to mean that we will commence the election on March 1, but
since it is electronic, it will run for 2 weeks, just as last time. The exact
time and date of start and end will be announced sometime very close to (but
after) 0000 GMT March 1.

Again, thanks to all of you for your commitment to the goals of the
organization, and in working with us this year. Please, stay involved with
LDraw.org and keep it moving forward!

Max Martin Richter
On behalf of the LDraw.org Steering Committee

--
[1] Try not to confuse the LDraw.org Steering Committee (SteerCo) with the LDraw
Standards Board (LSB). The Steering Committee sets the course for the LDraw
Organization while the Standards Board deals with the LDraw File Format.

Hi,

The release candidate of the AIOI 2016-01 can be downloaded here:

http://www.holly-wood.it/tmp/LDraw_AIOI_...bit_v1.exe

Change log:

* Update to Parts Library 2016-01
* Update to MLCad.ini 2016-01
* Update to LPub3D 2.0.19.877.2
* Update to LeoCAD 0.83.2 - 9306
* Update to Offline Parts Catalog 2016-01
* Update to LDCad 1.6 beta 1a
* Addition of LICreator 3.0

Your testing would be appreciated.

w.

 I found a new theme for the forums that might be liked better by some. It's a bit less white and more grey like the old forums software.  I still have to do some modifications to it (e.g. some images are broken) but you can give it a test drive.  

- Go to User CP
- In the sidebar under "Your Profile" click "Edit Options"
- On the right under "Other Options" change "Board Style" to "stb"
- Click Update Options

Please let me know what you think and if you notice any broken images which seems to be the biggest issue right now.

Has anyone taken a crack at making the #16477 Windscreen 16 x 8 x 6 Curved with 3 Pin Holes? 

Bricklink.com #16477 Windscreen

Guys,

is this:

www.bricklink.com/v2/catalog/catalogitem.page?P=973pb0926



a bigger (mirrored) version of the dragon pattern used on this torso:

www.bricklink.com/v2/catalog/catalogitem.page?P=973pb1200



If so, who could make me a shot with a 20 megapixels camera of the golden dragon?

w.

How come only color 16 shows up when an LDraw file has been exported to STL using LDView? All other colors go invisible. Is that intentional? (The data is still there though, since the STL file is good for the 3D pinter anyway).

And no, it's not a BFC issue; all I have to do is change the color to 16 and it shows the surface again.
https://www.dropbox.com/s/5oxvdy4qrks5xww/LDView_STL_Export.jpg

[url=https://www.dropbox.com/s/5oxvdy4qrks5xww/LDView_STL_Export.jpg?dl=0][/url]