What is the purpose of these resolve 17 updates?, they don't really seem to be fixing anything! Fusion page freezes if I add a Text+ node, resolve takes the entire length of a leap year to open as its stuck searching for console devices, and the software just feels unpolished. I understand It's beta but my God man it's frustrating and I have issues with resolve 16 cause its stuck loading on the fairlight page
Please guys look at these forums and fix these issues, the software is seriously messing up work!!!!!
This is one reason why I skip the betas and stick with the supported release.
I have a speed editor sitting next to me but I can't use it yet as I will NOT run v17 and the speed editor doesn't work in v16.
That being said, I am looking forward to seeing v17 being a supported release soon. Not sure when that will happen but I am looking forward to it from all the advancements I've seen. Getting pretty tired of flipping from page 1 to and back on the colour page!
Hello to everyone who responded, It gives me hope to know that these issues are not universal, If anybody has any ideas as to what could be causing my issues I’d be so grateful! I’m running an 3950x cpu and an RTX 3090 GPU with 64gb of so I truly doubt it’s my hardware, but maybe I have a software installed that’s causing conflict! any help at all would be much appreciated. Thanks.
Patrick, there are WAY too many variables to even begin to guess the cause. Please read over the information in this pinned topic, especially the part about how to create and post the log files. That will give the BM engineers something to work with to try and diagnose the problem.
Microsoft Windows 11 Pro x64 Version 23H2 build 22631.3527 MSI MS-7E07 Motherboard Intel i5-13600K 64GB DDR5 RAM ASUS GeForce RTX 4070 12 GB Driver version 566.36 Resolve (Studio) 19.1.2
You can see I list in each beta update all the items we fix. These are based on what we can reproduce based on testing, user reports, logs, example projects etc. If we can’t repo it’s often very hard to fix.
Any help you can offer with this info when reporting issue helps. Thank you.
Peter Chamberlain wrote:You can see I list in each beta update all the items we fix. These are based on what we can reproduce based on testing, user reports, logs, example projects etc. If we can’t repo it’s often very hard to fix.
Any help you can offer with this info when reporting issue helps. Thank you.
not all issues have logs, I can show you a small screengrab from another issue I have (although this might be fixed in a later version)
I did check the driver issues, but all my other software are functioning as expected (adobe softwares are just naturally bad so they don't count). The standalone version of Fusion 16 is performing well. More and more I'm thinking this is a resolve 17 issue, It doesn't gel well with my system. Is no one else having an issue where resolve 17 freezes if you go to the fusion page and add a text+ node?
miccetro wrote:17 freezes if you go to the fusion page and add a text+ node?
Nope. Working fine.
Same here.
I hate the title , it should be Resolve is unreliable for me !
Your hardware is top notch , so its not that , might be drivers. Maybe uninstall and reinstall resolve. Something to do with fonts ?
Sir thank you for suggesting to check fonts, as it turns out I use a font manager call fontbase, so it manages the installation of my font, I just removed it. Now resolve doesn't even freeze while loading again! I re-installed fontbase but removed my custom fonts from its database and resolve started to behave badly again. So maybe fontbase is the issue. I'll update my post when I find a new font manager.
Many thanks to everyone for their help and suggestions!
Lucas D. wrote:No problemo ! I should be working for BMD.
Lol you have a recommendation from me for sure.
Apparently the problem was fontbase, I installed another font manager (Nexus) and re-installed all my fonts and Resolve is still working as expected. So I'm not sure what kind of conflict it has with fontbase but everything I've tested so far in resolve is now working great and it starts much faster now as it no longer pauses at 'looking for control surface'.