Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 1,862
» Latest member: Aureliusz
» Forum threads: 3,396
» Forum posts: 28,788

Full Statistics

Online Users
There are currently 36 online users.
» 1 Member(s) | 31 Guest(s)
Baidu, Bing, Google, Yandex

Latest Threads
James Jessiman Memorial A...
Forum: LDraw.org Announcements
Last Post: Michael Heidemann
8 hours ago
» Replies: 5
» Views: 198
Modular Buildings
Forum: Official Models
Last Post: Johann Eisner
8 hours ago
» Replies: 11
» Views: 3,349
Ldcad new Shadows object...
Forum: LDraw Editors and Viewers
Last Post: tatubias
Yesterday, 14:18
» Replies: 2
» Views: 108
LEGO 2 LDraw 2 BL
Forum: Official File Specifications/Standards
Last Post: Jaco van der Molen
Yesterday, 6:33
» Replies: 24
» Views: 862
Technic 1999
Forum: Official Models
Last Post: Orion Pobursky
Yesterday, 3:54
» Replies: 6
» Views: 251
Ldcad part alignment
Forum: LDraw Editors and Viewers
Last Post: Roland Melkert
2019-04-23, 19:01
» Replies: 20
» Views: 351
Speed Champions wheel ins...
Forum: Part Requests
Last Post: Magnus Forsberg
2019-04-21, 8:04
» Replies: 9
» Views: 357
Call for LDCad 1.6 bug re...
Forum: LDraw Editors and Viewers
Last Post: Roland Melkert
2019-04-20, 21:51
» Replies: 18
» Views: 12,816
Windows installation prob...
Forum: Help
Last Post: Dani
2019-04-20, 20:44
» Replies: 2
» Views: 128
Jedi Fighters (75214 / 07...
Forum: MOCs (My Own Creations)
Last Post: Franklin W. Cain
2019-04-20, 20:22
» Replies: 0
» Views: 88

 
  Get Started link leads to old AIOI
Posted by: Don Heyse - 2011-08-25, 16:39 - Forum: Website Suggestions/Requests/Discussion - Replies (1)

The Get Started link on the left side of the ldraw.org website leads to a page that sends you to the old All In One Installer for Windows.

Print this item

  OMR Spec - Updated 8/25
Posted by: Orion Pobursky - 2011-08-25, 10:41 - Forum: Parts Authoring - Replies (9)

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.4 (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> - <Set Name> - <Sub Model Name>

Where:
<Set Number>: the number assigned on the container of the set
<Set Name>: The name of the set printed on the container in Australian English
<Sub Model Name>: This is Optional in most cases. This is required for alternate models that are detailed in instructions (e.g. the Creator theme). In this case the naming is left to the discretion of the author but should be descriptive of the model contained in the MPD.

Example:
The creator set 4896 - Roaring Roadsters has 3 models in the instructions:
Set 4896 - Roaring Roadsters - Roadster.mpd
Set 4896 - Roaring Roadsters - Dragster.mpd
etc...

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 one MPD.

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 pre-pended to the file name of each individual file in the MPD

The unofficial parts are allowed to be used. The filename of the unofficial part is subject to the naming rules above (e.g. 33056.dat would be renamed to <MPD Filename> - 33956.dat). It is highly encouraged that any parts created for use in a OMR file be submitted to the LDraw.org Parts Tracker.

If a part is unavailable either officially or on the LDraw.org Parts Tracker, a suitable substitution may be made. If the unavailable part is a patterned part with an unpatterned version available use the unpatterned version. A comment should be inserted stating that a substitution has been made or, if no substitution is available/suitable, that a piece has been omitted. Reference the step and page number of the instructions if possible.

Example:
0 // The next piece should have the Star Wars Hatch pattern per step X on page Y
or
0 // Bionicle piece X should go here per step Y on page Z

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 Description>
0 Name: <MPD Filename> - <Filename>.ldr
0 Author: <Author Name>
0 !LDRAW_ORG Official Model Repository
0 !LICENSE Redistributable under CCAL version 3.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

Example:
To Be Inserted Later

META commands:
--------------
All META commands are allowed in the model file but not specifically required except as specified for the header. If included, any META commands used should enable any instructions generated to be as close to the official instructions as possible.

Print this item

  All-In-One-Installer and parts paths
Posted by: Don Heyse - 2011-08-23, 21:24 - Forum: All Other Programs. - Replies (2)

So, this lpub/lsynth parts path issue made me realize I have Windows 7 now and can test the All In One Installer. So I did.

I picked everything but POV. That made it search in vain for some POV ini files to make lgeo happy, or something like that. Probably should give a warning that LGEO isn't much use without POV, but whatever.

Anyhow, I noticed the installer added registry entries for LDView and MLCad so they could find the official parts, and there was even a path to the lsynth parts for LDView in the registry. However the ldglite install was useless out of the box because the installer didn't create an ldraw.ini file in the Windows directory. Just to be sure, I made one like this and it worked.

C:\Windows>type ldraw.ini
[LDraw]
BaseDirectory="C:\Program Files\LDraw"

Would it be possible to add this to the installer?

Or would it be better to update ldglite to use the LDView registry entries to find the parts? (especially considering Microsoft has made it more difficult create an ldraw.ini file in the Windows directory in in recent versions of Windows)

By the way, does LDView use the generic ldrawini code, an enhanced version, or something else?

Don

Print this item

  Lsynth flexible elements not displayed in Lpub...
Posted by: Fabrice Vion - 2011-08-23, 13:55 - Forum: LDraw File Processing and Conversion - Replies (25)

I'm using mlcad and lsynth to produce a model including flexible elements (hoses ans wires).

But when I open the .ldr file in Lpub 4, the flexible parts are not visible.

Are there some parameters to set ? or file to instal ?


Thanks in advance for your help,
Fabrice

Print this item

  autogenerating a LEGO model possible?
Posted by: Thit Sonne - 2011-08-23, 13:40 - Forum: All Other Programs. - Replies (2)

by Thit Sonne

Hi,

Is it possible to autogenerate a Legomodel from a non-Lego drawing?
For instance draw up a CAD model, and autogenerate a Lego model, with suggested bricks?

Might be a stupid question, and the wrong thread to post in, but I am eager to know ;-)

Best regards Thit Sonne

Print this item

  Minifigs Patterns
Posted by: Stan Isachenko - 2011-08-22, 20:33 - Forum: Parts Authoring - Replies (86)

Hello. I'm trying to create minifig patterns. I can draw them in Adobe Illustrator. And have some questions.
1) Where I can get proportions of the minifig body?(I pick them from picture in hollywood tutorial, but not very exactly)
2) Is here people, who interested in it?
I don't have enough time to clean them to Ldraw library standarts, but as pattern for later work can. Thank.

Print this item

  OMR Spec - Updated 8/22
Posted by: Orion Pobursky - 2011-08-22, 12:51 - Forum: Parts Authoring - Replies (15)

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.3 (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 wis up to the discretion of the author with the following guidance:
- A logical nameing scheme is highly desired.
- Individual models in the set (e.g a vehicle or minifig) shall have thier own separate file inside the MPD.
- Minifig file name should have the name of the character, if known
- The <MPD Filename> is reqired to be prepended to the file name of each indiviual file in the MPD

The unofficial parts are allowed to be used. The filename of the unoffical part is subject to the naming rulles above (e.g. 33056.dat would be renamed to <MPD Filename> - 33956.dat). It is highly encouraged that any parts created for use in a OMR file be submitted to the LDraw.org Parts Tracker.

If a part is unavailable both officially or on the LDraw.org Parts Tracker. a suitible substitution may be made. If the unavailable part is a patterned part with an unpatterned version available use the unpatterned version. A comment should be inserted stating that a subtitution has been made or, if no substitution is available/suitable, that a piece has been omitted. Reference the step and page number of the instructions if possible.

Example:
0 // The next peice should have the Star Wars Hatch pattern per step X on page Y
or
0 // Bionicle piece X should ge here per step Y on page Z

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 3.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

Example:
To Be Inserted Later

META commands:
--------------
All META commands are allowed in the model file but not specifically required except as specified for the header. If included, any META commands used should enable any instructions generated to be as close to the official instructions as possible.

Print this item

  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.

Print this item

  i need help
Posted by: Matt Conroe - 2011-08-22, 3:47 - Forum: LDraw Editors and Viewers - Replies (1)

how to make the pieces connect like in LDD?

Print this item

  Sticky posts not threaded?
Posted by: Willy Tschager - 2011-08-19, 14:49 - Forum: Website Suggestions/Requests/Discussion - Replies (3)

Is it just my? All posts are threaded at:

http://forums.ldraw.org/list.php?19

but the sticky posts at the top aren't.

w.

Print this item