no UI for that – one has to modify the Installsettings.ini file BTW: this ini file and useUserProfiles exists since ages, don’t know when they introdu…
ravihara: The path is there bro. But max doesnt use it… getdir #usericons returns the new path inside installation folder and max wont use the old …
Does’nt work here either – always uses the setting from the create preview settings panel – regardless the mode which is set ( via MXS) in the actual …
Well – that still shows there is a problem. There is no reason besides some serious Max-internal flaw that purging that number of light’s should take …
It does’nt even matter if the lights are instances or not or what type of lights As the demo scene (created from scratch ) i linked in my post above…
I have the demo installed, but testing with the whole vray plugin removed shows the same result: as soon as i deleted all lights, saved that scene and…
Just tested this : deleting the lights and saved the scene, started fresh max session and loaded the scene -> result: locking problem is gone But t…
Okay – here is the proof that its a problem with that many lights in general – not only vray lights. A scene containing 2K instances of one photometri…
stigatle: 4600 lights should not make max completely lock up either. I have scenes with 10-50.000 objects that does not lock up max (all though it’s…
I checked the scene and have to say: those modelled vray light bands are insane ( >4600 light sources ). I can’t imagine this to be ever efficient….
skyrick: Little up, please do you have a idea ? Well -looks like they did’nt update the limit in the maxscript exposure when they updated the bi…
sounds like some faulty script in your scripts/startup folder, some installed plugin or some other thing that installs eg. file reset callbacks. Or th…
Just noted that i had written “on … create do”, of course that should be “on … open do” On create is structs only AFAIK…
placing the bitmap assignment into an “on <rollout> open” handler works rollout ui_imgtag “imgtag” ( local bm local nbm on ui_imgtag op…
Is this a new thing with an updated Max version, or does it happen in general, on the Maxx version you started to code the tool ?