If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
New! You can now log in to the forums with your chaos.com account as well as your forum account.
OK.....so things are getting even more strange.
While preparing a stripped down file for you guys, I saved the ies lights and fixtures out to their own file, and started from there. At one point I checked the asset tracker and saw that the file was still reading in massive amounts of textures, and I figured this was the slate editor not having been cleaned up. I proceed to delete all the active view-tabs and resave and close max, reopening the file.
At this point I have not done anything with the lights. Upon reopening, the error messages are gone. The ies lights are still reading the ies files from the server.
I have no idea what might have caused this, as one can not view ies files in the material editor afaik.
I could archive the whole thing without cleaning, but its quite large and usees railclone and forestpack extensively in case that would be a problem.
Do you want to try this massive file?
What I have found so far is that the error is related to the viewport V-Ray IES light shading. It is specific for this scene and can't be reproduced on a new one.
If you deactivate it (Enable Viewport shading) from the IES panel, the error will not occur anymore.
OK, found it. The problem is in the OSL shader that makes some changes on its compilation and IES files can't be properly loaded by 3ds Max after that.
It will be fixed by our developers.
If you experience the same issue again, then try to change the Windows regional settings Decimal symbol from "comma" to "dot".
So if I understand correctly, the osl-map module is buggy and breaks vray/max's ability to read all ies files (per session)?
At least that makes sense as to why the problem went away when clearing out the material editor.
Is the short term workaround still to disable viewport shading for the VRayIES lights?
The long term and proper "fix" is to fix the osl implementation?
I would rather not have to change the decimal setup in windows, as that would have to be done on all workstations and slaves, and makes typing numbers nasty on a Norwegian keyboard layout. There may be more implications I'm not aware about.
Yes exactly. There are changes in the OSL code that reflect to the correct loading/reading of IES files.
However, according to my test disabling the Viewport shading fixes the error messages and the IES light renders as expected.
Please let me know how it works for you.
Comment