Print

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

[mifki]

Updated to the new dfhack release. Not tested, sorry.

[Max™]

From a quick runaround in adventure mode on linux it is worth noting that the sliding tiles glitch didn't show up while traveling around and despite traveling/stopping in a forest retreat repeatedly it didn't crash, now if I could just figure out how to make it stop doing the am:0 am:5 am:0 am:26 spam in the terminal, looks promising though!

[mifki]

From a quick runaround in adventure mode on linux it is worth noting that the sliding tiles glitch didn't show up while traveling around and despite traveling/stopping in a forest retreat repeatedly it didn't crash, now if I could just figure out how to make it stop doing the am:0 am:5 am:0 am:26 spam in the terminal, looks promising though!

I didn't do anything related to this, so not sure if it's really that good, unfortunately.
am:... values were for you (players) to report them if a screen is rendered incorrectly, like the map isn't hidden where it should. Probably it's time to remove them.

[Max™]

Well, it definitely seemed more stable from poking at it earlier, and I would love if the am: values were just something you enable with a --debug flag or something, they drive me nuts as is, but yeah, the map and moving and overrides all looked good, I didn't try to break it zooming in and out yet but I'll try real quick and see what happens.

Edit: ok, the zooming can still give the broken text glitch, but it seems way more stable, I ran around in and out of travel mode, wandering through lots of different sites with folks running around, the sort of stuff I had to be leery of due to it crash, honestly if you disabled the am: reporting I'd be using it full-time instead of just in fort mode. So nice being able to walk into a mead hall or fortress storage room and tell what should be there at a glance again instead of having to scroll and check each square to look for the promising stuff.

[mifki]

Ok, I will disable these messages.

[Dirst]

Ok, I will disable these messages.

I would go with Max™'s suggestion and leave it as an option, and/or part of an exception handler if the plug-in knows it's in trouble.

[PeridexisErrant]

Bug report:  when viewing a screen in text mode, eg worldgen, item descrption, etc, 'reshape_graphics' is repeatedly printed to the console many times per second.  Windows, DFHack 40_24 r3, TwbT 5.44

[mifki]

Bug report:  when viewing a screen in text mode, eg worldgen, item descrption, etc, 'reshape_graphics' is repeatedly printed to the console many times per second.  Windows, DFHack 40_24 r3, TwbT 5.44

Isn't it because of some new screen refreshing plugin? It should print this when you resize window only. I will removing this debug message eventually, but it shouldn't be output repeatedly anyway.

[PeridexisErrant]

Ah, that's the culprit then. 

https://github.com/lethosor/dfhack-scripts/blob/master/autoresetgrid.lua

It would be good to hide debug output in what are functionally release builds, but that's not a bug.  Thanks for the explanation.

[lethosor]

Shouldn't that occur on every screen?

[mifki]

Ah, that's the culprit then. 

https://github.com/lethosor/dfhack-scripts/blob/master/autoresetgrid.lua

It would be good to hide debug output in what are functionally release builds, but that's not a bug.  Thanks for the explanation.

That script fixes some issues with TTF, doesn't it? And shouldn't be active in twbt mode then. Twbt will reallocate buffers and do something else every now and then which isn't food if it's not required.
I somewhat agree with you about debug messages but you see, otherwise we wouldn't know.

[lethosor]

The script resets the grid periodically (hence the name), which can address TTF issues as well as other flickering that can occur in all print modes.
I don't think printing debug messages to the console by default is necessary, but it could be enabled by the user. Why exactly is TwbT reallocating buffers if the screen size doesn't change, anyway?

[mifki]

Why exactly is TwbT reallocating buffers if the screen size doesn't change, anyway?

Because previously this method was called only when grid size actually changes, so there was no need to check. And btw, if the (vanilla) code did nothing in case of no actual changes, the script wouldn't work, you know. I'll check and optimize the code once I'm at home, and again, without the debug messages, we wouldn't know that's required.

[Antsan]

When calling quicksave from the ingame console the game freezes and saving doesn't happen.
I guess this is due to the game being paused by the message from the console, which cannot be closed as input is ignored.

[lethosor]

If you're referring to the command-prompt plugin, you have to dismiss it by pressing Esc for quicksave to work. (That's also not a TwbT issue, by the way.)