Another request would be to add a support for IES lights in Rhino. I know it was already asked before but I feel it is an important feature. (Rhino has no intention of supporting it according to their team, they focus on a wide range of applications, not just architecture).
I was going to create a post… yes this is really a pain in Rhino 6 or 7, besides the intensity problem, there is another major one : the light’s dimension aren’t producing entirely light, so we have to overlay lights to create for example the whole length of the space. Massive pain to array 20 lights to cover one length.. and that’s even before adjusting the lighting fall off and the lack of ies
I think as a general idea, the whole rhino lighting isn’t working well for enscape, I think sketchup and the rest of the software have it sorted it out and it works well. What would be good is to know if the devs at Enscape encounters the same lighting problem with Rhino? @Demian_Gutberlet ? thanks
At this point, I will be very happy if Enscape supports default Rhino 7 lighting fallout correctly at least as Enscape team doesn’t seem to have any plans to add IES for Rhino.
Please please support Rhino 7 fall out lighting. It’s really hard to use Rhino lighting with Rhino 7 update. Enscape won’t recognize the fallout at all, and what’s worse, the light intensity is completely wrecked. It’s either super bright, or too dim. No control is possible.
Thanks @Demian_Gutberlet and @Rick_Marx , but this is not really acceptable, I am hoping to be polite, but that’s sort of ridiculous to use many lights in a row to create one light. It’s been months if not years that we are loosing our time here, real time but not so much because we array dozen of lights… what the hell guys? some of us are part of the customer advisory board, we have been part of Envision and we are really asking a very simple thing here, if it’s Mcneels causing problems, at least we go complain there, otherwise Enscape has to find a solution, create your on lighting with IES etc.. it would be very hard to read another " will submit your feedback to the Dev" if Rhino3d is supported, it needs to works like the others.
@gautier_2 , I can understand your frustration, but as mentioned before this is, unfortunately (purely speaking about the LIGHT SIZE itself, not any other features like IES light support), a technical limitation we simply cannot work around currently or perhaps not even in the near future - I do wish I had more positive news, but since Enscape is a real-time rendering engine there’ll also be size limitations for lights (besides emissive light sources) unless raytracing might be used for those lights as well which could very well be something we’ll tackle in the future.
If there was a simple fix for this or a way to improve upon this we would’ve done so already.
Again, I wish I had more positive news, but there is currently no way for us to simply work around those light-size limitations that are present in basically any real-time rendering application, or any video game (which also uses real-time rendering engines of course).
@Demian_Gutberlet So is it a Rhino sided issue or the way Enscape is coded? Where is the hold up? Rhino has really been on the back-burner of Enscapes development for a while now and that is very disappointing.
@Tearch , we’re aware that Rhino is more behind in terms of developed/supported features compared to other CAD solutions - We are going to implement new additions though (Based on the Feedback we gathered) and it is likely that even .IES light sources may be supported in the future. If not, then at the very least more and more other functionalities that have been requested for a while now in this Forum. I’ll keep you posted as always.