Viewport compositor: UI doesn't load on startup, multiple error messages #99470

New Issue

D0ppelgaenger · 2022-07-05T22:36:55+02:00

D0ppelgaenger commented

2022-07-05 22:36:55 +02:00

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59

Blender Version
Broken: 3.3 Alpha, 3de2575ffb23, June 28, 14:11:42
Worked: unknown

Short description of error
When staring blender, it doesn't load the UI properly and gives errors, seen in the image. I know of sb else who this happened to, but it worked for them after they extracted the files to another folder (desktop), however for me it doesn't work no matter of the location.

Exact steps for others to reproduce the error
Download branch from experimental section of blender website (https://builder.blender.org/download/experimental/blender-3.3.0-alpha+temp-viewport-compositor-merge.3de2575ffb23-windows.amd64-release.zip)
Extract files
Start the extracted blender.exe version

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59 **Blender Version** Broken: 3.3 Alpha, 3de2575ffb23, June 28, 14:11:42 Worked: unknown **Short description of error** When staring blender, it doesn't load the UI properly and gives errors, seen in the image. I know of sb else who this happened to, but it worked for them after they extracted the files to another folder (desktop), however for me it doesn't work no matter of the location.![UIBug.png](https://archive.blender.org/developer/F13261555/UIBug.png) **Exact steps for others to reproduce the error** Download branch from experimental section of blender website (https://builder.blender.org/download/experimental/blender-3.3.0-alpha+temp-viewport-compositor-merge.3de2575ffb23-windows.amd64-release.zip) Extract files Start the extracted blender.exe version

D0ppelgaenger commented

2022-07-05 22:36:55 +02:00

Added subscriber: @Leo-Luther

Pratik Borhade commented

2022-07-06 05:41:02 +02:00

Added subscribers: @OmarEmaraDev, @PratikPB2123

Pratik Borhade commented

2022-07-06 05:41:02 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Pratik Borhade closed this issue

2022-07-06 05:41:02 +02:00

Pratik Borhade commented

2022-07-06 05:41:02 +02:00

Hi, thanks for the report. Bug reports on a feature branch are not handled on bug tracker.
cc @OmarEmaraDev

Hi, thanks for the report. Bug reports on a feature branch are not handled on bug tracker. cc @OmarEmaraDev

Omar Emara commented

2022-07-06 08:45:22 +02:00

This looks like Blender can't load its release files. The linux builds seems to work fine, I am not on windows so I can't debug this myself.
While we don't accept reports for this yet, it would be good to iron those things out before we publish the blog post.

Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Once you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Can you attach them here?

This looks like Blender can't load its release files. The linux builds seems to work fine, I am not on windows so I can't debug this myself. While we don't accept reports for this yet, it would be good to iron those things out before we publish the blog post. Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Once you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Can you attach them here?

D0ppelgaenger commented

2022-07-06 11:15:07 +02:00

Sure, here you go. Glancing over it, I think the issue is that importing the numpy C-extensions failed

blender_system_info.txt

blender_debug_output.txt

Also, I don't know if it is just windows acting up, but extracting the files using window's built in file extract for zip-files gives me an error that the file paths are too long for some elements, even tough I enabled long file paths in the regedit and in the group policies. Extracting with 7zip worked fine.

Sure, here you go. Glancing over it, I think the issue is that importing the numpy C-extensions failed [blender_system_info.txt](https://archive.blender.org/developer/F13262311/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F13262310/blender_debug_output.txt) Also, I don't know if it is just windows acting up, but extracting the files using window's built in file extract for zip-files gives me an error that the file paths are too long for some elements, even tough I enabled long file paths in the regedit and in the group policies. Extracting with 7zip worked fine.

Omar Emara commented

2022-07-06 11:49:30 +02:00

You mean that Blender loads fine when extracting with 7zip or that it just extracts fine but the same issue persists upon loading?
Maybe try renaming the zip file to something short and see if this fixes the issue? Because perhaps long file names cause issues at runtime as well.

You mean that Blender loads fine when extracting with 7zip or that it just extracts fine but the same issue persists upon loading? Maybe try renaming the zip file to something short and see if this fixes the issue? Because perhaps long file names cause issues at runtime as well.

D0ppelgaenger commented

2022-07-06 13:02:01 +02:00

Extracting the files only "worked" with 7zip, the default windows extract had issues with too long file paths. And while it gives the option to shorten the paths, I thought that shortened paths would for sure break things, I just gave up on the default extract and used 7zip, which seemed to work fine and didn't show any issues about long paths.
But as said, while the extract seemed to work fine, blender didn't.

Although I thought I already tried it yesterday, suspecting it to be the source of the issue, I tried again to extract after shortening the zip-file's name, and now it worked.
So I guess that 7zip automatically shortens paths that are too long without asking and therefore blender can't find the needed files.
As most of the time, user error after all :)

Extracting the files only "worked" with 7zip, the default windows extract had issues with too long file paths. And while it gives the option to shorten the paths, I thought that shortened paths would for sure break things, I just gave up on the default extract and used 7zip, which seemed to work fine and didn't show any issues about long paths. But as said, while the extract seemed to work fine, blender didn't. Although I thought I already tried it yesterday, suspecting it to be the source of the issue, I tried again to extract after shortening the zip-file's name, and now it worked. So I guess that 7zip automatically shortens paths that are too long without asking and therefore blender can't find the needed files. As most of the time, user error after all :)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Viewport compositor: UI doesn't load on startup, multiple error messages #99470