Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 4,959
» Latest member: Doe
» Forum threads: 5,961
» Forum posts: 50,534

Full Statistics

Online Users
There are currently 498 online users.
» 0 Member(s) | 494 Guest(s)
Applebot, Baidu, Bing, Google

Latest Threads
Part request 5649 Brick, ...
Forum: Part Requests
Last Post: Jeff Jones
6 hours ago
» Replies: 2
» Views: 45
LDCad 1.7 Beta 1 (win+lin...
Forum: LDraw Editors and Viewers
Last Post: Quandore
10 hours ago
» Replies: 124
» Views: 62,188
Events on my submits does...
Forum: Help
Last Post: Quandore
11 hours ago
» Replies: 7
» Views: 388
New function in the Parts...
Forum: Parts Tracker Discussion
Last Post: Quandore
11 hours ago
» Replies: 5
» Views: 256
Duplo 65110
Forum: Parts Authoring
Last Post: Philippe Hurbain
2025-04-24, 17:30
» Replies: 1
» Views: 108
Technic 2025
Forum: Official Models
Last Post: Paweł Turalski
2025-04-24, 16:27
» Replies: 1
» Views: 166
Request for parts 67244, ...
Forum: Part Requests
Last Post: Philippe Hurbain
2025-04-24, 11:43
» Replies: 7
» Views: 950
Parts we are Working on -...
Forum: Part Requests
Last Post: Willy Tschager
2025-04-24, 6:15
» Replies: 152
» Views: 109,097
Official Part Fixes
Forum: Parts Tracker Discussion
Last Post: Orion Pobursky
2025-04-22, 20:20
» Replies: 0
» Views: 121
New Meta command PREVIEW
Forum: Parts Tracker Discussion
Last Post: Roland Melkert
2025-04-22, 20:10
» Replies: 9
» Views: 1,150

 
  a topic
Posted by: his shoes? WHACK - 2013-12-05, 22:20 - Forum: LDraw File Processing and Conversion - Replies (19)

WHACK

Print this item

  LDPatternCreator - (Second Bug-Fix) Release 1.5.2
Posted by: Nils Schmidt - 2013-12-05, 16:32 - Forum: Parts Author Tools - No Replies

Hello,

Here is my second LPC release from this day with less bugs Smile
If you are already using version 1.5.1 you can simply update your installation by clicking on "Help -> Install Updates" and choose "Yes".

Change log:

New features:

  • On a fresh installation colour 8 is replaced with colour 72 by default.
  • You can close the image- & view-preferences with F5/F6 when they got focused.
Fixed bugs from 1.5.1 and older:
  • Fixed the fact that template creation with helper lines fails.
  • Fixed minor translation errors
  • Fixed that "Show Colors" doesn't display the colors. The problem come from the new opacity setting since release 1.4.4

As always, I included a short readme.htm in the installation directory.


Cheers & Leg Godt


Nils

Print this item

  Tower Crane
Posted by: Kieran Metcalf - 2013-12-05, 13:12 - Forum: MOCs (My Own Creations) - Replies (5)

[Image: 11220809395]

Print this item

  LDPatternCreator - (Bug-Fix) Release 1.5.1
Posted by: Nils Schmidt - 2013-12-05, 5:35 - Forum: Parts Author Tools - Replies (5)

Good morning,

Here is a fresh LPC 1.5.1 release with more features and less bugs Wink

Change log:

New features:

  • The usability of the image, view-preferences and colour forms is improved.
  • SlicerPro is now used for slicing
  • You can update the program by clicking on "Help -> Install Updates". A internet connection is required to update the program.

Fixed bugs from 1.5.0 and older:
  • Fixed an error within the template editor (occurs on renaming).
  • Fixed several translation errors and improved the French translation (thanks J.C. Tchang!)
  • ...and a few other small bugs.

As always, I included a short readme.htm in the installation directory.


Cheers & Leg Godt


Nils

Print this item

  needing help fixing the remaining geometry problems of electric plugs
Posted by: Steffen - 2013-12-04, 18:09 - Forum: Parts Authoring - Replies (2)

Hi, I could need some helping thoughts, hands or calipers in solving the remaining geometry problems
I spotted with the electric plugs Sad

Please download the accompanying small demonstration file electric_plugs_geometry_problem.ldr
(which uses unofficial parts currently on the PT). It contains the simple assembly

1 7 0 0 0 1 0 0 0 1 0 0 0 1 4169.dat
1 2 0 -122 -1 0 0 -1 1 0 0 0 -1 0 512p01.dat
1 47 0 -122 23 1 0 0 0 0 1 0 -1 0 266bc02.dat
1 4 0 -102 10.5 1 0 0 0 0 1 0 -1 0 766ac01.dat
1 1 0 -94.5 18 1 0 0 0 1 0 0 0 1 766ac01.dat

This assembly is taken from set 7866, where it occurs in this form.

The following geometry problems can be seen here:
1. The central pin of the blue plug is smaller than the hole of the red plug where it should fit in.
2. The thickness of the red plug is so large that it collides with the green part: You can see the 2 parts intersecting each other.

I am not sure how to solve these problems.

Solving problem 1: this can be solved by either
(a) enlarging the pin of the blue plug
(b) reducing the size of the hole in the red plug
Solution (a) would require to touch ALL official parts having a hole for that pin, and that are MANY parts.
Solution (b) can easily be applied, as just the hole in this plug file needs to be adjusted.
So deciding between (a) and (b) is not only influenced by the real world diameter which can be measured,
but also by the amount of official parts that would need correction then.

Solving problem 2: this can be solved by either
(a) Making the plug a little thinner to remove the object intersection. In real life, it just snugly sits there touching the 512p01.
(b) Repositioning the plug sockets in the light brick 266bc02. Doing so will require adjusting all light bricks the same way (repositioning the plug sockets).
Remark: it could be that the plug sockets at the light brick really are misplaced in all official lightbricks.
This can be concluded from the fact that all have the same position for them, but just 266ac01 uses a different position.
Checkout the attached Electric.ldr.

I am a little lost and desperate here.
Folks, can you provide help or share thoughts?



Attached Files
.ldr   Electric.ldr (Size: 1.24 KB / Downloads: 0)
.ldr   electric_plugs_geometry_problem.ldr (Size: 309 bytes / Downloads: 0)
Print this item

  some thoughts about train track part origin choices
Posted by: Steffen - 2013-12-04, 9:03 - Forum: Parts Authoring - Replies (5)

At part
http://www.ldraw.org/cgi-bin/ptdetail.cg.../85977.dat
some questions arose about where to put the origin of train track parts.

The X and Z choice usually is not a problem, both for curved or straight parts:
we there can simply follow the principles of our usual practice, i.e. "part center".
This is also what existing parts do, e.g. 3229a.dat, 3229ac01.dat, 3229ac04.dat.

Regarding the Y origin, there is the question
"Should the origin be (A) at the top of the studded sleepers or (B) at the top of the rails?"
The current status in the library needs to be explained historically:
The rail parts e.g. 3229a.dat existed in the library long time already.
As usual for parts, they had their origin at the top.
This origin was kept when 3229ac01.dat was created, an assembly of two curved rails.
This origin was kept when 3228ac02.dat was created, an assembly of two straight rails.
This origin was kept when 3228bc02.dat was created, an assembly of two straight rails plus sleeper.
This origin was kept when 948ac02.dat was created, a point.
This is the 4.5V blue and grey rails story.
The same origin was applied to the analogous 12V blue and grey rails, e.g. 73696c04.dat.

So to make a long story short: carrying over the origin choice of the single rail part to the rails assemblies
led to the effect that the vertical origin of all 4.5V and 12V train track parts and assemblies is at the top of the rails.

The origin question now again arises for the 9V train track.
http://www.ldraw.org/cgi-bin/ptreviewsum...aintrack9v
(with or without metal top), and for other train tracks where the rails are firmly attached to the sleepers.
There the question is if the vertical origin should be
(A) at the top of the sleepers or
(B) at the top of the rails.
Both solutions have advantages and disadvantages:
Solution (A) would make the new train track parts better match plates.
Solution (A) would be the intuitive one if one did not know about existing train track parts.
Solution (B) would make the new train track parts better match existing train track parts.
Both solutions are no problem for train track layout software like BlueBrick.

So what to do now? Current situation:
- Official train track parts out in the wild have "origin at rail top".
- *SOME* of newer train track parts with "origin at sleeper top" already "sneaked" out, e.g. 32087.dat
- all newer train track parts currently on the PT like 74746.dat or 53401.dat or 85976.dat follow the "origin at sleeper top" strategy

I have no real strong opinion here. We could opt for one of these solutions:
(i) make all train track parts have origin at rail top
(ii) make all train track parts have origin at sleeper top
(iii) let some have it this way, others the other way

Solution (i) would require to re-position official file 32087.dat.
Solution (ii) would require to re-position many official 4.5V and 12V files
Solution (iii) would create inconsistency but would minimize current trouble

After having written this, I slightly tend to solution (iii)...

Print this item

  [disregard] L3P doesn't like a part
Posted by: Michael Horvath - 2013-12-02, 5:59 - Forum: LDraw File Processing and Conversion - Replies (1)

I get this error when I try to convert the attached model using L3P 1.4 beta.

Code:
W:\LDraw\datsville\svn\trunk\helper_scripts\povray>"C:\Programs Windows\l3p14bet
a\l3p.exe" "W:\LDraw\datsville\svn\trunk\datsville_boxed\datsville.ldr" -o -il -
ic
SKIPPING "D:\LDraw\ldconfig.ldr" Line 296: Illegal color code: 0 !COLOUR Main_Co
lour                                           CODE  16   VALUE #7F7F7F   EDGE #
333333
SKIPPING "D:\LDraw\ldconfig.ldr" Line 297: Illegal color code: 0 !COLOUR Edge_Co
lour                                           CODE  24   VALUE #7F7F7F   EDGE #
333333
Processing W:\LDraw\datsville\svn\trunk\datsville_boxed\datsville.ldr
Recursive references: b\3024.dat
referenced by b\3024.dat line 468
referenced by building_001_park.ldr line 65
referenced by building_001_jessimanmemorial.mpd line 8
referenced by block_001.ldr line 9
referenced by layer_blocks.ldr line 8
referenced by datsville.ldr line 6
L3P v1.4 BETA 20131119 (Win32)  (C) 1998-2013 Lars C. Hassing [email protected]
s.dk
*** Abnormal termination.

W:\LDraw\datsville\svn\trunk\helper_scripts\povray>pause
Press any key to continue . . .

I've attached the problem part as well. Is there something wrong with it? Thanks.



Attached Files
.mpd   building_001_jessimanmemorial.mpd (Size: 19.19 KB / Downloads: 1)
.dat   3024.dat (Size: 45 bytes / Downloads: 2)
Print this item

  Numbering error : Minifig Ski Pole
Posted by: Christoph Mierowski - 2013-11-30, 18:27 - Forum: Parts Authoring - Replies (3)

Right now the Minifig Ski Pole is found as 90514.dat. But at Bricklink and in LDD it has the number 90540.
I assume that LDD and Bricklink can not be both wrong- sometimes Bricklink has wrong numbers - But Bricklink and LDD at the same time with the same number - I doubt it. So this official part needs renumbering.

Bricklink

Print this item

  How to deal with overlapping parts
Posted by: Taylor Bangs - 2013-11-30, 18:24 - Forum: Parts Authoring - Replies (3)

I'm in the middle of addressing Philo's comment on the lastest version of one of my parts, dealing with overlapping primtives/quads

Right now, I'm a bit stumped on how to deal with the front and back without any major proportional reworkings, if at all



Attached Files
.dat   32577.dat (Size: 28.07 KB / Downloads: 0)
.dat   32577s01.dat (Size: 9.35 KB / Downloads: 0)
Print this item

Thumbs Up 4860 Plate 2 x 2 with Wheels Holder Plane
Posted by: Christoph Mierowski - 2013-11-30, 12:17 - Forum: Part Requests - Replies (3)

So this part is interesting:

4860 @ peeron

4860 @ bricklink

it also appear in the part library as 4860.dat as moveto 4870.
But these part are not the same:

4860 @ peeron

4870 @ bricklink


Or are they?!

At least at bricklink they look diffrent....
and peeron don't list a 4870 part.


PS: Maybe the part request section isn't the right place for this topic, but when they are two diffrent part this is a part request for the missing one.

Print this item