PLAYER GUIDE • PURBACHAL RACING
Development Notes & Version History
How Purbachal Racing improved its car physics, moving world, and presentation through iterative testing.
Purbachal Racing has grown through iterative gameplay testing rather than a single release. A major design challenge was giving players the feeling of moving along a road while keeping the sports coupe stable in the camera view.
Early prototypes
Earlier experiments tried different vehicle bodies, camera distances and road motion systems. Several car shapes were too tall and obscured the road, making the driving perspective feel cramped. This led to a more restrained third-person camera.
The wheel rotation lesson
An early code issue selected groups containing cylindrical parts and rotated them as though they were wheels. Because the car also had cylindrical details, the whole model could tip during acceleration. Later versions separated the actual wheel meshes from other car parts, avoiding the unintended body rotation.
V15: approved driving baseline
Version 15 established the approved upright coupe, stable chase camera and readable forward-driving effect. The Purbachal-inspired roadside scenery was kept in place. That approved motion and car behaviour became the baseline for later additions.
V16: championship and atmosphere
The game expanded into a twelve-lap challenge with lap-completion moments. Eight lighting/weather themes, Bangladesh flags and more prominent aircraft were added to improve replay variety. Weather scenes are visual effects, not local weather forecasts.
V18: a more useful public website
This site update adds practical driving advice, event rules, a detailed weather guide, context on the Bangladesh-inspired world and a transparent development history. The racing engine is preserved; these articles are meant to help players understand the game before and after a run.
What comes next?
Planned work includes better device performance measurement, improved accessibility choices, more detailed road artwork and testing with web-game publishing platforms. Features should be validated in real browsers before being described as ready.