Bug 1193 - "usemtl" assignments that used to work with 4.6 (and earlier) don't work with 4.7
Summary: "usemtl" assignments that used to work with 4.6 (and earlier) don't work with...
Status: RESOLVED WONTFIX
Alias: None
Product: DIRSIG4
Classification: Unclassified
Component: Materials/Radiometry (show other bugs)
Version: 4.7.0-beta
Hardware: Other Other
: P5 normal
Assignee: Scott D. Brown
URL:
Depends on:
Blocks:
 
Reported: 2015-11-05 12:20 EST by Scott D. Brown
Modified: 2015-11-09 12:32 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott D. Brown 2015-11-05 12:20:33 EST
In previous versions of DIRSIG (prior to 4.7), the "usemtl" assignments in a OBJ file were expected to be integer IDs because DIRSIG 4.6.x and early only supported numeric IDs. Some users discovered that the input reader would strip off a numeric part of an alphanumeric material ID.  For example: "usemtl 1010_texture0.jpg" would just be read as "1010" and an entry with "ID = 1010" would be searched for in the material database.

In 4.7, we added the option to let material IDs (now referred to "labels") be alphanumeric.  Hence, "usemtl 1010_texture0.jpg" is now a completely valid label and unless the material database was updated to read "ID = 1010_texture0.jpg" (when it used to be simply "ID = 1010") it will fail.

If you have scenes that took advantage of this hidden feature of the OBJ material assignment, then you will need to:
(1) Update the "usemtl" entries in your OBJ to match your material file exactly,
(2) Update your material file to match your OBJ "usemtl" entries exactly,
(3) Use the "<assign>" options in the GLIST to remap the OBJ labels to DIRSIG material labels.
Comment 1 Scott D. Brown 2015-11-09 12:28:43 EST
Note that some of the standard scenes (for example, the "refinery" scene) utilized some of these assignment names in earlier releases of DIRSIG.