Bay 12 Games Forum

New Release 1.20.06b!

Download here!

Source!

Changelog:
1.20.06b
# Hotfix

* supporting a changed data type of the newest DFHack that caused crashes in Legends Viewer


I'm getting the *EXACT* same issue as Lemel.

I downloaded 1.20.06, and the issue persists.

I've had the issue happen using both the native export function in DF and using DFHack.

I did get one export to load when I did it immediately after world gen but before starting a fortress. But later, when I had an active fortress, I used DFHack's open-legends to export, and got the LV error.

I uploaded both the working export and the one causing the error to DFFD here: https://dffd.bay12games.com/file.php?id=15275

I'm hoping there's a fix for this -- I love Legends Viewer and would really like to use it again!

Again, I'm not reposting the error text because Lemel already did that, and it's exactly the same.

Thanks for posting! It is not the exact same issue, only related and results in the same error message.
Looks like one more property that got changed by DFHack from a number to a text.

Here is the hotfix release that should hopefully get rid of the last of these issues. 

New Release 1.20.05!

Download here!

Source!

Changelog:
# Compatiblity with DFHack 0.47.04-r2 + updates to events

### Added information
- added new 'historical event relationship' event
- added new 'historical event relationship supplements' information
- added type of moutain peak
- added evilness and local force to regions
- added profession to secret identities
- added summary to entity page

### Enhancements
- updated 'itemstolen' event
- updated 'body abused' event
- updated 'assume identity' event
- various smaller event updates

### Bugfixes
- compatibility with changed property export of DFHack 0.47.04-r2 #55
- added TitleRaceString and changed the ObjectListView to show the name of Race rather than the name of the object - THX @JakeTrans
- fixed a crash that could happen when there was no information about the new leader in the "new_site_leader" event due to hf culling

**Note:**
Use 'exportlegends info' or 'exportlegends all' of [DFHack](https://github.com/DFHack/dfhack/releases) to get lots and lots more info and less UNKNOWN data. The new legends_plus.xml features require [DFHack](https://github.com/DFHack/dfhack/releases) which is usually included in the Lazy Newb Pack for exporting the additional XML file!

I could load various test saves without problems, hopefully I got the majority of compatiblity issues with the new DFHack version.
If there are still crashes during loading or other bugs, please let me know here or on the Github Issues Page and include versions of DF and DFHack as well as the exported files or the save game.

Thanks all for bringing this to my attention.

I already fixed a few things so that LegendsViewer is once again compatible with DFHack 0.47.04-r2.
While I am at it, I want to update some event texts and other stuff to use more of the new information DFHack provides by now.
I will try to release a new version this week.

Is it possible for Legends Viewer to get any of the new religion data?
Right now, each civ has its gods listed, and on the civs and entities tab I can get a list of religions in the world, but there's no link between them (that I can see).
Listing the associated religions with the gods and mentioning the gods on the religion info screens would be a good start.

Also, more advanced, there is crossover of religions between civs now. Is there any data available for how much influence religions have in each civ?
In modded games where you have a civ with no native gods especially, they pick up a bunch of religions from other civs. Would be nice to get an overview of the gods my migrants are likely to be worshiping.

From what I know from poking at Legends Browser, that would require extending legends_plus.xml, the regular legends.xml barely has anything on entities (hueristics, that is, automated guesswork, needs to be done to identify a lot of entity related stuff with vanilla legends.).

Yeah, therahedwig is absolutely right. I looked into the code and I already have some "automated guesswork"  in place.

The temple structure had at some point the information of the worshipped deity and the religion that occupied it, so a connection was possible in some cases. But in all worlds I created with the new DF version, none of these properties "deity" or "worship_hfid" where in the "structure" nodes of the legends_plus.xml.

Generally okay, but.....anyone else discovered major problems in the Advanced Search UI? When you search by Race, the drop down and results are full of

Code: [Select]

LegendsViewer.Legends.CreatureInfo
rather than racial designations.

(the code section handtyped because copy pasting doesn't work at all, for some reason)

The code of the advanced search feature is nearly untouched since I took over the project, five years ago. It needs a bigger overhaul that I don't want to put in a small minor version release.
I currently don't have a lot of time, so bigger features have to wait, sorry!
I'll try to tackle some smaller urgent issues like the wrong race string for the next version.

So I made a very old, very large world with a 2 gig xml file.  It takes a solid 10 minutes to load into the viewer, but after that everything tends to work... except for civilizations.  I can't view larger civilizations (like, say, my current fort's civilization) at all.  Looking in task manager, it's eating up like 3600 megs of RAM for like 20 minutes before it stops using much RAM at all, but it doesn't load anything, just keeps a blank screen.
Anything I can do to fix it?  I wanna make statues commemorating my civilization's great deeds and conflicts.

Sadly, I think this is because of the sheer amount of events and is nothing that can be easily fixed.
But I think as a workaround you could open the "Civ and entities" Tab and there go to the "Events" Tab, click on "Deselect All"


Now you should be able to open the pages of the civilization. You can then selectively enable various event types to display their entries in the event log, but do not enable all events at the same time.

A heads up: Yesterday the df.history.xml file was changed in a way that causes Legends Viewer to reject the plus file: The history event "hist_figure_wounded" field "part_lost" was changed from an integer to a boolean, and it appears the parser doesn't like when it's not a numeric value, but rather the text "true"/"false".

I verified the cause by changing the script (locally) to omit that field, and that change causes the tool to accept the file.

Thanks, I updated the parser so it can handle integers and booleans for this property. Will be in the next version.

Thanks for trying. I've zipped up the files here: https://www.dropbox.com/s/80taz9tl6dz108o/DF_47_04.zip?dl=0. The files were produced using my version of exportlegends.lua, which I believe is the current one.

Edit:
An amusing entry (from the same export) :Look at Zan Gulfcloistered DF Legends Mode has the relations reversed...

Thanks, the problem were not the vague relationships but printing the race of culled unimportant historical figures in the nodes of family trees.
I don't use advanced world gen in my test worlds and therefore have never set [CULL_HISTORICAL_FIGURES:1]. There is often missing information in such worlds that lead to bugs. 

Haha, still have to look into the problem of the duck that became the owner of that dwarf. 

Quote from: Conor891 on March 08, 2020, 05:28:42 pm

Newest version doesn't seem to be working.

Loading the xml file in gives a popup saying "There was an error loading this XML file! Do you wish to attempt a repair?"


Selecting yes gives a Microsoft .NET Framework Exception: https://pastebin.com/5eTxq3EQ


If you select continue the program does nothing and never loads the legends file.

The XML files I used along with my world gen parameters can be found here if you need them: http://dffd.bay12games.com/file.php?id=14913

There was a bug in some recent DFHack builds, where exportlegends produced invalid XML data. It looks like it's been fixed already, so it should work if you try a newer build.

Yeah, I debugged with @Conor891 files, and it is exactly this error:
<historical_event>
<id>1161</id>
<type>body_abused</type>
<bodies>359</bodies>
<bodies>363</bodies>
<bodies>365</bodies>
<bodies>366</bodies>
<bodies>469</bodies>
<bodies>471</bodies>
<bodies>476</bodies>
<bodies>617</bodies>
<bodies>648</bodies>
<civ>83</civ>
<histfig>-1</histfig>
<site>118</site>
<abuse_type>1</abuse_type>
        --> <abuse_data><history_event_body_abusedst.T_abuse_data: 0000024565093F40></abuse_data>
</historical_event>