"problem with file : was the file saved using Mac line endings ?" the revenge.

[Mario Marietto]

Hi, 

I'm running Win 10 64-bit. bvhacker-1-9-0-1b appears to run fine when I open a .bvh file taken here : 

https://sites.google.com/a/cgspeed.com/cgspeed/motion-capture/daz-friendly-release

I have found some other BVH files elsewhere,but with them the program refuses to open them,giving this error : "problem with file : was the file saved using Mac line endings ?". 

I thought to have found a solution for this problem,reading here : 

https://groups.google.com/forum/#!topic/bvhacker/yu2x4_I9YXM ; 

but that solution didn't work for me. The error is still there. Why ? thanks very much.

[Jorge Abad]

Hi. I am new to the group. Well, Mario ... the problem is not that they were done on Mac or Linux, but the limit of 2048 characters per line.
  https://docs.microsoft.com/en-us/cpp/c-language/maximum-string-length?view=vs-2019
  This is solved by recompiling the code and replacing 2048 with 65535 in BVHFile.cpp:
if (line-> GetLength ()> 2048)
{
AfxMessageBox (_T ("Problem with file: was the file saved using Mac line endings?"), MB_ICONSTOP);
return false;

Or use my script to "remove fat":
https://www.daz3d.com/forums/discussion/281521/bvhacker-and-the-dreadful-sentence-problem-with-file-was-the-file-saved-using-mac-line-ending

[Shane]

I get the problem too. It worked fine on win 7, but on 10 it cries Mac. 
Any chance on updating the script?  I saw someone mention something about a double extension on the above link.  I'm not smart on this stuff.
I've been using 1.8 since it still works, but it loads files extremely slow now days. 
I really with this app were to get an update as I still have not been able to find a good replacement for it.

[davedub]

I did fix this a while ago, but have not got around to updating the website. The updated version is on my github here:

https://github.com/DaveDubUK/bvhacker/tree/master/bvhacker/Release

 - dave

[Shane]

Oh awesome. This is great news. Thank you!.