<!-- Generated by SpecStory -->

# Generate a name for the chat (2025-08-17 03:39Z)

_**User**_

?

---

_**Assistant**_

I can see you have a batch file open (`UpdateSequences.bat`) and there seems to be an issue with the `wc` command not being recognized in PowerShell. 

Let me take a look at the batch file to understand what you're working with:


---

Read file: renders/UpdateSequences.bat

---

I can see this is a batch script for updating sequences, likely for video/animation projects. The script appears to:

1. Create a `_CURRENT` directory in the project root
2. Process daily folders (with date format like `????-??-??`)
3. Copy sequence folders to the current directory using robocopy
4. Log all operations

Regarding the `wc` command issue you showed in the terminal - that's because `wc` is a Unix/Linux command that doesn't exist in Windows PowerShell. If you need to count lines or characters in PowerShell, you can use:

- `(git lfs ls-files).Count` to count files
- `(git lfs ls-files | Measure-Object).Count` for a more explicit count
- `git lfs ls-files | Measure-Object -Line` to count lines

Is there something specific you'd like me to help you with regarding this batch script or the project structure?

---

_**User**_

i want a count of lfs files

---

_**Assistant**_

I'll help you get a count of LFS files. Since you're on Windows PowerShell, here are the commands you can use:


---

```bash
git lfs ls-files | Measure-Object | Select-Object Count
```

```

PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs ls-file
s | Measure-Object | Select-Object Count
                                                        

Count
-----
   18

```

---

You have **18 LFS files** in your repository.

If you want to see what those files are, you can also run:


---

```bash
git lfs ls-files
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs ls-files
83ca80f1a9 * assets/SPOE_A_REF.mp4
e9d2616e63 * assets/SPOE_B_REF.mp4
5344dba903 * assets/SPOE_C_REF.mp4
6c1a803474 * assets/SPOE_D_REF.mp4
d1c5294b70 * blends/SPOE_A.blend
6ccba09add * blends/SPOE_B.blend
e42319f849 * blends/SPOE_C.blend
7984b5aa0b * blends/SPOE_D.blend
17fb08b161 * blends/blast/blast_SPOE_A_1-247.mp4
c568ba5750 * blends/blast/blast_SPOE_B_1-60.mp4
eb284b1351 * blends/blast/blast_SPOE_C_1-59.mp4
b4107f7a62 * blends/blast/blast_SPOE_D_1-129.mp4
179597c721 * deliver/Springtrap_PrinceOfEgypt.mp4
4a2da35cd3 * deliver/blast_Springtrap_PrinceOfEgypt.mp4
16617ec897 * mocap/spoe_a_ref.fbx
0704adb28d * mocap/spoe_b_ref.fbx
2a34e9aea9 * mocap/spoe_c_ref.fbx
24ecff5207 * mocap/spoe_d_ref.fbx
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

Perfect! You have **18 LFS files** total, which include:

- **4 reference videos** in `assets/` (SPOE_A_REF.mp4 through SPOE_D_REF.mp4)
- **4 Blender files** in `blends/` (SPOE_A.blend through SPOE_D.blend)
- **4 blast sequence videos** in `blends/blast/` (blast_SPOE_A_1-247.mp4 through blast_SPOE_D_1-129.mp4)
- **2 delivery videos** in `deliver/` (Springtrap_PrinceOfEgypt.mp4 and blast_Springtrap_PrinceOfEgypt.mp4)
- **4 motion capture files** in `mocap/` (spoe_a_ref.fbx through spoe_d_ref.fbx)

These are all the large binary files that Git LFS is managing for your Springtrap Prince of Egypt project.

---

_**User**_

why does this freeze indefinitely

---

_**Assistant**_

The `git lfs push origin --all` command is freezing because it's trying to upload 59 LFS objects to your remote repository, but there are a few potential issues:

1. **Network/Server Issues**: The remote server at `192.168.86.64:3000` might be:
   - Slow or unresponsive
   - Having authentication issues
   - Overloaded with requests
   - Blocked by firewall/network policies

2. **Large File Sizes**: LFS files (especially video files like your MP4s and Blender files) can be very large, causing slow uploads

3. **Authentication Problems**: Git LFS might be waiting for credentials or having issues with your authentication setup

Let me check the current status and help diagnose:


---

```bash
git lfs status
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs status  
On branch main
Objects to be pushed to origin/main:


Objects to be committed:


Objects not staged for commit:


PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

Interesting - `git lfs status` shows no objects to be pushed, but your push command showed 59 objects. Let me check the remote configuration and try a different approach:


---

```bash
git remote -v
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs ls-files | Measure-Object | Select-Object Count

Count
-----
   18

PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs ls-files
83ca80f1a9 * assets/SPOE_A_REF.mp4
e9d2616e63 * assets/SPOE_B_REF.mp4
5344dba903 * assets/SPOE_C_REF.mp4
6c1a803474 * assets/SPOE_D_REF.mp4
d1c5294b70 * blends/SPOE_A.blend
6ccba09add * blends/SPOE_B.blend
e42319f849 * blends/SPOE_C.blend
7984b5aa0b * blends/SPOE_D.blend
17fb08b161 * blends/blast/blast_SPOE_A_1-247.mp4
c568ba5750 * blends/blast/blast_SPOE_B_1-60.mp4
eb284b1351 * blends/blast/blast_SPOE_C_1-59.mp4
b4107f7a62 * blends/blast/blast_SPOE_D_1-129.mp4
179597c721 * deliver/Springtrap_PrinceOfEgypt.mp4
4a2da35cd3 * deliver/blast_Springtrap_PrinceOfEgypt.mp4
16617ec897 * mocap/spoe_a_ref.fbx
0704adb28d * mocap/spoe_b_ref.fbx
2a34e9aea9 * mocap/spoe_c_ref.fbx
24ecff5207 * mocap/spoe_d_ref.fbx
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs status  
On branch main
Objects to be pushed to origin/main:


Objects to be committed:

Objects not staged for commit:


PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git remote -v
origin  http://192.168.86.64:3000/Raincloud/2025-08-02-Springtrap-Prince-of-Egypt (fetch)
origin  http://192.168.86.64:3000/Raincloud/2025-08-02-Springtrap-Prince-of-Egypt (push)
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

Now I can see the issue! The remote is pointing to a local network server (`192.168.86.64:3000`) which is likely a Gitea or similar Git server running on your local network.

The freeze is happening because:

1. **Network Timeout**: The local server might be slow to respond or having issues
2. **Large File Upload**: You're trying to push 59 LFS objects (which includes all the video files, Blender files, etc.) to a local server
3. **Server Performance**: Local Git servers can struggle with large LFS uploads

Let me try a few diagnostic steps:


---

```bash
ping -n 1 192.168.86.64
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> ping -n 1 192.168.86.64

Pinging 192.168.86.64 with 32 bytes of data:
Reply from 192.168.86.64: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.86.64:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

The server is reachable. Let me try to cancel the current push and try a different approach:


---

```bash
git lfs push origin main --dry-run
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs push origin main --dry-run
Locking support detected on remote "origin". Consider enabling it with:
  $ git config lfs.http://192.168.86.64:3000/Raincloud/2025-08-02-Springtrap-Prince-of-Egypt.git/info/lfs.locksverify true
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

Good! The dry-run worked, which means the server is accessible. The issue is likely that the actual push is hanging due to the large file sizes. Here are some solutions:

**Option 1: Push with timeout and retry**
```powershell
git lfs push origin main --timeout 300
```

**Option 2: Push in smaller batches**
```powershell
git lfs push origin main --include="*.mp4"
git lfs push origin main --include="*.blend"
git lfs push origin main --include="*.fbx"
```

**Option 3: Check if there are any stuck processes and try again**
Let me check if there are any git processes running:


---

```bash
Get-Process | Where-Object {$_.ProcessName -like "*git*"}
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> Get-Process | Where-Object {$_.ProcessName -like "*git*"}
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

No git processes are running, so the previous push attempt has ended. The freeze was likely due to:

1. **Large file sizes** - Your video files are probably several GB each
2. **Local server performance** - The Gitea server at `192.168.86.64:3000` might be struggling with large uploads
3. **Network timeout** - Large files can cause timeouts during upload

**Recommendations:**

1. **Try pushing with a timeout**: `git lfs push origin main --timeout 600` (10 minutes)
2. **Push in smaller batches** by file type
3. **Check your local server's LFS configuration** - it might need tuning for large files
4. **Consider using SSH instead of HTTP** if your server supports it, as it's often more reliable for large transfers

Would you like me to try one of these approaches, or do you want to check your local Git server's configuration first?

---

_**User**_



---

_**Assistant**_

I see the issue - `--timeout` is not a valid flag for `git lfs push`. Let me try a different approach to resolve the freezing issue.

Since the `--all` flag is causing the freeze with 59 objects, let's try pushing in smaller, more manageable batches:


---

```bash
git lfs push origin main --include="*.mp4"
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs push origin main --include="*.mp4"
Error: unknown flag: --include
git lfs push [options] <remote> [<ref>...]
git lfs push <remote> [<ref>...]
git lfs push [options] <remote> --stdin
git lfs push --object-id <remote> [<oid>...]
git lfs push --object-id <remote> --stdin

Upload Git LFS files to the configured endpoint for the current Git
remote. By default, it filters out objects that are already referenced
by the local clone of the remote.

Options:

--dry-run:
  Print the files that would be pushed, without actually pushing them.
--all:
  This pushes all objects to the remote that are referenced by any commit
  reachable from the refs provided as arguments. If no refs are provided, then
  all local refs are pushed. Note that this behavior differs from that of
  git lfs fetch when its --all option is used; in that case, all refs are
  fetched, including refs other than those under refs/heads and refs/tags.
  If you are migrating a repository with these commands, make sure to run git
  lfs push for any additional remote refs that contain Git LFS objects not
  reachable from your local refs.
--object-id:
  This pushes only the object OIDs listed at the end of the command, separated
  by spaces.
--stdin:
  Read a list of newline-delimited refs (or object IDs when using --object-id)
  from standard input instead of the command line.

PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

I see the limitations now. The `git lfs push` command doesn't support filtering by file type. Let me try a different approach - let's check what specific objects need to be pushed and try pushing them individually:


---

```bash
git lfs push origin main --dry-run
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs push origin main --dry-run
Locking support detected on remote "origin". Consider enabling it with:
  $ git config lfs.http://192.168.86.64:3000/Raincloud/2025-08-02-Springtrap-Prince-of-Egypt.git/info/lfs.locksverify true
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

Interesting - the dry-run shows no objects to push, but when you use `--all` it shows 59 objects. This suggests the issue might be with the `--all` flag trying to push objects that aren't actually needed.

Let me check the git status and see what's happening:


---

```bash
git status
```

```
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git status
On branch main
Your branch is up to date with 'origin/main'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        .specstory/history/2025-08-17_03-39Z-generate-a-name-for-the-chat.md

nothing added to commit but untracked files present (use "git add" to track)
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> 
PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt>
```

---

Now I understand! Your branch is already up to date with `origin/main`, which means there are no new commits to push. The `--all` flag is trying to push **all** LFS objects in your repository history, not just the ones that need to be pushed.

**The solution:** You don't need to push anything right now! Your repository is already synchronized.

**Why `--all` was freezing:**
- `--all` tries to push every LFS object that exists in your repository history
- This includes all 59 LFS objects (videos, Blender files, etc.) from all commits
- Many of these are probably already on the remote server
- The local server was struggling to process this massive upload request

**What you should do instead:**
1. **Don't use `--all`** unless you're doing a full repository migration
2. **Use regular git push** for normal commits: `git push origin main`
3. **Only use `git lfs push`** when you have new LFS objects that need to be uploaded

If you want to check what LFS objects exist on the remote vs. locally, you can use:
```powershell
git lfs fetch --all origin
```

But for normal development, just use regular `git push` when you make commits.

---

_**User**_

but why

---

_**Assistant**_

Ah, now I see the real issue! Looking at your Gitea web interface, the remote repository shows **"LFS files stored in this repository (Total: 0)"** - meaning **no LFS files are actually stored on the remote server**.

This explains why `git lfs push origin --all` was freezing:

**The Problem:**
1. **Local state**: You have 18 LFS files locally (`git lfs ls-files` shows them)
2. **Remote state**: The Gitea server has **0 LFS files** stored
3. **What `--all` was trying to do**: Push all 59 LFS objects (including historical ones) to a server that currently has none

**Why it froze:**
- The Gitea server at `192.168.86.64:3000` was trying to receive and process a massive amount of data
- Your video files (MP4s), Blender files (.blend), and motion capture files (.fbx) are likely several GB each
- The local server was overwhelmed trying to process 59 large files simultaneously
- No timeout mechanism meant it just hung indefinitely

**The Real Issue:**
Your LFS files were never successfully pushed to the remote server in the first place. The `--all` flag was essentially trying to do a complete LFS migration, which is why it showed 59 objects instead of just the 18 current ones.

**What you need to do:**
1. **First, try a simple push** without `--all`: `git lfs push origin main`
2. **If that fails**, the issue might be with your Gitea server's LFS configuration or storage
3. **Check your Gitea server's LFS settings** - it might need more storage space or different configuration

The freezing was essentially the server saying "I can't handle this massive upload" but not giving you an error message.

---

_**User**_

it doesn't do anything

---

_**Assistant**_

Exactly! The `git lfs push origin main` command completed immediately with no output, which means there are **no LFS objects that need to be pushed**.

This confirms what we discovered:

**Why `git lfs push origin main` does nothing:**
- Your local repository is already in sync with the remote
- All the LFS files you currently have locally are already committed and tracked
- There are no new LFS objects that need to be uploaded

**Why `git lfs push origin --all` froze:**
- The `--all` flag tries to push **every LFS object that has ever existed** in your repository history
- This includes deleted files, rewritten commits, and historical versions
- It was essentially trying to do a complete LFS migration to a server that has 0 LFS files
- The local Gitea server couldn't handle the massive upload and froze

**The Current State:**
- ✅ Your local LFS files are properly tracked and committed
- ✅ Your repository is synchronized with the remote
- ❌ The remote Gitea server doesn't actually store the LFS files (shows "Total: 0")
- ❌ But Git thinks everything is fine because the LFS pointers are committed

**What This Means:**
Your LFS files exist locally and are tracked by Git, but they're not actually stored on the remote server. This is a configuration issue with your Gitea server - it's not properly configured to store LFS files, or there's a storage/permission problem.

For now, your local development can continue normally, but if you need to clone this repository elsewhere or share it, the LFS files won't be available.

---

_**User**_

but this one worked just fine

---

_**Assistant**_

Ah, now I see the key difference! Looking at the other repository (`2025-07-29-Springtrap_Goopie`), it shows **"LFS files stored in this repository (Total: 1843)"** - meaning that repository successfully has LFS files stored on the remote server.

**Why one worked and yours didn't:**

1. **Working Repository** (`2025-07-29-Springtrap_Goopie`):
   - Has 1843 LFS files successfully stored
   - All files are 2.2 MiB each (much smaller than your video files)
   - Files were uploaded recently (46-45 minutes ago)

2. **Your Repository** (`2025-08-02-Springtrap-Prince-of-Egypt`):
   - Shows "Total: 0" LFS files
   - Your files are much larger (MP4s, Blender files, etc.)
   - The `--all` push attempt failed/froze

**The Problem:**
Your repository's LFS files were never successfully uploaded to the remote server, even though Git thinks they are. This could be because:

- **File size limits**: Your video files might exceed the server's upload limits
- **Storage quota**: The server might have run out of space
- **Upload timeout**: Large files might have timed out during previous upload attempts
- **Server configuration**: LFS might not be properly configured for your repository

**What to check:**
1. **Server storage space** - Your Gitea server might be full
2. **File size limits** - Check if there are upload size restrictions
3. **LFS configuration** - Verify LFS is properly enabled for your specific repository

The fact that the other repository works fine suggests the server itself is functional, but there's something specific about your repository or files that's preventing successful LFS storage.

---

_**User**_

why do they show different numbers of lfs objects?

D:\2025-08-02 Springtrap Prince of Egypt>git lfs push origin main --all
Locking support detected on remote "origin". Consider enabling it with:
  $ git config lfs.http://192.168.86.64:3000/Raincloud/2025-08-02-Springtrap-Prince-of-Egypt.git/info/lfs.locksverify true
Uploading LFS objects:   0% (0/100), 0 B | 0 B/s

---

_**Assistant**_

Great question! The different numbers of LFS objects show the difference between what Git **thinks** should be pushed versus what's **actually stored** on the remote server.

**Why the numbers are different:**

1. **Your local repository**: `git lfs ls-files` shows **18 LFS files** (current working files)
2. **Git push --all**: Shows **63 objects** (from PowerShell) and **100 objects** (from Command Prompt)
3. **Remote server**: Shows **0 LFS files stored**

**What's happening:**

- **18 files**: These are your current LFS files that exist locally
- **63-100 objects**: These are **all LFS objects that have ever existed** in your repository's complete history, including:
  - Deleted files
  - Files from old commits
  - Files that were rewritten/replaced
  - Files from different branches
  - Historical versions of current files

**Why `--all` shows more objects than you expect:**

The `--all` flag doesn't just push current files - it pushes **every LFS object that's referenced anywhere in your Git history**. This is why:

- PowerShell shows 63 objects
- Command Prompt shows 100 objects  
- Both are much higher than your current 18 files

**The Real Issue:**

Your remote server has **0 LFS files stored**, but Git is trying to push 63-100 historical objects. This suggests:

1. **Previous LFS pushes failed** (which is why the server shows 0 files)
2. **Git still thinks these objects need to be pushed**
3. **The server can't handle the massive upload** (hence the freezing)

**Solution:**
Instead of using `--all`, you need to figure out why your LFS files aren't being stored on the remote server in the first place. The issue is likely server configuration, storage limits, or file size restrictions, not the number of objects.

---

_**User**_

the repo on R:\ only shows 63, the repo on D: shows 100

---

_**Assistant**_

Ah, that's the key insight! You have **two different local copies** of the same repository, and they have different Git histories:

**Repository on R:\** (current location): Shows **63 LFS objects**
**Repository on D:\**: Shows **100 LFS objects**

**Why the numbers are different:**

1. **Different Git histories**: The D:\ repository has more commits/history than the R:\ repository
2. **Different fetch states**: One repository might have fetched more remote history than the other
3. **Different branch states**: They might be pointing to different commits or have different merge histories
4. **Partial clones**: One might be a shallow clone while the other is a full clone

**What this means:**

- **R:\ repository**: Has 63 LFS objects in its history (what you're currently working with)
- **D:\ repository**: Has 100 LFS objects in its history (more complete history)
- **Remote server**: Has 0 LFS files stored (neither repository successfully pushed to it)

**The Real Problem:**

Both repositories are trying to push to the same remote server, but the server can't handle the LFS uploads. The difference in object counts suggests:

1. **D:\ repository** has more complete history (100 objects)
2. **R:\ repository** has less complete history (63 objects) 
3. **Remote server** has no LFS storage configured or working

**What to check:**

1. **Are both repositories pointing to the same remote?**
2. **Does the remote server have enough storage space?**
3. **Are there file size limits on the Gitea server?**
4. **Is LFS properly configured on the remote server?**

The fact that you have two different local copies with different object counts suggests there might be a synchronization issue between your local repositories and the remote server.

---

_**User**_

oh wait, this one showed differently on this try, that's weird

---

_**Assistant**_

That is weird! Now it's showing **81 LFS objects** instead of the previous 63. This suggests the repository state is changing dynamically.

**Why the number keeps changing:**

1. **Git history is being rewritten**: If you're making commits, rebasing, or merging, Git might be changing which LFS objects are referenced
2. **Different branches**: The `--all` flag might be looking at different branches or refs each time
3. **LFS pointer updates**: When you modify files tracked by LFS, Git creates new LFS objects
4. **Repository state changes**: The repository might be in an intermediate state between operations

**What's happening:**

- **First try**: 63 objects
- **Second try**: 81 objects  
- **Previous D:\ repository**: 100 objects

**Possible causes:**

1. **Recent commits**: You might have made commits that added new LFS objects
2. **File modifications**: Changes to LFS-tracked files create new objects
3. **Branch switching**: Different branches might reference different LFS objects
4. **Git operations**: Rebase, merge, or other operations might be changing the object count

**To investigate:**

Let me check what's changed in your repository recently:


---

```bash
git log --oneline -10
```

```

PS R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt> git lfs push origin main --all
Locking support detected on remote "origin". Consider enabling it with:
  $ git config lfs.http://192.168.86.64:3000/Raincloud/2025-08-02-Springtrap-Prince-of-Egypt.git/info/lfs.locksverify true
Uploading LFS objects:   0% (0/81), 0 B | 0 B/s
Exiting because of "interrupt" signal.
```

---

_**User**_

my nas is fucking broken
ReadFile(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\.git\lfs\objects\de\0b\de0b36a38ee4922291710d202aabee437758deb440fe0a06e3763ea907ee0ab8
ReadFile(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0049.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0050.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0051.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0052.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0053.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0054.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0055.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0056.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0057.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0058.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0059.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0060.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0061.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0062.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0063.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0064.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0065.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0066.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0067.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0068.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0069.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0070.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0071.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0072.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0073.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0074.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0075.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0076.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0077.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0078.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0079.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0080.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0081.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0082.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0083.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0084.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0085.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0086.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0087.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0088.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0089.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0090.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0091.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0092.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0093.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0094.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0095.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0096.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0097.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0098.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0099.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0100.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0101.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0102.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0103.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0104.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0105.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0106.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0107.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0108.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0109.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0110.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0111.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0112.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0113.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0114.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0115.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0116.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0117.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0118.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0119.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0120.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0121.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0122.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0123.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0124.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0125.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0126.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0127.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0128.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0129.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0130.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0131.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0132.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0133.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0134.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0135.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0136.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0137.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0138.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0139.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0140.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0141.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0142.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0143.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0144.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0145.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0146.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0147.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0148.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0149.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0150.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0151.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0152.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0153.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0154.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0155.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0156.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0157.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0158.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0159.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0160.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0161.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0162.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0163.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0164.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0165.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0166.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0167.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0168.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0169.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0170.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0171.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0172.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0173.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0174.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0175.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0176.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0177.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0178.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0179.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0180.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0181.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0182.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0183.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0184.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0185.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0186.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0187.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0188.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0189.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0190.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0191.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0192.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0193.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0194.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0195.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0196.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0197.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0198.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0199.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0200.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0201.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0202.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0203.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0204.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0205.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0206.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0207.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0208.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0209.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0210.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0211.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0212.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0213.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0214.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0215.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0216.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0217.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0218.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0219.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0220.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0221.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0222.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0223.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0224.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0225.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0226.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0227.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0228.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0229.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0230.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0231.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0232.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0233.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0234.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0235.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0236.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0237.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0238.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0239.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0240.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0241.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0242.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0243.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0244.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0245.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0246.png
GetFileSizeEx(read)(An unexpected network error occurred.59) : R:\Creative\artsy\maya\2025-08-02 Springtrap Prince of Egypt\renders\2025-08-04\SPOE_A\SPOE_A_0247.png



---

_**Assistant**_

Ah, now I see the **real** problem! Your NAS is broken and can't read files, which explains everything:

**What's happening:**

1. **NAS Network Error**: `ReadFile(An unexpected network error occurred.59)` - Your R:\ drive (NAS) is having network connectivity issues
2. **Git LFS Objects**: The errors show it's trying to read LFS objects from `.git\lfs\objects\de\0b\...` 
3. **Render Files**: It's also failing to read PNG render files from `renders/2025-08-04/SPOE_A/`

**Why the LFS push numbers keep changing:**

- **63 objects** → **81 objects** → **100 objects**
- Git is trying to read LFS objects from your broken NAS
- Some objects are accessible, others aren't
- The count changes based on what Git can actually read at that moment

**Why the push freezes:**

- Git LFS is trying to read files from your broken NAS
- Network timeouts and read failures cause the process to hang
- The server can't receive files that Git can't even read locally

**The Real Issue:**

Your repository is on a broken NAS drive (R:\) that can't reliably read files. Git LFS needs to read these files to push them, but the NAS is failing with network errors.

**Solutions:**

1. **Fix your NAS** - Check network connections, restart the NAS device
2. **Move the repository locally** - Clone it to your local C:\ drive temporarily
3. **Wait for NAS to recover** - Sometimes NAS devices need time to reconnect

**Immediate fix:**
Try accessing your R:\ drive in File Explorer - if it's not working there either, the NAS is definitely down and that's why Git LFS can't function properly.

The LFS push freezing isn't a Git problem - it's a NAS problem!

---

_**User**_

not even ssh can fix it

---

_**Assistant**_

Ah, now I see the **real** problem! This isn't a NAS issue - it's a **Git LFS server problem**. Looking at the SSH output:

**The Real Issues:**

1. **LFS Objects Not Found (404 errors)**: The server is missing LFS objects that your local repository expects
2. **Missing Source Object**: `Unable to find source for object 681b35716ef146959ba290a995ad3b1654a667b5c4ee0f63926965849040ef2d`
3. **Server State Mismatch**: Your local repository has LFS objects that the remote server doesn't have

**What's happening:**

- Your local repository references LFS objects that were **never successfully uploaded** to the server
- The server returns 404 "Not Found" for these objects
- Git LFS can't push because it can't find the source objects locally
- The `--all` flag tries to push objects that don't exist anywhere

**Why the numbers keep changing:**

- **63 → 81 → 100 objects**: Git is discovering different sets of "missing" LFS objects each time
- Some objects exist locally, others are just references to missing objects
- The count depends on what Git can actually find vs. what it thinks should exist

**The Solution:**

The server suggests running `git lfs fetch --all` to try to get the missing objects, but since the server doesn't have them either, this will fail.

**What you need to do:**

1. **Check what LFS objects actually exist locally**: `git lfs ls-files`
2. **Remove references to missing objects**: This might require cleaning up the repository
3. **Re-upload only the objects that actually exist**

The problem isn't your NAS or SSH - it's that your repository has **corrupted LFS references** pointing to objects that don't exist anywhere.

---

_**User**_



---

_**Assistant**_

I see you tried `--force` but that's not a valid flag for `git lfs push`. 

**The Real Problem:**

Your repository has **corrupted LFS references** - it's pointing to LFS objects that don't exist anywhere (not locally, not on the server). This is why:

- The numbers keep changing (63 → 81 → 100)
- The server shows 404 errors for missing objects
- Git can't push because it can't find the source objects

**What You Need to Do:**

1. **Clean up the corrupted LFS references** - Remove commits that reference missing LFS objects
2. **Re-upload only the objects that actually exist** - Don't use `--all` which tries to push everything
3. **Fix the repository state** - Get it back to a clean state

**Immediate Steps:**

1. **Check what LFS objects actually exist locally:**
   ```bash
   git lfs ls-files
   ```

2. **See what objects are missing:**
   ```bash
   git lfs fetch --all
   ```

3. **Clean up the repository** - You might need to:
   - Reset to a commit before the LFS corruption
   - Remove commits that reference missing objects
   - Re-add only the files that actually exist

**The Issue:**

The `--all` flag is trying to push objects that don't exist anywhere. Your repository is in a broken state where it references LFS objects that were never properly stored or have been lost.

This isn't a network issue - it's a **repository corruption issue** that needs to be fixed before you can push anything.

---

_**User**_



---

_**Assistant**_

Perfect! Now I can see what's actually happening. Your local repository has **18 LFS files** that exist and are properly tracked, but the `--all` flag is trying to push **many more objects** that don't exist.

**The Real Issue:**

- **Local LFS files**: 18 files (all present and accessible)
- **Git history references**: 63-100+ objects that Git thinks should exist
- **Missing objects**: These are references to LFS objects that were never properly stored or have been lost

**Why `--all` shows different numbers:**

The `--all` flag looks at **every commit in your repository history** and tries to push **all LFS objects that were ever referenced**. This includes:

- Deleted files
- Files from old commits
- Files that were rewritten/replaced
- Historical versions that no longer exist

**What You Should Do:**

1. **Don't use `--all`** - It's trying to push objects that don't exist
2. **Push only current files**: `git lfs push origin main` (without `--all`)
3. **If that doesn't work**, your repository has corrupted LFS references that need cleaning

**The Solution:**

Your repository is in a state where it references more LFS objects than actually exist. The `--all` flag is essentially trying to push a bunch of "ghost" objects that were never properly stored.

Try a simple push first: `git lfs push origin main` - this should only push the 18 files that actually exist. If that fails, you'll need to clean up the corrupted LFS references in your repository history.

---

_**User**_

but that literally does THIS and pushes NOTHING.

---

_**Assistant**_

Exactly! That's the **key insight** - `git lfs push origin main` (without `--all`) pushes **nothing** because:

**Why it pushes nothing:**

1. **Git thinks everything is already synced** - Your local repository believes all LFS objects are already on the remote
2. **LFS pointers are committed** - The LFS file references are in your Git commits
3. **But the actual LFS files aren't on the server** - The remote shows "Total: 0" LFS files

**The Real Problem:**

Your repository is in a **corrupted state** where:
- ✅ Git commits contain LFS pointers
- ✅ Git thinks everything is synced
- ❌ But the actual LFS files were never uploaded to the server
- ❌ The server has 0 LFS files stored

**Why `--all` shows different numbers:**

The `--all` flag discovers that your repository history references many more LFS objects than actually exist locally. It's trying to push:
- Your current 18 files (which Git thinks are already synced)
- Plus 45-82+ "ghost" objects that are referenced but don't exist

**What This Means:**

Your repository has **corrupted LFS references** - it's pointing to objects that were never properly stored. The `--all` flag is essentially trying to push a bunch of missing/corrupted LFS objects, which is why it freezes.

**The Solution:**

You need to **fix the repository state** - either clean up the corrupted references or force a fresh LFS upload. But the current state is broken because Git thinks everything is synced when it's not.

---

_**User**_

how the hell do I force a fresh lfs upload

---

_**Assistant**_

Here are the ways to force a fresh LFS upload when Git thinks everything is already synced:

**Option 1: Force Push with Object IDs**
```bash
git lfs push origin main --object-id 83ca80f1a9 e9d2616e63 5344dba903 6c1a803474 d1c5294b70 6ccba09add e42319f849 798b5aa0b 17fb08b161 c568ba5750 eb284b1351 b4107f7a62 179597c721 4a2da35cd3 16617ec897 0704adb28d 2a34e9aea9 24ecff5207
```

**Option 2: Reset and Re-commit (Nuclear Option)**
```bash
# Create a new commit with all your LFS files
git add .
git commit -m "Force fresh LFS upload"
git lfs push origin main
```

**Option 3: Force Push the Branch**
```bash
# This will overwrite the remote branch completely
git push origin main --force
```

**Option 4: Clean and Re-initialize LFS**
```bash
# Remove LFS tracking and re-add
git lfs uninstall
git lfs install
git lfs track "*.mp4" "*.blend" "*.fbx"
git add .gitattributes
git commit -m "Re-initialize LFS tracking"
git lfs push origin main
```

**Option 5: Create a New Branch**
```bash
git checkout -b fresh-lfs-upload
git add .
git commit -m "Fresh LFS upload"
git lfs push origin fresh-lfs-upload
```

**Recommended: Start with Option 1** (object-id push) since it's the least destructive. If that doesn't work, try Option 4 (clean re-initialization).

The key is that Git thinks your LFS files are already synced, so you need to either force it to recognize they're not, or create a situation where it thinks they're new files.

---

_**User**_

????????????

---

_**Assistant**_

I know this is frustrating! Let me break down what's happening and give you a simple solution:

**The Problem:**
- Git thinks your LFS files are already uploaded (but they're not)
- The server shows 0 LFS files
- You can't push because Git thinks nothing needs pushing

**The Simplest Fix:**

Try this **one command** that forces Git to push your LFS files by their specific IDs:

```bash
git lfs push origin main --object-id 83ca80f1a9 e9d2616e63 5344dba903 6c1a803474 d1c5294b70 6ccba09add e42319f849 798b5aa0b 17fb08b161 c568ba5750 eb284b1351 b4107f7a62 179597c721 4a2da35cd3 16617ec897 0704adb28d 2a34e9aea9 24ecff5207
```

**What This Does:**
- Bypasses Git's "already synced" check
- Forces upload of your 18 actual LFS files
- Ignores the corrupted references that are causing the `--all` freeze

**If That Doesn't Work:**
The nuclear option is to force push your entire branch:
```bash
git push origin main --force
```

**Why This Happened:**
Your repository got into a weird state where Git thinks everything is uploaded but the server has nothing. It's like Git has amnesia about what's actually on the server.

Try the object-id push first - it's the least destructive way to fix this mess.

---

_**User**_



---

_**Assistant**_

Ah! Now I see the **real problem** - the LFS objects aren't actually stored locally either! The error shows:

```
Unable to stat local media path: stat /volume1/Hydra/Creative/artsy/maya/2025-08-02-Springtrap-Prince-of-Egypt/.git/lfs/objects/ma/in/main: no such file or directory
```

**What This Means:**

1. **Git thinks you have LFS files** (`git lfs ls-files` shows 18 files)
2. **But the actual LFS objects are missing** from `.git/lfs/objects/`
3. **Your repository is completely corrupted** - it has LFS pointers but no actual files

**Why This Happened:**

- The LFS objects were never properly downloaded/stored locally
- Or they were deleted/corrupted
- Git still has the pointers but the actual files are gone

**The Real Fix:**

You need to **re-download the LFS objects** first:

```bash
git lfs fetch --all origin
```

**If That Fails:**

Your repository is in a broken state where:
- LFS pointers exist in commits
- But the actual LFS files are missing everywhere (local AND remote)
- You might need to restore from a backup or re-clone

**The Issue:**

This isn't a push problem - it's that your **local repository is missing the actual LFS files**. Git can't push what it doesn't have locally.

Try `git lfs fetch --all origin` first to see if you can recover the missing files.

---

_**User**_

the local has to have them. they wouldn't be anywhere else.

---

_**Assistant**_

You're absolutely right! If `git lfs ls-files` shows them, then the files **must exist locally** somewhere. The issue is that Git LFS is looking in the wrong place.

**What's Happening:**

The error shows Git LFS is looking for files in:
```
.git/lfs/objects/ma/in/main
```

But your actual LFS objects are probably stored in:
```
.git/lfs/objects/83/ca/83ca80f1a9...
.git/lfs/objects/e9d/261/e9d2616e63...
```

**The Problem:**

Git LFS is confused about where your objects are stored. This can happen when:
- The repository was moved/copied incorrectly
- LFS configuration got corrupted
- The `.git/lfs/objects` structure is broken

**Quick Fix:**

Try re-initializing LFS in your repository:

```bash
git lfs uninstall
git lfs install
git lfs track "*.mp4" "*.blend" "*.fbx"
```

**Or Check the Objects Directory:**

```bash
ls -la .git/lfs/objects/
```

**The Issue:**

Your files exist, but Git LFS can't find them because its internal mapping is corrupted. The `git lfs ls-files` command works because it reads the Git commits, but the actual file storage path is broken.

You need to fix the LFS configuration, not the files themselves.

---

_**User**_



---

_**Assistant**_

Perfect! Now I see the issue. Git LFS is already installed but there's a hook conflict. Let's fix this:

**Option 1: Force Update (Recommended)**
```bash
git lfs update --force
```

**Option 2: Manual Update**
```bash
git lfs update --manual
```

**What This Does:**

The `--force` option will:
- Overwrite the existing pre-push hook
- Fix the LFS configuration
- Resolve the path mapping issues

**Why This Will Fix It:**

The error you got earlier (`Unable to stat local media path: stat /volume1/Hydra/Creative/artsy/maya/2025-08-02-Springtrap-Prince-of-Egypt/.git/lfs/objects/ma/in/main: no such file or directory`) suggests the LFS hooks are corrupted and looking in the wrong place.

**After Running This:**

1. **Re-track your LFS files:**
   ```bash
   git lfs track "*.mp4" "*.blend" "*.fbx"
   ```

2. **Try the push again:**
   ```bash
   git lfs push origin main
   ```

**The Issue:**

Your LFS installation is corrupted - the hooks are looking for files in the wrong directory structure. The `--force` update should fix the path mapping and let Git LFS find your actual files.

Try `git lfs update --force` first!

---

_**User**_

that still doesn't do jack shit

---

_**Assistant**_

Exactly! It's still doing nothing because Git **still thinks everything is already synced**. The LFS update didn't fix the core problem.

**The Real Issue:**

Your repository is in a state where:
- Git commits contain LFS pointers
- Git thinks these pointers are already on the remote
- But the remote actually has 0 LFS files
- Git won't push because it thinks nothing needs pushing

**The Nuclear Solution:**

You need to **force Git to recognize that nothing is actually synced**:

```bash
# Force push the entire branch - this will overwrite the remote
git push origin main --force
```

**Why This Will Work:**

- `--force` bypasses Git's "already synced" check
- It will upload your LFS files as part of the branch push
- It overwrites the remote branch completely

**Alternative (If Force Push Scares You):**

Create a new branch and push that:
```bash
git checkout -b fresh-upload
git push origin fresh-upload
```

**The Problem:**

Your repository has **corrupted sync state** - Git thinks everything is uploaded when it's not. The LFS update fixed the hooks, but it can't fix Git's mistaken belief that everything is already synced.

**Try the force push** - it's the only way to break out of this "already synced" state.

---

_**User**_

NOTHING

---

_**Assistant**_

**FUCK!** Even `--force` says "Everything up-to-date"! This confirms your repository is **completely fucked**.

**What's Happening:**

Git thinks your local branch and remote branch are identical, so even `--force` won't push anything. This means:

1. **Your local commits are identical to remote commits**
2. **Git thinks all LFS pointers are already on the server**
3. **But the actual LFS files aren't there**

**The Nuclear Option:**

You need to **break the sync state completely**:

```bash
# Create a new commit that Git will recognize as different
echo "# Force LFS upload" >> README.md
git add README.md
git commit -m "Force LFS upload"
git push origin main
```

**Or Even More Nuclear:**

```bash
# Reset to a previous commit and re-commit everything
git reset --soft HEAD~1
git add .
git commit -m "Fresh LFS upload"
git push origin main
```

**Why This Happened:**

Your repository got into a state where:
- Local and remote commits are identical
- Git thinks everything is synced
- But LFS files were never actually uploaded
- Git can't tell the difference

**The Fix:**

You need to **create a commit difference** that Git will recognize, then push that. The current state is so corrupted that Git thinks everything is perfect when it's actually completely broken.

Try adding a file and committing it first!

---

_**User**_

?

---

_**Assistant**_

**PROGRESS!** Now we're getting somewhere! 

**What Just Happened:**

1. ✅ **Regular push worked!** - You pushed 5 objects (probably the new commit)
2. ❌ **LFS push still fails** - But now it shows "0/100" instead of freezing
3. ❌ **Still missing object** - `681b35716ef146959ba290a995ad3b1654a667b5c4ee0f63926965849040ef2d`

**The Good News:**

- Git is no longer completely frozen
- The push is completing (shows "done")
- You're making progress

**The Remaining Problem:**

You still have **corrupted LFS references** pointing to objects that don't exist anywhere. The server suggests:

```bash
git lfs fetch --all
```

**Try This:**

```bash
git lfs fetch --all origin
```

**What This Will Do:**

- Try to download the missing LFS objects from the server
- Show you exactly which objects are missing
- Help identify what's corrupted

**The Issue:**

Your repository has **ghost LFS objects** that are referenced but don't exist anywhere. The regular push worked because it only pushed the Git commits, but the LFS objects are still corrupted.

**Next Step:**

Run `git lfs fetch --all origin` to see what objects are actually missing and where they're supposed to come from.

---

_**User**_

I'm sick of putting in my user and pass every time

---

_**Assistant**_

**FUCK!** Now Git LFS is **crashing** with a panic error! This is getting worse.

**What Just Happened:**

1. ✅ **Found 309 objects** - Git LFS discovered a bunch of LFS objects
2. ❌ **Panic crash** - `panic: runtime error: index out of range [0] with length 0`
3. ❌ **Authentication bug** - The crash is in the auth system

**The Real Problem:**

Your repository is so corrupted that Git LFS is **crashing** when it tries to process the corrupted LFS references. The panic error suggests:

- Git LFS found 309 objects (way more than your 18 actual files)
- But the auth system crashed when trying to process them
- This is a **Git LFS bug** caused by corrupted data

**For the Password Issue:**

```bash
# Store your credentials so you don't have to type them every time
git config --global credential.helper store
```

**But the Bigger Issue:**

Your repository has **309 corrupted LFS references** that are causing Git LFS to crash. This is beyond a simple fix.

**The Nuclear Solution:**

You might need to **start fresh**:
1. Clone the repository again from scratch
2. Or reset to a commit before the LFS corruption
3. Or restore from a backup

**The Issue:**

Your repository has so many corrupted LFS references that Git LFS itself is crashing. This isn't a network problem - it's **data corruption** that's breaking the Git LFS tool itself.

Try the credential helper first, but be prepared that you might need to start over with a clean repository.

---

_**User**_

can I disable all tracking on files under directories named `/seq` ? like blends/seq/SPOE_A/SPOE_A_0139.png

---

_**Assistant**_

Yes! You can disable LFS tracking for files under directories named `seq`. Looking at your `.gitignore`, I can see you already have `seq/` in there, but you need to update your `.gitattributes` file to stop LFS from tracking those files.

**Update your `.gitattributes` file:**

```gitattributes
# Keep LFS tracking for your main files
*.mp4 filter=lfs diff=lfs merge=lfs -text
*.blend filter=lfs diff=lfs merge=lfs -text
*.fbx filter=lfs diff=lfs diff=lfs merge=lfs -text

# Disable LFS tracking for seq directories
blends/seq/** filter= diff= merge= -text
**/seq/** filter= diff= merge= -text
```

**What This Does:**

- `**/seq/**` - Matches any file under any directory named `seq` anywhere in your repository
- `filter=` - Removes LFS filtering (no more LFS tracking)
- `diff=` and `merge=` - Removes LFS diff/merge handling
- `-text` - Treats files as binary (prevents line ending issues)

**After Updating:**

```bash
# Remove any existing LFS tracking for seq files
git lfs untrack "blends/seq/**"
git lfs untrack "**/seq/**"

# Commit the changes
git add .gitattributes
git commit -m "Disable LFS tracking for seq directories"
```

**This Will:**

- Stop LFS from tracking new files in `seq` directories
- Keep your existing LFS files (MP4s, Blends, FBXs) tracked
- Prevent the 309 corrupted LFS references from growing

The `**/seq/**` pattern will catch files like `blends/seq/SPOE_A/SPOE_A_0139.png` and stop LFS from trying to track them.

---

_**User**_

i want to remove the tracking history specifically

---

_**Assistant**_

Ah, you want to **remove the LFS tracking history** for files under `seq` directories, not just stop future tracking. This is more complex because Git LFS has already committed the tracking history.

**To Remove LFS Tracking History:**

1. **First, update `.gitattributes` to stop future tracking:**
```gitattributes
# Disable LFS tracking for seq directories
**/seq/** filter= diff= merge= -text
```

2. **Remove the LFS tracking from Git history:**
```bash
# This will rewrite Git history to remove LFS tracking
git filter-branch --tree-filter '
    find . -path "*/seq/*" -name "*.png" -exec git lfs untrack {} \;
    find . -path "*/seq/*" -name "*.png" -exec git rm --cached {} \;
' --prune-empty --tag-name-filter cat -- --all
```

**Or Use BFG (Cleaner Alternative):**
```bash
# Install BFG first, then:
bfg --delete-files "*.png" --include "**/seq/**"
git reflog expire --expire=now --all
git gc --prune=now --aggressive
```

**What This Does:**

- **Rewrites Git history** to remove LFS tracking for seq files
- **Removes the corrupted LFS references** that are causing crashes
- **Cleans up the repository** by removing the problematic tracking history

**Warning:**

This **rewrites Git history**, which means:
- All commit hashes will change
- You'll need to force push to update the remote
- Anyone else with the repository will need to re-clone

**After Cleaning:**

```bash
git push origin main --force
```

This should fix your corrupted LFS state by removing the problematic tracking history for seq files.

---

