At no point in the "marker" scenario are you watching the ball out of the hand, or towards your player because the game has already told you exactly where it's going to be.
Seriously, wtf is going on in your head? I've already specified in post you quoted the the marker shouldn't appear until the point of release. You wouldn't be able to see it until the ball is in the air. It doesn't even need to stay on screen for the entire delivery. It doesn't have to be implemented like EA cricket, so you insisting that it has to be implemented exactly like EA cricket is just daft.
Just to take a quick look at this :
In DBC
- Your perspective from behind the batsman has you viewing the run-up from the start, eyes never off the ball/bowler
Which would be identical with an on-release pitch marker. You're convinced the marker has to happen before the delivery for some weird reason. And what, reverse camera is a DBC thing? I've been playing with reverse or first person cam since (I think) BLC 99, and I was watching the ball/bowler the whole way, and I was here posting on this board that reverse camera was the only correct perspective and everyone on here was nuts for preferring broadcast cam.
This idea that you must watch the pitch marker and not the bowler or ball is just flat out nonsensical. Ok, I guess you can just stare at the marker the whole time like a doofus, but there's no necessity that you do so, and excellent reasons not to.
- You select front or back foot prior to the delivery, which is premeditated according to your players attributes (predominately front or back foot player)
Ok, this is obviously the problem bit in DBC. If you have the info a pro batsman has at the point of release, there ought to be enough time to select your shot without premeditating your foot choice, which is the single biggest factor in shot selection. But by the time you've had a look at the delivery vs a quick in DBC, the timing window has already gone. You need to get your right stick pressed before the ball is halfway.
In fact, DBC effectively has auto foot selection built in, because the same input will often produce either a front foot or back foot result depending on the length of delivery, and I suggest there's a strong argument that auto foot selection is more of a backward step for cricket gaming than the concept of a pitch marker.
- You watch the bowler's entire motion, waiting until the ball leaves the hand and you get the )) or (( swing makers, then select your shot direction based on the ball and comet trail through the air (Is it on my pads, is it moving away from off?)
Ok, so further to the above, DBC requires shot input before most of the delivery has happened vs the quicks. That's the whole problem, and it's exactly the info shortage that an on-release pitch marker would fix.
I've argued before that a hypothetical two stage input system for DBC - where footwork is independent so you can delay your shot input until the ball is nearer the batsman - would be another solution, and is actually the one I would prefer.