• 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

Mac version status

I recently posted about a mount thing, but it turned out what had happened is that some of my settings got reset in an update. Restrict companion race causes a problem in the d20 universe when you purchase an animal.
 
Last edited:
I posted this in the bug reports, but that may have been the wrong area.

Since the recent update I've been unable to open my main portfolio. I've also tried importing the characters into a new portfolio. Both crash Herolab.

Not sure what I need to be posting to help troubleshoot.

Cheers!

buzzby, please email me with the crash report at colen@wolflair.com - loading saved portfolios seems to be working for everyone else, so it's hard to identify the problem unless you can get us the crash report. :(
 
Im not sure if this is a mac bug or a general bug. I usually create class variants, but this time I created a class, using copy. This was done in d20. This was done to create a bad that isnt alignment restricted. All I did was copy the class, remove the alignment restricted, and give them another skill appropriate to my campaign.

It all seemed to work fine. But when I create the character, and select this different class, and click on the class tab, i clicked under special abilities, and it was listed blank for all levels. When i print, it doesnt list them either. But when i go back to my class in the editor, they are clearly there.

I can mail my editted files if needed. If anyone has any thoughts on what i might be doing wrong, let me know.

Please email me at colen@wolflair.com with the edited files and I'll take a look.
 
Colen, I will do so. But i just discovered another bug related to variant classes. I can reproduce it every time.

Whenever i edit a variant class, the override dropdowns for the saves dont really seem to work. If I select something other than none, (good/med/poor) and select it, it doesnt show it as one of the three, but alsways show as 'none'. (even though i think one of them is actually poor and its not supposed to be), and when i click it enough times, i get a crash. I was able to reproduce this three or 4 times tonight.

Here is the beginning of the stacktrace.


rocess: Hero Lab [13537]
Path: /Applications/Hero Lab.app/Contents/MacOS/Hero Lab
Identifier: com.LWDTechnology.Hero Lab
Version: 3.9.4 (3.9.4.290)
Code Type: X86 (Native)
Parent Process: launchd [169]

Date/Time: 2012-03-27 19:21:27.077 -0400
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 1014530 sec
Crashes Since Last Report: 3
Per-App Interval Since Last Report: 55905 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: 82735BE3-58C0-44A5-AEB6-39551172547E

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
objc_msgSend() selector name: view


Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x90157f8b objc_msgSend + 27
1 com.apple.AppKit 0x905fb31f -[NSApplication sendEvent:] + 5683
2 com.apple.AppKit 0x9058f253 -[NSApplication run] + 917
3 com.LWDTechnology.Hero Lab 0x0025c317 C_Canvas_Base::~C_Canvas_Base() + 4375
4 com.LWDTechnology.Hero Lab 0x0025cd68 C_Canvas_Base::~C_Canvas_Base() + 7016
5 com.LWDTechnology.Hero Lab 0x0025d7a4 C_Canvas_Base::~C_Canvas_Base() + 9636
6 com.LWDTechnology.Hero Lab 0x0025dad3 C_Application_Entry::Entry(int, char**) + 339
7 com.LWDTechnology.Hero Lab 0x0025d85b C_Canvas_Base::~C_Canvas_Base() + 9819
8 com.LWDTechnology.Hero Lab 0x00002ba5 0x1000 + 7077
 
Last edited:
buzzby, please email me with the crash report at colen@wolflair.com - loading saved portfolios seems to be working for everyone else, so it's hard to identify the problem unless you can get us the crash report. :(

Colen,

I'm having the same issue with saved portfolios crashing. I just e-mailed you two crash logs, one from opening Hero Lab then the portfolio, the other from telling Recent Documents to open the portfolio.
 
Last night I had an issue with a tooltip getting "stuck". The tooltip would not go away, even if I clicked on it or something else. Hero Lab itself was completely unresponsive; I could not switch tabs or anything. Hovering/clicking on icons that should have had other tooltips did not help.

This happened after I was using LogMeIn to try accessing Hero Lab from my Mac through LogMeIn on my iPad. I think the issue may have been related to changing screen resolution while the tooltip was showing. I will try to reproduce it later today.

Thanks!
 
Because I don't see it in the thread here I thought I'd post this.

I just snagged the latest update through the updater utility inside the HL app on my MacBook Pro. I did this update just as I did the last. It worked then but it's not working this time. I get the following error when I try and start the HL app.

Unable to locate file: hl.xml

Thanks.

Victor
 
A possible solution to crash reports on opening older portfolio files. If you have a custom editor file you've used, open up a blank portfolio. Then open up the editor and open up the file. Choose one of the items in it and test it. Close the editor, and reboot Hero Lab. It should load the portfolio next time round. No idea why this works, but I found it out after having a portfolio constantly crash for me.
 
Unfortunately, this is not a Mac bug. The Statblock output has always truncated the text of longer descriptions.

If this is the case, and Lone Wolf has never fixed it, can anyone with experience creating custom outputs tell me if this is something that "Could" be fixed by creating a custom output stat block?
 
The "crash when loading portfolio" issue should be resolved in the beta we released on Friday.

Burner2501, I think I emailed you this - in case that wasn't you: It sounds like your update didn't work properly for some reason. Go through the beta application process here:

http://wolflair.com/hero_lab_mac_beta.php

And you should get the latest installer - download and install it and you should be good to go.
 
I downloaded the Mac Beta today on to a G5 Mac Pro OSX 10.6.8 system. It was a non starter. The application installs and loads but immediately displays a Hero Lab error message
"Unexpected error creating font 'editscript': 0000044c"
The some of the menus drop down are greyed out and they are all inactive. The program doesn't Quit on Apple +Q or menu Quit. I can Force Quit but the Application doesn't show as "Not responding". Only a Restart got me out.

Anything I can try to get it running properly?

MacBook Pro on OSX Lion, also getting an "Unexpected error creating font 'title': 0000044c" and then the program just completely crashes and refuses to open. Uninstalled and reinstalled, same issue.

I do have a decent amount of 3rd party fonts on my computer, maybe the one you use for "title" has been replaced?
 
We rely on the standard set of fonts that are installed on all Macs by Apple. If you're getting that error, make sure you have the "Arial" font installed - if not, you'll need to replace it for Hero Lab to work.

AFAIK there's no way for one font to "replace" another - to get this error, the original font must have been removed. Did you maybe run a third-party font manager application that removed it?
 
Last night I had an issue with a tooltip getting "stuck". The tooltip would not go away, even if I clicked on it or something else. Hero Lab itself was completely unresponsive; I could not switch tabs or anything. Hovering/clicking on icons that should have had other tooltips did not help.

was this issue resolved?

i am currently on v4.0b#315 (mac osx 10.7.4) and it is practically unusable due to this issue. i have to force quit and reboot every time.
 
Back
Top