616
Utilities and 3rd Party Applications / Re: Dwarf Therapist (Maintained Branch) v.37.0 | DF 42.06
« on: March 16, 2017, 01:19:28 pm »
Maybe I'm just confused, is there a link here to a 43.05 64x version of DT?
March 6, 2024: Dwarf Fortress 50.12 has been released.
News: February 3, 2024: The February '24 Report is up.
News: February 4, 2021: Dwarf Fortress Talk #28 has been posted.
News: November 21, 2018: A new Threetoe story has been posted.
Forum Guidelines

Hello, below I'll be giving my thoughts and impressions on how the current versions plays, including bugs and odd things I've noticed. They will go in order of least serious to most.
There's a bizarre bug where if you enable the snake people in the fortress defense mod, you will only get snake men visitors to your fort. I tested this by disabling them and getting new visitors from nearly all the civilizations, including mod races.
Javelins are still impractical to use. Meph, if you're reading this I noticed you tried to change things up, making it so that you can now build javelin ammo out of something other than steel. However, I'm still limited on what I can make them out of (no cobalt, for example). Altogether it just hasn't been worth the trouble of building the special furnace and using bronze for training and iron for combat, as I did in the one fort where I used them for military forces. One huge problem I want to stress is the lack of reactions for javelin ammo in the craftshops, so no bone or wood javelins to train with.
Stal's Armory Pack seems to be broken in that the armors do not show up even when I mark the green check. I turned on the other large arms & armor pack included in the launcher and its armor sets work fine. Nice implementation, by the way. I especially love the detail where you can couple bevors with sallets. Very immersive and gives a lot of decision making space when equipping troops.
Elves don't bring a guy with their traders who has a catalog like the humans and dwarves. I think this is a vanilla bug but I remember it being fixed in an earlier version of masterwork. Can it be fixed again? I want to mail-order giant rattlesnakes again!
I don't believe the FPS boosters mod is working (the one where junk decays). I did switch off the food one, because it didn't make sense to have food rot away after it's been cured and whatnot, but also because I can save my FPS perfectly well by just turning off "Prepare Lavish Meal." Corpses just aren't disappearing, and neither are old tattered clothes. I did check the green marks for these things BEFORE worldgen by the way.
Invasions seem to be much rarer than I remember. I've not had a fort that's been exciting at all in terms of invasions. My last fort had one undead siege in the first year with two squads of zombie frogmen, but nothing after that for the next two years, or thieves either. The fort before it took three years before the first siege of one squad of white tiger men, by which point I had a bunch of steel clad stormtroopers. I am taking the usual worldgen measures to get high invasions (high civ counts, pop counts, etc.).
I have to be very careful about what MDF launcher settings I use, namely the tilesets. Phoebus seems to be the most stable. I tried Meph's and it crashed me on worldgen 100% of my attempts. Also, trying to use the multi z-level viewing, though extremely useful and immersive, is asking to crash. Strangely, I couldn't get Advanced Paramaters worlds to load for embark, and then only about half the generic ones I generated would load to the embark screen.
I have random FPS cascades. The worst one took me from about 130 FPS and 21 dwarves in a first year fort down to 55 FPS when nothing special seemed to be going on. It has kept on happening since. Sometimes it goes on and on until the game crashes and sometimes it goes back to normal. This is the most serious difference I've noticed with the latest version. It's a game killer, big time. This one is so bad I think I'll just be going back to the last version, which I've still got on my PC. Not sure if it's MDF or a vanilla problem I'm just noticing in MDF, but if anyone else is experiencing this please post it to help the community learn more about it.
Some more details about the fort this happened in: It has steep cliffs, a population always below 80, a medium animal population (<110), a single-floor layout, lots of trees, unbreached caverns, and only one invasion in the past that I camped out during. No running water either, and the cascades happened after my cistern was finished. The last cascade that made me give up happened while I had 78 population and I suddenly just went down to 15 and this went on for about a game month before it crashed.
I also don't think it's my PC. It's ran 150+ pop forts much bigger than the one detailed above at >30 FPS, for 5+ game years in older versions, and I haven't been experiencing performance degradation with any of the other (many) games I play.
I hope this helps the mod devs out find and fix small quality of life problems. Sometimes I wish the frustrating kinks would be focused down first before new stuff like new races is focused.
There are some heavy problems in _latest_ version. Sum of my feedback:Sounds like the same problem everyone has when operating current version of MWDF. current bugfix run LAA from the dwarf launcher. fixes it for just about everyone. I use it. I can generate 1000 year old worlds large size with 20 civs and 10-15 races, etc. without it I crash just like you, and I have an ancient system too.
OS: win7 x64 8gb RAM
1. ctd when generating world or at world saving if
a) more than 4-6 races activated
b) more then medium world size, and small civs and location places
c) if history longness is "too much", earlest ctd was on 26th year but with few races, civs and locations at medium worldsize it is possible to generate 250 year history but not much more.
2. when I load my saved game it is roughtly 30% chance of ctdyep another sign that you aren't using LAA. But if you do have a video card check to see if you have play.tv... for some that caused a lot of issues.
3. when I resize window _AFTER_ saved game is loaded I always have an instant ctd
4. there is also a most frustrating random ctd on game savingDF in the first place is unstable, and the more you add in the higher chance you will crash during high end operations, such as game saves.
5. If I run DF from launcher for second time in a row I always see a gamebraking grafic promlems from distortion mentioned just above to complete absence of grafic titles. So I have to rerun launcher after exiting DF.yeah DF does not like you to have 2 games running simultaneous especially versions with as many things added in as MWDF.
The game is written old school, it doesn't care how much memory you have.
All of that is NOT a '2gb memory' problem because of
a) large excess of memory
b) x64 systemwe are running the 32x version of DF, it doesn't care if your system is 64x.
c) all executables are memory adress patchedso you actually used LAA on all the executables? you only have to do that for dwarffortress.exe
d) when I monitor memory usage DF never run above 1.8gb even just before ctd.and if it ever showed you higher than that then I would assume your system had a massive fail-safe error as it is suppose to shutdown apps that exceed their set limits, before they exceed them. in other words windows will never tell you when it makes the leap to 2gb, as it would get shutdown prior to that by windows.
And I obtain a strong personal opinion that appeared critical error is somewhere in the launcher, but it is only an opinion.the MWDF launcher really doesn't do much of anything other then switch tags in the raws and move graphic files back and forth from the graphic folders to the MW graphic repository folder. Most likely the primary source of memory issues is the 32x32 graphics sets. I hate to say it, but it was the primary thing added in the last 2 versions and we have had these major issues since then... switching to smaller sets wont matter as all the sprites were updated to the 32x32 graphic sets. the game handles almost all the graphics in house not out on a video card, causing massive cpu loads and memory loads. it doesn't take much for that to spike it over the 2GB mark. an arriving caravan, a new batch of critters, a raid, saving, loading, etc. will cause spikes. if it spikes for even 1 tick, windows will freeze and shut it down.