Print

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

[prototype2001]

So in a txt file in the DF Starter Pack folder - probably dfhack.init - are lines that enable unit_transparency and workshop_transparency. If you find them and change the 1s to 0s it will disable those options again. (Or you can remove those lines or comment them out by adding a # to the start of the line.)

Or there may be an option in the LNP, I don't know.

DFHack is a team effort, but Lethosor is indeed a vital pillar of the DF community.

I checked the ini couldn't find anything about transparency. Thanks for the help, setting unit the transperancy to 0 fixed my crashes, otherwise the game was completely unplayable. I can now run a fort into a FPS death rather then a ragequit of installing 100z pumpstacks followed by a crash.

[lethosor]

I checked the ini couldn't find anything about transparency.

Make sure you're looking for files with an "init" extension, not "ini". Also, it's possible that a different .init file was running the command - maybe "onLoad.init", "onLoadMap.init", or "dfhack-something.init". It's not particularly easy to track down where a command was run from, unfortunately, but any files with a .init extension in your DF folder (or possibly your world folder) could run commands on startup or when a world loads. (I checked https://github.com/PeridexisErrant/starter-pack but I'm not seeing a file that runs this command there.)

This is all entirely informational if you've fixed the issue on your end, of course - but hopefully it helps track down any similar issues in the future.

[Nilsolm]

I think it's the tilesets that set those settings. The files would be called something like onLoad_gfx_[tileset].init in data/raw.

[lethosor]

I think it's the tilesets that set those settings. The files would be called something like onLoad_gfx_[tileset].init in data/raw.

Turns out this is, in fact, documented here (I forgot that this was added)! I suspect one of the data/save/*/raw paths there is what you're referring to. Those would definitely be another good place to check for .init files. (There is a good chance that this pack puts them in the top-level "raw" or "raw/objects" folder when you install a graphics set - DFHack ignores them there, but they would be copied to the data/save/*/raw folder when creating a world using that graphics set.)

[PeridexisErrant]

The Starter Pack has updated to 0.47.05-r01!
As usual, you can download the starter pack here.

This is the first pack with DF 47.05 - a sweet bugfix release!  The starter pack also has updates for DFHack, TwbT, and Therapist to support it, of course.  Remember that you can copy your saves to the new version, and/or keep running multiple versions of DF from separate folders - so there's no reason at all to delay updating... strike the earth!

0.47.05-r01
 - updated Dwarf Fortress
 - updated DFHack to 0.47.05-beta1
 - updated TwbT to 0.47.05-beta1 (unofficial build by thurin)
 - updated Dwarf Therapist to v41.2.1

SHA256:  6660d219d355025f9e2cdf5c85a33f53d43e074cfcf718a0f911f221dc8aeb4b

If you want to say thanks, check out Toady's Patreon, or even mine! 

Spoiler: Full contents (click to show/hide)

Contents:

Core:
 - Dwarf Fortress 0.47.05
 - PyLNP 0.14a

DFHack 0.47.05-beta1:  (includes Stonesense)
 - TwbT 0.47.05-beta1

Utilities:
 - Announcement Window v1.3.0
 - Armok Vision v0.21.0
 - DF Story Maker 1.0
 - Dorven Realms R1
 - Dwarf Mockup 1.2.0
 - Dwarf Portrait v2.1.0
 - Dwarf Therapist v41.2.1
 - Isoworld 2.1
 - Legends Browser 1.19.2
 - Legends Viewer 1.20.06c
 - PerfectWorld 1.9
 - Picturefort 2.1
 - Quickfort 2.1.0
 - SoundCenSe 1.4.4
 - Soundsense 2016-1
 - Soundsense RS v1.5.1-travis
 - World Viewer 2.5.0

Graphics:
 - ASCII
 - CLA
 - DungeonSet
 - GemSet
 - Ironhand
 - Mayday
 - Obsidian
 - Phoebus
 - Spacefox
 - Vettlingr


Recent changelogs:

0.47.05-r01
 - updated Dwarf Fortress
 - updated DFHack to 0.47.05-beta1
 - updated TwbT to 0.47.05-beta1 (unofficial build by thurin)
 - updated Dwarf Therapist to v41.2.1

0.47.04-r12
 - updated DFHack to 0.47.04-r05
 - updated TwbT to 0.47.04-r5 (unofficial build by thurin)

0.47.04-r11
 - updated DFHack to 0.47.04-r04
 - updated TwbT to 0.47.04-r4 (unofficial build by thurin)

0.47.04-r10
 - updated Dwarf Therapist to v41.2.0
 - updated Legends Viewer to 1.20.06c with many crash fixes
 - removed Meph tileset due to many crash reports :-/

0.47.04-r09
 - updated DFHack to 0.47.04-r03
 - updated TwbT to 0.47.04-r3 (unofficial build by thurin)
 - updated Legends Viewer to v1.20.06

Older changelogs can be found in ./LNP/about/changelog.txt

[sheepish_gorilla]

Just in time for the weekend

[orius]

I'm getting a crash on embark when I load up or save an embark profile.  I don't know if it's DFHack or something else.  It's not SoundSense, I tested with and without it.  Running the Windows version.

[clinodev]

I'm getting a crash on embark when I load up or save an embark profile.  I don't know if it's DFHack or something else.  It's not SoundSense, I tested with and without it.  Running the Windows version.

The most common crash on embark I'm aware of is caused by the TWBT plugin. You can get around it by setting the print mode to STANDARD in either the launcher or init.txt until you've actually embarked (with the dwarves and wagon on the ground,) then save, quit, and turn TWBT back on. The crash only seems to happen on the first embark for any given world, so you can then play on as normal. I strongly suspect this is your problem.

The second most common cause of "Pack weirdness" is trying to play from a compressed copy of the Pack or Dwarf Fortress, which must always be fully extracted before use. I only mention this because you mentioned embark profiles, and not being able to save embark profiles is one of many "mysterious" results from playing from a compressed "PeridexisErrant's Starter Pack 0.47.05-r01.zip" file, for instance.

[Galnart]

I hope that the latest update works better than the one i had from months ago. I constantly got corrupt save files.
BTW how long has DFHack been in beta? i don't remember seeing the beta message on the last version i had

[lethosor]

DFHack support for 0.47.05 is in beta. It goes through this stage for most new DF releases.

If you do come across issues, please report them here so that other people know about them and can try to diagnose them.

[orius]

I'm getting a crash on embark when I load up or save an embark profile.  I don't know if it's DFHack or something else.  It's not SoundSense, I tested with and without it.  Running the Windows version.

The most common crash on embark I'm aware of is caused by the TWBT plugin. You can get around it by setting the print mode to STANDARD in either the launcher or init.txt until you've actually embarked (with the dwarves and wagon on the ground,) then save, quit, and turn TWBT back on. The crash only seems to happen on the first embark for any given world, so you can then play on as normal. I strongly suspect this is your problem.

The second most common cause of "Pack weirdness" is trying to play from a compressed copy of the Pack or Dwarf Fortress, which must always be fully extracted before use. I only mention this because you mentioned embark profiles, and not being able to save embark profiles is one of many "mysterious" results from playing from a compressed "PeridexisErrant's Starter Pack 0.47.05-r01.zip" file, for instance.

I'll try that then.  I don't run the LNP frpm a zip file anyway, so it's not that.

[BeardedShrimp]

When I downloaded and extracted the Starter Pack, Windows Security detected a Trojan inside the Dwarf Mockup utility.

[orius]

I'm getting a crash on embark when I load up or save an embark profile.  I don't know if it's DFHack or something else.  It's not SoundSense, I tested with and without it.  Running the Windows version.

The most common crash on embark I'm aware of is caused by the TWBT plugin. You can get around it by setting the print mode to STANDARD in either the launcher or init.txt until you've actually embarked (with the dwarves and wagon on the ground,) then save, quit, and turn TWBT back on. The crash only seems to happen on the first embark for any given world, so you can then play on as normal. I strongly suspect this is your problem.

The second most common cause of "Pack weirdness" is trying to play from a compressed copy of the Pack or Dwarf Fortress, which must always be fully extracted before use. I only mention this because you mentioned embark profiles, and not being able to save embark profiles is one of many "mysterious" results from playing from a compressed "PeridexisErrant's Starter Pack 0.47.05-r01.zip" file, for instance.

I'll try that then.  I don't run the LNP frpm a zip file anyway, so it's not that.

Okay, that worked.  I think maybe I'll handle this by creating a trash fort that I have no real interest in playing when starting a new world, and just retiring it on embark.

[Ziusudra]

When I downloaded and extracted the Starter Pack, Windows Security detected a Trojan inside the Dwarf Mockup utility.

False positive - https://www.reddit.com/r/dwarffortress/comments/krkb3z/fyi_skeeya_trojan_was_found_in_dwarfmockup/

[lethosor]

Okay, that worked.  I think maybe I'll handle this by creating a trash fort that I have no real interest in playing when starting a new world, and just retiring it on embark.

I don't think your approach would work, unfortunately, but you could try. My interpretation of clinodev's comment is that the transition from the world view to the fortress view is what causes TWBT to crash sometimes. TWBT only deals with tile display - it doesn't care about world history, e.g. how many times you have embarked in a world.