Log file no longer shows Geometry & Texture memory consumption

vozolgant

I no longer see this data in my log file. How do I bring it back? I need the log file to always show how much geometry & texture memory consumption is taking place.

The following no longer shows:

Iray (Statistics) : Geometry memory consumption: 434.493 MiB (device 0), 0.000 B (host)
Iray (Statistics) : Texture memory consumption: 3.245 GiB for 306 bitmaps (device 0)

daz 4.20.0.17

PerttiA

Go back to DS 4.15

For some reason, Nvidia has removed that information on later versions

hjake

at PerttiA; if that is true, then WOW that is a huge disappointment.

Does anyone know of any other way to get the metrics of how much video RAM is being used to render a DAZ scene file?

Sevrin

hjake said:

at PerttiA; if that is true, then WOW that is a huge disappointment.

Does anyone know of any other way to get the metrics of how much video RAM is being used to render a DAZ scene file?

Run Afterburner while working with Daz?

vozolgant

This is catastrophic. It's unthinkable. It will make optimization 1000 times more difficult.  This is truly unacceptable. It's a critical, critical mistake. I need that information to optimize scenes.

I'm really getting sick of this DAZ Studio program. Really sick of it. I'm getting the same feeling of disgust I had with Poser years back.  Sadly there's no viable alternative except for Blender, but Blender is overkill for what I need.

namffuak

hjake said:

at PerttiA; if that is true, then WOW that is a huge disappointment.

Does anyone know of any other way to get the metrics of how much video RAM is being used to render a DAZ scene file?

I use GPU-Z.

Protozoon

namffuak said:

hjake said:

at PerttiA; if that is true, then WOW that is a huge disappointment.

......

I use GPU-Z.

Me too, or Asus gpu-tool or Windows 10's performance monitor.

Richard Haseltine

vozolgant said:

This is catastrophic. It's unthinkable. It will make optimization 1000 times more difficult.  This is truly unacceptable. It's a critical, critical mistake. I need that information to optimize scenes.

I'm really getting sick of this DAZ Studio program. Really sick of it. I'm getting the same feeling of disgust I had with Poser years back.  Sadly there's no viable alternative except for Blender, but Blender is overkill for what I need.

We may hope nVidia can be persuaded to put the information back in, or to provide another, perhaps more convenient, way to access it.

vozolgant

Richard Haseltine said:

vozolgant said:

This is catastrophic. It's unthinkable. It will make optimization 1000 times more difficult.  This is truly unacceptable. It's a critical, critical mistake. I need that information to optimize scenes.

I'm really getting sick of this DAZ Studio program. Really sick of it. I'm getting the same feeling of disgust I had with Poser years back.  Sadly there's no viable alternative except for Blender, but Blender is overkill for what I need.

We may hope nVidia can be persuaded to put the information back in, or to provide another, perhaps more convenient, way to access it.

Sadly, NVIDIA makes it nearly impossible to contact their team to request this feature.  

How can we get the NVIDIA team to bring back this vital, vital information?