Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Is the defaut camera light(s) listed in your summary ( or lack thereof)
In other words, start a new scene, insert figure and nothing else.
Figure is lite by default light, does you script list this?
Would help me enormously.
Hi Bicc39,
No, the camera headlamp is not listed. I considered it was not really useful because most of the time people have already switched it off, or in it was disabled by default when a light was added to the scene (well indeed except if there are only surfaces lights).
But as I said, if several people ask for the same feature because they think it is really useful, then I can add a new tab "Additional Features", where I can organise these features (if it is possible via script). Or I can eventually add
For now we would have : "Saturation" (one vote) / Camera Headlamp OnOff control (one vote).
If you're really annoyed by camera headlamps creation you can disable the option in the render settings / general.
Well this got wishlist we right away as I was sorta confused about it but it's in my cart again, so hoping i can make sense of if after purchasing it, I'm assuming I should be able to since it is designed for beginners too, but not having to exit out of the different tabs to change lights is definitely a selling point. Put my vote in for both of the features asked for lol
Thanks! Whenever there is something you would not understand, feel free to ask here. But I would be astonished, this is really designed to be clear.
In the meantime I remember : saturation 2 votes, camera headlamp 2 votes! ;)
I have this waiting in my cart and it looks like another amazing gotta have item ! One question I didn't see is once you have these lights set the way you like can you then save all these settings into a light set so you can reuse it again without doing the whole set up and adjust again?
Purchased last night and download tonight now to install and try out ;)
I bought your amazing ILM product 2 days ago, and the 1st project I tried it out on had 18 emissive surfaces lights. (I picked this one because I knew it had a lot of lights to work with.) It was incredibly efficient to be able to adjust them all in one screen at the same time, then test the effects immediately, then be able to go back and make adjustments.
Before having ILM, I had to go back into all 18 materials channels, and adjust them all one at a time by hand.
A couple of things I noticed: One odd thing I noticed is that when the scripts is run, EVERY light is selected in the collective actions tab. I would think that no lights should be selected unless I select them. What would be nice is a button to "select all" like in my email. I would be annoyed if I opened my email, and every email message I had was selected...every time!
(Edit: to add that I went back in and checked. There is a "select all" button. See!? I knew that was a good idea!)
I ran the script. The default tab that pops up is the collective actions tab with "Light Operations" visible. I made the changes, then I had to close the script in order to do anything else, including rendering out the scene. So far; so good. Everything as expected. If I wanted to make adjustments, I had to rerun the script. The window would pop up, again at the collective actions tab, but my settings in "Light Operations" were all changed back to defaults. It took me a little while to figure out that the light settings weren't really changed. But the fact that the values I had just put in several parameters 2 minutes ago were replaced seems...odd.
If the default selection of lights could be changed so that none are selected, then having the values blank would make sense. If I select 1 light, then the current value of that light should appear. If I select several lights that all have the same value, again seeing the current value makes sense. But if I select several lights that have different values, I would expect to see a " ? ". In the materials tab or the lights tab, for example, if I select several surfaces that have defferent values, that is what happens. I see a " ? " in the parameter value box.
Please consider these as suggestions for improvements....not complaints. ILM is a great product as is, and after one session with it, I can tell you it's one of the best products I've ever invested in. All in all, it was smooth and easy to make adjustments to all 18 lights at the same time.
Thanks!
Hi. Indeed, the "save" lights option (in one single file I suppose) was not included, the main reason is that, if you have a set with any type of lights, then you would have to save some "Daz Studio Lights" which is a given "save filter" for the script, but also the environment category of the "Render Settings" which is another "save filter" for the script, and for the emissive surfaces, I don't know how the problem can be handled. For emissive surfaces should only surface settings be saved as material presets? (but then you would have to select the object to apply them, so when you load the light set you have to select all the emissive lights), and this would have been another "save filter". Should the whole objects be saved? Honestly, I rapidely forgot this idea because I did not see really how I could save so different things in one single file coherently.
Now there is one thing which can be done : empty your scene from all the rest which are not DS lights or emissive objects, and then save it as a new scene. I think when then you "merge" it into a new scene, it should load the environment, the DS lights, and the emissive objects (you have to get rid off the previous lights and objects). Or, yes, you can save separately "render settings", "lights", and "scene subsets" with emissive objects, and reload the 3 of them.
Thanks! Have fun with it!
Lol, I just realised that ILM was "Iray Light Manager"! Great to know you found it really helpful. 18 emissive surfaces! Indeed you must have saved a lot of time :)
The choice to select them all was "a decision" I made, and is not the default one. I took this decision, because I thought that if people used the collective actions tab, then they wanted to act on several lights (otherwise they would probably go to the other tabs), and the most logical for me was to have them by default all selected. I don't know if you saw this but you can unselect by "groups" of lights (you can deselect "spots", "points", "distant", "surfaces"). Well I have the impression that since you wanted collective actions, unselecting lights was faster than selecting them. That's my impression with the tests I made.
The risk is also for the beginners. If they play with the settings without noticing the checkable list (which happened to one of my testers, and yet, she's not a beginner!), they will simply conclude that it does not work.
For now I prefer keeping them all checked, but if this is an issue for several people, I mean if enough people consider the list should be unchecked by default, I can update the script, it is 4 lines to remove.
You are right, but well, this is why, it is written at the top of this box that the values are not representative of what you have in your scene when you open it. Actually I had no idea to which value I could initialize since it is collective, this is why it is initialized arbitrary values in the collective actions. The idea is that the script is made so that, (maybe when you get more used to it), you never have to leave the interface until you have the right light set. The script cannot remember which selection was made in the selection list last time you played with it, so for instance you have ten lights, and modify them from the second to the last (but not the first), how could the script know, the next time you launch it, that the value it has to display is the first one or the second one, or... I have the feeling there is no real efficient solution. But yes I can understand this part seems odd. The values are yet displayed "at their real values" in all the other tabs (DS lights, Surfaces lights), so you can just have a look at what you have in the other tab to know what is your "reference" value. Sorry about that, I'm not sure there is something I can do.
I understand the "if I select one light". Well I think this could be possible. I have to think about how I could make this. But then I'm gonna have to explain that the values are not representative, except if one lights was selected, and even more, only if the parameter for the selected light exists (for instance if you select an infinite lights there is no way to have the spread angle). I'm gonna think about that, and I'll add it to the "additional features" list.
Concerning the "?" this is not possible. Because the dials you have here allow only to put a float in it. They are not the same as the dials you have in Daz Studio where you can see a "?". I think the "?" is in Daz Studio coming from a c++ or other language script, but with this type of dials, when I tried (lol, because yes, this was tried) to put a "?" the value displayed was "NaN" for Not a Number", and this was confusing (and this created other issues).
Thank you!!!! "One of the best products I've ever invested in"!!! I enjoy reading this, because I think on my side that it's one of the most useful products I've ever created :)
What I retain is that I have to see 1. if enough people prefer the "collective action" list completely unchecked when they start, rather than completely checked, 2. If enough people prefer that when they select a light, the collective action tab displays when they exist the values used for this light. I thank you for these proposal of improvement, I'm gonna update my "additional features" list.
Thanks!
Ok..let's start a "I support the 3DLight version of Iray Light Manager" poll. I am positive there would be a lot of support for a 3DL version, either as an add on, or a stand alone product. I know I would! Adding and controlling lights is no less of a pain in 3DL than it is in Iray.
Would anyone else be happy to see a 3DL version of this?
1. dHandle
2.
Thank you for the information on saving the light settings, I went ahead and purchased last night before I even read your answer to my question on saving the setups as I figure I can't go wrong having this in my arsenal of products. Lighting is one of my least favorite things to do as I just don't get it and I think this will be a huge help having all the settings together. I will be testing it out today when I have plenty of free time to play.
I like the idea, but I hate how the script box prevents you from using other viewports directly.
Probably more Daz Studio's fault then yours though. They probably purposely make scripts run this way.
Thanks! Maybe now lighting may become one of your favorite things? ;)
Yes, this is annoying. That's the way scripts work, I'm not sure this is made on purpose. This is why I included all the additional features besides the lights themselves (perspective view change, lights placement, camera changes, preview mode changes, etc, etc...), in order to minimise the number of time you'll have to close the script to change something and re-open it. The only way to access the viewports totally while running a script is to have not a script, but a pluggin... Alas, this is another language, and I'm not ready for that... Not yet!
..... Seems that you are the only one.... :(
It would be a stand alone, because the script is already very very big, and "adding" things in it is pretty hard. But... For now, it does not seem there is a big demand for that...
A <?> will be displayed by a DzFloatSlider if the value is indeterminate - for example, if it's showing multiple properties as a single slider and they don't all have the same value.
Ouch I had forgotten those AoA Advanced lights. One more thing to include IF one day I make this. edit : Lol, I just understand the hunger strike joke! You're lucky that I spend a lot of time on each product finally!!
Thanks Richard. So yes, if it is multiple different properties are "compressed" in a single slider. Is it made by Daz script (dsa) or by another program?
I have found so far no way to force the script to display a "?" by default on a float slider when a script opens. I had already tried "undefined" and "NaN" as a value, and probably other things I don't remember, but in all cases the slider displays "nan".
Those AoA lights rock! People still resist switching to Iray because of the versitility of AoA's lights. Or at least, go back and forth between Iray and 3DL. That's what I do...switch back and forth.
Being able to control multiple AoA lights as well as the built in DAZ lights would be very useful. I hope more people chime in here so it's worth your effort to develop it.
If oProp is a DzFloatSlider then
oProp.indeterminate = true;
And of course, it works perfectly! I had seen the "indeterminate" in the scope list, but did not know at all it would do that. Thank you!!!!
Yes I agree they are excellent lights. I'm really afraid making this because I have absoluetely no clue how many people are still using 3Delight, and amongst them, some of them may be not ready to invest for 3Delight if they think they'll swap to Iray later on. It would be a nice experiment to "know", but a risky one!
Wow, I love this thing!!!!!!!!! It is so easy to use and so powerful! As you said it is intuitive - I learned the basic amazing features in about 10 minutes. That I can see all of my emissive surfaces and adjust them all at once is worth the price alone, and there is so much more. I love the camera - the latitude, longitude and radius system is a great way to navigate (DS should incorporate this feature.) and make it so easy to adjust light placement. I get so frustrated tweaking lights and they are so important to me, so for me this is the best tool ever! Thank you!
I use both Iray and 3Delight and would absolutely invest in both (I just got this the other day while on vacation and just got home, so hoping to play with it this coming week lol) i would absolutely buy a 3delight version especially if it involved AoA's lights... And I vote for the head lamp thing as well. I HATE that thing
You're welcome and thank you sooo muuuuch for this so nice feedback! I'm really glad to know you found it easy to use too :) For the perspective view part, (latitude, longitude), I adapted is a code shared here on the scripts forums by Praxis, and I thank him again for sharing this with us.
That's cool to know that I made your DS experiment better thanks to this tool! Cheers!
Thanks for the info. Well a thing is clear, is that if one day I make a 3Delight version, then I will absolutely have to drive also the AoA lights. For the headlamp, there is an option you can find bottom of the "render settings/general" making that NEVER appearing if it annoys you often. (choose auto-headlamp : never). Well headlamp can be understood, for the beginners, it may be required so that they are not "in the darkness" in there scenes... But I recognise that it happened to me many times to be annoyed by this lamp.
Sadly for me the never doesn't seem to stick lol.
I used this product last night and have to say there is no doubt in my mind I will be using this every single time I put something together. Lights make or break a scene and are something I really struggle with. And the amount of time this will save me? This will cut my time mucking about with lights by at least half if not 75%. This is really an incredible product. Thank you so much for providing something even someone still fairly new to this can figure out easily.
Hiiiii Ice Dragon Art!
Seeing such a nice comment, and the fact that you posted it on the 22 is a very nice birthday present for me :)
I had no time to answer before, I'm working on 3 projects in parralel, and all of them had decided to have issues :( But this is better now!
Yes this also cut my set up time, and I use it "as soon as I have a light"... well always! This is why it's better if it's available via the scripts menu!!
Sooooo happy with your feedback thanks!!!
This is an ongoing thread.
http://www.daz3d.com/forums/discussion/65698/vendors-we-all-don-t-use-iray/p1
It's been around for a while. I don't think rendering in 3DLight is going away any time soon...
I'm still hoping there's interest in having you develop ILM for 3DLight.
Oh...and Happy Birthday!
Happy Birthday! Mine was on the 11th lol. I will be most interested to see what you have coming up next!
Happy late Birthday. I hope you had a wonderful day.
I did get to buy this earlier than anticipated ,but haven't had a chance to play with it yet. caan't wait to try it out , hopefully this weekend.
Great and NECESSARY product. I bought it on the first day, and now I am putting lights everywhere and then opening Light Manager Pro to set them at one time. Genius! I, unlike many people, like the Auto Headlamp, and sometimes I would like to use it with other background lights, but the only option I can find for it is NEVER and WHEN THERE ARE NO SCENE LIGHTS.
So, add my vote to Headlamp ON/OFF tab.
This is very useful. So much easier to get the lights just the way I want them. I woudl think that I would vote to have control of the Headlamp too. I use it sometimes with a lower power sort of like a fill-in flash on a camera.
Been meaning to post here - so, soooooo tempted to get this. If it covered UberArea lights too it would have left scorch marks as it was bundled into my basket! If you update it, or do a 3Delight version then you'd have my money!
I did a couple screenshots for people to see, and a little tutorial on where I set up my lights (gave the coordinates) and then showed the render. One thing I noticed that I did not like, is that in the Collective tab, the lights were not listed in the same order as in the DS Lights tab. So when I checkmarked the first six lights (that I had in the DS tab) over in Collective tab, I assumed they would be the same six. They aren't. They should be. I don't want to hunt back and forth to see where lights are in the list, particularly if I am testing lights in order (say, the first six. But in Collective Actions, those six are now scattered throughout. Not good!)
The Collective Tab should show the same order as the DS Lights tab.
Example: DS lights were spot 1, 2, 3, 4 and in the Collective tab it is 1, 10, 12, 13.
Otherwise, this is useful for testing light brightness very quickly.
The second thing, IMO there is a bit of a lag between when the camera moves and when I do the sliders in the script. While it's a fun idea to be able to rotate/move lights within the script, I find it works better for me if I close it and go back into the studio where I get real time movement. I have an ultra fast computer (Alienware51) so I know it's not my computer.
But this product is a lot of fun and makes changing light intensities a breeze since they are all together. Highly recommend.
Here is the soft muted light render of Kathy, done with the script. Test front, side, overhead lights. Very easy to do!