Loading...
> >

Released : Iray Light Manager PRO (Commercial)

124»

Comments

  • V3DigitimesV3Digitimes Posts: 3,150

    Sorry for the double answers, there is obviously a problem on this forum page not allowing me to answer properly...

    The update is still in the pipe, so for now I'm gonna wait to see if everything goes well with it before I make a new update.

  • V3DigitimesV3Digitimes Posts: 3,150

    The update I mentioned successfully passed the test, it should be out in several days. In the meantime make sure you have a tone mapper and environement node in your scene before you launch it :)

  • Mark_e593e0a5Mark_e593e0a5 Posts: 1,594

    Update showed up in DIM a few minutes ago. On DAZ timescale, this is lightning fast laugh

  • V3DigitimesV3Digitimes Posts: 3,150

    Mark_e593e0a5 said:

    Update showed up in DIM a few minutes ago. On DAZ timescale, this is lightning fast laugh

    Well it seems that it went from the final review (before going to the store) to the store, then back to the final review, so I don't really know if the update is really live now (in general this is a more slow process). Anyway you'll know that you have the right version if, in the interface, you see version 1.2.
  • Mark_e593e0a5Mark_e593e0a5 Posts: 1,594

    Confirmed, the interface shows version 1.2

  • V3DigitimesV3Digitimes Posts: 3,150

    Fine... So this is live in store! Hurray!!!

    As a reminder, the main difference with version 1.1 is that 1.2 handles filament Viewport in the viewport drawstyle options, and accepts the fact that sometimes (if you never launched IRay in your scene for example) you have no environment or no tone mapper.

  • SevrinSevrin Posts: 6,308

    For whatever reason, LMP is not detecting the tone mapping and environment nodes that are present in the scene, and were present before running LMP.  Installed with DIM.

  • V3DigitimesV3Digitimes Posts: 3,150
    edited December 2020

    Do you see the Environment and Tone Mapping in the render settings?

    Daz it work if you go to NVIDIA Iray preview mode?

    The scripts has been tested by me and Daz, and we did no see this issue....

    Edit: the script actually reads the Tone Mapping and Environment in the render settings, the "shortcut" to have them in the scene was a shortcut for the users, they need to appear in the Render Settings I'm gonna have a look at this.
    Post edited by V3Digitimes on
  • V3DigitimesV3Digitimes Posts: 3,150
    edited December 2020

    I don't manage to reproduce your issue. Can you screenshot me what your render settings look like? (not in detail, I just need to see the group present in the render settings).

    Then if you see "Environment" in the groups of the render settings, relaunch the script and tell me if it solves your issue.

    And can you also tell me what version of Daz Studio you are working with? edit: If you still have the issue I'll write and post a debug script allowing me to see (allowing you to display) at which step of the environment properties detection the environment is seen as not existing (because it takes several steps for the script to reach this conclusion). And knowing which step does not see the environment in your specific case could allow me to find a solution for you.
    Post edited by V3Digitimes on
  • V3DigitimesV3Digitimes Posts: 3,150

    Ok I found something. If, in the render settings, you are FOR THE RENDER ENGINE in the "Viewport" or "Multipass Open GL", then the scripts will not be able to find the "Environment" since it is not accessible in the render settings. You have, while you set up your lights, to go back to "NVidia" Iray engine (or 3delight seems fine too) in the render settings, then back to "Viewport" when you are done and if you really need to be in viewport. Was this your problem?

  • SevrinSevrin Posts: 6,308

    1-My render and draw settings are all normal Iray.  I don't use the Viewport or OpenGL render engine.  However, I did have my Environment Intensity set to 0.0, but that was not a problem with the previous version of LMP.  That doesn't explain why it didn't find the Tone Mapping settings.  When I increased Environment Intensity above zero, LMP behaved normally

    2-Daz doesn't actually do a lot of "testing" of anything anymore, otherwise you wouldn't see half as many threads in The Commons.

  • V3DigitimesV3Digitimes Posts: 3,150

    OK thanks for the info, I never tested it with an environment at 0.0 (in this case I swap to scene only instead of switching off the environement), I'll have a look tomorrow to see what is happening. It should not be a problem the way I scripted the update, but maybe it triggers something somewhere in Daz Studio preventing the script to see an environment if it is set at 0....

  • SevrinSevrin Posts: 6,308

    V3Digitimes said:

    OK thanks for the info, I never tested it with an environment at 0.0 (in this case I swap to scene only instead of switching off the environement), I'll have a look tomorrow to see what is happening. It should not be a problem the way I scripted the update, but maybe it triggers something somewhere in Daz Studio preventing the script to see an environment if it is set at 0....

    This is the reason game companies, after doing all kinds of internal tests, do alpha and beta releases.  If something can go wrong, someone's going to make it go wrong.  I mostly use LMP to manage emissive and spotlight levels, and do my tone mapping and environment management using the DS controls, so this is not a huge problem for me, but when you get a strange error message like this, it's a concern.  I'll get the update when it shows up in DIM.

    Thanks for your quick response!

  • V3DigitimesV3Digitimes Posts: 3,150

    Yes, this product had beta testers during its development, alas for this "emergency update" due to DS 4.14, I did not used any beta testers.

    Excellent information concerning the environment set to "0.0", I saw exactly where the error was in the script, and this is very easy to solve, so this should not be long before I submit the version 1.21.

     

  • V3DigitimesV3Digitimes Posts: 3,150

    update submitted yesterday: now when an environment has a null intensity, it is not seen as non existing by the script (this issue appeared during the previous update).

    Sorry for the delay, this update is ready for a while, the reason for this delay is that I initially wanted to spend more time to develop something "more" on this script, which took me time and sadly did not work at the end. So I decided to stop the "bonus" development here, submit the update so that the "null intensity" issue disappears, and eventually I'll come back to this bonus feature later on or during a future update.

  • V3DigitimesV3Digitimes Posts: 3,150

    In theory, the update should be live now. Hard for me to check since I use my own dev script when I work. I just got a mail 3 days ago saying the product should be live the day after...

  • Mark_e593e0a5Mark_e593e0a5 Posts: 1,594

    Yes, it is live. DIM says that the package date is 2021-02-22. I installed it yesterday already, without really noticing it.

  • V3DigitimesV3Digitimes Posts: 3,150

    Thanks a lot for taking the time to confirm, that's really nice :)

Sign In or Register to comment.