| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 4,107
» Latest member: Manu
» Forum threads: 5,543
» Forum posts: 47,634
Full Statistics
|
| Online Users |
There are currently 269 online users.
» 1 Member(s) | 263 Guest(s)
Applebot, Bing, Facebook, Google, Yandex, Martin James
|
| Latest Threads |
LDCad 1.7 Beta 1 (win+lin...
Forum: LDraw Editors and Viewers
Last Post: Roland Melkert
11 minutes ago
» Replies: 61
» Views: 12,463
|
Part Snapping missing/err...
Forum: LDraw Editors and Viewers
Last Post: Roland Melkert
1 hour ago
» Replies: 207
» Views: 106,860
|
Shadow file contributions
Forum: LDraw Editors and Viewers
Last Post: Roland Melkert
1 hour ago
» Replies: 14
» Views: 425
|
LEGO Dimensions
Forum: Official Models
Last Post: Evert-Jan Boer
2024-05-18, 19:16
» Replies: 57
» Views: 19,925
|
Model Team
Forum: Official Models
Last Post: Marc Giraudet
2024-05-18, 17:26
» Replies: 37
» Views: 27,515
|
Tiles 1 X 8 from latest A...
Forum: Part Requests
Last Post: N. W. Perry
2024-05-18, 2:39
» Replies: 65
» Views: 27,890
|
New meta in LDConfig for ...
Forum: Standards Board
Last Post: Roland Melkert
2024-05-17, 21:49
» Replies: 13
» Views: 679
|
Rabbit from WTP
Forum: Part Requests
Last Post: Ben Alder
2024-05-17, 17:39
» Replies: 3
» Views: 311
|
Axle Length vs Axle Stopp...
Forum: Parts Authoring
Last Post: Max Martin Richter
2024-05-16, 20:34
» Replies: 22
» Views: 3,592
|
new Aircraft parts: 5118,...
Forum: Part Requests
Last Post: Rene Rechthaler
2024-05-16, 16:45
» Replies: 9
» Views: 1,405
|
|
|
| Techniques and Tutorials |
|
Posted by: Stan Isachenko - 2011-08-22, 10:09 - Forum: Rendering Techniques
- Replies (14)
|
 |
This topic for Publishing here tutorials for Pov-Ray rendering.
Koyan Tutorial - This is old tutorial may be useful for people, who begin to teach pov-ray.
But there is few problems.
This tutorial is made for L3p 1,3 if you use 1,4 you have manually copy colors definitions from files.
Also we can here share lightprobes and other.
|
|
|
| Re: Generic (non library related) way of indicating the nature of a LDraw file |
|
Posted by: Tore Eriksson - 2011-08-19, 13:35 - Forum: Parts Authoring
- Replies (3)
|
|
Orion Pobursky Wrote:
-------------------------------------------------------
> Interesting. I'd go with 0 !FILE_TYPE. This may clear up a few issue but,
> as we saw with ldconfig.ldr, a new meta depends on support for the
> program authors.
The more I think of it, the better I like 0 !LDRAW.
For example:
0 !LDRAW Unofficial Moonbase Module Model
where "!LDRAW" and "Model" are mainly interesting for the programs, (but yet somewhat interesting for the human user)
and where "Unofficial Moonbase Module" is interesting for the user. (but could maybe also be of interest for a sorting/categorizing software???)
Why "0 !LDRAW"?
* It's good to have the information that it's a file in LDraw format, even for files that aren't directly affliated with ldraw.org. Or else, many private files without "0 LDRAW_ORG" will not even have LDraw mentioned anywhere.
* It's shorter than most of the other metas suggested. Keep in mind that this will probably be typed by hand by the user in most cases.
* !LDRAW_ORG is already used for similar information on file type and more. I believe a similar name for similar information could make sense.
/Tore
|
|
|
|
| Generic (non library related) way of indicating the nature of a LDraw file |
|
Posted by: Roland Melkert - 2011-08-18, 17:52 - Forum: Standards Board
- Replies (5)
|
 |
Hi all,
I kinda sparked a discussion about how to determine if a file is a part or not in
http://forums.ldraw.org/showthread.php?tid=503,503
Resulting of that I think there is a need for a way of indicating the goal of a document similar to the !LDRAW_ORG meta, but for private or 3rd party documents instead. This meta can then be used by software to do goal depended preparations.
Maybe something like:
0 !NATURE < model | part | shortcut | alias >
or
0 !HINT [ docNature=<model | part | shortcut | alias> ]
The second one is more advanced / generic and opens the door to adding more stuff in the future.
I know the first one has overlap with !LDRAW_ORG but like tore said in the above mentioned thread, it suggests 'ldraw.org owns this' which isn't very friendly if it's your own private creation.
It's also possible to get the information from keywords and or comment lines in the header, but that isn't fool proof parsing wise imho.
What do you think?
|
|
|
|
| Scott Wardlaw appointed as LDraw Colormaster |
|
Posted by: Willy Tschager - 2011-08-18, 14:36 - Forum: LDraw.org Announcements
- No Replies
|
 |
Hi folks,
in sync with "Section 6.08: Appointed Key Positions" of the LDraw Bylaws the LDraw Steering Committee has appointed Scott Wardlaw as LDraw Colormaster.
Scott has maintained the LDraw color file LDConfig.ldr since 2009 and will be from now on officially responsible for corrections and additions.
Congratulations!
Willy Tschager
On behalf of the LDraw SteerCo
|
|
|
|
| Datsville |
|
Posted by: Roland Melkert - 2011-08-14, 19:52 - Forum: MOCs (My Own Creations)
- Replies (87)
|
|
Hi all, I've been playing around with datsville.
But somehow I thought it was bigger, I'm using the version from datsville.googlecode.com.
Anyone has a newer / bigger version?
Also why is everything stuffed in a gigantic MPD (33000 lines!) Not very efficient for use in svn.
|
|
|
|
| OMR Spec - Updated 8/14 |
|
Posted by: Orion Pobursky - 2011-08-14, 7:17 - Forum: Parts Authoring
- Replies (12)
|
 |
Here's the latest draft. Discuss!! (Note: there is a quote bug that's removing the text between <>. Be aware of that and restore the text if needed)
--
The Offical Model Repository Specification
Version: 0.2 (will turn 1.0.0 upon ratification by the LSC)
Author: Orion Pobursky
Purpose:
--------
The Official Model Repository (OMR) is a database of file in the LDraw File Format describing models that are released as sets by Lego®. For consistency between models and ease of indexing by software, a standard for the file headers, names, and hierarchy in the OMR is needed. This document will outline the extra requirements (in addition to those set forth in the current LDraw File Format specification) for a model to be included in the OMR
Base Requirements:
------------------
All files in the model will conform to the current LDraw File Format
Base File Naming:
-----------------
Each model in the OMR will consist of several files that are packaged together into a single MPD file. For sets that include instructions for multiple models, each model will have its own MPD file. Each MPD for the set will be named in the following manner:
<Set Number>( <Optional Specifier> )-[main or alt<Number>]
Where:
<Set Number>: the number assigned on the container of the set
<Optional Specifier>: Sometimes different sets with the same number are released, the specifier will be a single digit number, in parentheses, that is different between different sets, to distinguish these sets from one another.
[main or alt<Number>]: The main model of the instructions (i.e. the model featured on the cover of the container) will have the word "main". For sets that feature more than one model on the front of the container (e.g. the Creator line), the largest or most prominent model is the main model. For alternate models that are detailed in instructions, the word "alt" and a single digit number starting at 1 will be used. For playsets or other sets where there are multiple models that are part of an integral whole, all of the submodels will be contained in the main model MPD.
Example:
Set 4896 - Roaring Roadsters. This creator set has 3 models in the instructions. The roadster is featured prominently on the box. 4896 is the only set with that number. Therefore:
Roadster MPD: 4896-main.mpd
Dragster MPD: 4896-alt1.mpd
etc...
MPD File Structure:
-------------------
The MPD will conform to the MPD File Specification.
The naming of the individual files in the MPD is up to the discretion of the author with the following guidance:
- A logical naming scheme is highly desired.
- Individual models in the set (e.g a vehicle or minifig) shall have their own separate file inside the MPD.
- Minifig file name should have the name of the character, if known
- The <MPD Filename> is required to be prepended to the file name of each individual file in the MPD
The only unofficial parts allowed to be referenced in the model files are those currently residing on the LDraw.org Parts Tracker. No part files shall be contained in the MPD.
File Headers:
-------------
Each individual model file in the MPD must have a standard header format.
Standard Header:
0 FILE <MPD Filename> - <Filename>.ldr
0 <MPD Filename> - <File Desciption>
0 Name: <MPD Filename> - <Filename>.ldr
0 Author: <Author Name>
0 !LDRAW_ORG Official Model Repository
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt
0 !THEME Theme name
0 !KEYWORDS words, more words,…,
0 !KEYWORDS words in second row, …, final words
0 !HISTORY YYYY-MM-DD [<Author Name>] Free text description of change. This can wrap to a
0 !HISTORY YYYY-MM-DD [<Author Name>e] second row with the same date if necessary. However authors should lean toward writing longer
0 !HISTORY YYYY-MM-DD [<Author Name>e] single !HISTORY lines(and not feel constrained to the historic 80-character limit on line length)
Where:
<MPD Filename>: The name of the containing MPD
<Filename>: The name of the file
<Author Name>: The name of the author. Real full name are highly desired but not required. If the full name is not provided, a first or last name, with or with out initials, is requested.
Optional commands are !THEME, !KEYWORDS, and !HISTORY
META commands:
--------------
The only META commands allowed in the model file are those associated with the header, 0 FILE (for MPD support) and 0 STEP. STEP commands not specifically required but they are highly desired. If included, the step commands should follow the instructions as closely as possible.
|
|
|
|
|
