Print

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

[Parker147]

13.05 Release

Changes

• Utilizes remaining historical figure XML data. Includes entity reputations, related sites, related entities, skills and artifacts held.
• Filled in the historical figure link event so it displays marriages, apprenticeships, imprisonments etc in the log.
• Auto map resizing.
• Added artifacts to the advanced search.
• Added checkboxes for quickly searching for vampires and werebeast historical figures.
• Improved and fixed a minor issue with the file selection.

[Intrinsic]

Sweet!

[Quietust]

I've just done a bit of work mapping out all of the various history_event structures for use in DFHack - with this information, it may become a possibility for a tool like this to gather its history information directly from Dwarf Fortress (using the DFHack RPC socket API) instead of from an XML dump, allowing it to get at even more information (possibly even from an active fortress).

[Parker147]

I would definitely be interested in getting the info from DFHack rather than the XML dump. Just by looking at some of the history data structure off the github page I am seeing data that doesn't exist in the XML that would be great to have. I will have to look into it more if I get the time to see if I can help out any.

[EmeraldWind]

Ran into an error on a modded save. It is using the Rise of the Mushroom Kingdom mod and was genned in 34.09.

Save is here: http://dffd.wimbli.com/file.php?id=6531

Code: [Select]

Active Interaction already exists.
   at LegendsViewer.Legends.HistoricalFigure..ctor(List`1 properties, World world)
   at LegendsViewer.Legends.XMLParser.AddFromXMLSection(Section section, List`1 properties)
   at LegendsViewer.Legends.XMLParser.AddItemToWorld(List`1 properties)
   at LegendsViewer.Legends.XMLParser.ParseSection()
   at LegendsViewer.Legends.XMLParser.Parse()
   at LegendsViewer.Legends.World..ctor(String xmlFile, String historyFile, String sitesAndPopulationsFile, String mapFile)
   at LegendsViewer.FileLoader.load_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

[Parker147]

Here is 13.06 with a fix for that. Thanks for reporting the crash.

[tyrannus007]

So how is the DFHack integration going?

[Rose]

Nevermind, thought this was the therapist thread.

[Parker147]

So how is the DFHack integration going?

I haven't looked into it any yet, unfortunately. I don't really have any idea when I will get around to it either, as much as I want to. I've been looking into creating graphs for related historical figures and think I found some tools that will make it easy to do. There is just some overhead material that I need to learn first to make it happen.

[EmeraldWind]

So how is the DFHack integration going?

I haven't looked into it any yet, unfortunately. I don't really have any idea when I will get around to it either, as much as I want to. I've been looking into creating graphs for related historical figures and think I found some tools that will make it easy to do. There is just some overhead material that I need to learn first to make it happen.

Although, instead of integrating directly with DFHack you could have someone write a plug-in that exports the data and then make Legends Viewer support the history export file as well as the official XML, but that could also take a long while.

[noushi]

I've run into the following error with my large world generated in 0.34.11, using v1.13.06:

Code: [Select]

Related Entity Error: Kubuk Boltroared
   at LegendsViewer.Legends.World.ProcessHFtoEntityLinks()
   at LegendsViewer.Legends.World..ctor(String xmlFile, String historyFile, String sitesAndPopulationsFile, String mapFile)
   at LegendsViewer.FileLoader.load_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

The XML is ~1.8GB, and at first I wondered if it was hitting the 2GB memory limit, but it only gets up to about 1.6GB resident before dumping.  I've tried exporting a couple times.  Let me know if an attachment would be helpful.

[Parker147]

Here is a fix for that hopefully.

Although, instead of integrating directly with DFHack you could have someone write a plug-in that exports the data and then make Legends Viewer support the history export file as well as the official XML, but that could also take a long while.

Something like that might be the way to go. Though, I would prefer to read the data directly into my program that way I could just save all the data to a binary file, which would probably be smaller and faster to load. I'm not sure how difficult it is to tie in with DFHack, but the XML export utility might also make the data easier to access for other developers that want to use it too. I probably wouldn't support that official XML once I can get the data from DFHack. I think it might be a little difficult to juggle reading from both.

[noushi]

Here is a fix for that hopefully.

Fixed indeed.  I salute you, sir!

[EmeraldWind]

Here is a fix for that hopefully.

Although, instead of integrating directly with DFHack you could have someone write a plug-in that exports the data and then make Legends Viewer support the history export file as well as the official XML, but that could also take a long while.

Something like that might be the way to go. Though, I would prefer to read the data directly into my program that way I could just save all the data to a binary file, which would probably be smaller and faster to load. I'm not sure how difficult it is to tie in with DFHack, but the XML export utility might also make the data easier to access for other developers that want to use it too. I probably wouldn't support that official XML once I can get the data from DFHack. I think it might be a little difficult to juggle reading from both.

You wouldn't necessarily need to export it as XML either. If you came up with your own reliable format, you could use it and maybe put up the parsing functions for other people that may want to use the data for something else. Whichever is the best solution. I only thought of it because Overseer uses an export of the map instead of reading directly from the game which has benefits like not sharing RAM and CPU with DF and you can run it when you are not running DF.

[Pozzo]

Hello!

Just got this error, after trying to look at a world I just retired an adventurer in. Partially modded game.

Spoiler (click to show/hide)

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.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ListBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.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.269 (RTMGDR.030319-2600)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
LegendsViewer
    Assembly Version: 1.13.7.0
    Win32 Version: 1.13.07
    CodeBase: file:///C:/Users/Alex/Desktop/Dwarf%20Fortress/Legends%20Viewer/LegendsViewer.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.278 built by: RTMGDR
    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.282 built by: RTMGDR
    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.269 built by: RTMGDR
    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.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    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.