- User Since
- Dec 9 2018, 9:52 PM (28 w, 1 d)
Apr 2 2019
@Andrea Müller (Archimondro) I agree, I had to go back to V2.79 because I could not complete the task I needed to do. I was doing rope simulation and need rigid body for that and need to chain them. At the moment that is impossible in V2.80 beta, unless I work a few hours on it instead of a few minute.
Mar 27 2019
How can you chain objects if you need to select first and second object?
Mar 3 2019
Feb 22 2019
@ALESSANDRO NASCIMENTO MILHIOLO (alessandromilhiolo) the only problem with that is, every time you download a new build you need to add the --factory-startup. By deleting the userpref.blend file all is solved. It creates a new blank one and it is done. Well, not exactly because you need to activate some of the add-ons and setup you Preferences but you only need to do it once. Since I deleted that file, I used another 5 or 6 daily builds and all run ok and create video from image sequences.
Feb 13 2019
Alessandro, just remove the userpref.blend file for the C:\Users\....\AppData\Roaming\Blender Foundation\Blender\2.80\config\ folder and see if it starts to work. Do not activate any addons to see if it will work.
Feb 12 2019
What are the findings from my userpref.blend file?
Feb 11 2019
@Alessandro Caragnini (alessandro) NASCIMENTO MILHIOLO (alessandromilhiolo) I download dailies frequently because they fix one thing and mess up something else. At the moment I do not find the left click setting that used to be in Preferences. Startup screen only shows it at first run which in this case was okay because I removed the blender config file and that forced blender to create a new one and at the same time I could set left click, on 2.80 I am used to that. That is actually how I got it to create the image sequence movie with my own old file that was crashing all the time and I did not change anything in the security settings. The config setting should be already set with the correct permissions because I have 2.79b installed and the config file resides there but in its 2.80 folder.
Feb 10 2019
I ran the test with the above arguments and it did not crash. It finished creating the mp4 file.
Feb 9 2019
I downloaded the 'Image Sequence Rendering' file. I moved it to a drive where there is plenty of space to eliminate possible problem with that, as previous messages suggest.
Followed Christopher's instructions and before running the render I changed the output folder. Initially I forgot to do that and got the message 'Could not open file for writing', of course because based on the test file it was trying to write to a drive that was not activated on my computer. That was R: drive.
This morning I downloaded the latest build of V2.80 and this time it started without crash but when tried to run the image sequence file it crashed just like before.
Feb 8 2019
Well, this is interesting. I downloaded the same build, the one I just downloaded to my laptop for testing, and on my desktop the daily build Blender V2.8 is crashing upon opening so I cannot even test if this version would work with that image sequence file. A build from a couple of days ago, build 2019-02-05, was opening regularly and I used it normally for other work.
As another test, I have Blender V2.80 version with integrated Mantaflow as well and that worked with the same V2.80 video sequence file where the daily build crashed all the time. The Mantaflow integrated blender is rather old one though.
Just for the sake of more testing, with V2.80 build 2019-02-08 I transferred all the same image files, that crashed on my desktop, to my laptop which has a CUDA but not supported by Blender 2.80. I did not import the 2.79b version settings. The video was created without crash. Now I go back to my desktop and download this same latest build and will test it again.
Feb 6 2019
At the moment I use V2.79b to create the video from the images, the build 2019-02-05 still crashes. It does not matter where the render device is set, CPU, Open CL, graphics card or video card+CPU, it will crash. Not sure if video encoding utilizes the video card anyways. I have 4GB of VRAM on the ASUS R9 290X DirectCU II OC and 32 GB RAM, Intel i7-4790K CPU @ 4Ghz with windows 10.
Jan 18 2019
This is one of the actual files I tried to use. I created several because I thought that I messed up something with the setup but all resulted with the crash.
Jan 13 2019
Dec 13 2018
Unfortunately with current files that had that problem it still exist. It works only if I start from scratch with the suggested Factory Defaults.
What controls this behavior?
I work on files that I created in V2.79 and is about 2GB in size so no way I can recreate it in 2.80. I put a lot of work in it already.
Dec 12 2018
I did the Load Factory Defaults suggested by billreynish and that solved the problem. Thank you but not sure why this happened in the first place. I do not recall changing anything. Interestingly every time I downloaded a new daily build this problem was carried over.