Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 5,005
» Latest member: DirkVDB
» Forum threads: 6,000
» Forum posts: 50,747
Full Statistics
|
Online Users |
There are currently 381 online users. » 0 Member(s) | 376 Guest(s) Applebot, Baidu, Bing, Google, Yandex
|
Latest Threads |
71613/30346c01 too high?!
Forum: Part Requests
Last Post: Gerald Lasser
4 hours ago
» Replies: 1
» Views: 60
|
Viking Creature Heads
Forum: Part Requests
Last Post: Jeff Jones
7 hours ago
» Replies: 7
» Views: 3,118
|
Technic 2025
Forum: Official Models
Last Post: Paweł Turalski
8 hours ago
» Replies: 3
» Views: 2,540
|
Technic 2024
Forum: Official Models
Last Post: Vito Tarantini
8 hours ago
» Replies: 53
» Views: 39,882
|
57792 needs a fix
Forum: Part Requests
Last Post: Sylvain Sauvage
9 hours ago
» Replies: 4
» Views: 98
|
bionicle cordak blaster
Forum: Part Requests
Last Post: Jeff Jones
Yesterday, 13:38
» Replies: 0
» Views: 46
|
File Format for the Studi...
Forum: Off-Topic
Last Post: j2152662
Yesterday, 7:56
» Replies: 5
» Views: 1,964
|
Friends Animal Series
Forum: Official Models
Last Post: Takeshi Takahashi
2025-05-15, 17:57
» Replies: 22
» Views: 5,924
|
File paths in various pro...
Forum: LDraw Editors and Viewers
Last Post: Roland Melkert
2025-05-15, 17:17
» Replies: 5
» Views: 300
|
2025 - New Parts -> Raw M...
Forum: Part Requests
Last Post: Gerald Lasser
2025-05-15, 12:02
» Replies: 3
» Views: 879
|
|
|
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
|
|
|
Forum search engine underpowered? |
Posted by: Philippe Hurbain - 2017-02-02, 14:02 - Forum: Website Suggestions/Requests/Discussion
- Replies (3)
|
 |
I was trying to find again this post, so I keyed in "ldcad tread long" in the search field that returned nothing (though all these words ARE in the post). Of course I didn't remember the exact words used so I tried many variants, without any success. Finally I called Google to the rescue, and "ldcad tread long site:ldraw.org" cheerfully gave me the right post (I tried variants there too and many of them gave the right answer despite the exact words were not in the post...)
Ideas to improve?
|
|
|
|