- Nov 22, 2021
- 446
- 5,412
"Acting" lessons
"Acting" lessons
Relationship goalsQUINN: Where the hell is it?
View attachment 2558107
TREMOLO: Good morning babe.
QUINN: Morning, and I told you to stop calling me that, it's disgusting.
View attachment 2558109
TREMOLO: ..............
View attachment 2558112
View attachment 2558113
SMACK!!
View attachment 2558114
QUINN: OOOOOWWW!!!!
View attachment 2558115
QUINN: Very dumb move!
TREMOLO: Wow! Calm down babe, it was just for fun!
View attachment 2558116
QUINN: So is THIS!!!
TREMOLO: OOOOOF!!!
View attachment 2558117
TREMOLO: (WHEEZE)
View attachment 2558118
I'd let Quinn knee me anyday of the week.Relationship goals
Nice little story. Where does the hand print come from?QUINN: Where the hell is it?
View attachment 2558107
TREMOLO: Good morning babe.
QUINN: Morning, and I told you to stop calling me that, it's disgusting.
View attachment 2558109
TREMOLO: ..............
View attachment 2558112
View attachment 2558113
SMACK!!
View attachment 2558114
QUINN: OOOOOWWW!!!!
View attachment 2558115
QUINN: Very dumb move!
TREMOLO: Wow! Calm down babe, it was just for fun!
View attachment 2558116
QUINN: So is THIS!!!
TREMOLO: OOOOOF!!!
View attachment 2558117
TREMOLO: (WHEEZE)
View attachment 2558118
Hmm what a nice and healthy relationship I hope it's similar The little mark on her butt looks so sexy I think QUINN should get a tattoo to make it permanentQUINN: Where the hell is it?
View attachment 2558107
TREMOLO: Good morning babe.
QUINN: Morning, and I told you to stop calling me that, it's disgusting.
View attachment 2558109
TREMOLO: ..............
View attachment 2558112
View attachment 2558113
SMACK!!
View attachment 2558114
QUINN: OOOOOWWW!!!!
View attachment 2558115
QUINN: Very dumb move!
TREMOLO: Wow! Calm down babe, it was just for fun!
View attachment 2558116
QUINN: So is THIS!!!
TREMOLO: OOOOOF!!!
View attachment 2558117
TREMOLO: (WHEEZE)
View attachment 2558118
Speaking as a simp for Quinn, I LOVED this. EXCELLENT work!QUINN: Where the hell is it?
View attachment 2558107
TREMOLO: Good morning babe.
QUINN: Morning, and I told you to stop calling me that, it's disgusting.
View attachment 2558109
TREMOLO: ..............
View attachment 2558112
View attachment 2558113
SMACK!!
View attachment 2558114
QUINN: OOOOOWWW!!!!
View attachment 2558115
QUINN: Very dumb move!
TREMOLO: Wow! Calm down babe, it was just for fun!
View attachment 2558116
QUINN: So is THIS!!!
TREMOLO: OOOOOF!!!
View attachment 2558117
TREMOLO: (WHEEZE)
View attachment 2558118
As was already said, if the whole process can not fit all at once into your GPU and you are rendering by GPU only, then it will quit before it renders anything. But in addition to the techniques to make the scene smaller in terms of needed memory there is how much memory is already being used. Other open apps on you PC at the time of rendering can be using some, but also unfortunately Daz itself can sometimes block out a chunk of your GPU outside the scope of making the render and it does not allow that bit of memory to be used either. Doing things like rendering to another window rather than to file and not saving/closing that render prior to doing another render will leave you less room to render again. Also, Daz just sometimes does not release some GPU memory (from doing a render or having used the IRAY preview). Closing Daz completely down; starting it back up; and reloading your scene is the only way to clear blocked memory sometimes.I hope I can continue this. Because:
You don't have permission to view the spoiler content. Log in or register now.
Thanks, I'm already discussing how to fix the problem with Night Hacker in DM, things are starting to move somehow, albeit with problems. I'm already using the DAZ optimizer, which cuts textures, disable AUX view in the top right window and close everything possible on PC, restarting DAZ after render - I'm a little tormented because I'm trying to create a complex scene with several characters. But I managed to render a trial version of this scene and I like it.As was already said, if the whole process can not fit all at once into your GPU and you are rendering by GPU only, then it will quit before it renders anything. But in addition to the techniques to make the scene smaller in terms of needed memory there is how much memory is already being used. Other open apps on you PC at the time of rendering can be using some, but also unfortunately Daz itself can sometimes block out a chunk of your GPU outside the scope of making the render and it does not allow that bit of memory to be used either. Doing things like rendering to another window rather than to file and not saving/closing that render prior to doing another render will leave you less room to render again. Also, Daz just sometimes does not release some GPU memory (from doing a render or having used the IRAY preview). Closing Daz completely down; starting it back up; and reloading your scene is the only way to clear blocked memory sometimes.
ohoho, Raizen is in trouble. He won't be able to patent fuckmeeyes anymore...
Great job
Love some butty thicc Josy
Yeah, in rendering you have A LOT more video memory you use than in games, not only is speed effected but just whether you can render AT ALL. I learned a lot of tricks with my little 4G of VRAM. First thing I did was to grab a 12G 3060 video card... HUGE difference! So worth it and not overly expensive.Not exactly the same thing, but the concept is identical, screen space rendering saves the day, rendering things you can't see is a waste of resources.
Yes, yes you are... as I don't have a clue what's up your ass right now.Am I a joke to you?
If you were trying to render these three on 6G of VRAM using my scene subsets, than your problem could partially have been due to the fact that I set all my characters in them to be high resolution for the textures and subdivisions, you may need to lower the Mesh Resolution... I usually set them to around 2/3 or 2/4. 1/2 is probably better.... see graphic below... that is usually what I will raise the default resolution up to in order to get higher resolution and subdivide the mesh which takes way more VRAM.... you can lower the 2 (top value) and 4 (bottom value) down to 1 and 2 and it will take up less VRAM, and probably render a little faster even. I definitely never used a high resolution mesh on my old video card..
Very nice!