[Bf-committers] 2.7x to 2.8x Migration
chadf at triularity.org
Wed May 2 23:19:38 CEST 2018
While it might be the best practical solution (given the current
environment), I wouldn't consider it ideal. An "ideal solution" might be
something along the lines of it detecting a potentially incompatible old
.blend file, notifying the user, and automatically converting it (via a
bundled external program, if need be). Something like this, if done right,
could conceivably also convert very old files (like 2.4x) without forcing
users to go through great efforts to use older models in modern blender
versions. When someone wants to open an old version of a word doc, they
generally aren't expected to install the old version of word, just so they
can convert their document to something the new version of word can use.
But again, ideal may not be in practical reach.
At the very least, it should warn users when it loads a .blend file that
*might* have data loss due to dropped data structures (that aren't
perfectly auto migrated), so that novice-to-immediate users don't stare at
pitch black objects and wonder why the "cool looking model" file they just
download doesn't look like the preview image.
On Wed, May 2, 2018 at 3:51 AM, Dalai Felinto <dfelinto at gmail.com> wrote:
> Hi there,
> We now have a page to help users with migrating 2.7 files to 2.8:
> The big topic that is open for discussion and external contribution is the
> Blender Internal conversion.
> The ideal solution would be a Python script for Blender 2.79 that converts
> Blender Internal materials to EEVEE-compatible Cycles materials. It doesn't
> need to be a perfect conversion, but at least a way for users to not stare
> at pitch black objects when opening their 2.7x files in EEVEE.
> We are not prioritizing this at the moment. So this is a perfect
> opportunity for someone from the community to help the Blender 2.8 project
> Thank you,
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers