LDraw.org Discussion Forums
OMR specification and unofficial files - Printable Version

+- LDraw.org Discussion Forums (https://forums.ldraw.org)
+-- Forum: General (https://forums.ldraw.org/forum-12.html)
+--- Forum: Official File Specifications/Standards (https://forums.ldraw.org/forum-32.html)
+--- Thread: OMR specification and unofficial files (/thread-18076.html)

Pages: 1 2 3


OMR specification and unofficial files - Philippe Hurbain - 2015-11-22

Following the problem mentionned here and after discussions with Mikeheide about MPDCenter, I think that OMR specifications should be updated to make it clear that unofficial parts MUST be included in OMR conform files.
It is more or less implied by this paragraph of the specification but it should be made much more explicit

Quote:Unofficial parts are allowed to be used. The filename of the unofficial part is subject to the following naming rules:

<Set Number>[-<Optional Qualifier>] - <Unofficial Part Number>.dat

Where:
<Set Number> is the the number printed on the model's container.
<Optional Qualifier> is a sequential number, starting with 1, added if there is more than one set that could be assigned <Set Number>.
<Unofficial Part Number> is the unofficial part number assigned in that very moment.

Example:
33956.dat would be renamed to 3345 - 33956.dat or 3345-1 - 33956.dat.



Re: OMR specification and unofficial files - Willy Tschager - 2015-11-22

Philippe Hurbain Wrote:Following the problem mentionned here and after discussions with Mikeheide about MPDCenter, I think that OMR specifications should be updated to make it clear that unofficial parts MUST be included in OMR conform files.
It is more or less implied by this paragraph of the specification but it should be made much more explicit

Quote:Unofficial parts are allowed to be used. The filename of the unofficial part is subject to the following naming rules:

<Set Number>[-<Optional Qualifier>] - <Unofficial Part Number>.dat

Where:
<Set Number> is the the number printed on the model's container.
<Optional Qualifier> is a sequential number, starting with 1, added if there is more than one set that could be assigned <Set Number>.
<Unofficial Part Number> is the unofficial part number assigned in that very moment.

Example:
33956.dat would be renamed to 3345 - 33956.dat or 3345-1 - 33956.dat.

How about?

Quote:Unofficial parts are allowed to be used. The filename of the unofficial part is subject to must respect the following naming rules:

<Set Number>[-<Optional Qualifier>] - <Unofficial Part Number>.dat

Where:
<Set Number> is the the number printed on the model's container.
<Optional Qualifier> is a sequential number, starting with 1, added if there is more than one set that could be assigned <Set Number>.
<Unofficial Part Number> is the unofficial part number assigned in that very moment.

Example:
33956.dat would be renamed to 3345 - 33956.dat or 3345-1 - 33956.dat.

w.


Re: OMR specification and unofficial files - Philippe Hurbain - 2015-11-22

I'd be even more explicit:
Quote:Unofficial parts are allowed to be used, in this case they must be included in the MPD. The filename of the unofficial part is subject to must respect the following naming rules:
...or something like that!


Re: OMR specification and unofficial files - Michael Heidemann - 2015-11-22

Unofficial parts are allowed to be used in models and must be included in the mpd-file in that case. The filenam.......

The first sentence is the relevant sentence. In the todays specification the integration of unofficial files in the mpd-file is not explicid needed.


Re: OMR specification and unofficial files - Willy Tschager - 2015-11-23

Unofficial parts are allowed to be used, but must be included in the MPD as subfiles. The filename of the unofficial part is subject to the following naming rules:


Re: OMR specification and unofficial files - Philippe Hurbain - 2015-11-23

Fine for me!


Re: OMR specification and unofficial files - Michael Heidemann - 2015-11-27

I like this and are going to implement this change into MPDCenter.


Re: OMR specification and unofficial files - Michael Heidemann - 2015-12-26

There is nothing to do because the current MPDCenter already cares about the unofficial parts.

http://forums.ldraw.org/showthread.php?tid=18367&pid=18367#pid18367


Re: OMR specification and unofficial files - Damien Roux - 2016-03-03

I have actually missed that thread but as I'm reworking my sets to make them OMR compliant, I'd like to express my point of view on this inlining of unofficial parts :


I personally don't like that at all. For several reasons :
I would not be able to use a LGEO equivalent for rendering a part if it is defined like that (this is my main concern).
I don't like to have anything which is not a part in my sets.
Ldview will simply download the part if it is missing.
If the part is changing on the tracker, it will never show up in the model.
Imagine the origin is changing, it quite easy to see and to update. Same if name is changing.
I am 100% sure OMR repository models will not be updated to remove the inlined part when it will be official.

I have the feeling that this rule has been made for only a few particular cases. I am pretty sure more than 90% of unofficial parts become official without a name change and a origin redefinition.
A lot of unofficial parts inlcuded on my sets are patterned parts I submit to the tracker before building the set. As for me there is no reason to inline those parts as the origin won't change, and rarely the name, even if the name changes all viewers will give an error and point this out.


The two points of view have pros and cons. But I think there is much more cons in inlining the part than there are pros, at least for a render guy as me.

Could you express on that?

Maybe, I have a suggestion:
What about two status: OMR compliant with/without unofficial parts.
It could be much easier to check when parts become available (just a quick open in ldview to see if everything is still OK) than with an inlined part that no one is aware about.


Re: OMR specification and unofficial files - Travis Cobbs - 2016-03-04

I don't understand why LGEO-type replacements wouldn't work for unofficial files included in the MPD. I'm pretty sure LDView will happily do that, as long as the included part has the unofficial part meta-statement.
Changing origins is one of the main reasons that this is required. We don't want models in the OMR to suddenly stop working because the unofficial part's origin was changed. With the file baked in, the model will continue to look correct indefinitely.