For some reason there is no download available and it asks me to check order status.
Well that’s sorted now but…
Anyone else having trouble with saved scenes opening with genesis being a stretched mess and completely unusable? It seems to be when using files saved in the old format, which presents a BIG problem for me unless there is some kind of work around.
I don’t use Genesis, and all my old 4.5 RC2 scenes load and render without issue. Continued experimentation with older content is going well, no horribly broken figures on loading so far. The various pw* plugins work just fine in early testing. Sure wish I had my Atmopheric Camera.. sigh. It can wait.
I do get the “This program has stopped operating” when I exit DS4.5 RC3 64-bit, ut this is about 30-45 seconds after I’ve closed the app and there’s no data loss/file corruption so I consider it an annoyance, I guess I should go file a bug even though it’s just “nuisance level”.
I feel pretty warm and fuzzy about RC3 for my purposes. SO FAR (heh)!
I pretty much use nothing but Genesis when it comes to humanoid figures, and I haven’t had those sorts of problems myself. Sadly, I have no idea why this might be so, and why others have a problem. Check the log file for errors? :(
Edit: oh wait! Could you show the scene list, to show how items are parented?
For the speed increase in the newer version of 3Delight, some highlights from the change log at 3Delight: “
“Improved ray tracing performance of some transparent curves. Very dense fur patches which necessitate shader evaluation for ray-tracing will benefit the most from this optimization (we experience a maximum speed increase of 300%).”
I think this one was what caught my eye, but i didn’t notice it only applied to curves. I guess we have one more reason to wait for LAMH!
Motion Blur doesn’t work on (just) camera movements, though.
And I have some daz scenes that do not render fine (missing bucket on one eye). I’ll try again later.
I had this installation error, twice, I can’t install RC3, some advice? maybe a corrupt download?
Unfortunately, there seems to be a bug with the installers produced by the version of BitRock InstallBuilder used to build the previous installers, which causes the uninstaller that is created by the installer to be invalid (0 bytes). When the new installer attempts to run the uninstaller created by the previous installer, it fails - which also causes the new installer to fail and the message that you are seeing to be displayed. Luckily, in this scenario the number/names of files in the new installer are the same… so to work around the issue, you can go to the path indicated by the dialog (in your case: “C:\Program Files\DAZ 3D\DAZStudio4\Uninstallers\”) and delete the uninstaller (in your case: “Remove-DAZStudio4_Win64.exe”), which should have a size of 0 bytes if it is the same issue we’ve become aware of. You should then be able to run the new installer without it failing and it should create a new uninstaller that isn’t 0 bytes.
FWIW, the change log for 4.5.0.95, in the Pending Release section, indicates…
Updated Bitrock InstallBuilder to version 8.3.0; addresses bugs in the installers being generated by previous versions
... so we are aware of the issue and we want it fixed too - as much as, if not more than, you do.
OK. Are we limited in “Images”? I restarted the render. It gets to 98/99 at 99% on the Render Dialog then drops back to 95% and 95/99.
In 9 minutes it chewed up over 10G of disk. This happens whether rendering to Image, Window, or RIB. Here is a quick capture from the render dialog’s memo area.
In case anyone was wondering, the DS4.5 rc3 installer now works properly on Windows 8 (at least for me). You may need to delete the default content uninstaller first though.
Any information when Ubersoft and Uberspot lights will be recompiled for the RC3 onwards version and what sort of effect using the existing versions has on performance?
I tend to rely on ubersoft lights rather than Uberenvironment due to the environment sphere and the effect not matching up.
For some reason there is no download available and it asks me to check order status.
Well that’s sorted now but…
Anyone else having trouble with saved scenes opening with genesis being a stretched mess and completely unusable? It seems to be when using files saved in the old format, which presents a BIG problem for me unless there is some kind of work around.
I have seen this one during a fairly early build of 4.5. I did it by applying a V4 pose to Genesis that changed the rotation order and broke the binding of the figure. This was done with a DUF save and load. It looked like Genesis turned to liquid, which looks similar to your image.
That has been fixed. Without more information I can’t be sure but what it looks like is you saved a .daz file in some version of DAZ Studio before RC1, which had genesis posed using a previous generation pose. Upon loading the .daz file the binding, like my pose, broke.
There is a work around, though it is time consuming. Reinstall the old version of DS, save out character presets for your saved characters, (Note a character preset does not carry the pose.) then you can apply those presets to Genesis in the current version and quickly recreate your scene as poses will not break the binding anymore.
SO FAR (heh)!
I guess we have one more reason to wait for LAMH!
