[Bug]: Tree View not visible when using custom model folder

[a3nima]

Checklist

• The issue exists after disabling all extensions
• The issue exists on a clean installation of webui
• The issue is caused by an extension, but I believe it is caused by a bug in the webui
• The issue exists in the current version of the webui
• The issue has not been reported before recently
• The issue has been reported before but has not been fixed yet

What happened?

I'm launching forge with

--forge-ref-a1111-home e:/SD/stable-diffusion-webui

The models show up, but tree view does not work

Steps to reproduce the problem

use forge with reference cmd and different model folder than original.

What should have happened?

tree view should be visible no matter what folder you're in.

What browsers do you use to access the UI ?

Other

Sysinfo

sysinfo-2024-03-21-22-38.json

Console logs

Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]| 60/60 [00:27<00:00,  1.78it/s]
Version: f0.0.17v1.8.0rc-latest-276-g29be1da7
Commit hash: 29be1da7cf2b5dccfc70fbdd33eb35c56a31ffb7
Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\adetailer':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\deforum-for-automatic1111-webui':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-forge-layerdiffuse':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-webui-animatediff':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-webui-ar_xhox':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-webui-aspect-ratio-helper':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-webui-custom-autolaunch':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-webui-inpaint-anything':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-webui-regional-prompter':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\sd-webui-tinycards':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\Stable-Diffusion-Webui-Civitai-Helper':
Already up to date.

Pulled changes for repository in 'D:\BILD-AI\webui-forge\webui\extensions\stable-diffusion-webui-images-browser':
Already up to date.

Launching Web UI with arguments: --forge-ref-a1111-home e:/SD/stable-diffusion-webui --update-all-extensions --ckpt-dir e:\SD\stable-diffusion-webui\models\Stable-diffusion --vae-dir e:\SD\stable-diffusion-webui\models\VAE --hypernetwork-dir e:\SD\stable-diffusion-webui\models\hypernetworks --embeddings-dir e:\SD\stable-diffusion-webui\embeddings --lora-dir e:\SD\stable-diffusion-webui\models\lora --controlnet-dir e:\SD\stable-diffusion-webui\models\ControlNet --controlnet-preprocessor-models-dir e:\SD\stable-diffusion-webui\extensions\sd-webui-controlnet\annotator\downloads
Total VRAM 24576 MB, total RAM 32678 MB
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 3090 : native
Hint: your device supports --pin-shared-memory for potential speed improvements.
Hint: your device supports --cuda-malloc for potential speed improvements.
Hint: your device supports --cuda-stream for potential speed improvements.
VAE dtype: torch.bfloat16
CUDA Stream Activated:  False
Using pytorch cross attention
ControlNet preprocessor location: e:\SD\stable-diffusion-webui\extensions\sd-webui-controlnet\annotator\downloads
[-] ADetailer initialized. version: 24.3.2, num models: 10
Loading weights [e9337ae032] from E:\SD\stable-diffusion-webui\models\Stable-diffusion\sdxl\cyberrealisticXL_v11VAE.safetensors
2024-03-21 23:33:35,306 - ControlNet - INFO - ControlNet UI callback registered.
model_type EPS
UNet ADM Dimension 2816
Running on local URL:  http://127.0.0.1:7860

To create a public link, set `share=True` in `launch()`.
Startup time: 19.3s (prepare environment: 7.1s, import torch: 3.2s, import gradio: 0.9s, setup paths: 0.8s, initialize shared: 0.1s, other imports: 0.6s, list SD models: 0.1s, load scripts: 3.4s, create ui: 2.8s, gradio launch: 0.2s).
Using pytorch attention in VAE
Working with z of shape (1, 4, 32, 32) = 4096 dimensions.
Using pytorch attention in VAE
extra {'cond_stage_model.clip_l.logit_scale', 'cond_stage_model.clip_l.text_projection', 'cond_stage_model.clip_g.transformer.text_model.embeddings.position_ids'}
To load target model SDXLClipModel
Begin to load 1 model
[Memory Management] Current Free GPU Memory (MB) =  23305.6796875
[Memory Management] Model Memory (MB) =  2144.3546981811523
[Memory Management] Minimal Inference Memory (MB) =  1024.0
[Memory Management] Estimated Remaining GPU Memory (MB) =  20137.324989318848
Moving model(s) has taken 0.58 seconds
Model loaded in 8.8s (load weights from disk: 0.6s, forge instantiate config: 1.4s, forge load real models: 5.9s, calculate empty prompt: 0.9s).

Additional information

No response

[BrickMissle]

I noticed even with the --forge-ref-a1111-home arg, you also are still using --ckpt-dir and --vae-dir and other such args along with it? I was under the assumption the forge-ref one worked by itself? Maybe the new arg plus the old args is confusing to forge, because it's getting two orders at once? I could be wrong, but I wonder if removing all the older directory changing arguments would help?

edit: I am only running the --forge-ref-a1111-home arg, and I get the same error as OP. So that ain't it...

[a3nima]

I'm also only running the one argument: --forge-ref-a1111-home
the output in the console seems to be the result of this.

[catboxanon]

Will be fixed when AUTOMATIC1111/stable-diffusion-webui#15035 is merged into this repo as part of whenever the next upstream sync happens.