Step 1
Choose your OLS database
Point TuningBay Desktop at the folder or disk that contains your own OLS project archive.
OLS Packer · private local index
OLS Packer turns your existing OLS project archive into a private local index. Find the closest project for a loaded BIN, select the layers you need and apply them through TuningBay Inspector — while the source database stays on your computer.
It is built for tuners and file sellers who already own a valuable WinOLS project base and want to reuse it through a faster, controlled workflow without exposing that database to a remote service.
Step 1
Point TuningBay Desktop at the folder or disk that contains your own OLS project archive.
Step 2
OLS Packer creates the searchable index on your Windows computer. Your OLS files, paths and index data do not leave the selected disk.
Step 3
Open a BIN in TuningBay Inspector and search the private index for the closest matching project from your own database.
Step 4
Apply the selected Stage and solution layers to the loaded file, then inspect the result inside the same TuningBay workspace.
OLS files, paths and index data stay on the selected Windows disk.
Folder selection, indexing, matching and Apply run through TuningBay Desktop and Inspector.
Indexing, searching and no-match results are free. A successful Apply uses 5 credits.
No. The OLS database, local paths and generated index stay on your computer. The protected desktop module performs indexing and matching locally.
No. OLS Packer is designed to use your existing OLS project archive through TuningBay Desktop and Inspector without opening WinOLS for the matching and Apply flow.
A successful Apply costs 5 credits. Building the index, searching it and receiving no-match results do not consume operation credits.
The protected OLS Packer module currently runs on Windows x64 through TuningBay Desktop.