Because of it only uses the CPU, not even the GPU. Pov-ray is not a real time
software because I saw RTX do real time GPU I have an, NVIDIA GeForce RTX 3060
12GB it can do real time ray-tracing because its RTX GPU, It can do ray tracing
on other apps. Because of POV-Ray is CPU based software renderer, not real-time
RTX.

Post a reply to this message

Attachments:
Download 'task magnaer pov ray.png' (5 KB)

Preview of image 'task magnaer pov ray.png'

On 07.03.2025 1:21, MrScottyPieey wrote:
> Because of it only uses the CPU, not even the GPU. Pov-ray is not a real time
> software

I'm a bit confused what the expected answer should be, "And?" or "So?"

-- 
Ilyich the Toad
https://dnyarri.github.io/

Post a reply to this message

Ilya Razmanov <ily### [at] gmailcom> wrote:
> On 07.03.2025 1:21, MrScottyPieey wrote:
> > Because of it only uses the CPU, not even the GPU. Pov-ray is not a real time
> > software
>
> I'm a bit confused what the expected answer should be, "And?" or "So?"
>
> --
> Ilyich the Toad
> https://dnyarri.github.io/

Or... that's not even relevant... a) POV *can* do real time. Using +RTR command
line... only partial export and persistent data allowing some more practical use
of it have so far been implemented solely in Uberpov. But then again if one
wants to use its "ghost" feature for motion blur partial export is not a
realistic option.   b) This discussion has occured several times in the past and
the development of Apple's M1 M2 and other increasing number of cpu cores
architectures have proved the POV developers right in their strategy. Also the
fact that pov runs flawlessly on phones without any heat using Termux. To
modularise without adding dependancy layers like opencl or nvidia cuda would be.
Also not reducing the toolset to mesh-specialized tools, the only ones for which
what you describe makes sense. TLDR: POV is much more than a mesh renderer. And
does have a real time rendering agenda.

Post a reply to this message