Blender 2.77 RC2

Hi, Blender Foundation has release second RC build of Blender 2.77.
Several important bug fixes are implemented since last RC1.


Check out:

http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.77

http://download.blender.org/release/Blender2.77/

Please report bugs to https://developer.blender.org/maniphest/project/2/type/Bug/
Use the template and add all information you can get and attach a simple as possible .blend when needed.

Have fun, mib
EDIT: Original picture from http://www.pokedstudio.com/
.blend https://www.blender.org/download/demo-files/

Hi!

Anyone testing particles?
Got some strange behavior here.
Particles are not refreshing as in previous versions. For now it seems only to be happening from 1st-2nd frame. Then on seems to work fine. If anyone can confirm any strangeness, i’ll then dwell deeper to see if it can be replicated and what causes it - to make a thorough report.

Edit:
Seems it’s happening with Newtonian Physics only, for now.

Smoke sim still not working, am I right?

paolo

False alert. Everything works fine. Thank you for testing @burnin!

Hi burnin, particles work for me, may you add a test .blend.
@sourvinos, smoke sim is working, check Quick Smoke with space search quick.
@cgstrive, sorry cant help here.

Cheers, mib

In fact it doesn’t work here, OS X.

paolo

@mib2berlin
Sometimes Physics activates instantly at frame 1, other times it starts on 2nd when played… i think it’s just the way it’s coded. Yes!

@sourvinos
Smoke works as it used. (win7sp1x64)

@cgstrive
Script works here. (Starting from default scene&preferences or customized)

Edited

Where are the wonderful Bmesh Booleans? Boolean Modifier has Bmesh option disabled

Have you reported this to the tracker?

I’m very happy to see that Blender simulated smoke caches can be read by Houdini:


However trying to export velocity, density, heat* etc from Houdini to Blender is not enough. Blender will crash on reading that data. It seems to me that Blender packs A LOT of secondary data that when absent will cause this crash.

Here’s a Houdini VDB sequence to test:
http://cgstrive.com/HoudiniVDB.rar

Here’s a guide how Houdini VDB writing is done (works with Free version also):
https://support.solidangle.com/display/AFHUG/Writing+Volumes+To+VDB

Would be fantastic to export data to Blender from other apps.

From this wiki page :

Currently, importing caches from other software is not supported, as it was deemed out of the scope of this project for it might require drastic changes to the smoke simulator itself.

Kevin often mention an idea of an OpenVDB object. It is probably a later project.
Currently, he took responsibility of the Alembic patch.

Due to the nature of the smoke simulator, the files store a lot of information on the state of the cached simulation, e.g. the resolution. Here are all the metadatas written in the .vdb files by Blender:

blender/smoke/active_color: [0.7, 0.7, 0.7]
blender/smoke/active_fields: 0
blender/smoke/base_resolution: [21, 21, 32]
blender/smoke/dp0: [-1, -1, -1]
blender/smoke/dt: 0.1
blender/smoke/dx: 0.03125
blender/smoke/fluid_fields: 0
blender/smoke/max_bbox: [1, 1, 1]
blender/smoke/max_resolution: [21, 21, 32]
blender/smoke/min_bbox: [-1, -1, -1]
blender/smoke/min_resolution: [0, 0, 0]
blender/smoke/obj_shift_f: [0, 0, 0]
blender/smoke/obmat: [[2, 0, 0, 0],
 [0, 2, 0, 0],
 [0, 0, 3, 0],
 [5.96046e-08, -1.19209e-07, 1, 1]]
blender/smoke/resolution: [21, 21, 32]
blender/smoke/shift: [0, 0, 0]
creator: Blender/Smoke

I guess if you can replicate this in Houdini then you might make it work, but importing/reading other software’s caches is not really supported at the moment.

More like a volume object that can hold VDB grids. (I already have a branch with a prototype working.)

If only GM200 cards worked in 2.77 lol

If I’m not mistaken, no one is really sure why that happens though?

I heard that 2.77 changes python version, is this why several addons have errors (and may or may not work) that worked in 2.76?
Primary concern is fbx export: Unity fails to import fbx from .blend in 2.77 though regular fbx export seems to work.
Will these errors be fixed in the final release or does someone have to manually update the scripts to work with 2.77?

If you’re running into these errors, it’s probably best to report the bug via official channels.

But still I would think that would be top priority seeing how Blender users spent thousands of dollars to use those cards with cycles lol.

It’s on 3.5.1 now.
>source<
About addon maintenance i think it’s best to contact developer or fix it yourself :spin:

Is the zip for windows 64 already built?Can i just unzip and use it or do i have to compile it?