Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows support #9

Open
tbarbieri opened this issue Feb 2, 2011 · 14 comments
Open

Windows support #9

tbarbieri opened this issue Feb 2, 2011 · 14 comments

Comments

@tbarbieri
Copy link

Does Partio currently support windows? Has anyone made a fork or any patches to get partio to compile for Windows?

Thanks!

Tony

@aselle
Copy link
Contributor

aselle commented Feb 2, 2011

I have compiled and briefly tested Windows compilation around release time. I have not built or tested the python components. Are you having trouble?

@tbarbieri
Copy link
Author

I edited the scons file to work with msvs. I got it to compile, but the tests fail. A few others ran the tests on Linux and also their results failed. Are the tests broken? Thanks!

Tony

@aselle
Copy link
Contributor

aselle commented Feb 2, 2011

Ah.. the windows support was done with respect to the CMake build files, so it's nice to have them working with visual studio too. which tests are failing for you?

@tbarbieri
Copy link
Author

$ ./test.exe
Testing with file 'test.bgeo'
Testing with file 'test.bgeo.gz'
Testing with file 'test.geo'
Testing with file 'test.geo.gz'
Testing with file 'test.ptc'
Partio: failed to find attr 'normal' for PTC output, using 0,0,0
Partio: failed to find attr 'radius' for PTC output, using 1
Partio: Unable to write data type FLOAT[2] to a ptc file
Partio: Unable to write data type INT[1] to a ptc file
Testing with file 'test.ptc.gz'
Partio: failed to find attr 'normal' for PTC output, using 0,0,0
Partio: failed to find attr 'radius' for PTC output, using 1
Partio: Unable to write data type FLOAT[2] to a ptc file
Partio: Unable to write data type INT[1] to a ptc file
Testing with file 'test.pdb'
Testing with file 'test.pdb.gz'

$ ./testcache.exe
Partio Unable to open file /tmp/test.bgeo
Partio: Magic number '-1256600978 of '/tmp/test.bgeo' doesn't match bgeo magic '1114072431
Partio: Magic number '1858738613 of '/tmp/test.bgeo' doesn't match bgeo magic '1114072431

$./testkdtree.exe

This one I get an Assertion Fail something to do with vector. I get a vector subscript out of range.

Thanks!

Tony

@ruchitinfushion
Copy link

I m on Win X64 & here is link (http://forums.cgsociety.org/showthread.php?p=6826936#post6826936),where you can get partio tool which i compiled on Win X64 using MS VC++ 2010 express with the help of Win7.1SDK.Hope this will help.Enjoy

@tbarbieri
Copy link
Author

do you have the build stuff in a fork somewhere so I can build it myself? Just wondering :). Thanks for your hard work!!!

@aselle
Copy link
Contributor

aselle commented Feb 8, 2011

Yeah, I'm happy to integrate the changes to make windows work again into the mainline. When I tested windows, I did with with the cmake build method.

@crydalch
Copy link

crydalch commented Mar 5, 2012

Hello!

I recently tried to load partio tools with partview, and I'm getting the same "doesn't match bgeo magic '1114072431" error; I thought it might be related to Houdini 12 (that's where I'm generating the bgeo from), but apparently its not? I'll keep digging, just wanted to chime in.

Thanks!

@efalconer
Copy link

You are correct, the issue is with Houdini 12. They have changed the GEO/BGEO format to a JSON/BJSON file format which the current version of Partio doesn't support. In the short-term you can use the gconvert command-line utility to convert from the newer formats to the old.

I'm in the process of writing a new reader that can handle it and as long as my company allows me to upload the results when it's complete I'll post the changes.

@aselle
Copy link
Contributor

aselle commented May 2, 2012

I am also in the process of writing such a reader. I can push my current
state on that if you want to compare notes.

On Wed, May 2, 2012 at 9:16 AM, Eric Falconer <
[email protected]

wrote:

You are correct, the issue is with Houdini 12. They have changed the
GEO/BGEO format to a JSON/BJSON file format which the current version of
Partio doesn't support. In the short-term you can use the gconvert
command-line utility to convert from the newer formats to the old.

I'm in the process of writing a new reader that can handle it and as long
as my company allows me to upload the results when it's complete I'll post
the changes.


Reply to this email directly or view it on GitHub:
#9 (comment)

@efalconer
Copy link

That would be useful. I'm not sure my changes will be suitable for the main branch at this point since it's using the Houdini UT_JSONParser classes since I didn't have time to sort out their tokens for their BJSON stream. I imagine people will want to be able to build partio without having to link against the Houdini libraries.

At this point I have successfully pulled out all the values for both the new GEO and BGEO files, just figuring out how to generate the appropriate ParticleAttributes and ParticleAccessors in partio.

@fpsunflower
Copy link
Contributor

We just ran into the Houdini 12 format change here at Imageworks -- @aselle do you have a patch we could take a look at?

@aselle
Copy link
Contributor

aselle commented Aug 31, 2012

I can post what I have. I haven't really gotten around to finishing it off
or packaging it as an importer. I hope to get around to finishing it next
week. A temporary workaround is to write to .bhclassic which will make the
old format. Then you can register a reader for that in partio in the io.cpp
I believe.

On Thu, Aug 30, 2012 at 1:19 PM, Christopher Kulla <[email protected]

wrote:

We just ran into the Houdini 12 format change here at Imageworks --
@aselle https://github.com/aselle do you have a patch we could take a
look at?


Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-8172954.

@fpsunflower
Copy link
Contributor

Good to know. There's no rush - the workflow of using gconvert is fine for us too.

pmolodo pushed a commit to LumaPictures/partio that referenced this issue Sep 24, 2013
partioExport  -filename flag
implemented  an optional   -fp/-filePrefix   flag  that works along side the normal  functionality
also tagged plugin file with new release version and (sigg)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants