Hi Tim,
Right - there are around 25,000 parts using stud.dat, and around 900 sub-parts using stud.dat - too many to edit.
But there are only 50 or so actual low-res stud replacements.
So my idea is to have some kind of meta data on stud.dat itself saying "if you need lower quality and higher framerate, don't use me, use stu2.dat instead". The substitutions are made on the parts being replaced, and the 25,000 parts using stud.dat benefit automatically.
Right now to use this list I'd have to hard code it into the app, which will then be wrong if a new stud and low-quality pair are created.
As far as I can tell, stu2.dat is not actually directly used by the library.
cheers
Ben
Right - there are around 25,000 parts using stud.dat, and around 900 sub-parts using stud.dat - too many to edit.
But there are only 50 or so actual low-res stud replacements.
So my idea is to have some kind of meta data on stud.dat itself saying "if you need lower quality and higher framerate, don't use me, use stu2.dat instead". The substitutions are made on the parts being replaced, and the 25,000 parts using stud.dat benefit automatically.
Right now to use this list I'd have to hard code it into the app, which will then be wrong if a new stud and low-quality pair are created.
As far as I can tell, stu2.dat is not actually directly used by the library.
cheers
Ben