Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 4,438
» Latest member: lego
» Forum threads: 5,673
» Forum posts: 48,474
Full Statistics
|
Online Users |
There are currently 301 online users. » 1 Member(s) | 296 Guest(s) Applebot, Bing, Google, Yandex, 3CFigs
|
|
|
box3-7a.dat |
Posted by: Ronald Vallenduuk - 2013-09-07, 8:53 - Forum: Parts Authoring
- Replies (2)
|
|
Hi all,
Been away for a while but have started on another part. In the primitive reference for box3-7a.dat it says "... and 1LDu in the {y} dimension". However the box is 2LDU tall (as you can see in the image). It's already being used in official parts so it may be a little late to change the part but the description in the primitive page should be changed.
It made me wonder though. Why are most cuboid primitives 2x1x2 while some (like the box3- ones) are 2x2x2?
Ronald
|
|
|
custom LDConfig.ldr |
Posted by: Santeri Piippo - 2013-09-06, 17:39 - Forum: MOCs (My Own Creations)
- Replies (2)
|
|
Not sure where else to post this but I've been using an edited LDConfig.ldr for a good while now and figured to share it. I altered it to have colors more closer to what I percieve as the real colors of the parts (the black for instance felt way too blue to me). Also the bricks have black edges, aside from the pearlescent and some bright colors. Also I removed the LEGOID stuff because it made it quite unreadable IMO and Peeron-esque names since they're nice and short.
Yeah I meant this for personal usage but I figured to share it.
from left to right: black, blue, green, teal, red, pink (..?), brown,
gray, dark gray, yellow, white, tan, lime, dark tan (or sand as I call it),
pearlescent gray, pearlescent gold
Link here: https://dl.dropboxusercontent.com/u/6605...Config.ldr
|
|
|
Problems with Windows 8 |
Posted by: warwick holden - 2013-08-31, 18:38 - Forum: Help
- Replies (16)
|
|
Hi! I have tried searching the forums for this problem, but without success! If I've missed a post - I apologise. I tried to install L Draw All-in-One installer onto a laptop running Windows 8. The laptop is a Sony Vaio with Win 8 Professional 64 bit installed. The install went OK, but towards the end of the install there were a number of error messages along the lines of "Can't find file". At the end the final install a message said that Pov-Ray had failed to install. The main programs were installed in the 'Program (x86)' folder. Should I have installed elsewhere?? Such as direct onto the C drive?? Any help appreciated. By the way - all other programs worked fine!
|
|
|
Clips and Minifig Radio |
Posted by: Roland Melkert - 2013-08-31, 16:23 - Forum: Parts Authoring
- Replies (1)
|
|
I was playing around and noticed that the Minifig Radio parts (e.g. 3962a) don't fit onto clips (or minifig hands).
Also the 61252 clip seems to have a bfc problem.
Just reporting in hopes somebody picks this up.
|
|
|
Aligning Categories to user expectations |
Posted by: Allen Smith - 2013-08-28, 21:34 - Forum: Parts Authoring
- Replies (25)
|
|
Someone just posted the following to a local LUG mailing list I'm subscribed to (emphasis added):
Quote:Thinking about it, I can remember what derailed my learning LDraw/Mcad/ et al... it was the parts management system… [T]he hundreds of variations with a surface graphic made the whole stack completely unmanageable.
While I don't know the author, I really have to agree with the sentiment. Regular bread-and-butter categories one uses all the time for building are clogged with enormous numbers of decorated parts which are almost never used. Over the years, the single most-requested feature for Bricksmith was to add a "Favorite" category, and I can't help bust suspect this was part of the reason.
A couple years ago when I was adding !CATEGORY support to Bricksmith, I came to the conclusion the situation was actually getting worse. Notably, Duplo elements were being piled into the regular categories like "Brick". The !CATEGORY keyword was also inconsistently applied, so some bricks fell into defined categories, and some fell into implicit categories based on the first word of their description. Some logical first-word categories were being exterminated for inexplicable reasons, but only in a piecemeal fashion. Since it was all inconsistent, it was insanely difficult to find anything. I actually gave up and intentionally ignored !CATEGORY for any single-word category name.
I would like to take a cue from Bricklink here. Separate decorated elements out of the most commonly-used categories of Brick, Tile, and Slope. I think this would be a huge win for regular users.
I would also like to see !CATEGORY be dependable. When I last checked in on the situation (at least a year ago), every Categorization was potentially subject to a review squabble (and endless limbo) on the part tracker. That was the point at which I gave up on implementing the feature and went back to using the description for almost everything.
|
|
|
|