On Mon, Jan 2, 2012 at 7:51 AM, Knapp magick.c...@gmail.com wrote:
On Sun, Jan 1, 2012 at 1:08 PM, David Jeske dav...@gmail.com wrote:
Getting my 2 cents in on an old thread...
On Dec 2, 2011 3:29 PM, Campbell Barton ideasma...@gmail.com wrote:
There are many options here, I was going to list
On Mon, Jan 2, 2012 at 9:04 PM, Campbell Barton ideasma...@gmail.comwrote:
I think this is enough - we could disable loading the file at all and
then blender wont crash - or only allow loading when --debug is passed
for people who know what there doing. not sure its worthwhile -
people are
Hi,
When I reviewed BMesh todos with Campbell I specifically asked for ensuring we
don't crash old binaries. The software of course cannot read the bmesh faces
(showing emppty mesh), but files should not crash on it. You get the warning
expect loss of data first of course.
-Ton-
no-crash, no-face - feature committed, also saves on undo memory and
disk space :).
save as legacy blend still works of course.
On Mon, Jan 2, 2012 at 10:18 PM, Ton Roosendaal t...@blender.org wrote:
Hi,
When I reviewed BMesh todos with Campbell I specifically asked for ensuring
we don't
no-crash, no-face - feature committed, also saves on undo memory and
disk space :).
save as legacy blend still works of course.
On Mon, Jan 2, 2012 at 10:18 PM, Ton Roosendaal t...@blender.org wrote:
Hi,
When I reviewed BMesh todos with Campbell I specifically asked for ensuring
we
On Tue, Jan 3, 2012 at 12:32 AM, Rasmus Lerchedahl Petersen
rus...@eecs.qmul.ac.uk wrote:
no-crash, no-face - feature committed, also saves on undo memory and
disk space :).
save as legacy blend still works of course.
On Mon, Jan 2, 2012 at 10:18 PM, Ton Roosendaal t...@blender.org wrote:
Guys compatiblity is really good right now.
Stop thinking about that while we have awful bevel tool and have no brige face
and inset tools.
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Getting my 2 cents in on an old thread...
On Dec 2, 2011 3:29 PM, Campbell Barton ideasma...@gmail.com wrote:
There are many options here, I was going to list all the ones I could
think of but most have some fairly annoying drawbacks.
You missed one of the best ones imo...
New '2.6' is made
Ye gods, not this AGAIN! :)
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
On Sun, Jan 1, 2012 at 1:08 PM, David Jeske dav...@gmail.com wrote:
Getting my 2 cents in on an old thread...
On Dec 2, 2011 3:29 PM, Campbell Barton ideasma...@gmail.com wrote:
There are many options here, I was going to list all the ones I could
think of but most have some fairly annoying
Well, what about earlier versions of blender? They won't have the
newer version checking code. But I like the idea of exporting
function, or something close.
___
Bf-committers mailing list
Bf-committers@blender.org
2011/12/2 Αντώνης Ρυακιωτάκης kal...@gmail.com:
Well, what about earlier versions of blender? They won't have the
newer version checking code. But I like the idea of exporting
function, or something close.
Yes, that is true but the idea does fix the problem for the next time
it comes up, as it
One other idea just jumped up at me. Write a python add on for the old
software that would allow for loading of the new format. Then users of
2.4 or whatever can download it and add it to their old blender.
On Fri, Dec 2, 2011 at 1:22 PM, Knapp magick.c...@gmail.com wrote:
2011/12/2 Αντώνης
There are many options here, I was going to list all the ones I could
think of but most have some fairly annoying drawbacks.
Currently BMesh triangulates the mesh when loaded in trunk or 2.4x,
You could argue both ways...
since mesh data is core to most blender projects...
a) being forwards
Maybe we must have separate compatibility save mode from regular save?
Like if I wanna save for older versions I use check box compatibility save
(disabled by default). Kind of Compress option.
I think all will be satisfied with this.
___
Bf-committers
From an user perspective... Here's my 2 cents...
I don't mind at all losing backwards compatibility... We achieve progress
by moving forward.
And I think the merge should be for 2.63... Not only because of Mango going
full swing later, but because is a good idea to have a more stable BMesh
ready
On Thu, Dec 1, 2011 at 9:39 AM, ertuqueque ertuque...@gmail.com wrote:
From an user perspective... Here's my 2 cents...
I don't mind at all losing backwards compatibility... We achieve progress
by moving forward.
And I think the merge should be for 2.63... Not only because of Mango going
As discussed last meeting, heres an updated bmesh merge proposal,
http://wiki.blender.org/index.php/User:Ideasman42/BMeshMergeProposal
Main issues I'd like feedback on are...
- Aim for 2.63 release.
- Who is able to help with testing, running regression tests etc.
- Can admin's agree on
People already accept loss of their animation, psys and scripts. Why you think
they will not accept loss of their mesh data?
I think the point for artists is not have a good compatibility, but better have
a good tools.
___
Bf-committers mailing list
On 01/12/11 11:26, Campbell Barton wrote:
As discussed last meeting, heres an updated bmesh merge proposal,
http://wiki.blender.org/index.php/User:Ideasman42/BMeshMergeProposal
Main issues I'd like feedback on are...
- Aim for 2.63 release.
- Who is able to help with testing, running
20 matches
Mail list logo
