| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,964
» Latest member: Eli Godoy
» Forum threads: 6,526
» Forum posts: 53,880
Full Statistics
|
| Online Users |
There are currently 166 online users.
» 1 Member(s) | 159 Guest(s)
Applebot, Baidu, Bing, DuckDuckGo, Google, Yandex
|
| Latest Threads |
Adding Minifig Categories
Forum: Official File Specifications/Standards
Last Post: Orion Pobursky
3 hours ago
» Replies: 18
» Views: 1,699
|
Parts Request: Ninjago Dr...
Forum: Part Requests
Last Post: Cobra
6 hours ago
» Replies: 11
» Views: 3,168
|
Parts Request: Ninjago Dr...
Forum: Part Requests
Last Post: Gerald Lasser
10 hours ago
» Replies: 1
» Views: 59
|
Update your email
Forum: Parts Tracker Discussion
Last Post: Orion Pobursky
Yesterday, 20:00
» Replies: 8
» Views: 329
|
Part Request: 42029 - Dup...
Forum: Part Requests
Last Post: arron
Yesterday, 3:09
» Replies: 2
» Views: 163
|
LDraw.org 2026-06 Parts U...
Forum: LDraw.org Announcements
Last Post: Orion Pobursky
2026-06-28, 2:49
» Replies: 0
» Views: 393
|
Husky 16606pb001
Forum: Part Requests
Last Post: Sylvain Sauvage
2026-06-27, 21:15
» Replies: 4
» Views: 3,465
|
Wheels needed for Set 772...
Forum: Part Requests
Last Post: Alfred Schmitz
2026-06-25, 12:02
» Replies: 11
» Views: 3,316
|
47430
Forum: Parts Authoring
Last Post: Jeff Jones
2026-06-23, 15:13
» Replies: 1
» Views: 832
|
Part request: Antimatter'...
Forum: Part Requests
Last Post: Liam Moore
2026-06-23, 2:10
» Replies: 0
» Views: 291
|
|
|
| Patterned part numbering |
|
Posted by: Merlijn Wissink - 2017-02-08, 7:52 - Forum: Parts Authoring
- Replies (1)
|
 |
LDraw has a (in my opinion kinda weird) standard for patterned part numbering. However, sites like Rebrickable and Brickset nowadays scrape a lot of information from Lego itself. This information also includes the design id for patterned parts. Like every brick, every pattern has its own unique design-id.
For example, this part has the design-id 25660 and this part has the design-id 32734.
Would it be a good idea to change the patterned-part numbering of LDraw parts (for future parts obviously, not for current parts) to use the design-id when available?
|
|
|
| [Bug] LPub3D & POV-Ray for rendering with a space in the directory path |
|
Posted by: David Manley - 2017-02-03, 6:13 - Forum: LDraw File Processing and Conversion
- Replies (2)
|
 |
Trevor,
I've identified what I believe is a bug when using POV-Ray for rendering images in LPub3D. When the directory path to the LDraw file does not contain any spaces, POV-Ray is invoked successfully and the appropriate images rendered. An example of the command line generated by LPub3D to invoke POV-Ray (from the POV-Ray log) is:
Code: Preset INI file is 'D:\USERS\VISTA\DJM\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI', section is '[800x600, AA 0.3]'.
Rendering using command line '+ID:\users\djm\personal\2017\LEGO\BUILDI~1\DACHSH~1\LPub3D\tmp\PLILDR~1.POV
+OD:\users\djm\personal\2017\LEGO\building_instructions\dachshund\LPub3D\parts\4589_128_1753_150_DPCM_1_23_-45.png +W1753 +H1240 +UA +LD:\PROGRA~1\LDraw\LGEO\lg
+LD:\PROGRA~1\LDraw\LGEO\ar +A'.
Rendering with 2 threads.
Persistence of Vision(tm) Ray Tracer Version 3.7.0.msvc10
This is an official version prepared by the POV-Ray Team. See the
documentation on how to contact the authors or visit us on the
internet at http://www.povray.org/
However, when the directory path contains a space, POV-Ray generates an error (from the POV-Ray log);
Code: Preset INI file is 'D:\USERS\VISTA\DJM\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI', section is '[800x600, AA 0.3]'.
Rendering using command line '+ID:\users\djm\personal\2017\LEGO\BUILDI~1\DACHSH~1\LPub3D\tmp\CSILDR~1.POV "+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png" +W1753 +H1240 +UA +LD:\PROGRA~1\LDraw\LGEO\lg
+LD:\PROGRA~1\LDraw\LGEO\ar +A'.
Persistence of Vision(tm) Ray Tracer Version 3.7.0.msvc10
This is an official version prepared by the POV-Ray Team. See the
documentation on how to contact the authors or visit us on the
internet at http://www.povray.org/
<snip>
</snip>
Could not find file '+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png.ini'
-
Cannot open INI file '+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png'.
-
Cannot process command-line at ' +W1753 +H1240 +UA +LD:\PROGRA~1\LDraw\LGEO\lg +LD:\PROGRA~1\LDraw\LGEO\ar +A' due to a parse error.
This is not a valid command-line. Check the command-line for syntax errors, correct them, and try again.
Valid command-line switches are explained in detail in the reference part of the documentation.
Failed to start render: Failed to parse command-line option
Note the difference between the respective +O command line argument quoting. The first (without spaces)
Code: +OD:\users\djm\personal\2017\LEGO\building_instructions\dachshund\LPub3D\parts\4589_128_1753_150_DPCM_1_23_-45.png
compared to the second )with spaces);
Code: "+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png"
I believe the issues may be the double quotes around the entire +O parameter values, causing POV-Ray not to see the +O as intended.
Regards,
David
|
|
|
|
|
