Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Aklidien

Pages: [1]
1
This download fixes it for 42.06, are you using it?

Using Virtualbox is fine, if your hardware is good enough. gcc, lisp tool and even visual studio will not notice that they are in virtualised environment.

A lot of things changed in structures. Hopefully figured out all critical changes. It will not blowup immediatly, but cant guarantee it will not corrupt save later. Make backups. Report if it happened.
Save it as Dwarf-Therapist-WIN-36.0.0/share/memory_layouts/windows/v0.42.06_graphics.ini:
Spoiler: v0.42.06 windows (click to show/hide)

In my case path was /usr/local/share/dwarftherapist/memory_layouts/linux/v042.06.ini
Spoiler: v0.42.06 linux (click to show/hide)

Thank you so much for this, sv-esk and Blue_Dwarf! As a very new player, I was having quite a bit of anxiety without DT (especially when >50 dwarves). The Windows memory layout works like a charm, and it's up and running again.

I just have a few questions to get my bearings regarding DT:
   • I read earlier in the thread that DT is reliant on DFHack updating their memory layouts. If that is the case, how were you able to pull this code together before the DFHack devs?
   • Does this code need more thorough testing before Splinterz is willing to post it as the v37.0 download? If so, is there a structured process that people go through to help Splinterz test?
   • PeridexisErrant posted earlier that https://dfhack.readthedocs.org/en/latest/library/xml/how-to-update.html is how the utility devs update their memory layouts / programs for each new Dwarf Fortress release. Is the whole process best left to them, or is there any portion of it that non-devs can help out with?

Pages: [1]