Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
Transparent sticker colou...
Forum: General LDraw.org Discussion
Last Post: Magnus Forsberg
1 hour ago
» Replies: 3
» Views: 395
|
The Emperor Zurg
Forum: Part Requests
Last Post: Julian Raymond Ruan
5 hours ago
» Replies: 0
» Views: 107
|
Parts request
Forum: Part Requests
Last Post: Peter Grass
9 hours ago
» Replies: 1
» Views: 241
|
Batman Cowls
Forum: Part Requests
Last Post: Peter Grass
Today, 1:13
» Replies: 1
» Views: 277
|
A fresh list of "most com...
Forum: Part Requests
Last Post: tom alphin
Today, 0:11
» Replies: 7
» Views: 744
|
Fix for slightly incorrec...
Forum: Part Requests
Last Post: Huib Versteeg
Yesterday, 9:50
» Replies: 4
» Views: 909
|
Lego Town Racer 1996 - 63...
Forum: Official Models
Last Post: Chris Böhnke
2025-09-13, 23:39
» Replies: 14
» Views: 2,192
|
Eyesight on Linux
Forum: Rendering Techniques
Last Post: Orion Pobursky
2025-09-13, 18:56
» Replies: 12
» Views: 8,849
|
Another common varient: 1...
Forum: Part Requests
Last Post: Rene Rechthaler
2025-09-12, 14:51
» Replies: 8
» Views: 5,659
|
1Lx1Lx2L brick with studs...
Forum: Parts Authoring
Last Post: SNIPE
2025-09-12, 10:14
» Replies: 0
» Views: 841
|
|
|
LDForge |
Posted by: Santeri Piippo - 2014-09-07, 1:37 - Forum: Parts Author Tools
- Replies (27)
|
 |
After over 1 year of development, a beta build of LDForge 0.3 is out with massive changes and improvements. Release highlights: - multi-document support
- various optimizations that make LDForge a LOT faster than before
- able to download parts off the PT if desired
- circle tool with ring finder algorithm makes adding rings to parts mostly trivial, can also be used for edge circles and discs
- magic wand tool for easier group selection
- support for logoed studs
- support for direct colors
- auto-subfiler! just select and fire!
- various little new features, improvements and bug fixes
Note that this is beta-quality software and has not yet recieved complete exhaustive testing (i.e. I gotta get that kolhii stick done). This means, don't use in production work lest you risk a crash eating your work! I decided to post this after I managed to finally squish the nasty showstopper bugs. I'm thinking about just making the release 1.0 at this point.
|
|
|
LPUB - how to change assembly scale in a submodel |
Posted by: Jetro de Château - 2014-09-06, 20:43 - Forum: LDraw File Processing and Conversion
- Replies (2)
|
 |
I'm trying to get to grips with LPUB. Specifically I'm trying to show separate subfiles in an MPD file to show a bigger assembly size than the main (complete) model. So far I have found the metacommand for assembly size is 0 !LPUB ASSEM MODEL_SCALE GLOBAL 1.0000 (=100%), but I have not found a way to make local changes for a single step or for subassemblies.
I have looked for a complete list of metacommands for LPUB, but the best I've come up with is this
https://sites.google.com/site/workingwit...tacommands
and that still looks incomplete - the precise metacommand I found in my LPUB file for assembly size includes the word GLOBAL, which makes me suspect there might be a LOCAL version too. (I've tried "LOCAL" and it didn't work for me)
Can anyone point me in the right direction?
|
|
|
Cheese slopes |
Posted by: Stephen - 2014-09-04, 10:39 - Forum: Parts Authoring
- Replies (2)
|
 |
http://peeron.com/inv/parts/54200
Peeron Title:"Slope Brick 31 1 x 1 x 2/3"
LDraw Title:"Slope Brick 31 1 x 1 x 0.667"
http://peeron.com/inv/parts/85984
Peeron Title:"Slope Brick 33 1 x 2 x 2/3"
LDraw Title:"Slope Brick 31 1 x 2 x 0.667"
Both above .dat files internally use a slope gradient of 12/20 which is 30.96°, close enough to 31°.
I can't find a photograph of these two aligned together, so can anyone confirm that they are both using the exact same slope angle and that LDraw is correct and the Peeron title is wrong?
|
|
|
Minifig/Figure accessory category |
Posted by: Philippe Hurbain - 2014-09-04, 7:43 - Forum: Parts Authoring
- Replies (11)
|
 |
Moving here a discussion started on PT
Steffen, reviewing 96484.dat Wrote:I think this should be renamed to become a normal minifig accessory.
In fact, there is no real difference between a minifig or friends or fabuland accessory.
Maybe we should rename the whole category from "minifig accessory" to
"figure accessory"........? Steffen, reviewing 96482.dat Wrote:I don't see the necessity for the "Friends" theme in the title.
Isn't this simply a normal minifig accessory?
Arent't all accessories theme-inspecific?
this hairdryer could be used by a Friends figure, a Fabuland figure
or a minifig figure. Thus maybe we should rename the whole
category "Minifig Accessory" to "Figure Accessory".........? Arezey Wrote:If we need to rename Minifig Accessory for generalization, I suggest just dropping the 'Minifig' and rename the category to Accessory. Steffen, I can see your point, and I agree with Arezey to simplify even further to "Accessory". But I would like to keep original theme in the file (as keyword) but that would make the re-categorization of existing official parts much mode difficult I guess...
I have a related concern with flower shaped accessories, such as parts 96483 and 95832. I initially categorized them as "plant", which makes some sense with 95832 (though it's an acessory, the small hole is compatible with 3741/99249 stems), but it's less clear for 96483 that only has a small pin... Opinions?
|
|
|
Physical colour shortcuts |
Posted by: Magnus Forsberg - 2014-09-03, 16:17 - Forum: Parts Authoring
- Replies (5)
|
 |
Is it correct that DATHeader should warn me when I scan a "Unofficial_Shortcut Physical_Colour"?
It tells me that:
"ERROR Description for Physical_Colour parts should mention the used colors", but I'm not scanning a "part".
I'm scanning a "shortcut".
The header specification says:
Physical_Colour
The purpose of the Physical_Colour qualifier is to identify a part which is encoded as a specific colour of a part (e.g. 70770)
A part file with the Physical_Colour qualifier will typically, but not necessarily, contain only one sub-file reference (line type 1) entry, where the entry has a specific colour value and not colour 16.
It says nothing about the Shortcuts
|
|
|
|