# AEMS bank path fix and selectable-car load check, r423

The first sequential browser pass after adding AEMS playback found 404s for four selectable cars: 3000GT, Eclipse, RSX, and Skyline. Their executable profiles name banks `CAR_06_ENG_MB_SPU.abk`, `CAR_04_ENG_MB_SPU.abk`, and `CAR_09_ENG_MB_SPU.abk`, while the extracted folders preserve two-digit directory names (`06`, `04`, `09`). The viewer converted each ID to an integer and requested non-existent `/aems/6`, `/aems/4`, or `/aems/9` paths.

The loader now pads the numeric bank ID to two digits when constructing the AEMS path. The four previously failing models were reselected in the packaged host-Chrome viewer. Each reached its rendered-car key and the `original AEMS/Ginsu recordings` ready state. The rerun reported no page exceptions, console errors, failed requests, or HTTP errors.

Combined with the immediately preceding sequential pass, which loaded the other 25 stock car/AEMS mappings, all 29 selectable cars now reach the AEMS/Ginsu-ready state. This checks recording-bank loading, not the perceptual correctness of every engine sound. The selected RPM bands remain approximate as documented in [the mixer trace](engine-aems-ginsu-browser-mixer-r422.md).