Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.Daz 3D is part of
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Yeah, my fear is that DAZ will do away with Puppeteer for DS5, I hope I am proven wrong! And yeah, LAM2 was such a natural fit, those scripts were made for each other!
Thanks, and yes they work magnificently, sure I could have manually set up the cams, but that would have been too time-consuming and irritating, it's the very reason why scripts are made in the first place, I'm glad you like the renders, I should have rendered this scene ages ago, I'll; most likely do a bit more to finish it up proper!
Thanks, I'm glad you like it, I'm motivated in doing it better justice soon!
Off-topic, I wish DAZ had a multi-quote system in place for this forum!
Thank you both!
That is a good idea. I will add it.
It seems that we still have some days to write a letter to Santa (aka Riversoft) :) and here is a suggestion.
I mostly do VN and I try to have several renders per scenes while using the timeline and/or different point of views. My usual workflow relied on a freebie called iray interior camera (a cam with parented iray section planes) that was my main render cam, and a set of cams that correspond to my different renders. So whenever I do a render, I create a copy of the render cam position to a new cam labelled with an id (and I keep track of these ids in the VN script). And when I want to rework a render, I just had to load the scene, use the camera with proper id, do the required modifications, copy my cam parameters to the main render cam and render. All the cam parameters copy were done with a script by mcasual.
Clearly the Camera Cutaway is a huge improvement over the iray interior camera (that had a fixed focal length, aspect ratio, etc, and no associated script). But a mean to copy the camera parameters from a cam to another cam would be quite welcome. There is no standard way to do that in DS (besides creating a new cam) and the mcasual script only copies the viewport transforms and not the other cam parameters. IMO it is a useful feature that could definitely be part of Camera Doctor.
There is a standard way to do this in DS. Select the first camera. In the Parameters pane, you can right-click on any of the left side tree and copy selected items. Then select the other camera and then paste selected items.
The visual switcher has now earned a spot on my toolbar. No more dgging in a menu to find it.
That is a high accolade!
I have very few on my toolbar because space is so precious: Look at Camera and Visual Switcher. To share with others... why is Visual Switcher so indispensable to you?
I use UltraScenery a lot, and I have created sets of cameras to go with it, to view the scenery from various locations and angles. Every UltraScenery landscape is different, due to the abundance of options and random elements. The visual switcher gives me a quick way to pick a camera that appears to have a good view of the generated landscape. Honestly, I haven't even tried all of the Camera Doctor tools yet. I may find other indispensable items in there, too.
I always look forward to your script products! Thanks for this bundle. I have been playing around, nothing crucial, and ran into a snag when I try to run CD Camera Visual Switcher - DS throws up an error window.
DS version 4.12, installed via DIM. I have a couple close up cameras and a "regular" camera in the scene. I would appreciate any suggestions. Thanks!
Log file lines:
2021-12-25 18:08:12.937 Loading script: E:/Daz 3D Content/Scripts/RiverSoft Art/Camera Doctor/CD Camera Visual Switcher.dse
2021-12-25 18:08:12.941 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RSConstants.dsa
2021-12-25 18:08:12.944 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RSBuildPanels.dsa
2021-12-25 18:08:12.947 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RSCameraFocusConstants.dsa
2021-12-25 18:08:12.950 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RS2019HelperFunctions.dse
2021-12-25 18:08:12.954 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RS2020HelperFunctions.dse
2021-12-25 18:08:12.960 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RS2021HelperFunctionsConstants.dsa
2021-12-25 18:08:12.963 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RS2021HelperFunctions.dse
2021-12-25 18:08:12.969 DEBUG: FOUND: E:/Daz 3D Content/data/RiverSoft Art/Common/RSCameraFocusFunctions.dse
2021-12-25 18:08:12.984 WARNING: Script Error: Line 428
2021-12-25 18:08:12.984 WARNING: TypeError: cannot call button(): unknown return type `DzButton*' (register the type with qScriptRegisterMetaType())
2021-12-25 18:08:12.984 WARNING: Stack Trace:
<anonymous>()@E:/Daz 3D Content/Scripts/RiverSoft Art/Camera Doctor/CD Camera Visual Switcher.dse:428
2021-12-25 18:08:12.985 Error in script execution: E:/Daz 3D Content/Scripts/RiverSoft Art/Camera Doctor/CD Camera Visual Switcher.dse
Thanks for sharing.
I believe this was an issue that was fixed in Daz Studio 4.15.0.21. From the change log:
Registered DzButton for discrete script access
I love Camera DOF so far, however, I cannot figure out why F/Stop is disabled. I tried creating a new camera, did not change anything about the new camera, and F/Stop was even disabled on that. Anyone else have this issue? I'm sure I am doing something stupid, just haven't been able to figure out what.
It is your version of Daz Studio. "Note that the f/Stop tool is only available in Daz Studio 4.15.1.83 and above."
Thanks RiversoftArt, that was the problem. Wish I was more observant. This is working great now, your stuff is the best!
Awesome! Thanks!
Just picked up the bundle today - looks like a really handy set of tools.
I'm just having an odd issue with F/Stop in Camera DOF; it seems that no matter what I click in the preview window, the script always sets the F/Stop to 0.10 resulting in a very out of focus result.
Daz version is 4.16.0.3
Hee's what I'm doing and what happens:
New scene with a couple of figures
Create a new camera
Run the DOF script and enable camera controls
Focal distance works a charm, just like tapping a focus point on a DSLR - lovely!
Switch to F/Stop and no matter where I click, the F/Stop value always changes to 0.10 and throws focus out.
I expect I'm missing something but not sure what? A couple of screenshots attached showing what I've described.
Just to add that after today's update to 4.20 the DOF is working as expected.
Interesting. I had noticed this problem in the last couple weeks and had just decided to investigate. I can confirm it is fixed in v4.20. One of the v4.16 versions must have broken a function the script called and now it is fixed. Thanks for sharing.
RiverSoftArt,
I bought the Camera Doctor bundle on February 14 and installed it the same day. I'm just getting around to exploring it now. The first script that I wanted to try was Camera DOF. Each time I try to run it, I get an error window. From the end of my Log file:
2022-03-11 20:17:09.049 Loading script: G:/My DAZ 3D Library - Passport/scripts/riversoft art/camera doctor/cd camera dof.dse
2022-03-11 20:17:09.054 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RSConstants.dsa
2022-03-11 20:17:09.057 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RSBuildPanels.dsa
2022-03-11 20:17:09.059 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RSCameraFocusConstants.dsa
2022-03-11 20:17:09.063 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RS2019HelperFunctions.dse
2022-03-11 20:17:09.068 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RS2020HelperFunctions.dse
2022-03-11 20:17:09.081 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RS2021HelperFunctionsConstants.dsa
2022-03-11 20:17:09.083 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RS2021HelperFunctions.dse
2022-03-11 20:17:09.088 DEBUG: FOUND: G:/My DAZ 3D Library - Passport/data/RiverSoft Art/Common/RSCameraFocusFunctions.dse
2022-03-11 20:17:09.102 WARNING: Script Error: Line 521
2022-03-11 20:17:09.102 WARNING: TypeError: cannot call button(): unknown return type `DzButton*' (register the type with qScriptRegisterMetaType())
2022-03-11 20:17:09.109 WARNING: Stack Trace:
<anonymous>()@G:/My DAZ 3D Library - Passport/scripts/riversoft art/camera doctor/cd camera dof.dse:521
2022-03-11 20:17:09.110 Error in script execution: G:/My DAZ 3D Library - Passport/scripts/riversoft art/camera doctor/cd camera dof.dse
Other scripts seem to work OK but I haven't tried them all yet.
I'm running Daz Studio 4.15.0.2 on a Windows 10 Pro laptop.
I believe this was an issue that was fixed in Daz Studio 4.15.0.21. From the change log:
Registered DzButton for discrete script access
Thanks. I'm leery of version 4.20 right now and I don't think there's any way to step up to version 4.15.0.21 or 4.16.
RiverSoftArt,
I backed up my essential Daz Studio system files a short while ago and bit the bullet by installing Daz Studio 4.20. Everything seems to have gone OK. All of my installed content is present and Camera POV works now.
Great! I personally have no problems with 4.20 though I had seen some people have. I am glad everything is working for you.
As a postcript, I discovered that the update to 4.20 seems to have wiped out a lot of content files in many folders across many directories on the 1 TB drive onto which I install content. Fortunately, I had recently copied all of my installed content from my 1 TB external drive to a new 5 TB external drive because my 1 TB was starting to get full. I had planned to start using the 5 TB drive as my main content drive. After starting to reinstall affected content via DIM, I found it easier to copy large amounts of directory data from the 5TB drive to the 1 TB drive.
Since there's a sale on I came across this, it looks awesome but I have some questions.
First is about the PoV cam. When using the r/l eye to look, is the point of origin for the cam at the edge of the pupil or is it the center of the eye ball? If the eyes move side/up/down after creating the cam the cam will move with the rotations without going back to the script?
My other question is about the DoF cam. What I usually do is create a null and get as close as possible to the closest pupil, parent it and use a DoF script (can't remember where I got it) that calculates then sets the DoF on the selected cam. I need to be as accurate as possible with the null placement because I like to use a very shallow DoF. Is this script doing what I manually do? If it doesn't, can it come close and allow me to tweak it so I get my accuracy?
Thanks.
Center of eyeball. The cameras are parented to the eyes or to the head (depending on your choice). If parented to eyes, it will move with the eyes.
The DoF camera does not have anything to do with the face camera. It can be applied to any camera. It calculates the exact distance from the camera to the object (center point) you select. You can of course tweak it yourself during or afterwards.
i've moved to 4.20 and Camera DOF doesn't work for me anymore... the camera no longer focuses on what is selected in the scene, it only focuses on the selected focal distance.
Also causes the program to freeze and crash when you try to click on reset camera, highlighted node, selected node etc.
EDIT: Sorry my recollection on how to use it was incorrect... re-watched the tutorial and i'm up and running again.
Oh great! These are the best types of support questions!
Is it possible to add the visual switcher to a panel (tab)?
Unfortunately not. These are scripts and cannot be added to a panel. You can add the button to the toolbar though.