Do not use 15.2!!!

15.2 is EXTREMELY buggy. I have had tons of crashes, timeline and media disappearing, and inability to control playback in the editor. This release will cause you endless amounts of frustration and loss of productivity.

Another super annoying bug is when going into Fusion, it uses the clip that the playhead is on and not the selected clip, this is a royal pain in the butt.

I HIGHLY recommend not installing 15.2 if you are doing any production work.

I agree. I upgraded mid-project like an idiot and now that project is at a halt and I am unsure if it is safe to go back to the previous version.

I had problems with the latest update. I uninstalled 15.2 and installed the previous version without any problems. Perhaps Black Magic is in too much of a hurry to become the leader in video editing. Do they have Beta testers?

After my own problems with 5.2, I exported the project in case of trouble (as I usually do when updating), then reinstalled 5.1.2 and loaded the project normally (not the backup exported one). I don't see any problems now that I'm back in 5.1.2.

5.2 is an exciting update with some useful features, and I much appreciate BMD's continued work on Resolve, which I love, but I definitely had problems. Over the years, updates have been remarkably clean, but not this time for me. I'll be interested to see if others share this experience, or if there is a specific combination of hardware and operating system or something that leads just a few of us to grief.

Late 2013 Mac Pro 6 core, D700s, 32 GB, ThunderBay RAID 0, High Sierra.

This advice from you : I advise the contrary . ..Just learn to tame the race beast .. ...

We have mentioned this again in previous posts and it is becoming even more prominent now.

Resolve's development should focus on stability for a while and slow down on the new features. It is excellent for Color Grading and Editing but when the Fairlight and Fusion Tabs are involved... all hell breaks loose.

15.2 can be buggy to a nerve-wracking point. I wasted 3 hours yesterday trying to make a Fusion clip work as expected and i eventually rendered it with the Fusion standalone to save my sanity.

It is excellent for Color Grading and Editing but when the Fairlight and Fusion Tabs are involved... all hell breaks loose.

15.2 can be buggy to a nerve-wracking point.

Fairlight in use daily (averaging 10 hours a day) with none of the issues mentioned in this thread, each release improving on the last, 15.2 is no exception.

I have also experienced a lot of freezes and crashes with 15.2. Contemplating going back to 15.1.2. BMD needs to focus on stability before adding new features. It's a great app when it works, but if there are constant issues it take more time than it's worth, and it becomes more beneficial to use multiple different apps.

only have it on one machine ( my wimpiest, a z800/2x5680/1050Ti), have an episode of a 1hr tv series in there, and i'm about halfway though the show, many ofx and nodes in use, and it's been zero hassle, zero issues, zero drama so far

only note i've had is abotu archive from 15.1.2 not being seen as a valid archive, but that's lower than zero hassle as the folder contains the media and a .drp, and they worked perfectly

I have been observing since some time that at the same time as new features are added, the stability of the programme is diminishing, as if this were not important. We're going to end up with a program that does everything, but doesn't allow you to deliver the work. What a paradox!

only have it on one machine ( my wimpiest, a z800/2x5680/1050Ti), have an episode of a 1hr tv series in there, and i'm about halfway though the show, many ofx and nodes in use, and it's been zero hassle, zero issues, zero drama so far

only note i've had is abotu archive from 15.1.2 not being seen as a valid archive, but that's lower than zero hassle as the folder contains the media and a .drp, and they worked perfectly

What kind of Fusion work are you doing and how complicated is your mix in Fairlight? What VSTs are you using?

I was loving it save for a few quirks but am unable to render any long timelines. No big loss I will revert back but it was a lot more stable in some ways. Not being able to render is kind of a big one for me though. Specifically I was trying MXF DNXHR 10bit files so trying some quicktimes. Brutal because it crashes at 99%. Errors I get now I didn't yesterday are:

x00003e04] | IP | WARN | 2018-11-15 12:13:40,429 | Add parameter [serializedTrackerState] failed: parameter exists already.
[0x00003e04] | OpenFX | WARN | 2018-11-15 12:13:43,716 | propGet: kOfxStatErrValue
[0x00003e04] | OpenFX | WARN | 2018-11-15 12:13:43,716 | propGet: kOfxStatErrBadIndex
[0x00003e04] | OpenFX | WARN | 2018-11-15 12:13:43,716 | propGet: bad handle (0000000000000000)
[0x00000ab0] | OpenFX | WARN | 2018-11-15 12:13:44,873 | propGet: kOfxStatErrValue
[0x00000ab0] | OpenFX | WARN | 2018-11-15 12:13:44,873 | propGet: kOfxStatErrBadIndex
[0x000056a8] | OpenFX | WARN | 2018-11-15 12:13:44,944 | propGet: kOfxStatErrValue
[0x000056a8] | OpenFX | WARN | 2018-11-15 12:13:44,944 | propGet: kOfxStatErrBadIndex
[0x000056a8] | OpenFX | WARN | 2018-11-15 12:13:45,124 | propGet: kOfxStatErrBadIndex
[0x000056a8] | OpenFX | WARN | 2018-11-15 12:13:45,124 | propGet: kOfxStatErrBadIndex
[0x000056a8] | OpenFX | WARN | 2018-11-15 12:13:45,124 | propGet: kOfxStatErrBadIndex
[0x000056a8] | OpenFX | WARN | 2018-11-15 12:13:45,124 | propGet: kOfxStatErrBadIndex
[0x000056a8] | GPUManager | INFO | 2018-11-15 12:13:45,285 | Loaded Shaper LUT 'IWLTBAP\01 - Standard\F-9650-STD.cube'
[0x000047c8] | IO | ERROR | 2018-11-15 12:13:45,604 | Failed to open video file <O:\H264Output\Filename.mxf> for decoding, error: <File does not exist, or file format is not recognizable.>
[0x000047c8] | IO | ERROR | 2018-11-15 12:13:45,604 | Failed to read video track information from file <Filename.mxf> in O:\H264Output, track 0: codec DUMMY is not supported
[0x00003e04] | SyManager.Signals | INFO | 2018-11-15 12:13:52,088 | Main view page is changed to 11

I'm happy to find this thread.
Seams like I'm not getting paranoid. Others tear their hair off their heads too..

Extremely disapointing update.

What's the point in new features when old features doesn't work properly?

I'm finding Studio 15.2 quite workable on my two systems, and really like some of the new features.

I find this warning...overstated.

I find this warning...overstated.

Do your Fusion comps display alpha in timeline? Or is alpha exchanged for black?

I've only tested a Fusion title, but it worked fine. Alpha was as expected.

So please stop talking about overstatements.

We have mentioned this again in previous posts and it is becoming even more prominent now.

Resolve's development should focus on stability for a while and slow down on the new features.

We don't need new ResolveFX. We need Fusion working in Resolve or a better Connection system. I swear, I'm going to stop paying for upgrades if this keeps up.

So please stop talking about overstatements.

I think the generality of the warning is overstated. I have it working fine for my projects.

If a specific feature isn't working, then a qualified warning is more appropriate.

I swear, I'm going to stop paying for upgrades if this keeps up.

[Peter Chamberlain]

If you find issues guys please report specifics, your full system config and attach a link to diagnostic logs so an engineer can review.

If we can repo bugs they are easier to fix.

BMD needs to focus on stability before adding new features.

They can do both, just let users have more than one version installed. The lack of QA and beta testing wouldn't be as big of an issue if you could keep the old versions installed until you could safely migrate, and you could do it per-project. Resolve is the first and only professional application I've ever used that had this restriction. For me, at least, it's an unheard of policy.

LOTS of software companies run multiple releases, like LTS, STS, and Experimental/Beta. If BMD let you have 3 tracks like that you could manage your risk and options easily.

If you aren't really doing anything in Fusion then it works great. I did edit a couple things with no issue. As soon as you get in fusion and start making magic, drama ensues. If you aren't a heavy fusion or fairlight user it could be safe....

I swear, I'm going to stop paying for upgrades if this keeps up.

That's the crazy thing though... BMD could sell Fusion Enterprise or Resolve Enterprise for $1500/yr and thousands of people would buy it. Many people using Resolve for a while have basically spent less than $0.02 per day on it, but earn more than $2000 a day using it. There's millions of dollars in revenue available if BMD were to offer a premium SKU.

Right now, my needs are completely irrelevant to BMD. If the new feature for Resolve 16 was Twitch streaming, they could sell 5,000 more dongles but if they remove or break a feature 10,000 existing users need, they lose nothing. I LOVE the fact that I can leave my dongle in the studio by accident and just order a replacement from B&H and have it delivered to my house next day and it costs me so little and I don't need to register anything or set some code/countercode up. But the downside is BMD is always, by business necessity, looking to add more new users vs keeping old users.

If you find issues guys please report specifics, your full system config and attach a link to diagnostic logs so an engineer can review.

If we can repo bugs they are easier to fix.

Unfortunately not all bugs are easy to reproduce.

Last week i had to render a 15'' TV commercial 4 or 5 times before audio exported glitch-free. 4 times without changing one single thing in the project. I just kept on exporting it until it was fine.

How can one troubleshoot this? All i know is that glitches were appearing either at the first few seconds or during shots with Fusion FX.

There is a general memory handling instability throughout Resolve. That's all i can suspect from my experience.

If you find issues guys please report specifics, your full system config and attach a link to diagnostic logs so an engineer can review.

AFAIK people reported pretty specifically about problems with blacked screen in Fusion comps in Dual Screen mode. Nothing changed in 15.2
The caching and smooth playback of Fusion comps are not fixed either.
At the moment if you use Fusion comp and have alpha chanel in it and in Timeline you composit it over another clip, the alpha becomes black.

Bring possibiliy to test new versions alongside with 'stable' version and we'll all be happier.
Because now there is no time to mess around with 15.2 cause I got to roll back to 15.1.2 to finish a project in stable environment.

Speaking of memory, I applied a Sapphire 12 today effect and it said I was out of GPU memory which has never happened before. I have 12gigs...

Not being able to render is kind of a big one for me though. Specifically I was trying MXF DNXHR 10bit files so trying some quicktimes. Brutal because it crashes at 99%.

I got the same problem

Rather than "do not use" perhaps "test before you use".

At the very least, back up your database your projects before you use.

I'm not having just one feature that isn't working, it is simply unstable for production use.

Just from the media page, I tried to browse to a folder to add some files, hard crash every single time.
Needed to use DeltaKeyer, multiple crashes
Needed to use LumaKeyer, crashed twice
Started playing one clip on loop with no way to stop it - had to quit program
Horrible audio screeching when starting a clip with audio
No audio on Fusion page
In DeltaKeyer, eyedropper doesn't work - oh wait, old bug, still never fixed
After using a qualifiers, main track was dimmed out, had to quit program and restart
Auto-Save is not enabled on a new project, so the whole point of not having to save first is moot
Went from Fusion page to Edit page, my main track was gone as well as the file in the Media page - happened 4 times, and even though I had started hitting Cmd-S every few minutes, twice I lost over an hour of work

So, is my original post overstated? Nope. I stand by it. Do NOT use 15.2 for any production work.

Maybe it would be of great help if the activation key (or Dongle) for Resolve + Fusion would also work for standalone Fusion. With that we could at least finish our work without pulling our hair out - until the integration of Fusion into Resolve is completed and works rock-solid.

If you find issues guys please report specifics, your full system config and attach a link to diagnostic logs so an engineer can review.

AFAIK people reported pretty specifically about problems with blacked screen in Fusion comps in Dual Screen mode. Nothing changed in 15.2
The caching and smooth playback of Fusion comps are not fixed either.
At the moment if you use Fusion comp and have alpha chanel in it and in Timeline you composit it over another clip, the alpha becomes black.

Bring possibiliy to test new versions alongside with 'stable' version and we'll all be happier.
Because now there is no time to mess around with 15.2 cause I got to roll back to 15.1.2 to finish a project in stable environment.

I have kind of the same sentiment, but with other bugs. I've reported numerous bugs over the last few years that never were addressed. Even a bug that I reported in 12.5 betas still existed in 15.0 release. I haven't actually checked if it exists in 15.1, 15.1.1, 15.1.2, or 15.2 yet. I had a thread I started that listed a bunch of bugs that were reported in 15.0 betas, but still existed in 15.0 release. What's the point of spending the time to report the bugs if they aren't going to be fixed? It ends up being a waste of our time.

It is excellent for Color Grading and Editing but when the Fairlight and Fusion Tabs are involved... all hell breaks loose.

15.2 can be buggy to a nerve-wracking point.

Fairlight in use daily (averaging 10 hours a day) with none of the issues mentioned in this thread, each release improving on the last, 15.2 is no exception.

Hello, Reynaud
Great to hear your success, but what system specs have you?

ResolveStudio 14.3...014 | MiniMonitor | DTV 10.9.7 | Win8.1 x64 | ROG G751JL, 2.8GHz Intel i7HQ, 24GB DDR4, 1TB HD, 500GB EVO 850, 2GB GTX965M | Mackie MCU Pro | Softube Console 1 Mkii | Shuttle Pro 2 | more...

I'm finding Studio 15.2 quite workable on my two systems, and really like some of the new features.

I find this warning...overstated.

System specs Jim?

ResolveStudio 14.3...014 | MiniMonitor | DTV 10.9.7 | Win8.1 x64 | ROG G751JL, 2.8GHz Intel i7HQ, 24GB DDR4, 1TB HD, 500GB EVO 850, 2GB GTX965M | Mackie MCU Pro | Softube Console 1 Mkii | Shuttle Pro 2 | more...

Strange to me is the number of reports of Resolve 15.2 problems, with absolutely no context given, regarding what computer platform is in use, let alone the lack of providing other host computer system specs.

And no diagnostics logs -- how in the world is BMD's little tech department going to fix what's wrong if a majority of people with valid complaints do so without providing helpful data?

I wonder if Windows machines hosting Resolve 15.2 are faring better than their Mac counterparts-- but the majority of you Guys and Gals with problems shockingly aren't cooperating with Peter Chamberlain to aid him and lurking observers like myself (still on v14.3) in making *that* simple determination.

I've moved on to a Final Cut Pro X purchase and edit-practicing sessions on an iMac (for now) as this Resolve 15 instability-and-failure-to-properly-report conundrum is unproductive, and egregiously irritating on both ends of the equation.


ResolveStudio 14.3...014 | MiniMonitor | DTV 10.9.7 | Win8.1 x64 | ROG G751JL, 2.8GHz Intel i7HQ, 24GB DDR4, 1TB HD, 500GB EVO 850, 2GB GTX965M | Mackie MCU Pro | Softube Console 1 Mkii | Shuttle Pro 2 | more...

I'm not having just one feature that isn't working, it is simply unstable for production use.

Just from the media page, I tried to browse to a folder to add some files, hard crash every single time.
Needed to use DeltaKeyer, multiple crashes
Needed to use LumaKeyer, crashed twice
Started playing one clip on loop with no way to stop it - had to quit program
Horrible audio screeching when starting a clip with audio
No audio on Fusion page
In DeltaKeyer, eyedropper doesn't work - oh wait, old bug, still never fixed
After using a qualifiers, main track was dimmed out, had to quit program and restart
Auto-Save is not enabled on a new project, so the whole point of not having to save first is moot
Went from Fusion page to Edit page, my main track was gone as well as the file in the Media page - happened 4 times, and even though I had started hitting Cmd-S every few minutes, twice I lost over an hour of work

So, is my original post overstated? Nope. I stand by it. Do NOT use 15.2 for any production work.

Nope. You're still overstating it because you don't know if those problems are universal. For example, I'm not having those same problems so it could be that there is a problem with Resolve 15.2 and your specific OS and hardware combination.

At this point you have yet to even state something as basic as your OS. What use is this post if BMD doesn't know what conditions cause said issues?

I'm not having just one feature that isn't working, it is simply unstable for production use.

Just from the media page, I tried to browse to a folder to add some files, hard crash every single time.
Needed to use DeltaKeyer, multiple crashes
Needed to use LumaKeyer, crashed twice
Started playing one clip on loop with no way to stop it - had to quit program
Horrible audio screeching when starting a clip with audio
No audio on Fusion page
In DeltaKeyer, eyedropper doesn't work - oh wait, old bug, still never fixed
After using a qualifiers, main track was dimmed out, had to quit program and restart
Auto-Save is not enabled on a new project, so the whole point of not having to save first is moot
Went from Fusion page to Edit page, my main track was gone as well as the file in the Media page - happened 4 times, and even though I had started hitting Cmd-S every few minutes, twice I lost over an hour of work

So, is my original post overstated? Nope. I stand by it. Do NOT use 15.2 for any production work.

BMD needs FULL system specs (just put them in your sig like I have) and logs, otherwise how can you expect anything to be fixed?

I've reported numerous bugs over the last few years that never were addressed.

Keep reporting them if they are important to you, though some bugs are less significant than others and probably aren't worth bringing up again until things have smoothed over more.

What's the point of spending the time to report the bugs if they aren't going to be fixed? It ends up being a waste of our time.

Given the number of bug fixes mentioned in the release notes of every version, you know that BMD are listening so it's not a waste of time.

Last week i had to render a 15'' TV commercial 4 or 5 times before audio exported glitch-free. 4 times without changing one single thing in the project. I just kept on exporting it until it was fine.

How can one troubleshoot this?

I'm not sure, but there has got to be more you can say. I'm curious/worried myself about your report, but you've offered so little to go on. Do you use third party vst plugins? Native plugins? Particular audio fx? What kind of glitches? Any suspected correlations?

It's not as if they have a lot of leisure time to investigate, in an open-ended sort of way....

Do they have Beta testers?

While I'm sure they do, they don't make it easy to participate. Which is terrible, since there are lots of people willing to try a bleeding edge software and give valuable feedback.

But even worse than apparently having no outside beta testers is that they have no bug reporting system, at least not one that's open to outsiders. In many projects, once a bug is reported it has to be explicitly dealt with -- assigned a priority, replicated / confirmed, and given consideration for fixing or not fixing.

But the Black Magic bug reporting is post to the forum, and hope. The documentation for scripting is lousy, scripting itself appears to be buggy, and XML import / export doesn't even work when Davinci Resolve is generating the XML!!! Okay, that's my big issue right now, other people have other priorities, but lacking a bug tracking system, all we can do is complain to each other.

I quite like DR, the parts that work, but ignoring bug reports is inexcusable.

Tac

I just need to create a FUSION fragment and it will crash, and the same result will be on any page.

Great to hear your success, but what system specs have you?

Have run Resolve on various systems of varying vintages and with very different specs (the oldest a 2009 Mac Pro running El Capitan, the newest is outlined in my signature) with identical stability and general performance in the version 15 release cycle.

It is worth stating that the overall performance of 15.2 is simply astounding on all systems tested.
The developers have delivered an application that not only outperforms previous releases within the version 15 release cycle, but it is especially apparent when compared with the version 14 release cycle.

I think the wide division of opinion shows just how diverse the use of Resolve is.

For some, who use a particular subset of the funcationality, V15 seems to be acceptably reliable and robust. For others, who use a different subset of the functionality, the reliability and robustness is yet to reach an acceptable standard.

As others have said, a bug-tracking system would be incredibly useful for *everyone*, users and BMD alike.

It would give users confidence that any bugs they have encountered are acknowledged and they'll be able to see the progress that has been made in resolving those issues. It also allows for the collection of far more data -- since others can weigh in with other datasets and additional information if they encounter a bug that has already appeared on the "active" list.

I'm sure BMD are aware that by making this product a very attractive NLE, they're now attracting a much wider audience of users with quite different needs/wants. I certainly hope they haven't bitten off more than they can chew -- given the very attractive pricing model (when compared to the competition).

I continue to recommend Resolve to people (and scores have switched to it on my recommendation) but I do add the caveat that V14 appears to be the most robust option for the time being.

If Version 15 works for *you* and your production environment, that is fantastic... but it is undeniable that there are people out there who are having significant problems. It would be a great idea for BMD to take a moment to focus on addressing bugs before adding new features -- but that is their decision.

Either way, I'm happy with what I'm using and believe it is worth what I paid for it.

I'm not having just one feature that isn't working, it is simply unstable for production use. Just from the media page, I tried to browse to a folder to add some files, hard crash every single time. Needed to use DeltaKeyer, multiple crashes Needed to use LumaKeyer, crashed twice Started playing one clip on loop with no way to stop it - had to quit program Horrible audio screeching when starting a clip with audio No audio on Fusion page.. In DeltaKeyer, eyedropper doesn't work - oh wait, old bug, still never fixed... After using a qualifiers, main track was dimmed out, had to quit program and restart... Auto-Save is not enabled on a new project, so the whole point of not having to save first is moot... Went from Fusion page to Edit page, my main track was gone as well as the file in the Media page - happened 4 times, and even though I had started hitting Cmd-S every few minutes, twice I lost over an hour of work.

So, is my original post overstated? Nope. I stand by it. Do NOT use 15.2 for any production work.

I haven't encountered this many problems, but there are a few issues. Zero problems with adding files to bins, no problems with keys on the Resolve color side, but I haven't used Fusion for anything in this version. No audio issues.

My workaround for the Auto-Save issue is to create empty project "templates" that have all this stuff turned on and preset where I need it to be. This way, timelines, bin structure, configs, Auto-Save, keyboard shortcuts, everything is ready to go when the project is created: I just save the project as a new name and get to work.

I have run into some keyboard shortcut issues, even some very basic stuff like copying-to-clipboard failures. I had an interesting one today: I copied a node, started going through a sequence, and suddenly the clipboard was empty and I could no longer paste. I had to go back and re-copy in order to paste the node. So there are a few little things like this lurking around. None of these are deal-killers for me -- I'm 3 days into a 5-day feature project, and it's going fine. I do save frequently and make 2 backups a day, but that's me.

Surely many problems are given by using basic equipment not suitable for a program of this power. But of course, what can be expected when the license is given with such cheap cameras?. No offense, the most usual thing for people who buy cameras like the pocket is that their equipment is not at the level of 7-10K. Therefore BMD should make sure that Resolve can work with solvency on more basic equipment.

Surely many problems are given by using basic equipment not suitable for a program of this power. But of course, what can be expected when the license is given with such cheap cameras?.

Well this part is rude.

I don't find my workstation to be low-end.

And problems I mentioned in this thread have been reported before. And these are problems that make Fusion inside Resolve unusable. It's 15.2 version now. Not 15 beta. This is official release iteration 5 if I remember. And still Fusion is left behind by developers like no one wanted to look in it's direction.
But new features are here. How sweet.

Editing and Media are working fine on my side though.

If you find issues guys please report specifics, your full system config and attach a link to diagnostic logs so an engineer can review.

If we can repo bugs they are easier to fix.

Unfortunately not all bugs are easy to reproduce.

Last week i had to render a 15'' TV commercial 4 or 5 times before audio exported glitch-free. 4 times without changing one single thing in the project. I just kept on exporting it until it was fine.

How can one troubleshoot this? All i know is that glitches were appearing either at the first few seconds or during shots with Fusion FX.

There is a general memory handling instability throughout Resolve. That's all i can suspect from my experience.

try to set the render speed at 50, instead of 100. it helped me sometimes.

i dont really like bringing this subject up again, or being a part of it, but even though i really like to work in resolve for alot of reasons, i have to agree on the ''instability'' part. or at least/especially in the fusion page. i just cant render/cache without getting gpu, or ''did not complete!'' warnings. even in the most simple comps. with 2 1080 ti's. every update brings some ''general stability improvements'', but it really feels like it's in the very core of the software. i know i should send some logs, and i did, but i just cant send logs each time something like this comes up, it just happens so many times. alot of functions are also very new ofcourse, so its not unimaginable that there are some things not really polished yet, but how many years should it take? i keep seeing things like ''the most advanced software''. well yeah, at the moment for color grading maybe. editing is also really advancing.

i really like the direction the software is going, and i just know many people are working very hard at it. i wish i could be of help

Well this part is rude.

I don't find my workstation to be low-end.

I don't think I've been understood, or I haven't explained myself well. My English is not very good.
If you read my previous comment, I also have problems, with old bugs that are not fixed. Very annoying. For me Fusion panel is unusable, and I have two computer, mid and highend.
My comment was not for something in concrete said here, but a comment in general, the route that Resolve has followed, to reach everyone guys, IMHO. That leads to problems with basic equipments and it seems that BMD does not realize it.

That leads to problems with basic equipments and it seems that BMD does not realize it.

Resolve 15 isn't really for basic equipment. For example, if you want to use Fusion they recommend 32GB RAM, anything below that and I'd say 'good luck!'. That means if you want to use Fusion on a Mac laptop, you'd need one made in 2018 (and costing a small fortune). Old graphics cards are bad news too.

I'd stay away from Windows 10 also, or at least restrict its internet access so that it doesn't auto-update and break your software for you, which is a well-documented feature. I don't think it's a coincidence that most of the serious complaints are coming from Windows users (something I have noticed since the Resolve 14 betas and probably earlier).

For example, if you want to use Fusion they recommend 32GB RAM, anything below that and I'd say 'good luck!'.

If good luck means shorter buffer for cached preview, than it's not such a bad luck. You can work with 16GB without a problem (and I did with Fusion Studio standalone after my memory failure).
I even worked with previous version of Resolve pretty well on my Dell XPS laptop with 8GB RAM. And I'm talking previous versions of Resolve with Fusion and working in Fusion specifically.

There are places where hardware configuration is crucial. Also there are places where an unknown hardware failure can cause problem (I had bent pin on MOBO generating ocasional crashes and memory instability for example). And I think lots of us know it.

What we're talking here mainly is making two steps back after taking one forward. Striking new features before old features are stabilised and bugs are fixed.
Davinci is marketed now as a Editing/VFX/Sound Bhemoth - but it's only marketing mambo jumbo right now untill major bugs get fixed. And BMD don't fix them like they didn't see them. Do we really have to say it so many times in this thread?