All the parts missing for the Phantoka and Mistika Bionicle Toa sets? Is there a possibility that you could create all of the pieces missing from 8685-1 to 8690-1?

What might cause this type of rendering error of certain LSynth parts in Stud.io's photoreal renderer? In this model it's the Technic flex-system (rigid) hose; not all types of flexible parts seem to have this problem. (And the POVRay renderer does it correctly, it's only in Eyesight that there's a problem.)

Attached Files

Thumbnail(s)
   

I did noticed that I tried to download some models, & some of them are quite good, Also behind are some text files within the models. How do I use these text files, Is there a programming feature within LeoCAD, to adapt these text files?

Richard L. West

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 LDraw Parts Libary 2019-01
* Update to LDCad 1.6c
* Update to MLCad 3.51
* Update to LeoCAD 19-01
* Update to LPub3D 2.3.12.0.1356
* Update to Offline Parts Catalog 2019-01
* Update to LDConfig.ldr 2019-08-07

You can download the AIOI from:

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

Willy Tschager
(LDraw Content Manager)

Just a question, does LeoCAD have an option for color picker feature?  Will that included in next version of LeoCAD, just asking though? 

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 alignment for the Technic Panel in relation to the Dark Grey axle in the above photo seems to off by more than I would expect. Since my parts are still in storage, can someone check this out for me? I've attached the sample LDR file.

Attached Files

  panel_aligment.ldr (Size: 821 bytes / Downloads: 3)

Hello!

Between part 98282 and other bricks are distances visible (for comparison see part 50745).
Who can check this in detail and correct it if necessary?

(I don't know how to insert an image from PC )

Best regards
Alfred

Attached Files

  part_98282.jpg (Size: 13.48 KB / Downloads: 50)

Thread for Technic sets released in 2000

Hey,

here is a new LDPartEditor release which let you swap the mouse button layout (for rotation and translation in the 3D view).


  mouseButtonLayout.PNG (Size: 4.38 KB / Downloads: 100)

I also provided an alternative 64-bit linux release since I had some problems with LDPE on another linux distro (Ubuntu).


As always, you can download LDPE from this page:
http://nilsschmidt1337.github.io/ldparteditor/

Changelog:
(3 new features and 2 bug fixes)

With this release you will be able to...

• ...swap the middle and right mouse button assignment (view translation and view rotation)
  
• ...get the PNG textures from the PartsTracker when you are using the PartReview tool.
  This is useful for the review of !TEXMAP patterns.
  
• ...configure a viewport scale factor (this is only necessary for 4K screens with a high pixel density)
  

1. Display issues on a 3840x2160 display: empty regions & misplaced cursor.
   
2. The vertex window popup was causing an internal error (with no negative side effects for the user).
   

1. Download the zip-Archive
   
2. Extract the archive content to the location of your choice
   
3. On windows, double-click "run.bat" to start LDPE.
   
4. On linux/mac, you have to excecute the shell script "run.sh" to start LDPE.
   

1. On windows, double-click "update.bat" to search for updates.
   
2. On linux/mac, you have to excecute the shell script "update.sh".
   

• 64-bit Java Runtime Environment (JRE) 1.8
  
• OpenGL 2.1 compatible Graphics Card
  
• Operating System (64-bit): Windows [7 or newer], Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
  
• RAM: 4GB
  
• Video-Memory: 1 GB
  
• Free Disk Space: 100 MB
  

• Operating System (64bit): Windows 7,8,10, Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• OpenGL 3.3 compatible Graphics Card
  
• CPU: Multicore-Processor with 4 cores (or more)
  
• RAM: >4 GB
  
• Video-Memory: >1 GB
  
• Free Disk Space: 512 MB
  
• For a faster start, LDPartEditor and the LDraw™ library should be installed on an SSD.