Forum Moderators: wheatpenny Forum Coordinators: Guardian_Angel_671, Daddyo3d
DAZ|Studio F.A.Q (Last Updated: 2024 Nov 29 12:43 am)
Very nice Steve!
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
The latest update for Reality 3 is available. Read all about it!
Cheers.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
BTW, the question from StainlessHolz has been answered in the Pret-a-3D forums.
Cheers.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
Quote - Guys, I really have a serious 'Merge' problem and I hope anyone here can help me.
Somehow the Reality_Scene_data gets lost when I merge a .DUF scene into another existing .DUF scene.
Now I know I have seen Reality_Scene_data (1), Reality_Scene_data (2), ect in scenes before (back in the days when all worked well)
Example:
I load the 'SpotCam' scene I saved to disk. (top image) As you can see there is Reality_scene_data present in this scene.
Now I merge that same scene again. (bottom image) Now I would expect there would be another Reality_scene_data hidden object that should be named 'Reality_scene_data (2)' or something like that, but it isn't there!
Would any of you be so kind to try to reproduce it? I'd hate to bother Paolo with this if it is just 'me' who has this problem, cuz the he's busy enough as it is without having to spend time on silly questions from me.
Thanks in advance :)
Yikes!! This is waaay over my head and one of the reasons I'm intimidated by both DS 4.5 and Reality. Did you ever get this solved?
Quote - > Quote - Guys, I really have a serious 'Merge' problem and I hope anyone here can help me.
Somehow the Reality_Scene_data gets lost when I merge a .DUF scene into another existing .DUF scene.
Now I know I have seen Reality_Scene_data (1), Reality_Scene_data (2), ect in scenes before (back in the days when all worked well)
Example:
I load the 'SpotCam' scene I saved to disk. (top image) As you can see there is Reality_scene_data present in this scene.
Now I merge that same scene again. (bottom image) Now I would expect there would be another Reality_scene_data hidden object that should be named 'Reality_scene_data (2)' or something like that, but it isn't there!
Would any of you be so kind to try to reproduce it? I'd hate to bother Paolo with this if it is just 'me' who has this problem, cuz the he's busy enough as it is without having to spend time on silly questions from me.
Thanks in advance :)
Yikes!! This is waaay over my head and one of the reasons I'm intimidated by both DS 4.5 and Reality. Did you ever get this solved?
First, you should not be intimidated by both since they both are very intuitive and easy to grasp, even by a 'blond gal' like myself. :)
Nope, haven't got the solution yet. I have a work-a-round though.. I manually assign the needed values to the props that 'lose' their settings by merging, then save the complete scene under a different name. Then I use the 'Save values" option in Reality so I don't have to re-assign the values when re-opening the scene.
When I reload the scene I simply call Reality and use 'Re-load values' so every setting is in place again.
I only wished it worked simply by merging...
Quote - I've just merged two scenes in fine. Both saved as full scenes. Second scene had some hair settings that had been altered and they were preserved..
Oi! That must mean it's something in my configuration.. I use the latest version of DS and the very latest of Reality..
Reggie, could you run one more test? Can you open a scene and then merge the same scene? Now do all duplicate items have their Reality settings preserved?
And if you choose "Show hidden items" do you have one or more items that are called Reality_Scene_Data?
No rush, do it if you feel like it :)
Innocent and beautiful John! :)
There will be a point in time when someone who started using Daz / Reality / Lux will take up photography and use the techniques he/she learned thanks to Paolo and find his/her results to be very good.
The hardest thing for a Daz user is to let go of all the 'tricks' learned to get a nice image and switch to thinking like a photographer.
I remember well Paolo saying so back in the days I sarted using Reality.
These days I roam the web and look at youtube vids photographers make to show their 'secrets'. Recently I search for 'Glamour photography' and there are many, many vids showing how to set up lighting for that.
THe wonderful thing is that with Reality you can apply those techniques and get the very same result you see in the vids.
I'd say: "Paolo for President"! :)
Quote - I don't think duplicates would save the settings as their names would change when they are merged. You get Genesis[2] instead of Genesis.
Unless you rename things before the merge, then I doubt it would work.
I'll try tomorrow.
I have tried it myself Reggie and you were right. Thank you for setting me on the right track!
- there is only ONE Reality_Scene_Data object these days.
- objects that exist in the scene and also in the scene that is merged (thus getting renamed by Daz to "-objectname- (2)" lose their Reality setting.
Problem solved! :)
Quote - There will be a point in time when someone who started using Daz / Reality / Lux will take up photography and use the techniques he/she learned thanks to Paolo and find his/her results to be very good.
The hardest thing for a Daz user is to let go of all the 'tricks' learned to get a nice image and switch to thinking like a photographer.
I remember well Paolo saying so back in the days I sarted using Reality.
These days I roam the web and look at youtube vids photographers make to show their 'secrets'. Recently I search for 'Glamour photography' and there are many, many vids showing how to set up lighting for that.
THe wonderful thing is that with Reality you can apply those techniques and get the very same result you see in the vids.
I'd say: "Paolo for President"! :)
Absolutely agree with all of that (except that I'm sure Paolo would not want to be president!). I was very keen on photography when I was a teenager. I had a manual SLR, light meter, etc., did a bit of my own D&P and had all the books out of the library. I've forgotten much of it, but what I do recall has been very useful when using Reality. Not only that, I've painlessly relearned quite a bit about photography through using Reality and it's given me the confidence to have a go at doing some profile portraits for our website at work. Having seen what the pros have produced in the past, I think I may be able to do almost as good a job (and save us a lot of money in these hard times!). It may end up being a disaster, but won't cost anything more than a bit of my time.
You're dead right about how it can be a bit of hurdle for people who have got into the paradigm of DAZ (or Poser) lighting—we had someone here recently with exactly this difficulty. It's easier for "dissidents" like me. I could never get my head around the shenanigans and anti-intuitive knowledge required to do good renders in DAZ and Poser's built-in systems. I guess those into fantasy and sci-fi will miss some of the jiggery-pokery that can be done with biased rendering, but, after all, special effects have to be faked in movies for exactly the same reasons that they do in Luxrender, and the solutions are similar: mattes, compositing, etc. Post-effects and clean up are almost as old as photography and movie-making themselves, after all.
Quote - The wonderful thing is that with Reality you can apply those techniques and get the very same result you see in the vids.
Thank you for pointing that out. That is what I mean when I say that, with Reality and Lux, "lights are predictable"
Lights in 3D programs generally behave in a weird way that only makes sense when you account for all the shortcuts and corners cut to get there. For example, the idea that you can turn off shadows should be look at as something very, very, very suspicious that you should not touch except in the most extreme circumstance. The fact is, because that option is available we all have abused it. I don't exclude myself. Guilty as charged. And you know what? It shows. An image with fake shadows will "smell" unrealistic. We might not be able to point out what it is but it just doesn't look right.
So, I'm glad that you and others are getting to appreciate the work with real lights. BTW, your suggestion to look at photography videos is defintely spot on.
Cheers.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
Quote -
- objects that exist in the scene and also in the scene that is merged (thus getting renamed by Daz to "-objectname- (2)" lose their Reality setting.Problem solved! :)
Glad you found it. The Reality settings for a given object in the scene are linked to the object based on its name. If it gets renamed then Reality doesn't know how to connect the information.
Imported OBJ, strangely, don't get renamed by Studio when you import multiple copies of them. That's why the settings only stick to one. With two objects with the same name there is ambiguiity which one will take the settings. Once they are renamed then they can be tretaed individually.
Cheers.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
Apropos to nothing whatsoever, I've seen over the last couple hundred pages of this thread a variety of issues people have had. Not saying that this is the issue with any particular problem; but, when I'm having difficulties doing something that I want to do either in studio or luxrender I ask myself a simple question. Am I trying to get my car to make coffee? Cars are made to take you from point a to point b; coffee makers are made to well.. make coffee. So, if you're having an issue with Daz Studio, Reality or Luxrender; are you trying to make the software do something it wasn't designed or equipped to do. Not all programs are capable of doing everything that we, as users, can dream up. That's why they make upgrades. Usually it's because enough people ask for one thing; or, one person asks for one important omission to be included. Think about that before you think that a particular piece of software is broken because it won't do what you want it to do.
Quote - Guys, I really have a serious 'Merge' problem and I hope anyone here can help me.
Somehow the Reality_Scene_data gets lost when I merge a .DUF scene into another existing .DUF scene.
Now I know I have seen Reality_Scene_data (1), Reality_Scene_data (2), ect in scenes before (back in the days when all worked well)
Example:
I load the 'SpotCam' scene I saved to disk. (top image) As you can see there is Reality_scene_data present in this scene.
Now I merge that same scene again. (bottom image) Now I would expect there would be another Reality_scene_data hidden object that should be named 'Reality_scene_data (2)' or something like that, but it isn't there!
Would any of you be so kind to try to reproduce it? I'd hate to bother Paolo with this if it is just 'me' who has this problem, cuz the he's busy enough as it is without having to spend time on silly questions from me.
Thanks in advance :)
I know this isn't related to what you're asking, but your screen capture has two aspects I'd like to understand (thanks!):
how do you get the Reality icon in the menu bar (or whatever that bar is called!) ?
Is what's shown in the preview window both a spot light and a mesh light all parented with a camera? Seems very useful...
Hello.
Reality 2.5.1.122 has been released. You can find all the details in the News section of our site:
http://preta3d.com/blog/2013/02/04/reality-2-5-1-122-has-been-released/
Happy rendering.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
You're very welcome.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
Quote - "Pobble said:" I know this isn't related to what you're asking, but your screen capture has two aspects I'd like to understand (thanks!):
how do you get the Reality icon in the menu bar (or whatever that bar is called!) ?
Is what's shown in the preview window both a spot light and a mesh light all parented with a camera? Seems very useful...
Go to 'Edit' > 'Customize' in DazStudio. Now find the Reality Icon on the left side (Think it is in 'Render'), then drag it to the right side (See image), then click 'Accept'. Your Daz Studio screen will flicker a few times and then your Reality icon will show on your main screen.
As to the second question: It are the camera and the spotlight you will have to parent to the meshlight. If you do it the other way around (parent the meshlight to the camera or spotlight) Reality will not see the meshlight anymore.
To position your meshlight: Choose the parented camera or parented spotlight in the viewport, then go to your scene-tab, select the meshlight, go to the parameters tab and position the meshlight with the sliders.
You will see the cam or spot 'go with the meshlight' in your viewport, so you will be able to place it exactly right.
Hope this helps :)
There might be a bit of overload. Please try again. Also make sure that you don't use download optimizers as they interfere with the normal download of programs.
Cheers.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
Quote - > Quote - "Pobble said:" I know this isn't related to what you're asking, but your screen capture has two aspects I'd like to understand (thanks!):
how do you get the Reality icon in the menu bar (or whatever that bar is called!) ?
Is what's shown in the preview window both a spot light and a mesh light all parented with a camera? Seems very useful...
Go to 'Edit' > 'Customize' in DazStudio. Now find the Reality Icon on the left side (Think it is in 'Render'), then drag it to the right side (See image), then click 'Accept'. Your Daz Studio screen will flicker a few times and then your Reality icon will show on your main screen.
As to the second question: It are the camera and the spotlight you will have to parent to the meshlight. If you do it the other way around (parent the meshlight to the camera or spotlight) Reality will not see the meshlight anymore.
To position your meshlight: Choose the parented camera or parented spotlight in the viewport, then go to your scene-tab, select the meshlight, go to the parameters tab and position the meshlight with the sliders.
You will see the cam or spot 'go with the meshlight' in your viewport, so you will be able to place it exactly right.
Hope this helps :)
Hmm, interesting, I don't have a "customize" option under edit
Regards, Michael
Quote - As to the second question: It are the camera and the spotlight you will have to parent to the meshlight. If you do it the other way around (parent the meshlight to the camera or spotlight) Reality will not see the meshlight anymore.
To position your meshlight: Choose the parented camera or parented spotlight in the viewport, then go to your scene-tab, select the meshlight, go to the parameters tab and position the meshlight with the sliders.
You will see the cam or spot 'go with the meshlight' in your viewport, so you will be able to place it exactly right.
Hope this helps :)
This helps a lot! It took me a minute to understand the mesh/cam parenting thing, but I agree this arrangement is better than remembering to unparent it every time. Thanks!
Quote - > Quote - On mine it was under the Window tab on Daz
On mine, it used to be under Edit or whatever and now it's under Window -> Workspace !
Ah, there it is. thanks to both of you.
Regards, Michael
Same as they did before...
Start a scene, then go to the queue tab.
Add another scene by clicking Add Files and selecting the next scene
You'll now get a warning that criteria has to be set for the queue
For a time based queue, click on the check box next to Time, this will enable the time values and change the time from 23:59:59 (HH:MM:SS) to what ever period you want.
Click on the Loop check box if you want the queue to be permanently processed.
You'll see a countdown in the status bar.
Quote - Same as they did before...
Start a scene, then go to the queue tab.
Add another scene by clicking Add Files and selecting the next scene
You'll now get a warning that criteria has to be set for the queue
For a time based queue, click on the check box next to Time, this will enable the time values and change the time from 23:59:59 (HH:MM:SS) to what ever period you want.
Click on the Loop check box if you want the queue to be permanently processed.
You'll see a countdown in the status bar.
I kind of figured that but what about the other 2 settings prog & noise??
I LOVE that feature Charley great for when going out or overnight
Noise works on how many pixels change in two subsequent flm generations of the scene. As the scene converges, less samples change up to a point where no samples will actually be different between two flm generating cycles. This lets you stop the scene when the changes would be virtually undetectable to the human eye.
Progress is just using the Samples per pixel criteria.
Personally I just use time, whether a scene is ready is subjective and I like to alternate scenes on a time basis.
Quote - Noise works on how many pixels change in two subsequent flm generations of the scene. As the scene converges, less samples change up to a point where no samples will actually be different between two flm generating cycles. This lets you stop the scene when the changes would be virtually undetectable to the human eye.
Progress is just using the Samples per pixel criteria.
Personally I just use time, whether a scene is ready is subjective and I like to alternate scenes on a time basis.
Time along with the refine brush like I been doing got it! I am finishing some 1.1 renders but did start a few with 1.2 to make suare all was lining up... on a quick look I see a marked improvement with the eye glass reflection
Edit Queue rendering is always a feature I recommend when discussing the Lux render on other forums when some folks bring up Lux render time concerns..
Quote - > Quote - > Quote - Guys check this out! I posted earlier on the DS Reality forum that Reality had been updated and now I get this. Such a flaming evil thing to say LOL!
I got the same thing trying to view the Garibaldi Hair plug in forum!
Ok Bloody DS site glitches again..
New TOS. Look at http://www.daz3d.com/forums/viewannounce/16350_508/
From their TOS:
"What will happen to existing threads for products available at other sites?
The forum section that contained these threads will simply be closed and will no longer be available."
There you go.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
I´ve a problem with transparency maps.
Every surface under it is somehow lighting up.
I rendered it with SLG. Without there is no problem but i like to render fast so i want to work with it.
Heres an image, with and without transparency maps. The eyelashes have the same problem.