3Delight message #141 (Severity 1): D2045: PixelFilter reset to 'box' 1x1 (display driver requiremen

RainbowArtist

3Delight message #141 (Severity 1): D2045: PixelFilter reset to 'box' 1x1 (display driver requirement)
--------------------
I keep getting this message in the Rendering status window when rendering. The renders complete ok so it is not a real problem now, but it is odd.
I tried changing the PixelFilter to box from its default setting but it still keeps saying that when I render.Apparently it has something to do with the display driver but I have not changed or updated the driver. I noticed this after I started using the latest version of DS. Perhaps it is related to the 3Delight version upgrade in 4.6.3.52.

Also, I've noticed these & similar QT warning notices appearing frequently in the DAZ Studio log file
-------------------

WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 38 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 1 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 2 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 1 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 3 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 4 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 6 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 13 unknown for QWidget)
WARNING: QAccessibleWidget::rect: This implementation does not support subelements! (ID 3 unknown for QWidget)
-------------------

I don't know what means or if it is having any effect on DS operation.
Is this some bug in the QT program or DAZ's use of it or what?
Can anyone explain it?
Thanks

Richard Haseltine

This happens with the progressive render option checked in render Settings>Advanced tab - it's a 3delight issue, it's not clear whether it matters or not (I suspect it may be a factor in the way that progressive rendering requires higher sample rates to avoid noise in shadows and occlusion).

Mustakettu85

Richard Haseltine said:

This happens with the progressive render option checked in render Settings>Advanced tab - it's a 3delight issue, it's not clear whether it matters or not (I suspect it may be a factor in the way that progressive rendering requires higher sample rates to avoid noise in shadows and occlusion).

It looks like progressive mode (which is raytracer-only) simply forces the box filter, whether it's the built-in 3Delight or standalone. It has merits: box is a fast filter as compared to the more HQ ones like sinc.

So the result will be different from the "default" mode a) because of the filter; b) because of using the raytrace hider that handles some things differently.

RainbowArtist

Thanks for your quick response. That does seem to be the case of a 3Delight bug. I turned off the progressive rendering and the message didn't appear again. Then I turned it on and the message came back. I had not tried progressive rendering before and must say I like it, the faster preview to check lighting and procedural textures especially for large size renders.

I guess the QT messages are some minor QT bug too.

XoechZ

Yes, progressive rendering is very nice for quick preview renders. I do that all the time and I also get this message all the time. But I simply ignore it, because it seems to not affect anything in a negative way.

Mustakettu85

RainbowArtist said:

Thanks for your quick response. That does seem to be the case of a 3Delight bug.

Or maybe it's not a bug, but a feature =)