I tried different Proteus values and it was reproduced.
It occurs when the value of "REVERT COMPRESSION(compression)“RECOVER DETAILS(details)”“REDUCE NOISE(noise)” is small.
The value of “SHAPEN(blur)”“DEHALO(halo)”“ANTI-ALIAS/DEBLUR(preblur)” does not seem to be affected.
It does not occur at 2x, but only at 4x.
(VEAI scaling is 2x4x scale only; all other scaling is adjusted by Lanczos.)
I made an AviSynth script that patches a Proteus4X ProRes render with an equivalent Proteus2X render when it detects a hole, lol. ZIP file includes a demo.
Hi all, we are still attempting to recreate this issue and thus far, this does seem to be occurring due to each of your GPUs overheating. We have been unable to recreate this issue. Of those of you who have commented on this issue, can you please answer the following questions;
Is this occurring with v 3.2.7?
Is your GPU up to date
Do you have a cooling unit for your GPU?
If you enable low power mode, does this still occur?
Please post the following (even if you have already for us to have concise information for each case):
the GPU has a standard fan. In this test, including balanced mode, the temperature never exceeded 72 degrees.
I compared the results in balanced mode and low power mode. low power mode resulted in lower conversion fps and slightly lower temperatures, but both resulted in artifacts. The file sizes are exactly the same.
DxDiag will post with Machine name and Machine Id removed.
I also compared CPU (device=-1) and GPU (device=0) after seeing testthewest20’s post.
The artifacts are slightly smaller on the CPU, but occur at the same frames and same locations as on the GPU.
I don’t think it’s an overheating issue. I have everything up to date (Nvidia 3050 Studio driver). In my case, black spots popped up on the video when I zoomed in more than 2x. When I magnified exactly 2x, there were no spots. Tested on 3.2.7.
I tried it on another PC.
Occurred on the same frame. However, the size of the hole is different from both CPU and RTX2070SUPER.
As I recall, each GPU has a different model, but the fact that it still occurs suggests that the program side (filter side) must contain some error?
Are you seeing any black splotches with v4? I cannot see any, however, I wanted to double check prior to assuming in case my monitor needs to be recalibrated.
No black splotches were observed in V2 and V4 in this test.
However, this test is only to reject the false hypothesis that GPU heating is the cause. If V4 is developed without grasping the factors in V3, the same problem may be inherent.
I have not tested V4 alpha for a long time because of the large amount of blurring and the significant loss of detail.
Yes, I agree with you, I do not think that this has anything to do with overheating and the documents you have given us have added to that understanding.
Currently appears to be a specific model issue that will require us to create a replacement unfortunately We are still looking into other possibilities as well. Can you achieve the same issue with any other model on your end?
We are still looking into other possibilities as well. Can you achieve the same issue with any other model on your end?