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
There is no need for an uninstaller with Reality. Just delete the Reality folder in the plugins folder and delete the Reality_DS folder in C:\Program Files. The delete key is the uninstaller :)
In any case, yes, the installer will take care of all that is needed to upgrade a previous version.
Cheers.
Two possibilities:
- When you copied the number you also copied blanks and newlines. Try again.
- When you are typing you use lowercase letters. The serial number has uppercase letters.
To anybody reading this: the registration window does work. It has been used by thousands of users to register Reality. If the input is not accepted then you are entering the wrong data. Double-check and try again.
Hope this helps.
All is fine, it has been for days. Also, some of the people who posted in that thread were simply entering the wrong serial number. If the registration window does not accept your serial number, for example the buttons remain greyed, it means that you are entering the wrong data.
Literally thousands of users registered Reality 4 and they are using it to render as we speak, so the registration process works. If the registration window does not accept the input it means that the input is wrong, as, for example, entering lowercase letters when the serial number is all uppercase.
If the registration reports that the number is invalid please send me your license information to reality at preta3d dot com with the verbatim description of the error message. There are situations where the previous serial number does not match because the users did not enter the registration data correctly. We can fix that very easily.
You can also use this page http://preta3d.com/retrieve-reality-license/ to retrieve your previous serial number.
Hope this helps.
Please send me an email explaining what is happening. Forums are not the best way of handling tech support.
Thank you.
We have tested that scenario many times, and there are no issues in having multiples of anything in the scene. There is something else that is happening in your case but that is not how you described it.
If you can provide a description of the steps involved then I can look into it but there is no problem in having as many Genesis figures as you want.
Cheers.
Enchanted Pixie, Reality is actually very fast in handling its own operations. Our tests showed that it takes a fraction of a second to convert the materials for a whole Genesis figure.
Having said so, it came out after release that, In certain Windows configurations, with certain disks the database that we use reverts to verifying everything that is written, causing the slowdown that you have experience. I'm working on it and I hope to have a solution in a matter of days. It's avery specific issue that, once is resolved, will stop affecting Reality. We had about 80 beta testers on board for this release and this issue never came up. It is a very specific combination of OS and drives that was not present in our testing.
The code is actually very fast, faster than before. It's just this single issue that doesn't not happen to everyone, and that is the only possible restrain in achieving full speed.
I appreciate your patience and I will be announcing when the new update is ready.
Cheers.
BTW, I can't go back pages to read these posts, I simply don't have the time. If you have any open issue please contact me via the Support form in our website: http://preta3d.com/support/
Thank you.
There is no need for an uninstaller with Reality. Just delete the Reality folder in the plugins folder and delete the Reality_DS folder in C:\Program Files. The delete key is the uninstaller :)
In any case, yes, the installer will take care of all that is needed to upgrade a previous version.
Cheers.Thankyou for the assurances, and this is not sounding as bad as I had initially thought. I am not assuming what was done, only warning about a potential bad situation while uninstalling stuff in the Content Library of Daz Studio.
Just like using DIM, there is a critical note for some database engines and CMS (Content Management Service).
NEVER install stuff with Daz Studio running. It turns CMS into a pretzel, and then the smart tab will have issues, etc. Been there twice, once with DIM, and the second time weeding out old saved scenes from my content library (using the OS file-manager).
The second time I learned the second half of that rule. :red:
NEVER uninstall stuff with Daz Studio running.
(EDIT)
As I have noticed, after exiting the Daz Studio window, it can take some time for it to flush out all the ram and cache it was using before completely closing down. I would advise to make sure Daz Studio has completely done its close out and shut-down properly, before messing with files in the Content Library with the 'Delete' key.
some users have reported this, and a bug report was filed. Paolo is usually very good about fixing his software but that's all I can tell you.
In the mean time if you remove the R4 plugin from your plugins folder you can continue to use R2 until this is sorted or you might be able to get a refund. I'm going to wait it out but I feel your frustration.
...same here. It's an annoyance but not crippling for me. Overall I really like the new features and revamped UI enough to put up with it until there is a fix. The fact that when you save the file your settings are automatically saved (in 2 & 2.5 you had to remember to update/save the settings as well). The other nice thing is you can now minimise the Reality window to make adjustments to the scene without having to first close the Reality UI it then reopen it again. Both of these really help with the workflow.
On possibility that could be causing this in my case is I use multiple drives. I have all the main applications/plugins in the Programme Files folder on the C: boot dive but all my libraries/runtimes/scenes.on the larger D: drive. I'm an old XP user who rarely liked dealing with the windows "Documents" folders as the default. as I have my on system of oganistion.
There have been a couple operational issues that did concern me but each only occurred once so far.
--First I had the plugin get stuck in an infinite loop when changing surface parameters, forcing me to close it through Windows Task Manager.
--Second in one session Reality just stopped working (got a windows error message stating so) requiring me to save the scene, close and then reopen 4.7.
There was also the minor issue of AoA's advanced lights showing up under Cameras even though they were deleted from the scene and replaced with the Reality Sun before I opened Reality4 for the first time to run some tests.
We have tested that scenario many times, and there are no issues in having multiples of anything in the scene. There is something else that is happening in your case but that is not how you described it.
If you can provide a description of the steps involved then I can look into it but there is no problem in having as many Genesis figures as you want.
Cheers.
I described the problem in more detail over at RDNA the official Reality forums, sorry I do not have time to go into any more detail.
Unfortunately I am one of those hit with several of the problems. Reality is for me unusable, if I have not seen fixes by the end of 30 days I will return it.
So I got it working, any tips for the eyes, mine render all one color aside from the eye whites are all white
dkgoose, check if you have a texture in the cornea. If so then click on the transmission texture and in the Texture Editor convert the texture type from what it is to Color. Then set the color to pure white.
Cheers.
...same here. It's an annoyance but not crippling for me. Overall I really like the new features and revamped UI enough to put up with it until there is a fix. The fact that when you save the file your settings are automatically saved (in 2 & 2.5 you had to remember to update/save the settings as well). The other nice thing is you can now minimise the Reality window to make adjustments to the scene without having to first close the Reality UI it then reopen it again. Both of these really help with the workflow.
On possibility that could be causing this in my case is I use multiple drives. I have all the main applications/plugins in the Programme Files folder on the C: boot dive but all my libraries/runtimes/scenes.on the larger D: drive. I'm an old XP user who rarely liked dealing with the windows "Documents" folders as the default. as I have my on system of oganistion.
There have been a couple operational issues that did concern me but each only occurred once so far.
--First I had the plugin get stuck in an infinite loop when changing surface parameters, forcing me to close it through Windows Task Manager.
--Second in one session Reality just stopped working (got a windows error message stating so) requiring me to save the scene, close and then reopen 4.7.
There was also the minor issue of AoA's advanced lights showing up under Cameras even though they were deleted from the scene and replaced with the Reality Sun before I opened Reality4 for the first time to run some tests.
Is multiple drives a thread in this slowness? I'm using multiple drives, both are internal SATA 3GB/s 7200 RPM seagate drives that are optimized, both have over half their capacity unused.
...I'm thinking it could be as when I start up 4.7, and then load a scene or content which is on my "runtime" drive, the system has to swap between that drive and the C: Drive where the application resides. I imagine that if Reality is scanning the scene as it (the scene) loads, it then has to do the same as it is on the C: drive as well.
I also do not use the Windows default library folders for content or scenes as 1, it they are on the smaller C: drive and two, I tend to like a more streamlined setup that is organised better for my workflow and found always having to go to the default Win library folders to be somewhat of a bother (even with programmes like Excel or Word).
Reality does not scan the scene files. When you add anything to the scene Reality gets the object/figure from Studio's memory and converts the materials on the fly. This operation takes a very, very small fraction of a second. The issue with the slowdown, which does not affect everybody, it's an estimated 1/40 of the users, is caused by Reality writing to a database some information to keep track of the shaders.
I have optimized that function so that no slowdown happens.
I have a new build under test with people who have experienced this issue and I'm waiting for their results. Once it's verified to work I will release the update to the public.
Thank you again for your patience.
...thank you for the clarification.
Was attempting to figure the possible cause on this end. Ideally were everything on a single drive, all programmes and call ups should access quicker than having to deal with searching across multiple drives. At the time I built my system system,1TB drives were still a bit expensive and the largest practical format available (2TB drives were our but at the time, reliability was an issue). Today 3 - 4 TB seems to be the norm with 8TB (using sealed Helium technology) being the largest commercially available HDDs.
I use distributed rendering and with R4 question arose - [bla-bla-bla Warning: 3] [DServer:18018] Film file "NONE" not found! Camera Response Function will not be applied.
This happens if I stopped the session and then starts a new one. With R2.5 this did not occur.
maxarader, totally benign warning, you can ignore it.
thanks!
I'll send a pm if you want or if someone else can answer, here's an example of what I'm getting with the eyes, this is even with what you said to do?
...OK a big issue this time.
Was testing out loading an older scene into R4.
First, opened the Reality version of the bus stop scene with the two girls I was originally working with in 2.5 (originally created in Daz 4.6). When I opened the Reality4 UI and clicked on the Materials tab, the only surfaces that were listed were for an instances group I used to create the the car's right side tail lights.
So next,went back to the original 3DL file of the bus stop scene (never opened with Reality2.5), opened it, took out the AoA lights and added the Reality "Sun" (from the Reality, not the Reality Add Ons folder), and saved it under a dummy name. Just to make sure settings were saved properly, I closed then reopened the scene file saving it again in case 4.7 handled textures differently. However, after I opened the Reality4 UI and clicked on the Materials tab, once again, only the one instance group was listed.
I even went as far as making a minor change to the original 3DL file, saved it in 4.7, closed the app down, reopened it, and went through the same process as outlined above overwriting the previous R4 test version save, only to once again get the exact same result. I find it odd too why the Material tab is only seeing an instanced group.
Technically, Reality4 should have treated this last attempt as a brand new scene since it was never previously processed or rendered in any other version of Reality/LuxRender.
When I tested a totally different scene created in .4.6 (which I saved again in 4.7) and never bought into Reality previously, nothing showed under the Materials Tab.
So this is a bit disconcerting as it appears that if a scene was not completely created in 4.7 none of the surfaces will register in Reality4. Odd though, one test scene I did the other day used saved scene subbset of my Leela character (created in 4.6) and all her textures show up fine in the Materials Tab.
Am completely mystified by this.
Yea I've had the problem with previously built scenes not showing up in Reality and therefore not transferring to Lux.
...is there any kind of workaround? As I mentioned I really don't want to rebuild this from scratch as it was very difficult to compose and included some tricky kitbashing.
I'm wondering if it isn't due to an unforeseen conflict as the rollout dates for the general release of Daz Studio 4.7 and Reality4 were only 12 days apart.
Both the original and Reality versions of the scene open without issue in 4.7 and render fine in 3DL.
This would be a huge disappointment if it will not support rendering older scenes after all the waiting. I really like the new UI and improved features.
I've had similar problems, although I never use instances so I don't know about that part. Also, all of my scenes have been exported to Reality 2.5 at some point and then saved, so I don't have any "clean" old scenes to test.
This problem happened on a scene I'd done a lot of work on that I had previously done test renders with in R4, but suddenly, after reopening it, no new models of objects (of any kind) I added would show up in Reality. I needed to change some objects in the scene so this meant I couldn't finish the render as planned.
The only solution I could come up with was to save everything as a scene subset and load the subset into a fresh scene (I restarted DS for good measure). Everything was fine after that. Clearly only the specific objects you select when saving as a subset are saved—no Reality data, etc. As all poses and other object properties are saved in the subset I didn't have to re-do anything.
I have some problems with Reality 4, 64 bit for Studio. Reality doesn't update correct with Studio. Lights and cameras I deleted are still in Reality also it choice the wrong camera when rendering.
For the rest is it an intresting programm. But version 2.5 was better integrated in Studio. I read there will be an update?
When is the relase of this update?
Ditto. Wanted to re-render a pinup (girl lying on car Cars album style), got nothing, gave up on old scenes for now. :down:
I've had similar problems, although I never use instances so I don't know about that part. Also, all of my scenes have been exported to Reality 2.5 at some point and then saved, so I don't have any "clean" old scenes to test.
This problem happened on a scene I'd done a lot of work on that I had previously done test renders with in R4, but suddenly, after reopening it, no new models of objects (of any kind) I added would show up in Reality. I needed to change some objects in the scene so this meant I couldn't finish the render as planned.
The only solution I could come up with was to save everything as a scene subset and load the subset into a fresh scene (I restarted DS for good measure). Everything was fine after that. Clearly only the specific objects you select when saving as a subset are saved—no Reality data, etc. As all poses and other object properties are saved in the subset I didn't have to re-do anything.
...that's why I don't understand why it didn't work when I used the original 3DL backup of the scene that was never exported to Reality 2.5 (I renamed it so as I mentioned, it should have been treated as a "new" scene). However, this lso doesn't explain why the second test I did of a randomly chosen scene created in 4.6 (that was never exported to Reality) didn't work.
I'll try the scene subset approach.
This seriously needs to be fixed as (like I also mentioned) there was less than two weeks between the rollout of 4.7 and Reality4 so others like ourselves would have spent time working on scenes that were first started in 4.6. If it isn't we are still within the 30 day limit (though while Daz is only offering the upgrade through their store for another 5 days they better still honour the full 30 day return policy).
I still feel Reality is the better solution compared to Luxus (and has both excellent documentation and quicker support which the latter seems to be lacking in), but given the situation that would be the only option for exporting to LuxRender if this indeed is a permanent situation . The only other route would be to export through Blender and that UI is a nightmare to deal with compared to Reality's.
Ditto. Wanted to re-render a pinup (girl lying on car Cars album style), got nothing, gave up on old scenes for now. :down:
I have a render running right now so I can't test this (I don't have 4.7 installed yet either), but I seem to recall reading at RDNA that deleting the item in your scene that isn't showing/updating, then immediately un-deleting it (undo) will force Reality to read it.
I had an instance where the torso on G2F turned black (the rest was fine), no matter what I tried, I couldn't get it to not render black (pure black, no highlight or anything), even telling reality to reload the original setting didn't work. I deleted G2F, then un-deleted, and the torso was back. unfortunately this reset all the settings to the default (so far I haven't been able to reproduce this error).. This may work with some of your problem scenes.
...I'd have to do that for everything in the scene below. (3DL version attached). The list of items used is twice as long as the Content tab can display in the Daz UI (set to full screen view).
Quick question (and maybe this has already been addressed but can't find it)...
Basically my problem is that the Pure GPU rendering option is greyed out.
I'm using Reality 4, Lux render 1.31 64 Bit with a GeForce GTX 650 Ti BOOST. Is there something I'm doing wrong or is my card not compatible?
Thanks!
BTW Octane has worked for me, so I know my computer is capable of fast GPU renders.