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
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
I know that GIMP support was just added, but is there any documentation available for it? I am running into a problem using the GIMP plugin. the LDP-R combine script encounters multiple errors and doesn't complete. But first, this is my abbreviated DX
Operating System: Windows 8 Pro 64-bit (6.2, Build 9200) (9200.win8_gdr.130531-1504)
BIOS: BIOS Date: 02/05/10 19:13:52 Ver: 08.00.10
Processor: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 CPUs), ~3.4GHz
Memory: 16384MB RAM
Available OS Memory: 16354MB RAM
Page File: 8569MB used, 24168MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 11
The LDP runs fine in DAZ studio (for testing purposes, I'm only running the base LDP as it loads originally without modification rendering from the LDP camera using the Render_LDP option; the only thing added to the scene is a random prop) and outputs 8 renders into a folder like I believe it should, they are labelled '0_Fog.bmp' - '7_Mix.bmp'
I import the 8 pictures as layers into GIMP, arranged from top to bottom 7-0.
However, when I go to run the LDP-R Combine I receive 3 errors.
Error 1:
Calling error for procedure 'gimp-item-set-name':
Procedure 'gimp-item-set-name' has been called with value '-1' for argument 'item' (#1, type GimpItemID). This value is out of range.
Error 2:
Execution error for 'LDP-R Combine':
Error: ( : 1) Procedure execution of gimp-item-set-name failed on invalid input arguments: Procedure 'gimp-item-set-name' has been called with value '-1' for argument 'item' (#1, type GimpItemID). This value is out of range.
Error 3:
Plug-In 'LDP-R Combine' left image undo in inconsistent state, closing open undo groups.
Before terminating, the script seems to rename all but the top picture (7_mix.bmp) by removing the number (i.e. 6_sun.bmp becomes just 'sun')
Hi Daniel (^_^)/,
I have a system similar to yours. I received the same error as you, when I attempted to run the GIMP Filter without having any of the LDP-R images loaded _as_layers_. (EDIT: ah, I see you state that you definitely have the files open as layers... if you neglect to do that, then it will spit out the error you describe...).
Since you talk about only 8 layers, I'm guessing you haven't downloaded the "updated" version of the base LDP-R product. You will need that first, in order to be able to use the GIMP filters successfully. The "new version" of the LDP-R appears to render four extra "0_Custom" layers (for the custom lights, presumably).
The documentation should be found in your /ReadMe's/16860_ldp-r-manual_104.pdf.
I think the problem may be that you are importing the images as layers? I don't have GIMP but in Photoshop the workflow is to open the images all at once in separate tabs (at least that's how it looks in my layout), in order 0 to 7 and then run the combine action. That will pull them all into one document as layers, renaming several of them in the process. You shouldn't be manually combining them into layers - that's what the combine action does - unless there's been some major change (I'm just downloading the latest update now) or it works VERY differently in GIMP.
EDIT: Ok- Ignore me - I just started reading the updated LDP-R manual and the process IS different in GIMP. Sorry!
Tried out the latest update and it still deletes all other lights, at least I think it does, it either deletes them or rearranges the order.
Damn, hardware issues ain't fun.. Glad you found it though!
I have solved the issue, it was the motherboard.
Thanks
Have you installed the latest version? It let's you choose the directory prior rendering.
Are you using the latest Gimp version? Yes, there's additional information on how to use it included in the updated user guide. Also, you MUST switch to english Gimp language. (Explained in the user guide).
For PS, load as usual.
For Gimp, load as layers.
It does not delete any lights, although it places lights outside the customer folders, inside customer folder 1.
New update now available for free:
- Forces black background during rendering (reverts to whatever it was after rendering), in order for the layers to work properly
- Gimp scripts (similar to Photoshop acrtions) included (Photoshop is therefore not required)
- LDP-R Combine Night script / action included, that will create a night image
- 4 Custom layers included. Parents lights, including uber lights (+uber evn 2) to each of the custom folders, and get each layer rendered separatelly + mixed automatically in PS / Gimp
To get the new update, just re-download from your DAZ account.
Hhave fun! :)
I found something kind of odd, while rendering I have the scene tab open and I see LDP-R move the lights around changing the order.
Yes, it's supposed to do that.
For non LDP-R lights, if found outside the customer folders, they will ALL be placed within custom folder 1. If you already placed your custom lights in any of the new 4 custom folders, then they will remain there.
Howvever, custom lights will switch, appear and disappear, in order to render in layers.
Ok Awesome! There are also lots of new layers. Last render I did was like 12 layers. I need to go back in and add more lights.
So far pretty happy with the new update. I would like to know if you updated the documentation to see how to initiate the night time render settings. Also if you could link me to the LDP-R Mastery I am having trouble finding on your site. I found another odd issue. When ever I set the lights to render it moves the location of each of the lights.
Hey, no changes are needed inside DS for night renders. You just set the sun, hit render, then inside PS / Gimp select LDP-R Combine Night and you've got a nighr render ready to be tweaked. Yes, notes about this are added to the user guide.
Please refer to a post just above this regarding how LDP-R handles custom lights. They must be parented to each of the custom "folders". And they will move / appear / disappear while rendering in order to produce separate layers.
The LDP-R mastery can be found here:
http://www.dream-lounge.com/dreamlightclub/LDPR_Mastery/
Just to clarify (also stated in the user guide):
- Night renders need to special adjustments inside DS. Just point the sun and render. Then user LDP-R Combine Night in PS / Gimp + Add the cold filter when done tweaking.
- Custom lights must be parented to either of the LDP-R Customer Light "folders" or else they will be forced-parented to custom folder 1. Uber Env 2 and Uber lights can be used as well.
- Be sure to update the PS / Gimp scripts / actions since otherwise they will not combine the new custom layers.
Let's see some renders with custom lights folks! :)
P.S. When you add lantern lights for a night render, they will not be blue-tinted by the LDP-R Combine Night function, meaining you can add fire / lamps / lanterns in organge color to match the bluish night tint.
Ok here is what is happening now, its not just moving them into a folder but also moving them to another location in the scene if I have them at X1000 Y1000 Z1000 it moves them all to X0 Y0 Z0 and its not moving them back.
I have several point lights in this scene when I go to render none of them are where they are suppose to be.
this is a capture of where they all get moved to. the X and Z locations are all wrong.
Great render! That sounds like some sort of a bug. Is that for point lights only? Fixing this now...
I think its with all lights, even the ldpr lights.
Weird, since it was working perfectly during testing. I'm looking into this now. LDP-R lights however, will always be reset to 0,0,0, since that's where they should be.
I am not seeing the LDP-R Combine NIght in the actions tab in PS
I didn't as well. then I remembered that at least for me the action file is copied to the wrong folder by the installer.
It is installed by a separate installer named "Light Dome PRO - R (Photoshop)" or "Light Dome PRO - R (PS)".
If you use DIM you can see the location where that installer copied the new atn file.
Again for me, it dropped in the "program files\adobe\photo shop...." folder but on my machine photoshop action files are located in 'Program Data" not "Program files" so i had to copy them from the installed location to the place my PS loads them from.
You just need to tell PS where to find the new file. This is the way I did it.
Isn't the photoshop component a separate download? I have two, one is the daz installer and the other is a zip file. You were right Vanguard, I found it, thank you.
Thanks for the work around!
I didn't as well. then I remembered that at least for me the action file is copied to the wrong folder by the installer.
It is installed by a separate installer named "Light Dome PRO - R (Photoshop)" or "Light Dome PRO - R (PS)".
If you use DIM you can see the location where that installer copied the new atn file.
Again for me, it dropped in the "program files\adobe\photo shop...." folder but on my machine photoshop action files are located in 'Program Data" not "Program files" so i had to copy them from the installed location to the place my PS loads them from.
You just need to tell PS where to find the new file. This is the way I did it.
We're looking into this, but have a hard time reproducing it.
What DS version are you using?
Does anyone else have a similar issue? (Custom lights not being placed where originally designed to?)
DS 4.6 The lights are parented to an object in this case its the lantern. What I think is happening is once LDP-R changes the parent it also changes the location of the X, Z in the scene. The Y is still the same.
I think you found your problem, John.
I made this scene with several custom lights and they all stayed where they should be during the LDP-R render process.
My custom lights were all parented to one of the custom light containers that LDP-R adds to the scene.
I believe a parented object's coordinate system is relative to the object it is parented to (the entire reason to parent an object) and the LDP-R script assumes or requires that the parent be the LDP-R container, although I have no idea why they would need to be moved. I would think enabling and disable the illumination would be enough control fr the process, but I don't know the ins and outs of it.
So the fix would be to unapparent them
Hi Folks,
Just thought I'd pop my head over the parapet to let you know the current situation re the moving lights.
The issue is caused by the script taking the local transformations (relative to the parent) of any parented custom lights, and using that value with the custom light object at (0,0,0).
A version of the script that uses global transformations (and keeps the lights where you put them) has been sent to Dreamlight HQ, and should be working it's way through the system towards you.
In the meantime, as a workaround, I'd suggest you either add custom lights directly as children of one of the custom nodes, or with no parent at all.
Happy Rendering!
YAY! I love this set, it has allowed me to render scenes I have not been able to before. And yes if you have no parent set for the lights it will work.