Parsable Meta-Data for High-detail vs. Low-detail parts and primitives
2013-08-14, 0:05 (This post was last modified: 2013-09-01, 20:37 by Steffen.)
2013-08-14, 0:05 (This post was last modified: 2013-09-01, 20:37 by Steffen.)
Hi Y'all,
A while ago someone pointed me at the low-detail versions of the stud primitives, which cut the polygon prism side count in half.
I just want to confirm that there is no machine-readable way to determine which files are higher or lower res versions of each other, either via a meta command or a separate index file.
I am interested in coding Bricksmith to dynamically swap between high and low res primitives to improve rendering performance without having to hard code a list of "known swaps".
cheers
Ben
A while ago someone pointed me at the low-detail versions of the stud primitives, which cut the polygon prism side count in half.
I just want to confirm that there is no machine-readable way to determine which files are higher or lower res versions of each other, either via a meta command or a separate index file.
I am interested in coding Bricksmith to dynamically swap between high and low res primitives to improve rendering performance without having to hard code a list of "known swaps".
cheers
Ben