Hey,

I recieved a mail from Willy and transformed it into a new LDPatternCreator version.

Download and install the latest LDPatternCreator release directly from sourceforge.net.
Any previous version should be uninstalled first. Your program configuration will be preserved.

Change log:

New features:

• Included the latest #-#tang primitives (1-16tang.dat, 1-8tang.dat, 1-4tang.dat, 48\1-16tang.dat, 48\1-8tang.dat).
  

• "Add Vertex" was not compatible with the "Create a Spline..." feature.
  
• Version 1.7.2 triggered a false alert on Windows Defender. I had to increase the version number and re-build it.
  

Quote:Bug-Detail:

•     Select "Add Vertex [A]"
  
•     Set a vertex. Watch out for the small coordination windows in the bottom right-hand corner
  
•     Select "Add Primitive [F7]... Create a Spline..."
  
•     Click to add the spline starting point
  
•     Click to set the first direction of the spline
  
•     Click to add the next point
  
•     Click to set the next direction
  
•     You CANNOT click to apply the segment count because the "Vertex-Data" is still there hiding the segment count window underneath.
  

Hello,

I am working on a set of steam train driving wheels that I 3D print and I want to have LDraw parts to share. I know I can go the route of STL->Dat but the files are HUGE (10k+lines) and I would like to optimize a little better. 

So far my thought is to have a slice of the outer ring that is 1LDU thick but has the profile of the wheel then take and spin that 360 degrees. I can then create a center section of spokes and other features from there. The "problem" is that the largest size of steam driver I am looking to produce is 386 segments (123LDU diameter). Is that "too much" I see that there are other primitives that I can use to create some of the faces but I am worried that the resolution is not high enough for something so large. 

I have attached and example of this. 

I am really looking to make sure I am at least headed in the right direction and that I am not doing something needlessly over-complicated. 

I would think that the creation of a file would go something like this

• Create inner connection 
  
• Create rim(s) at sizes needed
  
• Create associated details
  
• Create the "final" wheel(s) which will have reference to the various pieces needed
  

Attached Files

  13-DR-FL-NG-Rim.dat (Size: 56.95 KB / Downloads: 7)
  BT-DR-FL-NG-Profile.dat (Size: 1.04 KB / Downloads: 5)
  12-DR-FL-NG-Rim.dat (Size: 53.3 KB / Downloads: 4)

Guys,

as you might have noticed a new script has been added to the PT links a while ago, listing the "Weekly New Parts":

Beside the new parts it gives you a good overview of the "Oldtimers", parts that are in review hell for ages because of some issues - mostly abandoned by their authors. I started reviewing and fixing some of them a long time ago and would appreciate if you could have a look and get them into an update:

https://www.ldraw.org/cgi-bin/ptdetail.c.../89918.dat
https://www.ldraw.org/cgi-bin/ptdetail.c.../43936.dat
https://www.ldraw.org/cgi-bin/ptdetail.c.../43750.dat
https://www.ldraw.org/cgi-bin/ptdetail.c...s/6088.dat
https://www.ldraw.org/cgi-bin/ptdetail.c.../48492.dat
https://www.ldraw.org/cgi-bin/ptdetail.c.../11467.dat
https://www.ldraw.org/cgi-bin/ptdetail.c...43ac01.dat
https://www.ldraw.org/cgi-bin/ptdetail.c...61dps6.dat
https://www.ldraw.org/cgi-bin/ptdetail.c...61dps7.dat
https://www.ldraw.org/cgi-bin/ptdetail.c...61dps8.dat

Thanks,

w.

Regarding the Mursten-era door (u8012) and windows (u8019–u8024):

The geometry of these parts is not quite right, and leads to collisions when the tabs are interlocked as intended. I propose this modification, which avoids these collisions, and also those that arise by placing the tab behind a neighboring brick (as seen here). But the real geometry may be a slightly thicker tab that fills the slot better, with the part itself being slightly less than a brick-width in Z (so maybe 18 LDU or so), relying on the part's flexibility to fit behind or in front of a neighboring brick.

This revision also subfiles the tab, for brevity's sake. I use u8021 as an example, but all seven parts would be affected.

Attached Files

  u8021.dat (Size: 3.28 KB / Downloads: 2)

Hello, I was rendering https://www.ldraw.org/parts/official-par...id=3900p01
and noticed a 4-4ering is missing on the printed side

1 16 0 4 0 14 0 0 0 1 0 0 0 14 4-4ering.dat

(I'm not hunting them, I'm just rendering a lot of parts)

I have posted a test release for LDView 4.4 Beta 4 to GitHub:

https://github.com/tcobbs/ldview/release...v4.4_Beta4

This release mainly contains bug fixes since Beta 3, along with a few new features. The Mac version should work better on macOS Big Sur, and has an updated icon (as well as updated LDR and MPD icons on Big Sur).

One of the bug fixes with the most potential to introduce unexpected problems involves a change to the curve smoothing. It now does not try to smooth out two facets that are joined by both a conditional line and an edge line. This can happen (for example) when a curved primitive like a torus extends to the edge of a part. This happens on part 88293, which is the part that was included in the original bug report that caused me to fix the problem. I suspect that it happens in other parts also. I would greatly appreciate it if people would let me know if they see any regressions in LDView's curve smoothing.

Note: because of this new behavior, I expanded the angle over which curves can be smoothed. This improves (for example) the hair on the Bart Simpson minifig head, and probably improves other parts as well. However, it's possible that I went too far, and it will result in areas being smoothed that shouldn't be, so please be on the lookout for that as well.

The ChangeHistory.html file that is included in the release lists all of the changes since LDView 4.3. In the macOS version, ChangeHistory.html is in the dmg. In the Windows version, ChangeHistory.html gets installed to wherever you install LDView (C:\Program Files\LDView by default). I'm actually not sure where it goes in the Linux version. Please see my Alpha 6 announcement for a list of what I feel are the most important changes relative to LDView 4.3.

Please let me know about any problems you find. The preferred way to do that is with LDView's GitHub Issues tracker. However, if you do not want to create a GitHub account so that you can do that, you can reply to this message.

My hope is that this is the last beta release before an official LDView 4.4 release.

So, I finished a whole project in LDPatternCreator, and when I went to export it to DAT, it hung up and I had to kill the program. When I re-opened it and loaded my project, the work was still there…but somehow shrunk down by a factor of 1,000!

How can I fix it? And if I can, would anyone be willing to try exporting it and send me back the resulting DAT file? The LPC project is attached…

Attached Files

  kobmand.lpc (Size: 93.7 KB / Downloads: 5)

Hello,

I received the following error message while uploading files.

   

First point, I use the letter ä in my real name. There seem to be difficulties here, presumably because of the character coding. How can I change that? In the profile, I can only change my login and password. This letter should be replaced by ae.
Second point, what does the error message "File name is not used by an existing official file" mean. 

Greetings

Manfred

Some parts have a print only on the underside, which is not shown e.g. in the "Patterned Part Summary" or in the normal Activity overview.

It is difficult to judge which patterns are available.

These parts are:
11203 (Plate 2 x 2 Inverted with Groove)
2654b (Dish 2 x 2 without Rim)
3660b (Slope Brick 45  2 x  2 Inverted)

I cannot recall any others at the moment, for sure there are some more.

A proposal:
- We generate a list of such parts, e.g. the wildcard "11203p*"
- If the preview rendering comes across such a part it will be rotated 180 degrees
- A small icon will be added to indicate that this is the bottom up view.

here's an example:

  proposal.PNG (Size: 31.48 KB / Downloads: 25)

Gerald

Hello,

I want propose a change to the file structure of the part files. This proposed change only applies to the files in the parts folder, the files in the sub-folders, such as s, are not affected by this.
These files usually contain a line with the keyword !KEYWORDS and are used to store search terms, a reference to Bricklink or other databases and the number of sets in which this part was used.
I would include three lines of the !KEYWORDS keyword. The first line contains one or more search terms, the second line is followed by the word sets, separated by a space, followed by one or more numbers of the sets in which this part was used. The third line contains after the keyword, also separated by a space, the word reference followed by the name of the reference, e.g. B. Bricklink, followed by the name of the part.
Multiple entries in one line are separated by a comma. The entries sets or reference do not need to be entered again.
The first two of these lines could be optional, the third line would be mandatory. The reference would be to Bricklink or a similar database, Bricklink would be prefered. This line can contain the words unknown or missing instead of the reference. This would look like this:

0 !KEYWORDS Reference unknown
or
0 !KEYWORDS Reference missing.

Unknown is used when creating a new part and there is no reference yet, for example. Missing would be used when updating the existing files to this supplement if no reference is stored.
For the 3626c8f minifigure head, this change would look like this:

0 !KEYWORDS Robo Emmet, Spaceship
0 !KEYWORDS sets 70816
0 !KEYWORDS Reference Bricklink 3626cpb1113

The 3626bp08 minifigure head after the change would look like this:
0 !KEYWORDS Star Wars, Princess Leia
0 !KEYWORDS Reference missing

The reference is also required if it is an unprinted part, since the names or the number of the part are different in the various sources.
For example the battery box
Lego element: 6257768
Design number: 16511
LDraw part: 58119
Bricklink number: 59510c01
The reference to a database would therefore also be a criterion for the release of a new part.


Greetings

Manfred