Introduction

Cricket 2002 arrives from HB Studios as an early-2000s attempt to translate the pleasantly complicated sport of cricket into a console-friendly package. It was released on PlayStation 2 (and Windows) in the period when developers were still figuring out how to balance realism against the tight CPU/GPU budgets of a console generation that had only recently discovered 3D textured polygons. If you already know HB Studios from later cricket titles, this is one of their earlier efforts where the constraints of the era are obvious - and interesting - from a technical standpoint. This review is purposefully detail-oriented: I'm interested in frames-per-second, input latency, animation pipelines, state machines, and the little places where the game's systems either sing in harmony or fall flat and require duct tape and prayer.

Gameplay

At a systems level Cricket 2002 feels like a collection of tightly integrated subsystems: an input mapping layer, an animation/pose blending system for player avatars, a physics and collision detection module for ball behaviour, a camera manager that attempts to keep the ball and action readable on a 4:3 screen, and AI routines for bowler and fielder decision-making. The controls are conservative by modern standards: face buttons and the left analog for running, with a combination of timed button presses and directional input to select shot types. This control scheme matches the PS2 controller's affordances, but it exposes two core technical compromises. One, the input abstraction is largely poll-based and tied to frame updates; sharp timing windows can be unforgiving. Two, the abstraction doesn't fully decouple input intent from animation length, so there are frequent instances where the player's requested shot "arrives" visually a few frames after the button press due to long animation clips, which is clearly a consequence of the animation system prioritising visual continuity over responsiveness. Batting and bowling are where the game's state machines are most visible. The batting state machine tries to manage dozens of discrete states - idle, forward defensive, back foot punch, sweep, lofted shot, misc. footwork transitions - and when it works, the result is readable: you can chain a defensive move into a drive without the avatar flopping like a malfunctioning marionette. When it fails, you see the classic "animation lock" problem: a long animation clip plays and ignores new input until it reaches a cancelable frame. That was common in the era, but Cricket 2002's implementation is only partially mitigated by a moderate set of cancel windows. For players used to modern input buffering and animation blending this will feel imprecise; for folks used to PS2-era sports titles, it's par for the course. Ball physics are implemented with a deterministic-ish model: a parametric trajectory influenced by initial velocity, spin vectors, and a simplified pitch interaction routine. The ball-pitch interaction is not full rigid-body dynamics; it's closer to a layered approach: base ballistic trajectory + randomised pitch deflection + bounce scaling based on nominal pitch condition. That produces a believable range of outcomes - seamers can get lateral movement at the wicket and spinners can produce exaggerated turn - though the system occasionally produces improbable bounces because the collision response lacks per-frame sub-stepping. In practice you see discrete jumps in the ball's lateral movement rather than smooth arcs, which is a symptom of using single-step collision responses at 60/30fps (depending on mode) instead of continuous collision detection. Fielding and AI are modestly competent. Fielders have priority-based behaviour trees: pick up the ball, throw to wicket, back up, or chase bounding balls. The decision heuristics are simplistic but effective, with parameters for risk tolerance, speed and throw accuracy. The throw accuracy is handled by a probabilistic model influenced by fielder stats and an RNG seed; you will see throws that miss by a hair because the RNG was not locked to a predictable seed per match, which increases perceived inconsistency. AI bowlers choose lines and lengths from a weighted table, which is easy to read for a player who likes to game the system, but it does offer a reasonable simulation of bowler style variance. Game modes are basic: exhibition, quick match, and tournament structures; there's a basic roster and stats tracking but nothing like the deep career simulation modern titles offer. The user interface is made up of several layers of 2D HUD elements over the 3D world. From a tech POV the UI is a classic PS2-era HUD with fixed-resolution bitmaps and rudimentary scaling, meaning the HUD is crisp on standard shows but will show pixelation if you upscale. Save system and state persistence rely on the PS2 memory card APIs (or Windows file I/O on PC builds) and are unremarkable, but reliable. Loading times are present but not egregious; the engine streams certain stadium assets as you approach them to keep initial loading reasonable, a smart move given PS2 memory limitations. In sum, the gameplay architecture shows thoughtful subsystem boundaries but leans on era-typical compromises: chunky animation clips, single-step physics, and simple AI heuristics.

Graphics

Rendered on PS2 hardware, Cricket 2002's visuals are a textbook study in polygon budgeting and texture juggling. Player models are low-to-medium poly for the time, with head and torso rigs getting the most attention and limbs simplified to preserve polygon budget. The animation pipeline uses baked keyframe animations exported from whatever toolchain HB Studios used circa 2001-2002, and the game relies heavily on animation transitions to hide clipping and joint popping. Facial detail is minimal - face textures are flat billboard-like images rather than rigged facial morphs - but the helmet, clothing folds and bat geometry get prioritized. Textures are modestly filtered; you can see the classic PS2-era texture compression artifacts if you peer closely at the kit logos and the pitch grass textures. Lighting is primarily static and baked into vertex colours and diffuse textures with a small per-vertex dynamic highlight for the ball and bright specular on glossy helmets. There's no global illumination or complex shadowing: shadowing is geometry-projected, with blob-like shadow textures under players when active. This technique keeps GPU load down but causes the shadows to detach visually from the models at sharp camera angles. Draw distance is tuned conservatively with level-of-detail (LOD) swapping. Stadium geometry uses aggressive LOD transitions, and the crowd is a clever 2D sprite sheet with a few animated frames; at a distance this reads as a lively crowd, but zoom in and you'll notice identical head sprites repeating in a pattern. The camera system deserves a detailed note because readable presentation matters more in cricket than in many other sports. The camera manager swaps between a set of predetermined cinematic anchors based on ball position and phase: bowler run-up, camera near the wicket, and a wide mid-field camera for fielding plays. Each anchor blends with the previous to avoid jarring cuts, but those blends are time-based rather than context-sensitive, leading to some odd camera positions during sudden run-out opportunities. The field-of-view (FOV) is narrow by modern standards; on a CRT you felt grounded in the pitch, but on a larger display the constrained FOV can make peripheral motion feel cramped. Performance is acceptable: the engine aims for 30fps for most gameplay and drops to lower rates during complex cutscenes. On PS2, CPU and GPU contend for memory bandwidth, and the renderer prioritises frame stability over fancy effects. When multiple players converge on the ball you can see a small framerate dip and a rise in pop-in as nearby crowd geometry and certain high-res textures are streamed in. Particle effects for dust and turf chunks are lightweight but well-handled, using sprite particles with lifetime culling. Audio is functional: ball impact, bat thwacks and crowd audio are layered but not very dynamic; the mixing engine uses a flat priority queue so important audio can sometimes be masked by crowd noise if too many sources are active.

Conclusion

Cricket 2002 is a PS2-era technical snapshot: it shows how a smallish developer like HB Studios carved a playable cricket simulation out of limited hardware. The core engineering is respectable - clean subsystem separation, deterministic-enough physics for a sports game, and a readable camera system - but the game is also a catalogue of the era's trade-offs: animation locking that undermines input responsiveness, single-step ball collisions that can produce discrete lateral jumps, and texture/LOD strategies that prioritise framerate at the expense of visual fidelity. If you play it with the expectations of a nostalgic technophile - appreciating the efficient streaming, the constrained animation pipelines and the clever use of sprite crowds - the experience can be charming. If you expect the modern standards of latency hiding, inverse kinematics for player placement, and continuous collision detection, this will feel dated. From a purely technical critic's point of view the title earns a solid middling score because it succeeds at the right problems for its time while leaving several solvable technical rough edges. I score Cricket 2002 a 6.8 out of 10: praiseworthy engineering for 2002, but not enough systemic polish to compete with later cricket sims that learned how to fuse animation and input more tightly and to replace single-step physics with more continuous approaches. Recommended for collectors, technical historians, and players who want a playable cricket sim that won't melt modern expectations; casual newcomers should try a more recent title for smoother, more responsive mechanics. If you're into tinkering, there's a lot to admire beneath the surface - and if you're into nostalgia, the game's slightly chunky frame and honest limitations are half the fun.

See Prices for Cricket 2002 on PS2 on Ebay

See Latest Prices for Cricket 2002 on PS2 on Amazon