Open GoogleCodeExporter opened 8 years ago
This also occurs with the latest version of Blender (2.62) and is definitely
going to happen with Blender 2.63 when BMesh is merged in (dev mailing list
indicates that standard .blend files will not contained the triangulated
EditMesh we're used to).
I think erwin may comment soon on how we can update it without his assistance :)
Original comment by BenT.Sol...@gmail.com
on 17 Feb 2012 at 1:12
If bParse DNA is updated to 2.62, Gamekit can read a 2.62 blend file.
But, it has a issue with a previous 2.5x blend file.
Original comment by harkon...@gmail.com
on 18 Feb 2012 at 6:42
FBT can read a 2.62 blend file(32/64 bit).
Turn off CMake OGREKIT_USE_BPARSE option.
Original comment by harkon...@gmail.com
on 18 Feb 2012 at 2:05
bParse should be able to handle forwards (and backwards) compatibility, unless
big changes happen (such as the refactoring of animation system and BMESH).
Not sure why FBT works and bParse doesn't.
Harkon, good to see you back! Do you have time to look into this, and BMESH
support?
Original comment by erwin.coumans
on 21 Feb 2012 at 5:40
Is this a duplicate of Issue 211 ?
http://code.google.com/p/gamekit/issues/detail?id=211
Original comment by erwin.coumans
on 21 Feb 2012 at 5:44
@Erwin, I think it is a different issue, not sure since he did not specify his
version of Blender he saved the blendfile with.
I am wondering what the main differences between FBT and bParse is, is there
any reason to prefer the one over the other?
I will try compiling without BPARSE today
Original comment by joeyferweda@gmail.com
on 21 Feb 2012 at 10:56
@Erwin, Hi, I will check this issue.
Original comment by harkon...@gmail.com
on 21 Feb 2012 at 4:03
struct ID's name field is changed to 'char name[66]' from 'char name[24]' in
SDNA 2.6x.
Maybe, bParse could not handle a array field, correctly.
Original comment by harkon...@gmail.com
on 26 Feb 2012 at 11:55
Thanks for investigating it. What is comment 2 about, update to 2.62 breaks
reading of 2.5files, why?
Original comment by erwin.coumans
on 30 Mar 2012 at 5:40
Is this still a problem after Thomas' update? Should I close this issue?
Original comment by kungfoobar@gmail.com
on 13 Jun 2012 at 4:39
Original issue reported on code.google.com by
thorwo...@gmail.com
on 1 Feb 2012 at 2:16