• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

SlotHold2 error

G

Guyanthalas

Member
I'm getting the following error when I attempt to access print preview in Hero Lab. Not sure if its core or 5e community pack.

Attempt to access field 'trkMax' that does not exist for thing 'SlotHold2'
Location: 'label' script for Template 'ohPick' (in Portal 'overload') near line 2
---
Attempt to access field 'trkMax' that does not exist for thing 'SlotHold1'
Location: 'label' script for Template 'ohPick' (in Portal 'overload') near line 2

I know next to nothing about how this program works or I'd have try to do some debugging myself. I'd be glad to learn though if someone can point me in the right direction.
 
Tried to recreate the error. Started up herolab with a brand new hero.
Using:
5e Core Pack v1.8
* PHB
* DMG Beta
* Elemental Evil Companion
* Princes of the Apocolypse
Playground Adventures
* Pixies on Parade
Output Options
* Hide validation
* Show hero portrait

Race: Dwarf, Mountain Dwarf, Brewers supplies.
Added 5 levels of warlock. changed level 2 HP to "4".

Hit print preview.
Attempt to access field 'trkMax' that does not exist for thing 'SlotHoldWa'
Location: 'label' script for Template 'ohPick' (in Portal 'overload') near line 2

Hopefully that helps. Let me know what else you may need.

*UPDATE*: I went through and did the steps one at a time. Print PReview is fine until I add a warlock level (Added just one). Removed it, print preview opens fine. Added bard. error comes back.
 
Last edited:
Not sure what's causing the error, I do get the same thing when using your details to create the character, but I do find that if I uncheck Enable Data File Debugging under the Develop tab, the error goes away.

I've had similar errors that only showed up when the Enable Data File Debugging was checked in the past. They eventually went away but I don't remember if I fixed the issues or LW did something that caused them to go away.

Sorry I am not more helpful.
 
Honestly this looks like an issue in the dossier logic. I would report it to LW. Also disabling Data File Debugging just hides minor errors from the user. It does not make them "go" away or fix them. :)

General Hero Lab Support & Community Resources is a sticky thread at top of Forum where you request official support for issues.

Remember POSTING bug reports in the forums means they won't get fixed...
 
Don't sell yourself short, that is plenty helpful!

The error is more of a nuisance than anything as it lets me print the sheets just fine. But as with any program that I don't fully understand (only have had it for 4 months) I worry that its going to miscalculate weapon damage or some other nonsense. So far I haven't seen any problems with the character sheets so maybe its just an odd debug warning.

Mergon said:
Not sure what's causing the error, I do get the same thing when using your details to create the character, but I do find that if I uncheck Enable Data File Debugging under the Develop tab, the error goes away.

I've had similar errors that only showed up when the Enable Data File Debugging was checked in the past. They eventually went away but I don't remember if I fixed the issues or LW did something that caused them to go away.

Sorry I am not more helpful.
Click to expand...
 
Because this is software you can't use a true engineer's method of fixing it . . . bang on it with a wrench until it works . . . :)
 
For sure. The only reason I didn't post it to LW directly was because I like to remove the "user error" element before bothering a developers time with something. As a business analyst most of my day is spent deciphering between bugs, features, and user error so I try to pay that forward as much as possible.

Since I'm using the Community Pack I wanted to double check it wasn't anything related to that thing.

ShadowChemosh said:
Honestly this looks like an issue in the dossier logic. I would report it to LW. Also disabling Data File Debugging just hides minor errors from the user. It does not make them "go" away or fix them. :)

General Hero Lab Support & Community Resources is a sticky thread at top of Forum where you request official support for issues.

Remember POSTING bug reports in the forums means they won't get fixed...
Click to expand...
 
Well what I have seen more of in this forum is that people ask if something is a bug. They don't get a clear answer. Then months later some else says I have this issue too. Months again go by with someone saying I have this issue also. But not one person reported the issue to LW.

LW has specifically asked that you report anything/everything you think is wrong to there support service. :) This way they can fix issues and track information of how many people are being affected.
 
Case 118102 has been resolved. It looks like this will get fixed next update. Thanks everyone for helping me narrow the problem down!
 
You must log in or register to reply here.
Back
Top