Thank you <3.

Richard60 posted at 3:12PM Sat, 14 November 2020 - #4404582

Going to go out on limb here and say that the number of frames is probably the issue. But not because of the number, which is a lot, but the fact that every bone/joint has a key in each frame. And even that is not the true cause (probably) but the fact that one of the enhancements that was put into Poser 11.1 was a feature to show how many Keys are in a figure when the body parts are collapsed in the Animation Palette. It is a pretty useless feature in that yes it tells you how many keys are in a body part, but you have no idea what they are until you expand out that body part and look for yourself. It use to show a Dark Color it indicate there are Keys set, Now it shows both the Dark Color and a number. However every time a key is made Poser goes back and re-calculates that number. So that if you put in 5,000 frames with 100 body parts it goes through and calculates 500,000 numbers. And it probably there that the Program quits. I know that Poser slows down on the Animation screens the more keys that are put in, and was not the case in earlier versions.

The good thing is BVH files are easy to edit. Using a good Text Editor (as you don't want to have formatting from Word Processors applied) open up your BVH file. The first thing you will find is the Hierarchy listing of the Bones. As you scroll down you will find where the motions are stored for the Hierarchy. Between the first line and where the motions begin You will need to copy this part and put into the headers of the smaller files you are about to make. Now taking the data edit into smaller sections Say 500 frames. Put the Header at the beginning and change the number of frames to show the new number. Save these files as BVH 1 BVH 2 etc.

Now you should be able to load these into Poser and Render out the segments and put them together in a video editing program.

I've just opened one of the BVH with notepad. the motions you've mentioned is simply a huge chunk of numbers Data. how can I know where to split them without hindering the Data? is there a way to know where each frame ends?

screenshot attached:

Richard60 posted at 3:01PM Sat, 14 November 2020 - #4404582

Going to go out on limb here and say that the number of frames is probably the issue. But not because of the number, which is a lot, but the fact that every bone/joint has a key in each frame. And even that is not the true cause (probably) but the fact that one of the enhancements that was put into Poser 11.1 was a feature to show how many Keys are in a figure when the body parts are collapsed in the Animation Palette. It is a pretty useless feature in that yes it tells you how many keys are in a body part, but you have no idea what they are until you expand out that body part and look for yourself. It use to show a Dark Color it indicate there are Keys set, Now it shows both the Dark Color and a number. However every time a key is made Poser goes back and re-calculates that number. So that if you put in 5,000 frames with 100 body parts it goes through and calculates 500,000 numbers. And it probably there that the Program quits. I know that Poser slows down on the Animation screens the more keys that are put in, and was not the case in earlier versions.

The good thing is BVH files are easy to edit. Using a good Text Editor (as you don't want to have formatting from Word Processors applied) open up your BVH file. The first thing you will find is the Hierarchy listing of the Bones. As you scroll down you will find where the motions are stored for the Hierarchy. Between the first line and where the motions begin You will need to copy this part and put into the headers of the smaller files you are about to make. Now taking the data edit into smaller sections Say 500 frames. Put the Header at the beginning and change the number of frames to show the new number. Save these files as BVH 1 BVH 2 etc.

Now you should be able to load these into Poser and Render out the segments and put them together in a video editing program.

Richard, thank you so much for your thorough answer! I wonder is there's a way to turn off that unneeded addition (I recall making huge animations 9-10 years ago on older poser versions and there wasn't any problem such as this).

What I did up until now was simply cut down the BVH to only the first 1000 frames, and then I was able to go into the keyframes and delete all the unwanted keyframes (which, as you explained so well, bogs down the system thanks to that counting : ). after the animation was cleaned, I simply saved it inside poser as a frames-range pose/animation.

I'll try to do what you've suggested. sounds like a decent workaround. thanks!

Azath posted at 8:34AM Wed, 11 November 2020 - #4404188

gsfcreator posted at 6:42AM Wed, 11 November 2020 - #4404187

I was wondering if there are any changes that will make the move worth it, for someone who renders with Octane? from what I've been reading, I cannot tell. seems like some improvements for the rendering engine, which is irrelevant for me.

please let me know if you think otherwise, and why so.

From the basic aspect if you are owner of Previous Poser versions there is actually no good reasons to Update as for the moment there is not a gain , It rather might cause if you are a big collector having to update allot of assets to get em to work right. then it depends on what graphic card you are running. The question if you use Pytons is , if and when are these going to be updated, will you have to buy em again? How could you legally access an update as allot of these came from RDNA and CP ?

as for a new Poser user there is no workaround they have to get Poser 12 if there interested learning to render with it and learn how to use it . these depend on it as every Previous version is removed from the Market . For them a take it or leave it .

but at the moment if you prefer Rendering and make art without a huge fix it is better to stick on the old version until Rendo shuts it totally down :)

exactly my thoughts :). and I don't know if it's legal for them to "shut it down". I've just purchased 2 extra licenses for poser pro 11 not long ago, and those licenses are supposed to be perpetual. so...they can choose to stop updating it - but shutting it down = they'll have to pay the buyers their money back.

if it's not broken - don't fix it (Actually I had high hopes that rendo will get to work together with DAZ like it was in the past, and get us the new G3 and G8 figures. that would be a reason enough for me to upgrade. and I trust that I'm not alone).

I was wondering if there are any changes that will make the move worth it, for someone who renders with Octane? from what I've been reading, I cannot tell. seems like some improvements for the rendering engine, which is irrelevant for me.

please let me know if you think otherwise, and why so.

Problem solved. I have no understanding as for why it happened (maybe someone with more knowledge can explain...)

but removing this from the left toe, left foot, right toe and right foot solved the issue.

i tried twice with my pc. CPU=Q6600, 4GB RAM(but only 3 recognizable by my xp32bit OS). mhz=2.4

first trial - 4threads = 3:40 seconds(2 minutes + for texture loading:|! )

second trial - 4threads, seperate process - around 2:32 seconds(but maybe its cause its the second trail? i havent closed poser between thr trials :)