Parsable Meta-Data for High-detail vs. Low-detail parts and primitives


Re: Parsable Meta-Data for High-detail vs. Low-detail parts and primitives
#23
Michael Heidemann Wrote:Now after reading your suggestion it seems to be easy Smile
If the resolution of ldraw/p/8 is still too high, just search for a lower number in the path! (f.e. ldraw/p/4)

I think it is important that the valid "LOD" paths (e.g. 8, 48, 4, etc.) we explicitly named in a config file or an official spec, rather than having client apps just go searching the directory structure. We have some folders in parts (s, textures) that are not LODs, and we may have future reasons to add sub-folders to the parts or primitives folder.

If we know that clients only treat sub-folders as LODs when they are told to, I think it will make future expansion of the library less difficult to plan.

Cheers
Ben
Reply
« Next Oldest | Next Newest »



Messages In This Thread
Re: Parsable Meta-Data for High-detail vs. Low-detail parts and primitives - by Ben Supnik - 2013-08-18, 15:12

Forum Jump:


Users browsing this thread: 1 Guest(s)