"Random & unique to him"? Seriously?
I'm assuming your cousin's Xbox of record is playing the same Cricket 22 that you're also playing on your device where - "the (
note - virtual) ball weight is completely off, you want to feel that weight, but it just "feels" like the weight of a tennis ball to you"?
Ergo, if it's not really "running the game fine" on your device because you can't actually "feel" the weight of a cricket ball through your console & it's all wrong, is it truly running just fine on another console right there within your own family as claimed? (If so, then I'm utterly bewildered & confused lol
.)
Conversely, does every C22 owner/user experience an issue with how you personally feel the ball weight or is that perhaps more random or unique?
How does one gauge the weight of a virtual item? How many pixels would it take to actually register as weight? (That's like the rhetorical "if a tree falls in a forest" question, don't answer that one
!!) What is it you're actually asking for with ball weight? Do you want your controller to madly vibrate or administer a significant electric shock for incoming deliveries above 90 MPH, for example? How does one convey a "heavy virtual ball vs a light virtual ball"? (You just don't make any of this clear. Any cricket fan can immediately understand what's meant by the term "heavy ball". But, how exactly should it be conveyed in C22 given that the controller already vibrates to signify issues with shot timing/feedback? Are you asking for an option to disable the shot timing feedback & instead vibrate for deliveries faster than 90 MPH?)
Is the weight of a virtual ball not a matter of user perception rather than tactile feel anyway? Perception of ball speed, animation timings, the actual sound recordings of "bat on ball" used by the devs conveyed through your individual TV speakers or audio system & how you subjectively hear them? (All assuming there's no A/V or control input lag locally with your hardware of course.)
Otherwise, your cousin has a Series S that apparently works fine so you're perfectly content to state as fact to the Series X owners out there experiencing the exact same issue as
@Hester that it's their unique device? (In essence & by implication from such a statement, you're also telling them that they should either mess around factory resetting their device, try/buy a different controller/peripheral, try/buy another display device entirely, start purchasing & swapping out various cables, or even return their Xbox for a repair at their own cost too!! Either way, that takes some stones bud I'll give you that much, no scratch that, "
weighty leather ones"
. What's more, you don't think that's all been tried already by those so affected?
This title has been absolutely RIDDLED with issues since release & patches remain a highly controversial subject, but C22 seriously crashing someone else's device can be so easily dismissed as a random & unique one off?
PLEASE, read back through this thread & you'll soon note multiple owners specifically of the SERIES X complaining of the exact same issue where their game just suddenly hangs, then there's a brief green screen for approximately 1-2 seconds as C22 inevitably crashes the Series X so badly (AGAIN) that it shuts the device down entirely. No other titles or apps they have even crashes their Series Xs' ( except MSFS 2020 but that's another issue entirely & not even MSFS 2020 shuts the device down
), otherwise, it's just C22 & C22 alone that crashes & actually crashes the Series X itself with it too.
(You'll also soon note that there have been ZERO owners of the Series S in this thread complaining of this specific issue too.)
Not sure if you're aware of this or not either.....? However, there are significant differences between the Series S & the Series X, not by any means limited to the fact that the Series S doesn't even natively support 4K as a start & how the Series X implements 4K.
......and
....
????
