Loading...
> >

Spotlights don't work anymore

AndySAndyS Posts: 1,438
edited May 2017 in Technical Help (nuts n bolts)

That is strange,

suddenly, the spotlights aren't working anymore in iRay. Render setting is "Scene Only".
Even the emitter ("Render Emitter" = ON") don't show the emitter area, if I set to sphere with diameter = 50 to make it visible.
The corresponding Display options are all set to "ON". Even "Sigle Sided" / "Double Sided" doesn't matter.

And - the Auto Head Lamp ("When no Scene Lights") don't work neighter.

HDRI Sky and Sun Sky work without problems.
Render Mode: CPU-only.

Post edited by AndyS on

Comments

  • SimonJMSimonJM Posts: 5,999

    From memory they should have 'photometric mode' enables if you load them when Iray is selected as render engine, but worth checking that? Are you sure they are not being blocked by any geometry?  Select them as a camera view and see what they are aimed at?

  • AndySAndyS Posts: 1,438
    edited May 2017

    Hi Simon,

    I knew what I forgot - the attachment: screenshot! smiley

    I noticed that on my simplest "photostudio" setup, which I use as standard. Today morning it worked and as I wanted to check some skin settings with it, the character suddenly rendered black. Especially strange: Looking at the camera (while rendering), you even can't see the emitter, which normally shows up in the render.
    Neighter new start of the application, nor new start of windows didn't help.

    Spotlight not showing2.jpg
    1920 x 1080 - 278K
    Post edited by AndyS on
  • AndySAndyS Posts: 1,438

    Hi,

    really nobody with a helpful idea? crying

    The log journal may idicate some missing or now not found shaders. Where to re-adjust something?

    Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(207,8): unreferenced local material 'material dzpm_spot_light' has been removed
    2017-05-27 01:05:17.810 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(MDLC:COMPILER):   1.0   MDLC   comp error: Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(215,4): 'nvidia::lights_photometric' is not a package or module name
    2017-05-27 01:05:17.810 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4003) : The module "::daz_3d::basic" was not found or failed to compile.
    2017-05-27 01:05:17.810 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4006) : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(21,8): could not find module 'nvidia::lights_photometric' in module path
    2017-05-27 01:05:17.810 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4006) : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(181,8): unreferenced local material 'material dzpm_diffuse_area_light' has been removed
    2017-05-27 01:05:17.810 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4006) : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(187,4): 'nvidia::lights_photometric' is not a package or module name
    2017-05-27 01:05:17.811 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4006) : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(193,8): unreferenced local material 'material dzpm_ies_light' has been removed
    2017-05-27 01:05:17.811 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4006) : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(200,4): 'nvidia::lights_photometric' is not a package or module name
    2017-05-27 01:05:17.811 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4006) : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(207,8): unreferenced local material 'material dzpm_spot_light' has been removed
    2017-05-27 01:05:17.811 WARNING: dzneuraymgr.cpp(1113): MDL Import Error (4006) : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(215,4): 'nvidia::lights_photometric' is not a package or module name
    2017-05-27 01:05:17.811 Iray INFO - module:category(MDLC:IO):   1.0   MDLC   io   info : Found MDL module daz_3d::basic in file Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl
    2017-05-27 01:05:17.814 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(MDLC:IO):   1.0   MDLC   io   error: Could not find MDL module lights_photometric in package nvidia
    2017-05-27 01:05:17.819 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(MDLC:COMPILER):   1.0   MDLC   comp error: Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(21,8): could not find module 'nvidia::lights_photometric' in module path
    2017-05-27 01:05:17.820 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(MDLC:COMPILER):   1.0   MDLC   comp warn : Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(181,8): unreferenced local material 'material dzpm_diffuse_area_light' has been removed
    2017-05-27 01:05:17.820 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(MDLC:COMPILER):   1.0   MDLC   comp error: Y:\Programme\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl(187,4): 'nvidia::lights_photometric' is not a package or module name

    I already copied the original program package in place - but no success.

  • FishtalesFishtales Posts: 6,162

    Is it possible it isn't finding your runtime? It seems by the log that it isn't finding the modules for loading items. I take it you have already stopped and started Studio and that the CMS is running?

  • AndySAndyS Posts: 1,438

    Hi Fishtales,

    If it isn't finding the runtimes, this is only for the spotlights.
    All other lighting, rendering, emissive shaders, etc. work fine.

    It appeared after performing the necessary shader mixer additions for this product: https://www.daz3d.com/forums/discussion/166876/iray-1-3-0-vmaterial-library-for-d-s

  • FishtalesFishtales Posts: 6,162

    You have had to move folders with that product? If that is the case then any existing scenes and settings will not know where to look for those folders.

  • geoff6geoff6 Posts: 250

    I might be pointing you down the wrong road here but I've had a similar issue in the past and found that increasing the Luminous Flux setting in the 'Light' parameters of the lights in question sorts it out. You need to really crank it up, start at 1000000 and experiment. Also, look at Render settings/Tone Mapping and look at the film ISO (default 100) or F/Stop. ISO is the film 'speed' so a larger number (say 400) makes the film more 'sensitive to light. The F/Stop is the aperature size, (default 8).

    Like I said, could be wrong but if you've tried the above, at least you've ruled out the obvious. Also, I've found that if there is an emitter, or a distant light in thescene, things can get a bit odd.

    Hope this helps,

    G

  • AndySAndyS Posts: 1,438
    edited May 2017

    laugh 

    geoff6 said:

    I might be pointing you down the wrong road here but I've had a similar issue in the past and found that increasing the Luminous Flux setting in the 'Light' parameters of the lights in question sorts it out. You need to really crank it up, start at 1000000 and experiment. Also, look at Render settings/Tone Mapping and look at the film ISO (default 100) or F/Stop. ISO is the film 'speed' so a larger number (say 400) makes the film more 'sensitive to light. The F/Stop is the aperature size, (default 8).

    even in this case I would see the visionized emission plane of the light (black or whit depending on "Two Sided" = ON/OFF). But please see above: this isn't shown neighter.
    Attachment produced with 4.9.4.110.
    But I can't use the newer versions due to some real NOGO-Bugs after 4.9.2

    working SpotLight.jpg
    495 x 445 - 28K
    Post edited by AndyS on
  • Richard HaseltineRichard Haseltine Posts: 102,783

    Have you tried uninstalling and reinstalling the Default Resources?

  • AndySAndyS Posts: 1,438
    edited May 2017

    Hi Richard,

    that's an interesting hint. I thought about "What else is there besides the program folders and the content library, which could have been corrupted?"
    Cause I tried the same setup with the latest Beta (4.9.4.110). That worked fine. With the Beta I accessed my content library itself.
    Where are these "Default Ressources" located?

     

    P.S.

    I replaced the complete content by what is stored in the install package of the Default Resources. But it didn't help.

    Post edited by AndyS on
  • AndySAndyS Posts: 1,438
    edited May 2017

    So,

    I found it. frown

    The procedure for adding the necessary shader mixer setting for the AEC nVidia libraries for the "IRay 1.3.0 vMaterial Library for D|S" freebee of MCDLabs over here, caused the issue.
    As I removed the additional path to the nVidia mdl libraries, the default lights worked again.

    The question is now, how to point to the nVidia libraries without blocking out the default lights if you want to use the fantasic materials library of MCDLabs.

    Post edited by AndyS on
  • Richard HaseltineRichard Haseltine Posts: 102,783

    I don't think I have a default MDL library folder - what is yours set to?

  • AndySAndyS Posts: 1,438

    Hi Richard,

    it was the setting following the instructions in this thread.

    AndyS said:
    It appeared after performing the necessary shader mixer additions for this product: https://www.daz3d.com/forums/discussion/166876/iray-1-3-0-vmaterial-library-for-d-s

    Here you have to enter the path to the AEC nVidia library. Please don't ask me about any shader mixer setting. I'm not used to it (right now).
    For the older version of DAZ it somehow overwrote the standard shader mixer setting. For 4.9.4.110 the required additional setting worked without conflicting.

  • Richard HaseltineRichard Haseltine Posts: 102,783

    Ah, well maybe it was a fixed bug then.

Sign In or Register to comment.