Your liveries, managed.
FORC3 Grid reads Assetto Corsa EVO’s own livery folder straight from your
browser. Connect it once and you can see every skin you have installed,
pack any of them into a .grid file to share, and install
packs other people send you — re-linked to your cars automatically.
Pick C:\Users\you\Saved Games\ACE —
or just pick Saved Games, or your user folder, and FORC3 Grid
will find it from there.
Your browser has to ask: a website can’t look at your drive on its own.
Nothing is uploaded — the folder is read on your machine.
No liveries installed yet.
Paint one in FORC3 Designer, or install a .grid pack someone shared with you.
Reaching the library…
It may be down for a moment, or your connection may be. Everything else
here works without it, and .grid packs work the way they
always do — export one from your garage and send it to anyone, over
Discord or however you like. Come back to this tab in a little while;
it checks again each time.
Nothing matches that.
Why a skin can’t just be copied
AC EVO ties every external livery to a car GUID — the id of one
specific car in your own garage, written into
external_livery.json. Your Ferrari 296 GTB and mine have
different GUIDs, so a livery folder copied straight across binds to
nothing and quietly does not show up.
A .grid pack records the car’s model instead
(ks_ferrari_296_gtb), which is the same string on every
install of the game. On the way in, FORC3 Grid looks up your saved car
for that model and rewrites the binding to point at it. That is the
whole trick, and it is why packs install correctly on a machine that has
never seen the original.
Liveries that are not packs yet
Almost none are, today. A livery normally travels as the folder the
game itself uses — six textures and an
external_livery.json — copied off someone’s
machine or zipped into a Discord channel. Install Livery takes
one of those directly: pick the folder, or drop the zip on this window.
It cannot know which car the folder is for, because the only car it
names is one in the sender’s garage. So FORC3 Grid reads the
folder name, suggests the closest match from your cars, and
asks you to confirm before it writes anything. From then on it is a
managed livery like any other — renameable, copyable onto your
other cars of the same model, and exportable as a
.grid.
What a pack contains
The six texture maps, a manifest, and a preview — about 3 MB. It does
not contain the game’s compiled .texturemips cache,
which is around 77 MB per livery, is regenerated on demand, and would
actively break the install if shipped stale.
Will other drivers see my skin?
Everyone who installs the same pack has the same textures on disk, which is the prerequisite. Whether AC EVO then shows a remote driver’s external livery in a multiplayer session is not something we have verified, and we would rather say so than promise it. The moment it is tested, this page will say plainly which way it went.
3D preview
Not yet. The groundwork matches FORC3 Designer’s renderer so it can be
added without changing the pack format — see js/preview.js.