HELP! "Unable to edit light - no light asset was provided"
-
@dkendig said:
this is with the service release? Please make sure you are working with 2.00.24261
Hi Devin, Thank your for your quick reply. I am indeed using build 2.00.24261. I did have Vray lights in components for months before the problem occurred for the first time. I exploded all components but it did not solve the issue. Only when I erase all lights and add them again (without components this time)am I able to open the light editor and change parameters. The file worked fine then, but after closing and opening the problem comes back again. Any suggestions?
-
I have 2.00_24622 because I have nightly access and I just got the error. And I will add this, when I deleted the component and added a brand new omni light, it gave me the same error. I should note that this light is nested withing another component, within a group, so it is buried in there a bit.
-
@valerostudio said:
I have 2.00_24622 because I have nightly access and I just got the error. And I will add this, when I deleted the component and added a brand new omni light, it gave me the same error. I should note that this light is nested withing another component, within a group, so it is buried in there a bit.
[attachment=0:8ueqmqhq]<!-- ia0 -->Light Comp Issue.JPG<!-- ia0 -->[/attachment:8ueqmqhq]If you're on nightly access expect these hiccups. The light issue was fixed, so you shouldn't have a problem now. Make sure you update your nightly to what ever is most current when you run into issues like this, or re-install the service release. Nighties are always provided to certain customers use at your own risk. If you run into new bugs in a current nightly, be sure to log the bug reports with the version you are using vsfwip@chaosgroup.com.
-
(Re: SU/Vray 20. plugin) I had that issue with lights inside components once before and a restart of SU fixed it for me that time. I just had it happen again in a different model and here's another thing I just tried that worked for me & is quicker: EXPLODE one of the components, pick the light and go to edit that individual light. You should be able to get to the edit box now, but don't, now just deselect and UNDO the EXPLODE and you should be back in shape!
-
I am still having the same problem over and over again. Last month was with one file and now the problem is coming up with every file I open. Has anyone gotten to the bottom of this? Help please!
-
did you update to the current version of vfs?
-
@andybot said:
did you update to the current version of vfs?
Hi andybot, I am working with Sketchup Pro and Vray 2.00.24261(edu)on a MAC with OS Mavericks.
-
I have been modeling a three-story lobby. I have been embedding V-Ray lights into components so that I only have to create one elevator lobby ceiling that is then repeated on all three floors. I have had no issues with this until a few minutes ago when I got this same "Unable to Edit Light- No Light Asset Was Provided" error message. At first it was just on one new light; I was trying to copy one component that consisted of my can and spotlight, make it unique, change the lighting lumen level, and then use for a different area. I got this error message, but was still able to go to my previous components and tweak the lighting. Then it started spreading, and all of a sudden I get the error on all lights.
If anyone's heard a fix for this issue, please share. Keeping my fingers crossed that shutting down SU and re-starting will do the trick!... -
@kturtle said:
I have been modeling a three-story lobby. I have been embedding V-Ray lights into components so that I only have to create one elevator lobby ceiling that is then repeated on all three floors. I have had no issues with this until a few minutes ago when I got this same "Unable to Edit Light- No Light Asset Was Provided" error message. At first it was just on one new light; I was trying to copy one component that consisted of my can and spotlight, make it unique, change the lighting lumen level, and then use for a different area. I got this error message, but was still able to go to my previous components and tweak the lighting. Then it started spreading, and all of a sudden I get the error on all lights.
If anyone's heard a fix for this issue, please share. Keeping my fingers crossed that shutting down SU and re-starting will do the trick!...An update to the latest service release (SP2) should fix the problem. A fast fix is usually closing Sketchup and opening it back up.
-
Hello,
I've got the same problem on my config (config in my signature).
How can i know if i have the SP2 release ?
-
it happened to me too. I placed a light in a component. and same error message popped up. my fix is I will create a new light outside the component. then cut it, then double click into the the component, then paste the light that I created outside the component. now the newly created light is inside the component. it worked for me. hope that makes sense.
-
Thank you Sketchuh !
I know that, but that is not a solution, it's a hint to get around a problem.
Another one : you make a copy of each of your VRaylights transformed in components on the first level of your file structure, change your settings on those ones and hide them when rendering.
But the bug is not solved.
-
Yes, it works after restarting SU, but when you have a model that loads 8GBs of your RAM, it's not the best sollution to restart, because it will load again very long time.
Another solving is to copy your IES inside another SU, test it, then copy it back to your model.
-
Nope, it is not solved and still does come back randomly. I think it might have something to do woth creating a light while within a group or component. I agree that just saying "restart" is not a good solution or answer. Let's hope that all of these bugs are gone with the next release that we so patiently wait for. Now I'm starting to sound like I did when I was using 1.49.01 and that's scary!
-
@valerostudio said:
Nope, it is not solved and still does come back randomly. I think it might have something to do woth creating a light while within a group or component. I agree that just saying "restart" is not a good solution or answer. Let's hope that all of these bugs are gone with the next release that we so patiently wait for. Now I'm starting to sound like I did when I was using 1.49.01 and that's scary!
For me it worked to cut/copy the IES model from the model which shows this bug into an empty skp, test it and copy it back.
-
I had the same problem. Rectangular vray light, inside component. I JUST RESTARTED SKETCHUP and the problem was fixed!
Advertisement