• 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

Hero Lab 8.0/7.6.5 is available now!

B

BJ

Administrator
Staff member
Hero Lab 8.0 is out in the wild! Changes you make to characters should now occur up to 50% faster than before (depending on the character and game system you’re using). This improvement should be especially noticeable with characters that include one or more “minions” (such as a character with an arcane familiar, a mount, and a hireling). The new release makes Hero Lab more responsive and pleasant to use, especially for complex Pathfinder characters.

Hero Lab 8.0 is available now for Windows and Mac. For iPad users, version 7.6.5 is available in the app store. So what are you waiting for ? Update all your devices now!

Apple users please note: iOS 8, OS X 10.5, and OS X 10.6 will no longer be able to run new versions of Hero Lab later this year as the new Apple dev tools will no longer support them.

Looking for a list of bug fixes and enhancements? As always, you can find them in Hero Lab itself under Help/More Documentation/Hero Lab Readme.

Happy gaming everyone!
 
So you know, it looks like 8.0a's editor is broken in a weird way on Mac (Macbook Air 6,2 running 10.12.2). Editing, saving, and compiling works fine, but doing Tools -> Test Thing with any class helper or class feature crashes the app with a EXC_BAD_ACCESS (SIGSEGV) error.

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000001c
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x1c:
-->
__TEXT 0000000000001000-0000000000586000 [ 5652K] r-x/rwx SM=COW /Applications/Hero Lab.app/Contents/MacOS/Hero Lab

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.LWDTechnology.HeroLab 0x000fadbb 0x1000 + 1023419
1 com.LWDTechnology.HeroLab 0x000f4873 0x1000 + 997491
2 com.LWDTechnology.HeroLab 0x0010d13d 0x1000 + 1098045
3 com.LWDTechnology.HeroLab 0x000d96ef 0x1000 + 886511
4 com.LWDTechnology.HeroLab 0x000d9fd3 0x1000 + 888787
5 com.LWDTechnology.HeroLab 0x000cb95a 0x1000 + 829786
6 com.LWDTechnology.HeroLab 0x000cb4ea 0x1000 + 828650
7 com.LWDTechnology.HeroLab 0x000cb922 0x1000 + 829730
8 com.LWDTechnology.HeroLab 0x000cb4ea 0x1000 + 828650
9 com.LWDTechnology.HeroLab 0x000cb39d 0x1000 + 828317
10 com.LWDTechnology.HeroLab 0x0004f13a 0x1000 + 319802
11 com.LWDTechnology.HeroLab 0x00054865 0x1000 + 342117
12 com.LWDTechnology.HeroLab 0x0005443b 0x1000 + 341051
13 com.LWDTechnology.HeroLab 0x002d00b7 0x1000 + 2945207
14 com.LWDTechnology.HeroLab 0x0032f57b 0x1000 + 3335547
15 com.LWDTechnology.HeroLab 0x0032fac9 0x1000 + 3336905
16 com.LWDTechnology.HeroLab 0x0032cbd8 0x1000 + 3324888
17 com.apple.AppKit 0x92e5037d -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 658
18 com.apple.AppKit 0x92e4fd6d -[NSWindow(NSEventRouting) sendEvent:] + 547
19 com.LWDTechnology.HeroLab 0x0032de7e 0x1000 + 3329662
20 com.apple.AppKit 0x92cde12e -[NSApplication(NSEvent) sendEvent:] + 2854
21 com.apple.AppKit 0x92570327 -[NSApplication run] + 1018
22 com.LWDTechnology.HeroLab 0x0030ea31 0x1000 + 3201585
23 com.LWDTechnology.HeroLab 0x0030e771 0x1000 + 3200881
24 com.LWDTechnology.HeroLab 0x0030f740 0x1000 + 3204928
25 com.LWDTechnology.HeroLab 0x003103bc 0x1000 + 3208124
26 com.LWDTechnology.HeroLab 0x0031057d C_Application_Entry::Entry(int, char**) + 253
27 com.LWDTechnology.HeroLab 0x00002b75 0x1000 + 7029

Thread 1:
0 libsystem_kernel.dylib 0x9f8ac8be mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9f8abe33 mach_msg + 51
2 com.apple.CoreFoundation 0x946b1746 __CFRunLoopServiceMachPort + 214
3 com.apple.CoreFoundation 0x946b0b78 __CFRunLoopRun + 1576
4 com.apple.CoreFoundation 0x946b02ea CFRunLoopRunSpecific + 506
5 com.apple.CoreFoundation 0x946f1d31 CFRunLoopRun + 129
6 com.LWDTechnology.HeroLab 0x00394859 0x1000 + 3749977
7 libsystem_pthread.dylib 0x9f99510b _pthread_body + 184
8 libsystem_pthread.dylib 0x9f995053 _pthread_start + 243
9 libsystem_pthread.dylib 0x9f99490e thread_start + 34

Thread 2:
0 libsystem_kernel.dylib 0x9f8b4312 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9f995fc0 _pthread_cond_wait + 723
2 libsystem_pthread.dylib 0x9f99711f pthread_cond_timedwait_relative_np + 27
3 com.apple.CoreServices.CarbonCore 0x9561bd93 TSWaitOnConditionTimedRelative + 142
4 com.apple.CoreServices.CarbonCore 0x955f3d8c MPWaitForEvent + 200
5 com.LWDTechnology.HeroLab 0x0039c630 0x1000 + 3782192
6 com.LWDTechnology.HeroLab 0x0034e3e9 0x1000 + 3462121
7 com.LWDTechnology.HeroLab 0x0039668e 0x1000 + 3757710
8 libsystem_pthread.dylib 0x9f99510b _pthread_body + 184
9 libsystem_pthread.dylib 0x9f995053 _pthread_start + 243
10 libsystem_pthread.dylib 0x9f99490e thread_start + 34

Thread 3:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x9f8ac8be mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9f8abe33 mach_msg + 51
2 com.apple.CoreFoundation 0x946b1746 __CFRunLoopServiceMachPort + 214
3 com.apple.CoreFoundation 0x946b0b78 __CFRunLoopRun + 1576
4 com.apple.CoreFoundation 0x946b02ea CFRunLoopRunSpecific + 506
5 com.apple.CoreFoundation 0x946b00db CFRunLoopRunInMode + 123
6 com.apple.AppKit 0x926bc687 _NSEventThread + 235
7 libsystem_pthread.dylib 0x9f99510b _pthread_body + 184
8 libsystem_pthread.dylib 0x9f995053 _pthread_start + 243
9 libsystem_pthread.dylib 0x9f99490e thread_start + 34

Thread 4:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x9f8ac8be mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9f8abe33 mach_msg + 51
2 com.apple.CoreFoundation 0x946b1746 __CFRunLoopServiceMachPort + 214
3 com.apple.CoreFoundation 0x946b0b78 __CFRunLoopRun + 1576
4 com.apple.CoreFoundation 0x946b02ea CFRunLoopRunSpecific + 506
5 com.apple.CoreFoundation 0x946b00db CFRunLoopRunInMode + 123
6 com.apple.CFNetwork 0x939c91bf +[NSURLConnection(Loader) _resourceLoadLoop:] + 536
7 com.apple.Foundation 0x95da47fe -[NSThread main] + 39
8 com.apple.Foundation 0x95da4598 __NSThread__start__ + 1262
9 libsystem_pthread.dylib 0x9f99510b _pthread_body + 184
10 libsystem_pthread.dylib 0x9f995053 _pthread_start + 243
11 libsystem_pthread.dylib 0x9f99490e thread_start + 34

Thread 5:
0 libsystem_kernel.dylib 0x9f8b4cbe __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9f994dca _pthread_wqthread + 1210
2 libsystem_pthread.dylib 0x9f9948ea start_wqthread + 34

Thread 6:
0 libsystem_kernel.dylib 0x9f8b4cbe __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9f994c59 _pthread_wqthread + 841
2 libsystem_pthread.dylib 0x9f9948ea start_wqthread + 34

Thread 7:
0 libsystem_kernel.dylib 0x9f8b4cbe __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9f994dca _pthread_wqthread + 1210
2 libsystem_pthread.dylib 0x9f9948ea start_wqthread + 34

Thread 8:
0 libsystem_kernel.dylib 0x9f8b4cbe __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9f994dca _pthread_wqthread + 1210
2 libsystem_pthread.dylib 0x9f9948ea start_wqthread + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x21d91dd0 ebx: 0x0ae42a98 ecx: 0x00000000 edx: 0xf21d4aa1
edi: 0x0e0a56f0 esi: 0x1eb05460 ebp: 0xbfffef98 esp: 0xbfffef80
ss: 0x00000023 efl: 0x00010206 eip: 0x000fadbb cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x0000001c

Logical CPU: 3
Error Code: 0x00000004
Trap Number: 14
Click to expand...
 
Roadie said:
So you know, it looks like 8.0a's editor is broken in a weird way on Mac (Macbook Air 6,2 running 10.12.2). Editing, saving, and compiling works fine, but doing Tools -> Test Thing with any class helper or class feature crashes the app with a EXC_BAD_ACCESS (SIGSEGV) error.
Click to expand...

I just did some tests with a simple class and didn't run into any problems - if there's a specific user file you're having problems with, can you please email it to me at colen@wolflair.com? Thanks for your help!
 
Hi, recent downloaded the update and it ran into an error that prevents it from running pathfinder.

The data files could not be loaded due to errors. Hero Lab will now attempt to load them in recovery mode. Once loaded, you can access the editor as normal to correct any errors.

The following errors occurred:

Resource 'acttabunds' - Bitmap file could not be loaded: C:\ProgramData\HeroLab\data\pathfinder\tablet_undo_small.bmp
Click to expand...

And when I click okay to enter recovery mode, this pops up.

The following errors occurred:

Resource 'acttabunds' - Bitmap file could not be loaded: C:\ProgramData\HeroLab\data\pathfinder\tablet_undo_small.bmp
Click to expand...

And after clicking okay on this pop up, it brings me back to the main game select screen.

I'm not sure if this is the best place to put it, but I hope that I can get a little help with this.

Edit: Forgot to addthat I do have the community files downloaded with this too. Could that be an issue?
 
Last edited:
Load Hero Lab, then go to "Find Updates" on the "Select Portfolio" screen, then re-download and import the Pathfinder data files - that should fix your error.

Hope this helps!
 
This update is crashing at around 95%. Hero Lab thinks it's finishing though. Tried it twice. Hero Lab redid my license key each time. No idea at this stage if it worked or not. Too late to troubleshoot.
 
daplunk, do you mean the install of the new update is crashing? If it's the same bug other users are experiencing, the install will have completed, so you don't need to try updating again.

The installer creates a log file that includes a list of what happened during the install, which may be able to help us resolve this. Please do the following:

1) In Windows, open an explorer window to any folder.

2) In the location bar (where it shows you the folder you're in), type:

%temp%

That's a percent sign, then the word temp, then another percent sign. No spaces or other characters.

3) Press enter to switch to the temporary folder.

4) Look in that folder for a file named something like "Setup Log 2013-10-20.txt" with the date you last tried to install Hero Lab on.

Please send any files with that filename for that date (there might be a few of them) to me at colen@wolflair.com. Thanks!
 
Hi Colen,

I received the same as the previous poster when performing an "in Heror Lab" update to 8.0c. That is an error occurred at the end of the install.
Windows 10 64bit.

See attachments for screenshot of error and the log file. It does appear that the installation actually completed before the crash/error however.
 

Attachments

You must log in or register to reply here.
Back
Top