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
#19
The scheme you posted would work for me as well and you're right about the cumbersomeness related to the 48-primitives. Oh well, just an idea anyway.

Anyway if the directories are named after the amount of divisions, a stud.dat in 48/ would imply a stud made out of 48-primitives. I'd suggest p/logostuds/stud.dat or something like that, then a program could substitute primitives with their counterparts in p/logostuds/ for stud logos, p/48/ for hi-res primitive substitution, p/8/ for fast-draw studs and so on. IMO we should keep this generic like this.
Reply
« Next Oldest | Next Newest »



Messages In This Thread
Re: Parsable Meta-Data for High-detail vs. Low-detail parts and primitives - by Santeri Piippo - 2013-08-18, 8:00

Forum Jump:


Users browsing this thread: 26 Guest(s)