Errors on hero following Pathfinder patch 12.8

Gigigidge · November 26th, 2015, 07:21 AM

Not sure where these errors are coming from, but after updating to the latest version of Hero Lab, my character shows these errors on loading:

Pick 'p3PBloodie' has been orphaned due to missing thing in batch '285'
Pick 'p3PBloodie' has been orphaned due to missing thing in batch '287'
Usage pool 'psyPEUsed' has been orphaned for pick index '0'
Usage pool 'psyPEUsed' has been orphaned for pick index '0'
Usage pool 'psyPEUsed' has been orphaned for pick index '0'
Usage pool 'psyPEUsed' has been orphaned for pick index '0'
Usage pool 'psyPEUsed' has been orphaned for pick index '0'
Usage pool 'psyPEUsed' has been orphaned for pick index '0'

As mentioned above, this character wasn't showing any errors prior to the patch, so I assume something in the patch caused it. If it's something that can be fixed by making changes to the character, I would need to know what changes I would need to make.

If there's a place I can post or send the character, please let me know and I'll be happy to do so.

I've already posted this to the Community Packs thread as well in case its another conflict with something, but since I don't know what they mean, I don't have any idea where they're coming from and where the fix needs to happen.

Gigigidge · 07:26 AM

Nevermind, I think I just solved the problem. Resetting the hero to full hit points and clearing the damage records did the trick.

I've never seen that error before, though, so it still seems related to the patch somehow, just not sure how.

Hirsute · April 29th, 2016, 03:16 PM

Sorry to necro a months-old thread, but I'm having this problem as well. Resetting to full hit points and clearing damage records does help, but only temporarily for me, and it doesn't actually seem to be the entering of damage that triggers it. This occurs when opening the portfolio.

I've got a brand new portfolio that has never been "played," and I'm getting this error on it.

Mine is "Pick 'p3PBloodie' has been orphaned due to missing thing in batch '407'.

Any ideas?

ShadowChemosh · April 29th, 2016, 03:31 PM

Quote:

Originally Posted by Hirsute

Sorry to necro a months-old thread, but I'm having this problem as well. Resetting to full hit points and clearing damage records does help, but only temporarily for me, and it doesn't actually seem to be the entering of damage that triggers it. This occurs when opening the portfolio.

I've got a brand new portfolio that has never been "played," and I'm getting this error on it.

Mine is "Pick 'p3PBloodie' has been orphaned due to missing thing in batch '407'.

Any ideas?

That is the "Bloodied Army" condition. Did you have the 3PP Pack loaded at one time and now you don't? If so then just make any change to the character (ie put a space in the name and remove it) and then re-save the character.

The message will go away then.

Hirsute · April 29th, 2016, 03:41 PM

Not that I know of, I don't think I've ever had it downloaded. I've "dirtied up the file", too, and it does indeed go away, but it always comes back... Odd.

I'll have to see if my wife has installed it on the computer we use at the gaming table for her to GM. If so, that may be where the problem is.

ShadowChemosh · April 29th, 2016, 04:00 PM

Quote:

Originally Posted by Hirsute

I'll have to see if my wife has installed it on the computer we use at the gaming table for her to GM. If so, that may be where the problem is.

Would be my guess. Its a 'Condition' so even though the source is not turned on its getting attached to the character. Its just the way "Conditions" work in HL.

Hirsute · May 8th, 2016, 10:24 AM

That was it. Every time the file got opened up on one specific computer, the next time I opened it elsewhere, the error popped up. Don't need the TPP, so have removed it from that computer with no recurrence.

Gigigidge Junior Member Join Date: Apr 2015 Posts: 16 November 26th, 2015, 07:23 AM	Nevermind, I think I just solved the problem. Resetting the hero to full hit points and clearing the damage records did the trick. I've never seen that error before, though, so it still seems related to the patch somehow, just not sure how. Last edited by Gigigidge; November 26th, 2015 at 07:26 AM.
#2

Hirsute Member Join Date: Oct 2014 Posts: 37 April 29th, 2016, 03:41 PM	Not that I know of, I don't think I've ever had it downloaded. I've "dirtied up the file", too, and it does indeed go away, but it always comes back... Odd. I'll have to see if my wife has installed it on the computer we use at the gaming table for her to GM. If so, that may be where the problem is.
#5