I’ve been having issues with my scene files’ Exposure Control lately. I have Physical Camera Exposure enabled but when I reload the scene(s) the Exposure Control is switched to No Exposure Control. Has anyone else had this issue? I can’t figure out what is causing it. It’s a tad bit annoying (understatement).
Hi Neal,
Are you still on beta 1? Have you tried the latest beta 3 ?
The described issue doesn’t occur in my tests so it would be good to get me your file if possible.
We can check out that issue too if you can send us some examples to our support mail.
Thanks Tashko! I’ll send one over in a bit.
I sent over one of the scene files which has both of the issues. Thanks!
I have the exact same issue with the Exposure Control deactivating itself on opening a particular file and those same 2 helper objects that won’t delete from the scene. I think the objects might have come from a 3dsky.org model, but I haven’t been able to pin down which one yet. Are you finding that it’s happening in multiple scenes, even fresh scene files?
Did you find a workaround to this issue?
I’m using VRay 3.6.04 and 3dsmax 2016.
Thanks.
Update: The 2 rogue helper objects that won’t delete are even present in a New max scene.
If I reset 3ds max to default user profile settings by renaming the ENU files and recreating them afresh, the issue is solved, with no weird helper objects in a new scene…until I open a file containing the helper objects and then they’re present in every new scene.
It’s pretty frustrating!
Have you tried running any cleaner scripts ?
anthonyh
Hi Anthony. Thanks for the suggestion - I’ve tried both those, but they don’t remove the helpers or find any missing plugins.
If you rename the helpers, you can delete them. It’s still pretty annoying but deleting them seems to have fixed the exposure issue.
Thanks Neal. Whilst renaming the helpers means you can delete them, when you re-open the scene, the helpers are in the scene again, though it does seem to mean that the Exposure Control settings are not affected like they were. Is that what you’ve found?
Cheers,
Andrew.
Unfortunately yes. If you load up any scene that has those in there they seem to come back on a fresh scene.
Did you try a fresh install of 3ds max and if so, did the helpers return as soon as you opened one of the offending files?
I cleared out the ENU file C:\Users\nealj\AppData\Local\Autodesk\3dsMax\2018 - 64bit which resets 3dsMax and fixes the issue…but it comes back if you load a scene with them in. I have not done a complete reinstall.
I came across this…
and this…
SO much fun…
Oddly enough, before I saw this yesterday I had also been looking further into this issue and came across exactly the same thread on the Autodesk Forum. It appears that they are well aware of this issue and are keen to remedy it.
I ran the script which identified the ALC Maxscript issue on my machine, but was unable to find the offending scripts they listed, so as suggested in the thread, I opened a support case with Autodesk Technical Support and within a few hours they came back to me with a very thorough explanation and a Fix Up maxscript to install, which removes the offending ALC script from your system altogether. I have then opened all the affected max files since it first occurred, the Fix Up script then removes the 2 helper objects and the file can be resaved to behave as normal and without the risk of further infection of the ALC issue.
I think I narrowed the source of the ALC script to an Anglepoise Lamp model from 3dsky.org, which I downloaded at the beginning of last week.
Neal, if you want the script from Autodesk, DM me your email, or log a support case with Autodesk if you haven’t already done it.
Like most long term max users, I have a lot to resent Autodesk for, but on this occasion, they have provided excellent customer support.
Sounds like Autodesk should just link the script publicly if it`s that big an issue.
I totally agree! They probably don’t want to publicly admit that it’s yet another bug within their software, albeit not one of their making…well not directly anyway. Apparently the MAXScript appears to have been written as a form of copy protection for a commercial plug-in, but it went rogue!
I wish they would just publicly release it. I spent hours trying to figure out what was going on.
“Sorry everyone but we decided to support our users…here is a script to fix a bug that is really annoying…also sorry we didn’t create the bug in the first place…we’ll try harder - Autodesk”