Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 5,326
» Latest member: Raina
» Forum threads: 6,186
» Forum posts: 51,831
Full Statistics
|
Online Users |
There are currently 260 online users. » 4 Member(s) | 251 Guest(s) Applebot, Baidu, Bing, Google, Yandex, Max Murtazin, Philippe Hurbain
|
|
|
Call for Votes: Sticker spec clarifications 2 |
Posted by: Travis Cobbs - 2021-08-10, 1:50 - Forum: Standards Board
- Replies (4)
|
 |
Please vote on adding the following clarifications to the LDraw.org Official Parts Library Specifications. The quoted text would be added verbatim.
Clarification to Sticker Geometry:
Quote:For stickers printed on a transparent medium, the type 1, 3, and 4 lines that comprise the pattern shall be preceded by a 0 BFC NOCLIP statement. If there is non-pattern geometry after the pattern geometry, the pattern geometry shall be ended by a 0 BFC CLIP statement.
The sticker should be oriented such that the top of the pattern aligns with the +Z axis. Exceptions to this rule may be made on a case by case basis.
New Sticker !KEYWORDS Entry section immediately following the Sticker Description section:
Quote:All stickers and sticker shortcuts should, at a minimum, include at least one !KEYWORDS entry in the form of Set <set number> where <set number> is the number of an official LEGO set in which that sticker appears. Only one set need be listed, but more may be if desired.
|
|
|
!DATA specification too hard to find |
Posted by: Travis Cobbs - 2021-08-04, 17:26 - Forum: Website Suggestions/Requests/Discussion
- Replies (1)
|
 |
Since !DATA was added to the MPD spec, it turns out to be quite hard to track down. If you look at the Documentation page, it isn't mentioned, so unless you know in advance that it is in the MPD spec, it's hidden. (And since "data" is so generic, a Google search for LDraw data doesn't even include the MPD spec on the first page of results.)
I would suggest adding a parenthetical to the MPD link indicating that !DATA is included there.
|
|
|
Improve parts with artefacts/ slowly rendering |
Posted by: Johannes Ahlmann - 2021-08-03, 21:52 - Forum: General LDraw.org Discussion
- Replies (5)
|
 |
Hi,
I am rendering Lego parts using Blender and https://github.com/TobyLobster/ImportLDraw (using "p" "48" ldraw geometries).
Some of the very basic and simple parts take forever to render, and other parts contain artefacts.
Is there a good place to raise a list of parts that are unnecessarily complex or that display render artefacts?
Examples of parts that render extremely slowly (20x slower than complex parts), some of which are the most basic bricks and plates.
2419
2445
2454a
2456
2730
3001
3006
3007
3020
3027
3030
3031
3032
3034
3035
3036
32525
3297
3702
3738
3832
3857
3865
3867
3895
3958
4204
4510
60479
6111
6112
6179
91405
92438
Examples of bricks with artefacts: - many domed bricks
- some bricks that have clearly been assembled from subparts with noticeable gaps/ discontinuities
Regards,
Johannes
|
|
|
Part Connectivity |
Posted by: Miguel Reizinho - 2021-08-01, 19:06 - Forum: LDraw Editors and Viewers
- Replies (5)
|
 |
Just wondering... I have some custom part files and I have added connectivity and conflict information in Stud.io by using part designer. Is there any way I could import that connectivity of these custom parts but in LDCad?
Any help would be appreciated.
|
|
|
Parts Tracker - Complete Part Download Option |
Posted by: Gerald Lasser - 2021-07-27, 9:09 - Forum: Website Suggestions/Requests/Discussion
- Replies (7)
|
 |
This is kind of a usability feature for people getting unofficial parts from the PT.
Right now the way to do this is: - Either a download of the entire unofficial lib
- slow
- huge
- manual transfer to Stud.io+ no need to worry about forgotten subfiles or prims
- Or manually download them one by one and the necessary subfile
- subfile/new prim might get overlooked
- tedious to go through all the required files
- manual transfer to Stud.io
+ small in size/bandwidth
- Use the LDView update feature
+ small in bandwidth+ quick- manual transfer to Stud.io
Now if you want to import new parts into Stud.io you need to extract them from the various download locations (either the unofficial files or the download folder of your PC and need to remember where to put the file accordingly)
That's why it might bw worth considering this proposal:
If a file still has dependencies on unofficial sub-parts or prims, add a Button which allows you to download "all required files"
The download will consist of a ZIP file with the correct structure inside (p/, Parts/ parts/s/, etc.) so that you can simply unpack it into the custom parts folder of Studio.
What's your opinion?
|
|
|
|