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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
...haven't installed the latest update to Reality yet.as it does not address the camera and old file issue.The geografting issue means nothing to me as I don't do erotic nudes or even have the genitals as I don't purchase figure bundles, only the base figures.
I'm basically tired of paying for broken software on my limited budget. 1.25 and 2.5 never had these issues.
Genitals aren't the only geografts. Some characters have tails and hooves (like Minotaur 6) and other things like genesis with four arms and a third eye, all of which are geografts. I thought it was DS 4.7 that broke some of the cameras? Sorry.
John
...just uninstalled everything relating to the Reality plugin. Tired of wrestling with this. If the vendor cannot or will not fix these issues then I guess I just have to accept the loss. A real bite when one is on a tight budget.
Genitals aren't the only geografts. Some characters have tails and hooves (like Minotaur 6) and other things like genesis with four arms and a third eye, all of which are geografts. I thought it was DS 4.7 that broke some of the cameras? Sorry.
John
...don't have any of those either as I don't do fantasy stuff so the new update is pretty much meaningless to me.
As to the cameras, think it was the first update after the release as I never had an issue with which was the rendering camera until then.
While I feel for you and any issues you might be having, I an tired of users saying something is broken because "they" are having problems. This tells all who read that statement that it could be universally true and could set a precedent for interested buyers. If software is broken, then all users would experience the problem, and I am not experiencing what you seem to be. I have only loaded a few older, pre R4 files and only had to adjust a few shaders (which I expected) and so far, whatever camera i am on in DS, transfers to R4 fine, I assume that is what you mean by flagging.
Granted there are a few quirks that bother me, but nothing that makes it broken or unusable to me and Paolo has done a good job of addressing posted issues and releasing some fixes.
...considering I have to use a workaround that strips all Reality information from the scene which results in the tedious process of resetting all the shaders manually again just to fix the camera issue, I call that "broken", especially since the issue is known and still has not been fixed. It shouldn't come down to the user having to deal with "fixing" issues in the software.
Again never had this type of issue occur between 1.25 and 2.5.
It worked for me just fine before this update too. I even loaded up my old R2.5 scenes and (to my surprise) didnt have any problem with cameras. I still use callad's lights and they come with cameras so I have a few in a scene. The only thing that didnt load was my material settings but thats understandable since R4 handles shaders differently.
.......the shader issue should have been mentioned up front,and again not sure if that is a Reality4 or Daz 4.7 thing (or both) as the rollout of the two was so close together (about 12 days). There was something about shader handling in the 4.7 release as well.
The idea that Reality 4 only works with new scenes created for it was a real blow. I can render a scene created in Daz 4.5 in 4.7 without having to mess around adjusting the shaders (or for that matter a scene rendered in Reality 1.25 in Reality 2.5). I expected the same would hold true with Reality4. I was in the middle of working with a fairly complex scene when ver 4 was released with all the materials and mesh lights already set. I moved it to Ver. 4 as the characters used SSS which the new version now handled.. Of course none of the materials appeared in the Reality materials tab.
The idea of having to rebuild the scene from scratch was ridiculous. Then someone mentioned a different workaround that would get the objects to show up but unfortunately that stripped all the Reality settings out as it was considered a "fresh scene". So spent a lot of time going through and recreating the materials. The 4.0.3 update caused me to have to do this all over again. Then comes the 4.0.5 update, and while I was pleased to find the surfaces showing in the materials tab, now I had the camera bug to deal with. To fix that I learned I need to go through several steps to effectively "create" a new version of the scene on my end which again kills all my Reality surface settings and mesh light assignments. Basically, what has been occurring in 4.0.5 is the Default Camera, (which is the one I always render through) is dropping off the Cameras Tab and one of the "work" cameras (like say "Camera 3" or "Camera 5") is randomly selected as the Daz "designated" one for rendering.
Since the new update hasn't addressed this or the shader issue, I did not bother to install it. I don't use geografting (which is the major "fix" in this version) since like I mentioned I do not do erotic scenes (actually have none of the Gen 6 Pro bundles) or scenes with fantasy creatures which may use it.
I just wanted to be able to render older scenes I created in the latest version without having to go through all this trouble again and again each time a new update is issued. Since this apparently is not going to happen I uninstalled Reality from my system completely. Disappointed, as I am on a very tight income and particularly don't like spending money on something that doesn't work as it should. I am past the 30 day return period because I hoped these issues would have been fixed in a subsequent update so now I just have to eat the cost and move on.
Uhh... That's not what most people use geografting for. :) Many creature figures and, of course, the Genesis and Genesis 2 Bot Armour make extensive use of geografts. I suspect that physical facial hair props might also be geografts in a few cases, too.
...I have yet to use it. Most times I hear about geografting, it is in relation to Gens on Genesis figures tails or other appendages on creature/monster morphs.
I primarily use regular hair content, much of it manually fitted so the style and movement morphs are not screwed up by the weight mapping. I also have Garibaldi Express, however that is based on 3DL curves, not fibremesh. To render it in Reality I have to convert the hair to an .obj.
It's the same with HD, Animation and Daz Dynamics, I have no use for either of those features either.
All I want to do is be able to render a scene without having to rebuild the materials every time there is another update because either they won't show in the materials tab or the rendering camera I am using is deleted from the cameras tab, requiring the workaround that strips all the Reality data from the scene. These are two significant issues that need to be fixed as they seriously impact the workflow.
Just because you don't have any use for those features doesn't mean others don't and your implication that those that do use such features do so merely for dubious reasons is out of order.
You also seem to forget that Reality is only a path to Luxrender and cannot alter how that works.
...however it is within Reality where these issues are occurring as they show up before submitting the scene to Lux. .
Reality is the "interpreter" so to say that translates Daz 3DL instructions into something which Lux understands and somewhere it is messing up on the syntax.
I still feel that correctly recognising materials and camera assignments is a basic function that is more important for the translation of instructions to Lux than say, geografting, and should have been dealt with in the first patch as this was a major concern from a number of people over on the Reality/RDNA forum
I'm not having problems with cameras or materials since the first update.
...what version of Daz Studio?
...and have you tried opening a scene worked that was worked on in 2.5?
I would post screen shots of what I am getting however I already uninstalled Reality.
Hi KK!
I've not had any of the issues you have noted either, using DS version 4.7.0.12. But I have only used Reality 4 with new scenes, not scenes set up in any earlier versions of Reality. I also don't use the default camera either (as I recall either Reality 1/2 or Luxus required a new camera, don't remember for sure, but I got into the habit of creating a new camera anytime I set up a new scene DS).
I think that most of your issues are coming from trying to render/use old scenes set up in earlier versions of Reality. To get consistent/reliable results you would probably need to do as was suggested over in the RDNA forum to ensure that any old code/settings that are causing problems are cleared and no longer cause problems if you wanted to continue to use those assets (and Reality 4) in future projects. I realize that you feel Reality 4 should seamlessly open/use projects from earlier versions, but this may actually be a much more difficult task than what you think. Reality 4 is completely new code. As I understand it, Reality was completely re-written to make future development of both the DS and Poser plugins from the same code base. That is why DS users never saw a Reality 3, which was only released for Poser. IIRC, Reality 4 actually uses a lot of the code developed for Reality 3, which was totally different than the code for Reality 1/2. So the simple fix you feel should have already been made, may not be that simple at all.
It's easy to understand how these issues may have been missed by Paolo and the beta program/testers. Having done a fair amount of beta testing myself in the past year or so, I seldom used old projects. I would guess that most, if not all of the beta testers were primarily focused on testing Reality 4 with new scenes. Another important note here is that old scenes can have embedded information for other plugins/features that may cause problems with any external rendering application. Again, since Reality 4 is new code, the fact that a scene works perfectly in Reality 1/2 does not necessarily mean it will work perfectly in Reality 4, as there may be things in the scene that the previous version(s) of Reality was perfectly happy with, and that the new version has issues with. This also makes "fixing" the issue very problematic for the developer, as duplication of the problem on his/her end may be virtually impossible.
I think it's also very important to try to put yourself in Paolo's shoes for a few minutes. Keep in mind he is only one person, and there are only 24 hours in a day. If there isn't enough time to fix everything, he will need to fix the problems that do not have any work arounds, and/or that affect the most users first. We have no idea what, and how many, bug reports Paolo has gotten. I would guess that there are several hundred to maybe even several thousand users, so forum "chatter" probably is not very representative of the user base (not to mention that forum chatter is often the last place where a developer may look to search for issues, anyone who really needs/wants things fixed needs to go through the official method for reporting). As a result, we probably have no idea what issues the majority of users need fixed.
So, even though these other fixes aren't important to you, and seem totally worthless to you, there may actually be some very compelling reasons for ranking them higher on the priority list than the ones you are having problems with. For example there may have been many more bug reports, support tickets, emails, etc. for the need to fix the issues with geografting compared to the issues you are experiencing. Additionally, it may also be seen that fixing bugs that help the program going forward will take precedence over fixing bugs going backwards (i.e. after the initial few weeks, fixing the bugs that users experience when assembling new scenes could be ranked higher than fixing bugs experienced by users working with Reality 1/2 scenes - this could be based on the fact that after the initial 1-3 weeks most users will primarily be setting up new scenes, not re-rendering/using old scenes).
I realize that this doesn't help you at all with you current issues, but possibly it can help you to understand that what you think should be a simple, quick, and easy fix may actually not be that easy, and the way you want to use the Reality may be much different to the way others (most?) are using it. I'm sorry for your problems. I've got to say though that IMHO Paolo does excellent work, and has always provided outstanding support for his products. Please keep in mind he is only one person, and we (the users) really have no clue what his work load might be right now supporting the release of Reality 4 for both DS and Poser. We also have no idea with regard to what might be an easy fix and what might take a lot of work to fix. Sometimes the things that look like a very simple fix to the users, are actually very complicated and extremely difficult to fix.
....well, I was in the middle of two projects when both 4.7 and Reality4 were released. For one, a contract project, I had to just go back to 3DL as there was a time deadline involved and I wasn't about to rebuild everything from scratch which, at that time, was the only solution. The other was to run a comparison between how far could I push the built in 3DL with AoA's advanced lights and SSS shaders and how the same scene would appear with an unbiased render engine.
Reality 2.5 didn't have the SSS handling so I waited as I heard Reality4 would. There was nothing to indicate at release time that the new update would not work with older files. I, along with many others, were at a loss when we would see the materials tab came up empty after we were given the understanding that 2.5 scenes would work in ver. 4. I even experimented with older scenes never opened in any version Reality and the same happened, no materials in the materials tab. When I would submit the same scenes to 2.5 everything worked fine. So it wasn't just whether or not the scene was opened/created in an older version of Reality beforehand, it was any scene created prior to the installation of Reality4.
Again, at the time, the only solution was to rebuild build the scene from scratch. Only later did someone discover a workaround that made it appear as if an older scene was a newly created one though the downside was, all previous Reality date was stripped out and had to be rebuilt/reset from scratch (including mesh lights).
In 1.25/ 2.5 I always used the Daz default camera as the rendering camera and never had an issue with it. Even in the first release version of Reality4 I could render through the Default Camera. It was after one of the following updates (I believe 4.0.5) that I started experiencing these camera assignment issues. Also with each new update I still had to reset all the materials in the scene by hand even though the scene had already been saved in the previous version Reality4. So what happens when 4.0.9 comes out?
If the materials issue was a known quantity that would never be resolved, it should have been mentioned up front.
From what you mentioned concerning the code for Reality4, it seems us Daz users have our own version of "DSON" now., it works, but only in certain conditions and not without more effort on our end. I have my thoughts about this but won't take it any further.
On the other hand it appears from comments I have been reading on the Unbiased Renders thread that the latest version of Octane with the Out of Core feature runs pretty smoothly and is still fast. Lux terminated further development on their GPU/CPU hybrid rendering due to ongoing issues and the fact it didn't offer that much more speed advantage over pure CPU rendering. This has made me sit back and reconsider. I have continued to lurk on the thread and seen some very excellent results with Octane. This is leading me to believe that the better solution to all this might be to find some way to scratch up the funds necessary for both the render engine/plugin and a slightly beefier Nvida GPU (my current Nvidia GPU has only 1GB VRAM which wouldn't even handle the Geometry in the current scene I have been struggling with).
My light setups have mainly been basic 3 point lighting with a key light, fill light and back or top light, using mesh lights. I have a few questions:
1) What is a curved light generally used for as opposed to a mesh light?
2) Are there any recommended light setups apart from 3 point lighting?
Dearest,
I ordered Reality 4 plugin for DAZ but I cannot even install it, after clicking the Windows32bit. exe a window pops up noticing my "OS is older than the minimum required to install Reality"
I nowhere could / can find minimum PC system requirements for Reality so this is a big disappointment.
So , what ARE minimum PC system requirements for Reality?
It would be good for a starter DAZ and affiliates would clearly mention more information on functionality and compatibility!!!
I had to ask for refunds for DAZ models apps and installments that later turned out not to function on my old machine.
I am starting to get somewhat annoyed now.
----------------------------------
Onderdeel Waarde
Naam van besturingssysteem Microsoft Windows XP Professional
Versie 5.1.2600 Service Pack 3 Build 2600
Fabrikant Microsoft Corporation
Systeemfabrikant Hewlett-Packard
Systeemmodel HP Compaq dc7600 Small Form Factor
Systeemtype Op x86 gebaseerde pc
Processor x86 Family 15 Model 6 Stepping 4 GenuineIntel ~2992 Mhz
BIOS-versie/datum Hewlett-Packard 786D1 v01.59, 1-3-2007
SMBIOS-versie 2.4
Map van Windows C:\WINDOWS
Systeemmap C:\WINDOWS\system32
Opstartapparaat \Device\HarddiskVolume1
Landinstelling Nederland
Hardware Abstraction Layer Versie = "5.1.2600.5512 (xpsp.080413-2111)"
Gebruikersnaam HP15247275837\Administrator
Tijdzone West-Europa (standaardtijd)
Totaal fysiek geheugen 4.097,00 MB
Beschikbaar fysiek geheugen 1,74 GB
Totaal virtueel geheugen 2,00 GB
Beschikbaar virtueel geheugen 1,95 GB
Ruimte voor wisselbestand 6,75 GB
---------------------------------------------------------------------------------
NVDIA graphics card:
NVIDIA Systeeminformatierapport gecreëerd op: 03/13/2015 16:06:01
Systeemnaam: HP15247275837
[Beeldscherm]
Besturingssysteem: Microsoft Windows XP, 32-bit (Service Pack 3)
DirectX-versie: 9.0
GPU-processor: GeForce 210
Stuurprogrammaversie: 340.62
DirectX-ondersteuning: 10.1
CUDA-kernen: 16
Kernklok: 589 MHz
Shader-klok: 1402 MHz
Geheugengegevenssnelheid: 1000 MHz
Geheugeninterface: 64-bit
Geheugen 1024 MB
Geheugentype: DDR3
Video BIOS-versie: 70.18.FF.00.64
IRQ: 16
Bus: PCI Express x16
Apparaat-ID: 10DE 0A65 21C11ACC
Onderdeelnummer: 0872 0000
[Onderdelen]
NvUpdtr.dll 15.3.33.0 NVIDIA Update Components
NvUpdt.dll 15.3.33.0 NVIDIA Update Components
NVCPL.DLL 6.14.13.4062 NVIDIA Windows Display driver, Version 340.62
nvCplUIR.dll 7.8.800.0 NVIDIA Control Panel
nvCplUI.exe 7.8.800.0 NVIDIA Control Panel
nvWSSR.dll 6.14.13.4062 NVIDIA Workstation Server
nvWSS.dll 6.14.13.4062 NVIDIA Workstation Server
nvViTvSR.dll 6.14.13.4062 NVIDIA Video Server
nvViTvS.dll 6.14.13.4062 NVIDIA Video Server
nvMoblSR.dll 6.14.13.4062 NVIDIA Mobile Server
nvMoblS.dll 6.14.13.4062 NVIDIA Mobile Server
nvDispSR.dll 6.14.13.4062 NVIDIA Display Server
NVMCTRAY.DLL 6.14.13.4062 NVIDIA Media Center Library
NVOGLNT.DLL 6.14.13.4062 NVIDIA Compatible OpenGL ICD
nvDispS.dll 6.14.13.4062 NVIDIA Display Server
NV4_MINI.SYS 6.14.13.4062 NVIDIA Windows XP Miniport Driver, Version 340.62
NV4_DISP.DLL 6.14.13.4062 NVIDIA Windows XP Display driver, Version 340.62
PhysX 09.14.0702 NVIDIA PhysX
NVCUDA.DLL 6.14.13.4062 NVIDIA CUDA 6.5.14 driver
nvGameSR.dll 6.14.13.4062 NVIDIA 3D Settings Server
nvGameS.dll 6.14.13.4062 NVIDIA 3D Settings Server
---------------------------------------------------
cheers
http://preta3d.com/purchase-reality-4/#requirements
For Poser Edition: Poser 9/Pro 2012 with SR3 (Service Release 3) installed or Poser 10/Pro 2014 with SR3 installed.
For DAZ Studio Edition: DAZ Studio 4.6 or higher
Mac OS: 10.7 or higher
Windows: Vista or higher
CPU: dual-core or higher. While Reality will run with a single core machine, physics-based rendering requires high-cpu computations, so multiple cores are advised.
RAM: 4GB or more.
Thank you for your answer....but where can I find these minimum PC requirements on the DAZ product page of The Reality 4 plug in?
It would have kept me from buying it.
Kind regards.
Syphonaptera If you don't have the right OS, DAZ has a 30 day money back policy.
Thnks for the reply , I know that ;)
But I really would like DAZ to present the minimum PC requirements on their sales-products page.
Cheers.
AFAIK Reality is a "Reseller" item rather than a brokered item, so it would be up to the vendor to provide this sort of details
I find it sad now. I remember well the days when Paolo's threads will fill to 100 pages in a few hours.
I think it is more than likely due to all the competition that was there already and that with now more is appearing well who knows.. With the likes of Luxus, Pose 2 Lux, Octane (if you can afford it) and quite a few more and now with the release of native Iray support for Daz Studio who knows..
I think that the main issue really is that Reality relies heavily on the folks making Luxrender the better Luxrender gets and on how fast they can add features into the program then the better for Reality and from what I have seen the next version of Luxrender is supposedly slower but supposed to make better use of the CPU..
Still not sure on GPU or Hybrid rendering with it as GPU rendering seems (for me at least a hit and miss affair), I have been playing around with it and Reality which is a good piece of software, I have all version from 1.25 up to 4 and some of it's features are quite cool..
But with the arrival of native Iray support for Daz Studio things start to get interesting and well so long as it is kept constantly updated (the one thing that is rather good with Reality is the constant program updates and its constant Acsel Shader updates) and that support by Daz and the vendors is strong well who knows what the future will bring for Daz Studio with Iray will be a case of wait and see..
I think it is more than likely due to all the competition that was there already and that with now more is appearing well who knows.. With the likes of Luxus, Pose 2 Lux, Octane (if you can afford it) and quite a few more and now with the release of native Iray support for Daz Studio who knows..
I think that the main issue really is that Reality relies heavily on the folks making Luxrender the better Luxrender gets and on how fast they can add features into the program then the better for Reality and from what I have seen the next version of Luxrender is supposedly slower but supposed to make better use of the CPU..
Still not sure on GPU or Hybrid rendering with it as GPU rendering seems (for me at least a hit and miss affair), I have been playing around with it and Reality which is a good piece of software, I have all version from 1.25 up to 4 and some of it's features are quite cool.. But with the arrival of native Iray support for Daz Studio well so long as it is kept constantly updated and support by vendors is strong well who knows what the future will bring for Daz Studio with Iray will be a case of wait and see..
New release 10x faster
http://forum.runtimedna.com/showthread.php?97658-Is-Lux-1-5-Going-to-get-Faster-because-of-GPU-Rendering
http://preta3d.com/sneak-peek/
New release 10x faster
http://forum.runtimedna.com/showthread.php?97658-Is-Lux-1-5-Going-to-get-Faster-because-of-GPU-Rendering
http://preta3d.com/sneak-peek/
Ahh awesome was not sure if what I had read was right or not, and by the look of it I was wrong on that part about the next version of Luxrender.. :D
Well . maybe this is a general tip for DAZ to communicate this to the vendors! The Daz minimum requirements also are compatible for Windows XP , logic alone would suggest all products available from all vendors are compatible with Windows XP , unless otherwise notified, just brainstorming here.... :)
Anyway, thanks for the replies all...
Cheers
I just started playing around with Reality this week (before last week my old machine would have had a rough time with it). I have not gotten into the GPU rendering but so far I really like the product I can make with very little effort in terms of dealing with lighting, shadows, etc. But the main thing I like, because most of the image-production work is done by LuxRender not Reality, is that Reality has a very nice and mostly-intuitive (to me) UI. I have not tried Iray but if it doesn't have as intuitive a UI, I would probably stick with Reality.
I just started playing around with Reality this week (before last week my old machine would have had a rough time with it). I have not gotten into the GPU rendering but so far I really like the product I can make with very little effort in terms of dealing with lighting, shadows, etc. But the main thing I like, because most of the image-production work is done by LuxRender not Reality, is that Reality has a very nice and mostly-intuitive (to me) UI. I have not tried Iray but if it doesn't have as intuitive a UI, I would probably stick with Reality.
I prefer Reality over Iray as I find Reality easier to use
New release 10x faster
http://forum.runtimedna.com/showthread.php?97658-Is-Lux-1-5-Going-to-get-Faster-because-of-GPU-Rendering
http://preta3d.com/sneak-peek/
...to get that speed advantage you need a CPU with AVX starting with the i7 2600 series Sandy Bridge CPUs (LGA 1155). Older i7s like the Nehalem/Bloomfield 930 I have (which uses the LGA 1366 socket) don't have this feature.
For those of us with even slightly older systems, it would require both a costly CPU motherboard,(and most likely, memory) upgrade which would make the latest version of Octane (with the Dazplugin) look like a good deal.
So, no speed bonus here.