| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 6,224
» Latest member: Longin
» Forum threads: 6,579
» Forum posts: 54,205
Full Statistics
|
| Online Users |
There are currently 20 online users. » 0 Member(s) | 16 Guest(s) Applebot, Baidu, Bing, Google
|
| Latest Threads |
Spider-Ham
Forum: Part Requests
Last Post: James Simpson
6 hours ago
» Replies: 1
» Views: 366
|
Missing Snowtrooper Parts
Forum: Part Requests
Last Post: Chirila
10 hours ago
» Replies: 3
» Views: 147
|
Town, Trains and Paradisa...
Forum: Official Models
Last Post: Chris Böhnke
2026-09-14, 22:01
» Replies: 26
» Views: 13,408
|
Existing Part Edit Reques...
Forum: Parts Authoring
Last Post: Rene Rechthaler
2026-09-13, 14:38
» Replies: 170
» Views: 451,591
|
We have a problem, again
Forum: Parts Authoring
Last Post: Rene Rechthaler
2026-09-13, 12:20
» Replies: 7
» Views: 9,045
|
Missing Stingrays/Hydrona...
Forum: Part Requests
Last Post: Chris Böhnke
2026-09-13, 7:21
» Replies: 6
» Views: 1,287
|
Lego Instructions app par...
Forum: Parts Authoring
Last Post: Gerald Lasser
2026-09-11, 22:53
» Replies: 1
» Views: 380
|
Missing Alpha Team (2001-...
Forum: Part Requests
Last Post: Zack Uhlenhuth
2026-09-10, 17:41
» Replies: 0
» Views: 226
|
Missing Knight's Kingdom ...
Forum: Part Requests
Last Post: Zack Uhlenhuth
2026-09-10, 17:12
» Replies: 0
» Views: 203
|
[Complete] Missing Robofo...
Forum: Part Requests
Last Post: Chris Böhnke
2026-09-10, 1:42
» Replies: 7
» Views: 1,659
|
|
|
| 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
|
|
|
|