lllyasviel / lllyasviel/FramePack

(Bug) Framepack hides script errors due to @echo off + (Idea) integrating Framepack in a space of Forge WebUI

Open
#672 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
17.3k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Hello !
Sorry, my report is messy and scattered.

While using framepack on Windows 11 with an NVIDIA RTX 3050 Ti GPU, I encountered repeated failures during environment initialization or GPU checks.

(for example: Xformers is not installed!; Flash Attn is not installed! (even after click on "Update.bat" and after "Run.bat" and i have a bad installation of .... i don't know !!!!! (herm)

For the first install of Framepack, after update and run: i have troubles...

My own solution:

> So: in python i did that:
> ```
> import torch
> print("PyTorch version:", torch.__version__)
> print("CUDA version (from torch):", torch.version.cuda)
> print("cuDNN version:", torch.backends.cudnn.version())
> ```
>
> WTF ????
>
> > >>> import torch
> > >>> print("PyTorch version:", torch.__version__)
> > PyTorch version: 2.6.0+cpu
> > >>> print("CUDA version (from torch):", torch.version.cuda)
> > CUDA version (from torch): None
> > >>> print("cuDNN version:", torch.backends.cudnn.version())
> > cuDNN version: None
>
> But i have a nvidia geforce rtx 3050 ti laptop gpu !!!!!!
>
> Solved by:
>
> `pip uninstall torch`
>
> `pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu118`
>
>
> Ok....
>
> Does it work ????
>
> ```
> import torch
> print(torch.cuda.is_available())
> print(torch.cuda.get_device_name(0))
> ```
>
>
> yes: i have now the good Pytorch version etc. for my GPU (and not for CPU)
>
> I can now install Xformers.
>
> `pip install xformers`
>
> And Flash Attn
>
> `pip install flash-attn --no-build-isolation`
>
> ....
> Ok, it's seem to work now: _(edit: no: see below )_
>

---------

**After digging into the .bat scripts (Update.bat, Run.bat ....), I noticed they begin with:**

`@echo off`

(Epic Facepalm) _(i erase all @echo off of all scripts manually)_

This causes all command-line errors (especially Python errors) to be silently suppressed, making troubleshooting extremely difficult.

If any command fails (e.g., Python can't find torch, CUDA not available, etc.), no error message is shown.

**This prevents users from:**
-diagnosing the issue themselves,
-sharing clear logs when reporting a bug,
-correcting simple mistakes manually.

**Scripts should allow users to see errors when they occur, especially during:**
-Python environment setup
-CUDA / GPU detection
-Dependency verification

---------

### Since both Framepack and ForgeUI are from the same author and share a vision around AI image/video workflows, it would be incredibly useful to:

**Create a Framepack Space in ForgeUI**
This would allow:
Visual testing and rendering of Framepack outputs
Maybe avoiding platform-specific script failures
Easier community testing and contributions

Thanks you <3 <3 <3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Update.bat and Run.bat, especially their @echo off lines, and reproduce the reported environment initialization or GPU-check failures on Windows. Verify whether command and Python errors are visible and can be collected for diagnosis. The separate ForgeUI integration idea needs a narrower scope before it can be treated as the same task.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.