Hi - I am the user that they are talking to in Jeremy's post! I cannot see how the solution proposed would give an accurate enough, or high quality enough results to be acceptable to users. As you can see, Autodesk have been aware of this shortcoming in the API for many years. The API needs to return the filepath of the texturemap.
Of course, many other companies have solved this issue (Universal Material Converter, Enscape, IrisVR, Lumion, etc)
Have they /really/ solved it? Are they using the Revit API, or exporting to FBX or another format which DOES include the filenames? I tried a number of solutions which not only loaded the geometry into Octane from the Revit API, but also exported the entire scene to disk in FBX format (which includes the material filenames), and then read the FBX scene back in to obtain those filenames, however the material identifiers obtained via the Revit API are /different/ to those contained in the .FBX file, so it also was not a viable solution. It also tripled the load time of the scene into Octane, so was never going to be popular with users.
Paul