Flamenco WinError 267 the directory name is invalid and ValueError: WindowsPath('.') has an empty name #103495
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#103495
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10
Graphics card: RTX 4090
Blender Version
Broken: 3.4.1
Worked: (optional)
Short description of error
So I have been using Flamenco for the past couple of weeks without issues. I come back today to start another batch job and each and every time I start I get this error:
I haven't changed blender or flamenco. I haven't touched any of the blend files. It just keeps persisting.
I decided to open a blank blend file to test and see if it might be something to do with the project. I start a render and I then get this.
I have no idea what is happening or what to do to fix it
Exact steps for others to reproduce the error
Added subscriber: @NathanRivera
Added subscriber: @dr.sybren
Changed status from 'Needs Triage' to: 'Needs User Info'
Thanks for the report. This is something to address in Flamenco for sure. If anything, it should tell you what's wrong instead of producing this ;-)
Could you check two things for me?
Again, in both cases Flamenco should just tell you what's wrong & how to solve it (something like "save the file to disk before submitting" or "a job name is required"). These questions are just for me to understand your situation better.
Hello Sybren,
Thank you for reaching out,
The blend file and the stored batch jobs are saved on a network drive that I have mapped to the other workers.
All of my devices are able to write to the drive no issues.
And yes I entered a job name In this case "Animation" was the name
What was the path of the blend file when you submitted it to Flamenco?
I just now notice that the steps to reproduce don't include actually submitting to Flamenco. I'm guessing "start a render" is indicating that, but it's hard to reliably reproduce a bug when I have to guess.
Here is a screenshot if it helps at all
But the path that I am submitting to is
Z:\Documents\Batch-Jobs
reading into the error logs it looks like it's having issues with a file in my temp directory?
Can you show the output on the system console (Window -> Toggle System Console)? I can't reproduce the issue with just a blank file.
Hello Sybren,
Here is the output from the system console,
thank you for your help!
Added subscriber: @DeJev
Hello Nathan,
I had the error "ValueError: WindowsPath('.') has an empty name" only when I had a new file by opening blender or creating a new one via Files-New and did not save it before submitting a job to flamenco.
It looks like It may be an issue with the Blend file itself. I started a few other projects and those seem to start up just fine. Unfortunately I still have no idea what specifically in that blend file is causing it to trip.
Hi, sorry for bringing up a dead post from 2 years ago. A google search for this exact problem I'm having brought me here, but I keep getting this error on Blender 4.0.2 and Flamenco 3.5.
I seem to be getting the problem when I'm opening old projects for clients (dating right back to projects originally made in Blender 2.79) and trying to submit them to Flamenco. It happens a lot in scenes where I've linked things from other blend files.
As with the OP, sometimes Blender/Flamenco falls over at BAT pack stage stating the directory name is invalid and a message like:
"Error performing BAT pack: [WinError 267] The directory name is invalid: 'C:\Users\matt\AppData\Local\Temp\bat-2halytyl-batpack\bat-zsuis9g0-Factory IO Board.blend'"
Notably, all of the forward slashes in the file path on the error message are doubled up \ which doesn't show here on the webpage, but it does in the text editor.
Anyway, the reason I'm bringing up this dead post is for anyone that is looking for a workaround to fix the issue... I've found one.
(Perhaps delete the default 'Scene' in this list at this stage so it doesn't interfere with your render options and compositing)
(Stage 6 is only only really important if you use linked content from other blend files. Localising stuff seems to break the links which is annoying if you want to update the source files later)
I hope this solution helps people. If anyone knows a better way or a proper fix, I'd love to hear it.
Can you find a commonality between those cases? Or maybe minimize a file that has this problem? With "minimize" I mean that you remove anything and everything that can be removed, while it still producing the error. That will help a lot in finding the root cause of this problem.
That error is what you get when using a file path where a directory path is expected. Looks like a bug, but I'd have to know how to reproduce the issue in order to make that assessment.
This is quite common (not just in Flamenco). I've written an explanation in https://flamenco.blender.org/faq/#why-are-all-the--doubled
It's strange that this would work, as it basically makes a new blend file with the old scene in it. Do you save that workaround-blendfile in the same directory as the broken one?
Thank you for the feedback
I'll keep my eye on this issue and if I can share something with the issue for analysis I will, but so far these are all scenes for various clients and I'm subject to NDA's as the scenes contain their products or assets.
The file path in the example above is the path of a linked in asset. Once I migrate the entire scene to a new blend file (whilst maintaining that linked file at the same path) it works fine. It seems like the linked assets aren't the problem but how some blend files are recording their path is. Again, in the example above, that Factory IO Board.blend file stored on my X:\ drive, so I assume the ...appdata\local\temp... is a duplicate used during the packing process or where it exists whilst the scene is open or something??
The workaround-blendfile is saved in the same directory and in most cases I will save the original buggy-blend file as it's name and add on _oldversion ("filename_oldversion"), then open a new blend file, append the contents from it as described in my previous post and save the NEW file with the old file's original name in its original folder and it works fine. I have the _oldversion file as a backup just in case.
To resolve this issue, I need to know how to reproduce it. An example setup would help tremendously. If possible, please just make a dummy setup that follows your workflow, but uses simple cubes and other non-NDA-covered things.
When submitting a job, Flamenco tries to reproduce the project directory structure, so that relative, in-project references remain valid when the files are rendered on the farm. When linking assets outside (what is detected as) the project directory, Flamenco/BAT will have to change any references to it. That's done by copying the blend file to a temp location and editing it; that path you see points to that temporary copy.
You can see this by looking at the job directory -- if it has an
_outside_projectdirectory, that will contain those files from outside the project.