Models wont load

[Curts7111]

Bug Description

When I...

Environment Information - Bug happens on:

• BlenderKit version: v3.12.0.240423
• Blender version 4.1
• Operating system & architecture: Win10
• Using VPN, proxy, or firewall? No

Error Logs

When I attempt to load a model it wont load into Blender. It says that is has loaded but it hasn't. All it does is leave an empty model folder in the assists folder. I have tried this many times throughout the day with different models and with the same result. Materials seem to load fine.
Now I am having problems with some of the Materials.

Steps to Reproduce

[agajdosi]

Hi @Curts7111, thanks for the report. Seems like duplicate of #1165. To debug this successfully I will need more detailed logs from you, could you please follow the instructions below? Also does this happen every time, or just in some project? If only in some project, I would be interested to seeing the file if it is possible.

Windows

Locate Blender.exe and Client's log file:
A. Client log is by default at: C:\Users\<your-username>\blenderkit_data\client\default.log.
B. Blender.exe is by default located at: C:\Program Files\Blender Foundation\Blender 4.1\blender.exe
Click on the Start button and search for PowerShell. Launch the PowerShell application twice.
In first PowerShell window, type (or paste by right-clicking) the following command: Get-Content C:\Users\<your-username>\blenderkit_data\client\default.log -Wait, hit Enter to execute the command. PowerShell will then monitor the log file, we will use it later. Make sure the path to Client log is correct.
In second PowerShell window, type (or paste by right-clicking) the following command into the PowerShell window: & "C:\Program Files\Blender Foundation\Blender 4.1\blender.exe" (make sure the path is enclosed in quotes). Press "Enter" to run the command, which will start Blender. All errors which happen during the run will be printed into the PowerShell window.
Use Blender as usual until you encounter the problem. Then, copy and paste all of the text from both PowerShell windows into this issues. To select text, hold down the left mouse button and then copy it by pressing the right mouse button.

MacOS

Locate the Blender binary and the Client's log file:
A. The Client log file is typically located at: /Users/<your-username>/blenderkit_data/client/default.log.
B. The Blender binary is by default found at: /Applications/Blender.app/Contents/MacOS/Blender.
Open Spotlight and search for Terminal. Launch two instances of the Terminal application.
In the first Terminal window, type tail -f command followed by path from step 1A, e.g. tail -f /Users/<your-username>/blenderkit_data/client/default.log and press "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct.
In the second Terminal window, type or paste the path from step 1B, e.g., /Applications/Blender.app/Contents/MacOS/Blender, and press "Enter". This will start Blender, and any errors will be displayed in the Terminal window.
Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue.

Linux

Locate the Blender binary and the Client's log file:
A. The Client log file is typically located at: /home/<your-username>/blenderkit_data/client/default.log.
B. The Blender binary can be located by typing which blender in the terminal. If the blender binary is not on the PATH, search for its location and use the absolute path for the following steps.
Launch two instances of the "Terminal" application.
In the first Terminal window, type or paste the following command: tail -f /home/<your-username>/blenderkit_data/client/default.log and hit "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct.
In the second Terminal window, type blender (or specify the absolute path to Blender binary if it's not on the PATH) and hit "Enter". This will start Blender and any errors will be printed into the Terminal window.
Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue.

Looking forward to your response. Thank you!

[Curts7111]

I could only get the first power shell to work. I could not get Blender to start from the 2nd power shell. I have blender on my computer as a portable file and not traditionally installed. The problem has gotten somewhat better but it still persists. It mostly happens with models but happens with materials sometimes as well. I wish I could give you exact situations as to when this happens but I have not figured it out yet. It seems random.Best regards.

…

On Wed, Jun 12, 2024 at 5:15 AM Andreas Gajdosik ***@***.***> wrote: Hi @Curts7111 <https://github.com/Curts7111>, thanks for the report. Seems like duplicate of #1165 <#1165>. To debug this successfully I will need more detailed logs from you, could you please follow the instructions below? Also does this happen every time, or just in some project? If only in some project, I would be interested to seeing the file if it is possible. Windows Locate Blender.exe and Client's log file: A. Client log is by default at: C:\Users\<your-username>\blenderkit_data\client\default.log. B. Blender.exe is by default located at: C:\Program Files\Blender Foundation\Blender 4.1\blender.exe Click on the Start button and search for PowerShell. Launch the PowerShell application twice. In first PowerShell window, type (or paste by right-clicking) the following command: Get-Content C:\Users\<your-username>\blenderkit_data\client\default.log -Wait, hit Enter to execute the command. PowerShell will then monitor the log file, we will use it later. Make sure the path to Client log is correct. In second PowerShell window, type (or paste by right-clicking) the following command into the PowerShell window: & "C:\Program Files\Blender Foundation\Blender 4.1\blender.exe" (make sure the path is enclosed in quotes). Press "Enter" to run the command, which will start Blender. All errors which happen during the run will be printed into the PowerShell window. Use Blender as usual until you encounter the problem. Then, copy and paste all of the text from both PowerShell windows into this issues. To select text, hold down the left mouse button and then copy it by pressing the right mouse button. MacOS Locate the Blender binary and the Client's log file: A. The Client log file is typically located at: /Users/<your-username>/blenderkit_data/client/default.log. B. The Blender binary is by default found at: /Applications/Blender.app/Contents/MacOS/Blender. Open Spotlight and search for Terminal. Launch two instances of the Terminal application. In the first Terminal window, type tail -f command followed by path from step 1A, e.g. tail -f /Users/<your-username>/blenderkit_data/client/default.log and press "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct. In the second Terminal window, type or paste the path from step 1B, e.g., /Applications/Blender.app/Contents/MacOS/Blender, and press "Enter". This will start Blender, and any errors will be displayed in the Terminal window. Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue. Linux Locate the Blender binary and the Client's log file: A. The Client log file is typically located at: /home/<your-username>/blenderkit_data/client/default.log. B. The Blender binary can be located by typing which blender in the terminal. If the blender binary is not on the PATH, search for its location and use the absolute path for the following steps. Launch two instances of the "Terminal" application. In the first Terminal window, type or paste the following command: tail -f /home/<your-username>/blenderkit_data/client/default.log and hit "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct. In the second Terminal window, type blender (or specify the absolute path to Blender binary if it's not on the PATH) and hit "Enter". This will start Blender and any errors will be printed into the Terminal window. Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue. Looking forward to your response. Thank you! — Reply to this email directly, view it on GitHub <#1166 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV64ATY7F4HHSNEFRCEUW2DZHA3URAVCNFSM6AAAAABI547DZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSHA2TSMBQHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[agajdosi]

Hi @Curts7111, even with just the first powershell it could help me to identify the problem - having the Client log from there would be nice.

If you are using the portable version you need to change the path to Blender .exe in the second powershell. Inside the portable directory, there should be file Blender.exe or similar. You need to copy its path, e.g. C:/Users/Curts/blender_portable/blender.exe and then run this command in the second powershell: & "C:/Users/Curts/blender_portable/blender.exe".

Basically you are just telling the PowerShell to start .exe and you tell it with complete (absolute) path to where PowerShell should find and start the executable.