Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[CharonM72]

Yeah 4 gigs is the memory limit for 32 bit applications. You'd need a 64 bit system, but also you need to make sure the application is running in 64 bit mode. Can it do that? Honestly I don't know.

[Parker147]

At the moment it is most likely limited by your system because the app loads everything into memory. It could be changed in the future to utilize the hard drive more, but it would take some work to make those changes. I also fear it would be a bit sluggish too.

[cosmiccoincidence]

Hello,
I've been a lurker on these forums for some time but made an account just to get some help with my legends viewer, I'm having the problem where my xml files are corrupt and cannot be read by the program. I saw the reply by PeridexisErrant about using notepad++ to find and replace the corrupt characters. Note that I am not that tech savy and downloaded notepad++ just for this purpose. Im now stuck because It seemed simple enough for me to find and replace them, but as I do not know what a "SOH" character is, I do not know how to then find it.

Thanks for all and any help. And thanks for this awesome addition to the game. Makes legends feasible.

[Parker147]

Are you using the newest version? It should now automatically detect corrupt XMLs and ask to attempt a fix and resave it.

[cosmiccoincidence]

It seemed my previous version was the issue. I got the new version and am able to repair the corrupt file now. Thank you, Thank you!! 
Legends viewer is the shit!

[Parker147]

There doesn't seem to be any substantial changes to the XML or other exports in 40.01. A few new events and what looks to be some different mechanics on site ownership. I'll see what I can get around to updating this week.

[DizzyCrash]

Should there be any trouble using it with the newest version of dwarf fortress?

[Parker147]

Should work fine, but I just uploaded the changes for the v40 data here.

If there is some problem though let me know.

[nenjin]

I was getting a few crashes trying to jump to sites and open a few historical figures with the last version. Whether that's specifically something about legends, or some buggy part of DF, who knows. I'll see what I get with the latest.

Also props again on this tool. The map functionality is just gorgeous.

[dennislp3]

This has always been my preference for viewing legends info...keep up the good work

[Parker147]

I was getting a few crashes trying to jump to sites and open a few historical figures with the last version. Whether that's specifically something about legends, or some buggy part of DF, who knows. I'll see what I get with the latest.

Also props again on this tool. The map functionality is just gorgeous.

If it crashes on specific historical figures it is probably caused by an oddity occurring in an event which I haven't accounted for. If you want me to look into a fix I prefer having the actual game save so I can look into the in game legends to investigate oddities.

This has always been my preference for viewing legends info...keep up the good work

Thanks, haven't done much development wise lately, but I recently found some tools that would let me drop the dependency on internet explorer which would allow me to not have to completely rewrite a lot of the interface to implement some ideas.

[Parker147]

Quick crash fix update.

[PeridexisErrant]

Quick crash fix update.

Cool, but could you also bump the version number for this kind of thing?  It's hard to keep track of what I've got in various packages otherwise. 

[Parker147]

Yeah, sorry, I'll try to get that sorted out. My versioning get messed up so I stopped messing with it til I get some things sorted out. I'll try to get it fixed on the next update.

[smjjames]

I'm getting an error and crash while looking at a particular war.

Spoiler: spoilered for length (click to show/hide)

Code: [Select]

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at LegendsViewer.Controls.HTMLControl.Dispose()
   at LegendsViewer.DwarfTabPage.NewPageControl(PageControl pageControl)
   at LegendsViewer.DwarfTabControl.Navigate(ControlOption control, Object navigateObject)
   at LegendsViewer.frmLegendsViewer.listSearch_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ListBox.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
LegendsViewer
    Assembly Version: 1.13.9.0
    Win32 Version: 1.13.09
    CodeBase: file:///C:/LegendsViewer/LegendsViewer.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34003 built by: FX45W81RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
SevenZipSharp
    Assembly Version: 0.64.3890.29348
    Win32 Version: 0.64.3890.29348
    CodeBase: file:///C:/LegendsViewer/SevenZipSharp.DLL
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.mshtml
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.0.3300.0
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.