- Jul 12, 2020
- 1,087
- 6,647
You should try changing the style to Dark BetaI can't see the previews
You don't have permission to view the spoiler content.
Log in or register now.
Previews:
![Girls-Only.png Girls-Only.png](https://attachments.f95zone.to/2023/07/thumb/2808299_Girls-Only.png)
![Helen-Melon.png Helen-Melon.png](https://attachments.f95zone.to/2023/07/thumb/2808300_Helen-Melon.png)
![Helen-scarlet.png Helen-scarlet.png](https://attachments.f95zone.to/2023/07/thumb/2808302_Helen-scarlet.png)
![Scarlet-Marlet.png Scarlet-Marlet.png](https://attachments.f95zone.to/2023/07/thumb/2808303_Scarlet-Marlet.png)
You should try changing the style to Dark BetaI can't see the previews
How tragicDefeat...
I didn't think much of it at first but... It all started with vibrating fans, then a shiver went through its components and suddenly the fans spun no more...
An eerie silence fell over the room... As I looked down to see its googly eyes staring back at me in agony & shame...
My child, for which I cared so much, which I praised in front of the other parents... Failed me... Failed us.
I couldn't look it in the eyes when I saw that Daz dropped back to the CPU... While I checked the vitals to see if something was off... I heard its pitiful whine in the background, begging me to give it another shot.
There was no mistake... The A6000 ran out of VRAM for a scene.
I then optimized the shit out of the scene, even going as far as reducing the quality for all non-main cast characters to a degree I'd normally never go. I feel dirty.
Still, I watched its once so strong arms struggle to get the bar up.
I had no choice... I had to remove some characters from the scene... And with every character I removed, I felt as if a dagger pierced my heart.
Okay for real now, I actually thought the scene wouldn't even go beyond 32GB... But fuck me...
That is most certainly not true. Most of the Daz devs (there's hundreds and hundreds of them!) would probably sacrifice their left nut to have the level of hardware you have right now. I understand the desire to create immersive scenes, but you should seriously learn to optimize your scenes better or cut some corners if you're often running out of 48 Gigs (!!!) of VRAM. That's a skill in and of itself, and without it, even if you have a hypothetical 96GB card, sooner or later, you will start hitting the max cap.There's not much difference between me and 90% of the other Daz devs in terms of equip.
Thank youYou should try changing the style to Dark Beta
Or you could switch to Dark Beta for the Images and then switch back if you prefer the default style.You don't have permission to view the spoiler content. Log in or register now.
Previews:
View attachment 2784770 View attachment 2784771 View attachment 2784773 View attachment 2784774
Well they load now, but someone resized them to 144pYou should try changing the style to Dark Beta
Or you could switch to Dark Beta for the Images and then switch back if you prefer the default style.You don't have permission to view the spoiler content. Log in or register now.
Previews:
View attachment 2784770 View attachment 2784771 View attachment 2784773 View attachment 2784774
The ones I shared are 360p and that's the Max resolution of every preview AFAIK.Well they load now, but someone resized them to 144p
Any chance for 1080p or higher versions? Thanks anyway
So here's a tip:You must be registered to see the links
I don’t know either. I have been toying with Turbo Loader.
I’ve had to. I’ve got way too many products installed and it took over three hours to load (not render) one scene with (3) G8/8.1F characters and a (1) G8M.
So I typically break out all my scenes into scene subsets. And I save a new version for every scene (new version of characters too).
Everything looked normal until I went to work on the next scene and load the figures in and they were completely messed up. Literally the only thing I did was reload a saved character.
But it was while working with TurboLoader that I learned something very scary about working with DAZ Studio…
Every time you touch a morph dial that dial then gets “activated” and will be saved as part of the character, even if the morph dial is set to ZERO.
So when I’m designing a new character I may touch several dozen body and head morphs (or expression morphs, etc.) to get what I want.
And every single one of those dials that I’ve touched, even if I’ve reset it back to zero, will now get saved with the character.
The TurboLoader Utilities addon has a “Scene Configuration” option that will save out a list of every morph dial that’s referenced in a character (or scene). That’s when I learned this.
Only way to clear it is to make sure those morphs aren’t available to Studio and re-load the character so those files are “not found” and then save out your character again.
And that’s when I noticed the 3DU characters, the Maxx character, and a bunch of others. Honestly at this point I probably need to uninstall over 50% of the crap that I do have installed.
The fact that every morph dial touched is “activated” on a character explains a mystery that I had encountered a few times. I create animations for a friend of mine, sometimes using premade characters that he sends to me. We check beforehand to make sure I have the models and morphs he used.
Occasionally when I open the scene file he sent, I will get a bunch missing content warnings from Daz for various morphs. When I go over the list of missing morphs with my friend, he always insists that he had not used them for the character, so I simply ignore them and carry on.
Based on what you discovered, I imagine my friend merely had touched the morph dials at some point and decided not to use them, setting them back to zero. Yet that caused Daz to save them permanently on the character.
That is exactly what’s happening, I guarantee you. It’s also bloating the characters and slowing down the loading. Just take a look at the DAZ Studio Log File when you load a complex scene. Notepad++ has an option where you can “tail” the loaded file so it auto-refreshes immediately as new lines are added to the bottom.Based on what you discovered, I imagine my friend merely had touched the morph dials at some point and decided not to use them, setting them back to zero. Yet that caused Daz to save them permanently on the character.
That’s another way to quickly see just how inefficient Studio is as well.
Lots of interesting things, not the dates, that's sad.You must be registered to see the links
Hello,
Soo...
1. Workstation
2. CH3 Status
3. Previews
1. Workstation
TLR at the end of the text.
Over the past weeks, I had a back-and-forth with the Nvidia tech support & also did a lot of research to see if memory pooling would still work through PCI-E, etc.
Nada... "Hey, let's charge almost 10,000€ for a GPU that can't even pool its memory like the predecessor."
That's pretty much the only reason why I want the A6000/Pro Cards.
But it's not going to happen with this GEN.
So I reconsidered and I'm doing the following now:
Instead of a Workstation with 2xA6000 ADA, I'm getting a custom-built workstation with 4x4090.
And on top of that, an A6000 (Old Gen).
I already have an old Gen A6000, and adding another with a NvLink will give me roughly 96GB VRAM.
I'd say 70% of my scenes can be rendered with 24GB. 30% need more than that. (Exceptions are updates like CH6 SG, which is 80% far above 24GB.)
So, I will have one PC with 2xA6000 Old Gen, that only renders the big scenes. (Every single update will have them.)
Meanwhile, the 4x4090 Workstation is going to render everything else.
And it's not just the raw speed of the GPU that's going to matter...
A good friend of mine is rendering on a 4090, and while he showed me a few animations, I noticed how fast they were rendering... But not because of the Cuda cores... But because of how fast the 4090 slurped the textures & other thingies into the memory.
Between each frame is a pause where the GPU loads all the textures & info into the memory... And while I created the Tabletop animations, this pause could take up to five minutes. (Before every single frame.)
This took longer than the actual rendering part & is also the reason why you never got a yoga/stretching cinematic in Chapter 3x5... As each memory loading pause took 15min and I abandoned it.
So it appears that it would also speed up animations by A LOT.
But I first have to test it, and then I can show you some graphs.
Oh, the custom Workstation (water-cooled GPUs) is also almost 8000€ cheaper than the previous double A6000 ADA Workstation.)
Both games would be made on both PCs. No more designated PCs. Both games are going to enjoy the fruits and WIAB won't face any downtime due to VRAM issues.
I can't get the workstation yet and have to wait for the Steam release, as you know, my old tax office hasn't submitted my 2021 numbers yet, and atm I wouldn't even get a loan for 2000€.
With the 5000 series GEN, I'll take another look at the Pro cards... But I need that scaleable VRAM.
TLR: Instead of a Workstation with 2xA6000s ADA, I get a custom Workstation with 4x4090 & a separate old Gen A6000 to upgrade my current WiAB PC to 96GB VRAM. New Workstation is almost 9000€ cheaper. Still can't get it before Steam, tho. Both Games would be made on both PCs. WIAB won't face any downtime.
2. Status of Chapter 3
CH3 is coming along great.
I still need to render ~400 renders. (96 of them are currently in the queue, and ~300 need to be set up.)
I've already started with postwork, and as soon as I have around 500 renders done in post, I will start testing.
We're getting pretty close now.
3. Previews - 4K attached
Sneaky MC
View attachment 2820768
Zoey-Moey
View attachment 2820769
New important environment
View attachment 2820770
WiAB: Probably early September.
SG: Probably late September.
- Ocean
" I already have an old Gen A6000, and adding another with a NvLink will give me roughly 96GB VRAM. "Out of curiosity, why put 4x4090 on a single pc instead of spreading them out on multiple pcs?
VRAM doesn't stack so it would only help with the speed, and I'm certain rendering 4 pictures on 4 pcs with a 4090 each is much faster than rendering them on a single 4x4090 pc.
This solutions always look good on paper, until you're faced with DAZ's (lack of) optimization for them.
Ya I've seen some banter on that as well; I've been curious if it's just a DAZ issue. I know Ocean has said he wants to move to Blender, so if Blender works well with VRAM stacking then that'll be another good reason to expedite the transition." I already have an old Gen A6000, and adding another with a NvLink will give me roughly 96GB VRAM. "
I dunno, I also read and heard that DAZ can't use the combined RAM of several cards but apparently Ocean heard otherwise.
I thought that the 4090s and all cards moving forward got rid of NVLink? There is a limitation with DS and number of cards.Out of curiosity, why put 4x4090 on a single pc instead of spreading them out on multiple pcs?
VRAM doesn't stack so it would only help with the speed, and I'm certain rendering 4 pictures on 4 pcs with a 4090 each is much faster than rendering them on a single 4x4090 pc.
This solutions always look good on paper, until you're faced with DAZ's (lack of) optimization for them.
I assume that this is to create the effect of presence and to deepen the immersion in the scene. Have you ever noticed that when you look at an object in front of you, all the details on the periphery of your vision and in the distance seem to be blurred? That's what I think he was trying to achieve.Can someone explain to me why Ocean blurs the background so much? he talks about how the environment is important, spends so much time, but the characters are always in the blurry, bad visible background
But only Ocean knows for sure. Maybe he did it just for lulz.Background blur is a common technique used by photographers for years as a way to keep the focus on their most important subject. The idea is to focus on the element in the foreground, by removing the hard lines and distracting detail in the background, to truly make the element pop.
Yep, it is a standard photographic principle called depth of field (DOF). It is important in highlighting the subject when the context (background) is less important. Look at any non-landscape image or film. They all use it. Even landscape if the image has a primary subject, like a tree.Can someone explain to me why Ocean blurs the background so much? he talks about how the environment is important, spends so much time, but the characters are always in the blurry, bad visible background