Yes. I've noticed this too. The lighting seems to be very odd in this version and the position of the Sun doesn't seem to be accurate for geographical location and time of day. Often I've found first class cricket being played under floodlights in the dark too...I've never gone off for bad light. Is bad light even a thing in the game?
That said, and always looking for positives, on an unrelated note I do think that BA have done a good job with spin bowling in this version. This is the first version where I've seen noticeable turn. I think DBC14 was best for drift but most versions have done little more than straighten with the turning ball. I don't know whether this is down to fiddling a bit with sliders or whether BA have just made turn more of a factor but I just had a great First Class game in career mode for Durham vs Surrey, picking up 4-94 in the first innings and 6-62 in the second. Lots of different wickets (catch in the deep, full-stretch dive at cover, catch at midwicket, LBW, caught behind, catches at slip and leg slip, bat pad, couple of nice clean bowled bowling outside leg and turing back in to hit leg or middle-and-leg) and lots plays and misses as the ball turns sharply past the bat. Genuinely a lot of fun.
!! (I couldn't play C19 with the later patches or C22 as a spec bowler mate, (especially as I use Elite Series 2 controllers lol 
).
. Sadly, if the patches don't help then lazy/rushed coding or a lack of implementation may be the root problem to have not changed, or at least mitigated these issues by now that so many complain about. I wouldn't mind so much if I went for 3 or 4 rpo in tests, 4 to 6 in ODI, or 8 to 12 rpo in T20/The Hundred if the game reflected those runs more realistically with the AI batsmen working the opportunistic singles & twos depending on my performance as a bowler & my field set etc. Instead, we all get smacked around the park without fail (from the first ball in the short formats) regardless of whether it's a batting or bowling PP, wickets lost, weak batting team, or any other aggravating factors, unless the AI has of course predetermined that the AI batting order will collapse early for a low score anyway. (There's nothing more infuriating than BA giving us these comprehensive field editors, we come up with all sorts of different creations, only to use them in game & what does the AI do? They then launch at least one six straight over the top of the assigned boundary riders in the field set on ball one of an over anyway. (They don't even bother to aim for the nearby gap in case it drops short for four (which of course it won't) because of this poor scripting issue plaguing C19 & C22.)
