[Bug] Rectangle Node

Whatever I do, whatever methods I try to use, I keep getting glitches. Decided to do infographics, get glitches, decided to do transitions - glitches, decided to render video - glitches, switched proxy mode, the program hangs.
And it's not even about the beta version, I've been encountering glitches like this since early version 16.
I want to open a program, create an effect. Be happy with what I created, and go to sleep. But instead, I spend months trying to work around the problems that exist in Fusion.

I added all the videos to the first post so you don't have to reread the topic.

This problem really pissed me off:

One more glitch with the Ellipse node:

One more glitch with the Rectangle node:

One more glitch:

Can I please get a trial period for the Studio version, about 5-7 days?

No

I tested it on Resolve Studio, I have the same glitch as you on the edit page

AND the glitch is backed in the rendered video... - So this is clearly a bug

I tested it on Resolve Studio, I have the same glitch as you on the edit page

AND the glitch is backed in the rendered video... - So this is clearly a bug

Thank you for checking.

I tested it on Resolve Studio, I have the same glitch as you on the edit page

AND the glitch is backed in the rendered video... - So this is clearly a bug

Thank you for checking.

What you can do in the mean time is to go in the Fusion tab again (when you modify the length of the composition on the edit page), then toggle the modifiers off/on.

I tested it and the glitch disappears (for me in my very simple test). But the problem appears again if the length of the composition is changed again.

At least you can finish your job now

But yeah it's clearly a bug in my opinion

It's even worse than that, the whole thing is flickering

I haven't looked carefully at this particular issue, but when I was writing a Fuse that let you perform a realistic bounce I experienced something very similar. The cache logic doesn't know that you are programmatically changing the content of an already rendered and cached image, that's why these glitches occurred for me.

My workaround was to add a keyframe at the very last frame of the clip. This helped Fusion understand that all the frames between the first and last keyframe could be changed.

That's interesting. But is it realistic to fix it?
What I noticed is that this problem does not exist if you use Expressions. If you use a modifier or Frame Render Script, the problem appears. Also maybe it's not even a caching problem, because if I write fu:PurgeCache() it doesn't help. If I clear the cache manually it also does not help.

I tried adding a Rectangle mask to the Merge node, and the image blinks just the same. Apparently the masks in Davinci are broken

I think is all about fusion cache...
this kind of trouble persist from lot of version...

try to clean cache, in davinci and in fusion also, and try disabling fusion cache.

I think is all about fusion cache...
this kind of trouble persist from lot of version...

try to clean cache, in davinci and in fusion also, and try disabling fusion cache.

It doesn't help.

Toggling the modifiers off/on (in fusion, after changing the size of the clip on the edit page), fixes it, at least for me for test based on Rezzimx's video. This is just a way to work around the problem in the meantime.

So I think it's just a bug that needs to be fixed

I wonder what is Davinci priority for bugs.
This problem is still present in beta 3.

I noticed that this glitch does not appear in all cases. In my other animations everything works fine. Maybe the problem is with the mask (node Rectangle, Polygon).

I checked and found something else, hopefully it will help the developers to solve the problem. When I try to animate the Length parameter in masks that have it using Anim Curves, this problem appears. If I try to animate the Height parameter, for example, then there is no problem. There appears to be a problem with the Length slider.

I've also had the glitch when just animating the position of a Text+ node with a Transform node.

How I understand that such sliders that cause such glitches are not a few. I was creating an animation a month ago and had such glitches when I tried to animate Shear in the Text+. Developers need to check all the parameters to fix it. If you need I can check every parameter in all nodes and write which specific controls cause such problems.

I am running Beta 3 Studio and I think this happens with most Fusion-based titles (for me, I frequently use the premade BMD ones like "Fade On" and it especially occurs with this one and a few others but with "Flip Over", it rarely occurs but still definitely happens at times) because when I change their length, most of the time you'll get a similar flashing glitch effect like Tymur has in his infographic (who is using a Fusion-modded Text+ title? I think that is what I saw).

For me, sometimes deleting the cache will fix it but many times it doesn't. Also, 18 seems to be slightly better than 17 in my experience but it still happens way too often and frankly, it's awful. If all else fails, my situation is a bit simpler because I just drag and drop a new title over the existing one and change the length to match the glitchy one and copy and paste my text and change the font settings and delete the old one and it's finished in a minute or so (but I am not usually doing anything too complex).

One suggestion I just thought of which probably won't work but might be worth a try is to get the Fusion composition or title to the exact length you want and then hold down the "alt" key and drag a copy of the comp/title onto a new track and then delete the original and hopefully the new one will work. I am not optimistic but maybe just maybe it will work. I am going to try it myself in the future and I will try to report back on the results.

Yes, the Alt duplicate method works. But imagine, for example, a customer approached you to do something, you send the work and say "well, there's this, the program is to blame. I think such glitches should be fixed in the first place.
And yes, I noticed a lot of cool changes in the program. The program is clearly getting better. But it takes so long to update.

Yes, the Alt duplicate method works. But imagine, for example, a customer approached you to do something, you send the work and say "well, there's this, the program is to blame. I think such glitches should be fixed in the first place.
And yes, I noticed a lot of cool changes in the program. The program is clearly getting better. But it takes so long to update.

Obviously, I am not going to say and wasn't trying to say anything otherwise. I was just trying to agree with you and help with an idea that might work for the moment and I am glad to hear that it did. Frankly, I am shocked that it did work and hopefully they get this fixed asap because like I said it is causing me problems too.

Ultimately, here's the the thing though, I don't work for BMD and didn't defend them or their software and so a "thanks" (or even nothing for that matter) would have been more in order and appreciated rather than your response (i.e., it sounds kind of like an argument or a disagreement more than anything else to me) because you are preaching to the choir here and I don't believe anything I said warranted it. I know you are frustrated and I am too so we are on the same side here. All I talked about is how I deal with the bug and that the issue for me has gotten better in 18 than it was in 17 and wasn't trying to speak on your situation or anyone else's or defend BMD/DR or anything like that (what I exactly said was "Also, 18 seems to be slightly better than 17 in my experience but it still happens way too often and frankly, it's awful.").

I didn't understand anything from the second paragraph)
But thanks)

But imagine, for example, a customer approached you to do something, you send the work and say "well, there's this, the program is to blame. I think such glitches should be fixed in the first place.
And yes, I noticed a lot of cool changes in the program. The program is clearly getting better. But it takes so long to update.

You're welcome...And, in short, I was saying I didn't understand anything you were saying here (quoted above) or at least, why it was being directed at me because I see no logical connection between what I said and this part of your response.

Is anyone tested the beta 4 to see if it was fixed?

I tested, not fixed

Exactly none of my work arounds work with consistency. Trying to blow out the cache, fusion cache. I've had to create another timeline, create the graphics in that timeline, export then reimport to project and insert into a timeline but that really really is painful for timings and dissolves and transitions going into anything involving a simple push of a solid color for text alone. Dumb. Thus we rarely use Resolve these days. Yeah great, updates galore. Never works. Not solid enough for a full end to end and so we are truly truly dependent on the normal AVID blah blah blah with exports and EDL roundtrips for color audio when simple simple stuff like this, offers up a perfect situation for "although its simple to want to do that" on a timeline, major compositing for films but can't be without the simplest glitches with just a sold color, pushing onto the screen, dissolving or using a preset of text, layering those and watch the black mask boxes or glitches show up and ruin everything, you can't deliver on time and spend forever finding a work around just for trying to use Resolve. Nope. Probably not trusting Resolve Edit etc for awhile. Blackmagic doesn't understand we are on 18 beta 3 or 4 etc but who cares if we get an update daily and are at Resolve Studio 108 by tomorrow. It just isn't stable or reliable in the most simple simple circumstances.

Exactly none of my work arounds work with consistency. Trying to blow out the cache, fusion cache. I've had to create another timeline, create the graphics in that timeline, export then reimport to project and insert into a timeline but that really really is painful for timings and dissolves and transitions going into anything involving a simple push of a solid color for text alone. Dumb. Thus we rarely use Resolve these days. Yeah great, updates galore. Never works. Not solid enough for a full end to end and so we are truly truly dependent on the normal AVID blah blah blah with exports and EDL roundtrips for color audio when simple simple stuff like this, offers up a perfect situation for "although its simple to want to do that" on a timeline, major compositing for films but can't be without the simplest glitches with just a sold color, pushing onto the screen, dissolving or using a preset of text, layering those and watch the black mask boxes or glitches show up and ruin everything, you can't deliver on time and spend forever finding a work around just for trying to use Resolve. Nope. Probably not trusting Resolve Edit etc for awhile. Blackmagic doesn't understand we are on 18 beta 3 or 4 etc but who cares if we get an update daily and are at Resolve Studio 108 by tomorrow. It just isn't stable or reliable in the most simple simple circumstances.

I've been dreaming since version 16 of Davinci that Fusion would remember the location of the windows. It's been two or three years now. And the windows still do not maintain their position. Sometimes it glitches and saves, but then it goes off again.

I think this problem should be prioritized and solved as soon as possible. It prevents from working properly with the mask.

Not fixed in beta 6

Blackmagic, do you at least plan to fix this bug this year?

Blackmagic, do you at least plan to fix this bug this year?

Someone with a paid license should report this to BMD support to get an official answer.

18 version. Not fixed.

This may be the same problem:

Is this a Resolve issue or Fusion? If sounds like a Fusion issue. Maybe this thread should move to the Fusion section so those who know Fusion more can help you folks and probably BMD will hear about it. Good luck.

Is this a Resolve issue or Fusion? If sounds like a Fusion issue. Maybe this thread should move to the Fusion section so those who know Fusion more can help you folks and probably BMD will hear about it. Good luck.

This is DaVinci Resolve>Fusion

It's been six months. In version 18.1.1 this problem is still present.

I wouldn't want to get excited prematurely, but it looks like the bug has been fixed in version 18.1.2.
I will also try to reproduce this problem with my other works and report more precisely.
In the video you can see how the column still twitches a bit, but it's much better than before.

This problem fixed too :

BMD please fix the same bug, only it occurs when we use Frame Render Script and for example try to refer to the parameter of another node.
For example in the Transform1 node in Frame Render Script I write:

Code: Select all

if (Transform2.Size==1) then
Size=1
end

It often happens that when we access another node or modifier with Frame Render Script, it starts to display incorrectly. In that case I clear the cache, or try to turn off/on the node and the glitch disappears.

This is exactly the same glitch as the one you fixed when stretching the composition (In version 18.1.2)

The same problem:

Probably the same problem only with the Vector Result modifier

Rectangle node One more glitch.
It's not just a glitch. Considering the constant problems with this node, it seems to me that this node is broken. It needs a radical repair.

i7-9700k 4.3GHz, 32GB RAM, SSD 1TB M.2, SSD 512GB M.2, GTX 1650(4GB).

I think your GPU is very underpowered, and that's likely the reason for the issues. I would love for Resolve to pop up an error message and say, "you need a much more powerful GPU in order to use this feature."

I know of no fix than to upgrade your system and go with something a lot better, and then I bet it will work. If you need to get something shipped for a deadline, then my advice would be to rent a big system for a day from a local supplier, copy the files over, open up the session, and render it. I bet it'll be fine with a 3090 or a 4090 GPU (or, god forbid, a recent high-end Mac).

i7-9700k 4.3GHz, 32GB RAM, SSD 1TB M.2, SSD 512GB M.2, GTX 1650(4GB).

I think your GPU is very underpowered, and that's likely the reason for the issues. I would love for Resolve to pop up an error message and say, "you need a much more powerful GPU in order to use this feature."

I know of no fix than to upgrade your system and go with something a lot better, and then I bet it will work. If you need to get something shipped for a deadline, then my advice would be to rent a big system for a day from a local supplier, copy the files over, open up the session, and render it. I bet it'll be fine with a 3090 or a 4090 GPU (or, god forbid, a recent high-end Mac).

Underpowered for the Angle slider to work properly? That even sounds ridiculous. As for other glitches, such glitches were when using the modifier Anim Curves and it fixed (1 year later). Now the same problem only with other modifiers. And maybe there is a problem not only with modifiers but with the Rectangle node itself.
I check any bugs before sending them to this forum on my friend's PC which is powerful enough. Video card 4070 ti 12GB, processor i7-13700KF, 32GB RAM. So the problem is not my video card.

Stopped using Davinci because of these glitches that don't allow you to use templates properly. It's impossible to edit a video.
Decided to update and see if anything has changed. Nothing has changed after 9 months. Been having this bug for about two years now.
Do the developers even plan to ever remove this bug? It has been fixed in the Rectangle node, but nothing has been fixed in the rest of the nodes.