I would like to write a plug-in for maya that can import and export bgeo format!
And the plug-in can import and export geo format，but fail to bgeo.
And I don‘t know how Organization and management of bgeo format file.
help!
east
bgeo format file
11191 18 4
-
- SandFX
- Member
- 11 posts
- Joined: 3月 2009
- Offline
-
- Simon
- Member
- 2199 posts
- Joined: 7月 2005
- Online
-
- SandFX
- Member
- 11 posts
- Joined: 3月 2009
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
Ich have put the files from sourceforge into a VS2010 Solution and after some corrections they to compile and work for ascii files, but bgeo files written by this example code can not be read by houdini 11. Its not a little endian problem and a quick compare between the generated file and a houdini one shows just little differences. In the Data folder are Reference files written by houdini and GPD files written by GPD. I hope somebody has some ideas what could be wrong. Help is very much appreciated
dulo
dulo
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- josh3light
- Member
- 120 posts
- Joined: 2月 2008
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- edward
- Member
- 7722 posts
- Joined: 7月 2005
- Online
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
Well the code is there and it gives results and the files dont look too bad in the hex monitor but houdini doesnt load them. In the first versions it was a problem with the little endian preprocessor setting but now everthing compiles right and it should work .. at the moment i am just using the ascii version and i am trying to add support for volumes …
-
- symek
- Member
- 1390 posts
- Joined: 7月 2005
- Offline
I don't remember details at the moment, but original code seems to have a small bug/issue related to legacy headers or something. Binary data has a wrong layout. We've faced it during a creation of python module for r/w bgeo files. Fix wasn't so big, I just need to find a source code which I haven't seen for a while.
The biggest problem for us was a plethora of environments we were tried to compile our extension. A long as we stayed on Linux land having 2.5 and 2.6 pythons (plus versions of gcc) all was fine. On Windows though, well…
Anyway, GPD certainly works with binary files with that minor patch.
I'll try to narrow it.
skk.
The biggest problem for us was a plethora of environments we were tried to compile our extension. A long as we stayed on Linux land having 2.5 and 2.6 pythons (plus versions of gcc) all was fine. On Windows though, well…
Anyway, GPD certainly works with binary files with that minor patch.
I'll try to narrow it.
skk.
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
This is a new Version of the lib with examples as VS2005 Solution.
Fixed some uninitialized Variables fileNprim = 0; fileNpt = 0 ;
Seems like gcc can init members with zero ???!! otherwise the code could never have worked ..
Also attached some files written by example makesphere. geo file is read by houdini but bgeo is not. but if you compare the bgeo file written by GPD and the bgeo file written by houdini the differences are minor.
Fixed some uninitialized Variables fileNprim = 0; fileNpt = 0 ;
Seems like gcc can init members with zero ???!! otherwise the code could never have worked ..
Also attached some files written by example makesphere. geo file is read by houdini but bgeo is not. but if you compare the bgeo file written by GPD and the bgeo file written by houdini the differences are minor.
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
I dont get it .. i really start to freak out ..
the following code
unsigned short first = 9;
UTwrite(os,&first);
first ++;
UTwrite(os,&first);
results in this binary stream :
00 09 00 0d 0a
the same unsigned short smaller than 9 is written as 00 09 and if its greater than 10 its written as 00 0d 0a ???? !!!
what the hell is going on here ??
the following code
unsigned short first = 9;
UTwrite(os,&first);
first ++;
UTwrite(os,&first);
results in this binary stream :
00 09 00 0d 0a
the same unsigned short smaller than 9 is written as 00 09 and if its greater than 10 its written as 00 0d 0a ???? !!!
what the hell is going on here ??
-
- dulo
- Member
- 383 posts
- Joined: 6月 2010
- Offline
-
- Quick Links