Page MenuHome

No such file or directory
Closed, ArchivedPublic

Description

System Information
Operating system: Windows 10
Graphics card: Intel(R) HD Graphics 4000

Blender Version
Broken: 2.80

Short description of error
Normally I could save blender files in blender 2.8, but today somehow it says "cannot open file C:\(location of the file) for writing: No such file or directory" I tried to change the location of the file but didn't work either. I can't even save it in the desktop.

Exact steps for others to reproduce the error
I don't really know why did this happen. I just tried to save it as I did with many other projects

Details

Type
Bug

Event Timeline

Marco (nacioss) triaged this task as Needs Information from User priority.

Seems like you are using an old build of 2.8. Please try with the latest one here: https://builder.blender.org/download/

I downloaded this version like 2 weeks ago

just uninstalled blender and reinstalled it and still without working

just uninstalled blender and reinstalled it and still without working

Did you download a recent version and install it? The point it not to re-install Blender, it is to get a more recent version.
Two weeks is a very long time ago at the rate bugs are being fixed.

I deleted all my blender data, went to the official page and installed the most recent version, but still not working...

Stephen Swaney (stiv) raised the priority of this task from Needs Information from User to Waiting for Developer to Reproduce.May 15 2019, 4:14 AM

Sometimes (but almost never) it randomly saves and now it says this:

Also didn't save the test btw

I tried to save an empty project and still without saving. Also watched some videos and that's not a texture or object problem

well, I searched for like a month and still without getting the solution, I'll use another program cz give up...

IT WORKED, lol 1 and a half months but finally the problem got fixed ty so much

Brecht Van Lommel (brecht) closed this task as Archived.
Brecht Van Lommel (brecht) claimed this task.

Good to know that's the problem, this should be solve at some point when we do code signing of our buildbot builds like we do for releases.