Cannot Reinstall Repository

[HawkeMaylan]

Select Topic Area

Question

Body

Due to errors with githubs reverting commits not properly importing unity items back I had to uninstall and attempt to reinstall the project. However I get the error posted below even though my account reports no usage of git LFS (I own the repository) nor any storage in it as I disabled the git LFS on the repository a long time ago.

Cloning into 'C:\AoTTG 2 Retribution Mod Unity Project\Aottg2-Unity-Retribution-Mod\Aottg2-Unity-Retribution-Mod'...
remote: Enumerating objects: 65956, done.
remote: Counting objects: 100% (3319/3319), done.
remote: Compressing objects: 100% (706/706), done.
remote: Total 65956 (delta 3032), reused 2666 (delta 2613), pack-reused 62637 (from 3)
Receiving objects: 100% (65956/65956), 356.97 MiB | 32.40 MiB/s, done.
Resolving deltas: 100% (49001/49001), done.
error: unable to create file Assets/AssetBundle/Varreosa/New Resources/Building Models/DistrictBuildings/Just Models/Materials/Huge_med_set.jpg81c5a648-736e-4f4b-8c7e-d4ef5510fea8DefaultHQ.mat: Filename too long
error: unable to create file Assets/AssetBundle/Varreosa/New Resources/Building Models/DistrictBuildings/Just Models/Materials/Huge_med_set.jpg81c5a648-736e-4f4b-8c7e-d4ef5510fea8DefaultHQ.mat.meta: Filename too long
error: unable to create file Assets/AssetBundle/Varreosa/New Resources/Building Models/Village Buildings/Just Models/Materials/Huge_med_set.jpg81c5a648-736e-4f4b-8c7e-d4ef5510fea8DefaultHQ.mat: Filename too long
error: unable to create file Assets/AssetBundle/Varreosa/New Resources/Building Models/Village Buildings/Just Models/Materials/Huge_med_set.jpg81c5a648-736e-4f4b-8c7e-d4ef5510fea8DefaultHQ.mat.meta: Filename too long
Updating files: 100% (19794/19794), done.
Downloading Assets/AssetBundle/Act 4/Imported Maps/AOTTG materials/textures/Building Textures/aot brick texture.jpg (173 KB)
Error downloading object: Assets/AssetBundle/Act 4/Imported Maps/AOTTG materials/textures/Building Textures/aot brick texture.jpg (0230f93): Smudge error: Error downloading Assets/AssetBundle/Act 4/Imported Maps/AOTTG materials/textures/Building Textures/aot brick texture.jpg (0230f93c2d58381d099c5335240d7d4347a5b208a79de96db2ed234aaf6a06ff): batch response: This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access.

Errors logged to 'C:\AoTTG 2 Retribution Mod Unity Project\Aottg2-Unity-Retribution-Mod\Aottg2-Unity-Retribution-Mod.git\lfs\logs\20251118T030329.9078629.log'.
Use git lfs logs last to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: Assets/AssetBundle/Act 4/Imported Maps/AOTTG materials/textures/Building Textures/aot brick texture.jpg: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Would you like to retry cloning ?

[syednoor058]

It looks like you’re running into two separate issues:

1. “Filename too long” error (Windows)

This part is not related to Git LFS.
Windows has a default MAX_PATH limit of 260 characters, and some Unity asset paths in this project exceed that.

You can fix it by enabling long paths:

On Windows 10/11

Search gpedit.msc → open

Go to:
Local Computer Policy → Computer Configuration → Administrative Templates → System → Filesystem

Enable: “Enable Win32 long paths”

Restart your PC

Alternatively, enable it via the registry:
reg add HKLM\SYSTEM\CurrentControlSet\Control\FileSystem /v LongPathsEnabled /t REG_DWORD /d 1 /f

2. Git LFS error: “This repository exceeded its LFS budget”

Even if you disabled LFS now, your repository still contains old LFS pointers in its history.

So when you clone, Git tries to download those LFS files → fails → shows this error.

This means:

Your repo still has LFS files stored on GitHub,

And the owner’s LFS bandwidth/storage is fully used.

How to fix it

Option A — Increase LFS storage/bandwidth (requires the repo owner)
Buy/add LFS packages from GitHub Billing → Storage.

Option B — Remove LFS usage from the repo
If you want to completely get rid of LFS:

a. Remove LFS hooks locally:
git lfs uninstall

b. Remove LFS pointers from your repo history:
git lfs migrate export --everything

c. Force-push the cleaned repo:
git push --force
(Repo owner only)

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬