- Jun 5, 2017
- 678
- 10,997
- Aug 9, 2022
- 12
- 58
Complete animation is available on my Twitter at:
You must be registered to see the links
- Aug 9, 2022
- 12
- 58
- Nov 21, 2022
- 96
- 3,854
- Dec 24, 2020
- 661
- 14,631
- Apr 30, 2020
- 438
- 3,860
- Jun 4, 2019
- 3,822
- 16,349
The virus had swept through the entire ship, the UCE Hooded in just over 68 hours. The symptoms saw the heart rates, blood pressure readings and temperature rising, as well as increased sensitivity in the nipples and genital areas. Eventually, those affected sought sexual from anyone or anything they could.
When she found her cabinmate pleasuring herself with the entire head of their sonic shower, Ensign Lizbeth ran from the aroused crew members. Making her way across the ship, Lizbeth tried to avoid the roving gangbangs and the predatory officers, hoping to get to the communications station and sending an SOS.
Little did she realise that the navigator, in an attempt to double penetrate herself with the ship's controls, had inadvertently set the Hooded on a course with a black hole.
As Lizbeth approached the station, she could already feel the trickle of arousal seep from her pussy. Each step made her more and more horny, aching for release. Leaning against the corridor and still desperate to send a message to Earth, Lizbeth tweaked her uniform's sensors to vibrate, something to relieve the pressure as she patched into the communications array. The orgasm built higher and higher as the Hooded approached the event horizon of the black hole.
The final message from the Hooded was Ensign Lizbeth's aroused gasps on the cusp of orgasm. An orgasm that would take an eternity to pass.
When she found her cabinmate pleasuring herself with the entire head of their sonic shower, Ensign Lizbeth ran from the aroused crew members. Making her way across the ship, Lizbeth tried to avoid the roving gangbangs and the predatory officers, hoping to get to the communications station and sending an SOS.
Little did she realise that the navigator, in an attempt to double penetrate herself with the ship's controls, had inadvertently set the Hooded on a course with a black hole.
As Lizbeth approached the station, she could already feel the trickle of arousal seep from her pussy. Each step made her more and more horny, aching for release. Leaning against the corridor and still desperate to send a message to Earth, Lizbeth tweaked her uniform's sensors to vibrate, something to relieve the pressure as she patched into the communications array. The orgasm built higher and higher as the Hooded approached the event horizon of the black hole.
The final message from the Hooded was Ensign Lizbeth's aroused gasps on the cusp of orgasm. An orgasm that would take an eternity to pass.
- Jul 3, 2021
- 4,817
- 23,259
Yeah, you do have to be careful with what your PC can handle. What I used to do when I had an older video card (a 1050TI with only 4G VRAM at the time, I now have a 3060 with 12G which is MUCH better, more video card memory is VITAL) is I would hide EVERYTHING that was not visible, and I mean EVERYTHING... if the far part of an arm of a character was not visible to the camera, I would hide it. What happens is when you load in a scene, everything you load gets stored in your system memory. When you go to render it, whatever is visible (or marked visible, whether you can actually see it or not) is loaded into your video card's memory to be rendered and for the shaders (which are programs run on your video card itself) can access them. So when you click that EYE icon to hide something, it will not be loaded into video card memory. Even part of a character's arm as I stated makes a difference. You could free up video memory and increase the detail on what is visible and maybe it wouldn't be too bad.... dunno... certainly it speeds up renders. For example, here's a scene I rendered on my older 1050TI...
Not a lot is visible except his arms and parts of her body... so I hid quite a bit, here's what it looked like from my interface. It's a little creepy! LOL... body parts missing, I only kept the room's walls and lights intact as they effect lighting and shadows...
I would maybe check your lighting as well, yeah... angle the light to bring out the contrast and shadows more perhaps?
Anyhow, your render did look great. If you can afford it, a "cheap" RTX3060 12G model (not the TI model as it has less memory) REALLY helped me.
- Aug 17, 2022
- 136
- 2,578
Sunny day by the pool.
You don't have permission to view the spoiler content.
Log in or register now.
WARNING: Wall of text in the spoiler. If not interested, look at the tits and move on, but I know there's a few people here that enjoy some more Academic discussions. The text is for them, I don't expect anyone to actually read through it.
You don't have permission to view the spoiler content.
Log in or register now.
- Jul 3, 2021
- 4,817
- 23,259
I was closely examining certain models, in this case the one I used for my Jade (BeingADIK) model for skin moles etc... basically comparing them to game characters in order to try and identify what assets were used and... well... I really liked this view! LMAO... I was checking for breast moles and, well... thinking switched to the little head and this render was born. 
- Apr 16, 2022
- 22
- 196
This is a good advice, you can also go much further.
-Turning down texture max size in render settings
-Rendering at a lower resolution.
-Lower model subdivision level. (this will help a lot but can affect close-up quality).
-Using the spot render tool to render the image in parts.
Hiding items in a scene does reduce vram usage, but for some reason hidden items still use a little bit of vram during a render so deleting them fully is the only way to get 100% of the vram back.
cpu rendering is also viable if you have a half decent cpu, it just takes 10 times as long.
Also also using a
You must be registered to see the links
is essential for low-iteration images.
- Jul 3, 2021
- 4,817
- 23,259
I used to reduce texture size using scene optimiser which worked well. I never had to delete anything. I only had 4G of VRAM but was able to do quite a bit just by hiding. The bonus is that once I got a better card I could reload the scenes and unhide things... which I actually ended doing.
I have an interesting render from the dark days of low VRAM... the following render was one I started by accident as I didn't have the camera selected, but I let it go anyhow as it looked interesting... almost some sort of strange art. heheheh... but it showed just how much I hid from view (I had also reduced texture size for these)...
First, the accidental render...
This may look confusing until you see what the real scene was SUPPOSED to be...
If it wasn't visible, I hid it. I actually created a script so I could just click on something and press "V" to hide it rather than clicking the eye icon which really helped.
This is one of my old renders I did after reducing texture size and just hiding everything...
And this is the same scene after I reloaded it on my new video card and unhid everything and reset the texture sizes back... you can mainly notice the texture difference on the ground outside the door, otherwise it's not that bad...
- Apr 16, 2022
- 22
- 196
It's impressive what you managed to do with just 4gbs of vram. How come you didn't resort to cpu rendering though, just too time costly?
Another way to work around low spec is to render by layer, so background -> optional objects -> characters -> foreground, and then compose.
Main problem is additional work that has to be done, so depending on purpose it may be ok or not, but that is basically professional workflow that allows to change each element of VFX without the need to re-render everything and optionally crank up details on specific parts.
Main problem is additional work that has to be done, so depending on purpose it may be ok or not, but that is basically professional workflow that allows to change each element of VFX without the need to re-render everything and optionally crank up details on specific parts.
- Nov 8, 2017
- 111
- 1,877
- Jul 3, 2021
- 4,817
- 23,259
Yup. CPU rendering would take literally hours. I done all those renders using denoising, usually with around only 100-200 iterations in about 5-10 mins.
I actually managed to get THREE characters in one render, which I thought was impossible on that old card with only 4G of VRAM, but after hiding everything that wasn't visible, I got the following render (using denoising in about 5 mins, give or take)...
This is what the scene looked like from DAZ, so you can see there isn't much left of poor Liam's (in the door) body! Heheh. I also stripped down the bathroom etc...
- Mar 14, 2022
- 371
- 3,623
- Jul 3, 2021
- 4,817
- 23,259
I don't do postwork but looks good! When I want to emulate something, I will generally search online for real life images of what I want and then see what I can do to duplicate it. I mostly like to see what I can do with just rendering. Nice work.
- Jun 19, 2019
- 63
- 383
Sigrid
(first is just a portrait with the second image as a background )
(first is just a portrait with the second image as a background
)
