Print

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

[Lasitus]

0.40.22 works for me, but when updating to 0.40.23, I'm getting this:

Resetting textures
stonesense: Only PRINT_MODE:2D is supported on OS X
Plugin /Applications/Macnewbie/Dwarf Fortress/hack/plugins/stonesense.plug.dylib has failed to initialize properly.

Changing to 2D does start up, but is rubbish for the graphics packs, who mostly want PRINT_MODE:TWBT.  I see the error print in main.cpp for stonesense, but for some reason this is never hit for 0.40.22.

Note: Both versions are using what is currently in DFHack/df-structures/master with lethosor/df-structures/sidebar-modes-pr and DFHack/dfhack/develop with lethosor/dfhack/0.40.22-plugins

I realize this isn't a release, just reporting my findings and wondering if anyone has come across this error before on OSX using a graphics pack.

[lethosor]

That change to Stonesense was made back in 0.40.19, I believe, since danaris and I have both seen consistent crashes, system lockups, and kernel panics when using Stonesense when DF is using an OpenGL-enabled print mode (i.e. anything other than 2D, 2DSW, 2DASYNC, etc.). It's possible that Stonesense is failing to load entirely in 0.40.22, but there shouldn't be any difference between the two versions.

[Lasitus]

Hmm, CLA worked fine for me in the 0.40.19 release version of Macnewbie as well.  I didn't see an option in the dfhack.init to turn stonesense off or mention of that ability on the readme.  I don't use stonesense, so I would much rather have the graphics pack.  I tried "disable stonesense" and "stonesense disable" in dfhack.init, but it didn't work.

[mifki]

I don't quite understand what's your problem. Doesn't it start at all with PRINT_MODE other than 2D? That message about stonesense should be harmless, but if it somehow prevents the game from starting, you can just delete stonesense plugin file since you don't need it.

However, TWBT doesn't support 0.40.23 yet, so PRINT_MODE:TWBT will not work anyway at the moment.

[Lasitus]

That was it... TWBT must be the reason it didn't start.  I had assumed the reason for not starting was that print, since it was the last print before going down (and therefore only tried 2D and TWBT.)  I was thinking why error out of the game for something like that...  I changed it to standard, got the game to start in a reasonable view.  (2D seemed only playable on the ASCII tileset.)  The message still happened, but it started in standard mode.

Thanks for the help.

[fricy]

(2D seemed only playable on the ASCII tileset.)  The message still happened, but it started in standard mode.

Please elaborate. All packs are set up so they work best in twbt mode, but fall back to 2D mode if twbt is absent. If they don't work right I need to fix that.

The launcher loads the default print mode from data/init/init.txt, and keeps this setting if you load a different pack. In case you mixed 40.19 dfhack with 40.2x (as I understand?) this is a side effect... Twbt print_mode is only avaliable if the launcher detects the plugin, and the plugin needs to be recompiled for every version, using a new symbols.xml is not enough to make it work. To get rid of the print mode you can delete hack/plugins/twbt.plug.dylib.
BTW: make sure you don't use the keyboard layouts from .19 with .2x, they have changed significantly, the graphic packs should be ok, only minor changes there.

[lethosor]

(2D seemed only playable on the ASCII tileset.)  The message still happened, but it started in standard mode.

Please elaborate. All packs are set up so they work best in twbt mode, but fall back to 2D mode if twbt is absent. If they don't work right I need to fix that.

PRINT_MODE:TWBT should fall back to STANDARD, actually.

[milo christiansen]

And STANDARD has some weird bugs (for example pressing F11 will crash DF on my system).

It's really too bad DF doesn't have better graphics code.

[lethosor]

I find STANDARD to be fairly stable, actually. What version of SDL are you using?

[Lasitus]

(2D seemed only playable on the ASCII tileset.)  The message still happened, but it started in standard mode.

Please elaborate. All packs are set up so they work best in twbt mode, but fall back to 2D mode if twbt is absent. If they don't work right I need to fix that.

In 2D mode, the CLA and Phoebus pack (all I tried) started as a tiny fraction of the window and the rest was white.

The launcher loads the default print mode from data/init/init.txt, and keeps this setting if you load a different pack. In case you mixed 40.19 dfhack with 40.2x (as I understand?) this is a side effect... Twbt print_mode is only avaliable if the launcher detects the plugin, and the plugin needs to be recompiled for every version, using a new symbols.xml is not enough to make it work. To get rid of the print mode you can delete hack/plugins/twbt.plug.dylib.

Yes, I am running Macnewbie 40.19 with 40.23 dropped in and a dfhack and Dwarf Therapist compiled with updates for 0.40.23.  I don't mind selecting standard, but thanks for the tips.

BTW: make sure you don't use the keyboard layouts from .19 with .2x, they have changed significantly, the graphic packs should be ok, only minor changes there.

This is good to know, thanks.  So you are saying just don't select Macnewbie key bindings right?

[lethosor]

(2D seemed only playable on the ASCII tileset.)  The message still happened, but it started in standard mode.

Please elaborate. All packs are set up so they work best in twbt mode, but fall back to 2D mode if twbt is absent. If they don't work right I need to fix that.

In 2D mode, the CLA and Phoebus pack (all I tried) started as a tiny fraction of the window and the rest was white.

Oh, this is a known problem with retina displays.

[milo christiansen]

I find STANDARD to be fairly stable, actually. What version of SDL are you using?

Whatever came with the Windows version of DF (it may be a Windows only thing, and other OpenGL games work fine so it's probably not my graphics card).

Other than locking up when switching from windowed to full screen it works fine. (well, TWBT makes the whole screen go black when a DFHack GUI element is displayed unless I use the legacy mode, but that is probably not related?)

[lethosor]

Wait, switching to full screen crashes for you with PRINT_MODE:STANDARD but works with TwbT?

[fricy]

This is good to know, thanks.  So you are saying just don't select Macnewbie key bindings right?

Don't use any of the keybinds that are displayed in the launcher, customize the default that comes with 40.2x.

In 2D mode, the CLA and Phoebus pack (all I tried) started as a tiny fraction of the window and the rest was white.

Oh, this is a known problem with retina displays.

Thx lethosor for the explanation. In that case: Retina Display Manager (or whatever the name is) is included with the utilities.

Other than locking up when switching from windowed to full screen it works fine. (well, TWBT makes the whole screen go black when a DFHack GUI element is displayed unless I use the legacy mode, but that is probably not related?)

That sounds suspiciously like the SDL fullscreen bug. I thought that was a *nix problem only.
-Nope, there's a bug report already for windows too. And twbt shouldn't work in fullscreen if standard has problems...
Going black is a workaround that mifki uses to cover up some display artifacts: afaik twbt can't distinguish between the map and the dfhack text display, so everything would get displayed with the text font, which can be very ugly depending on the difference between the map and text tileset.

[milo christiansen]

It works fine in full-screen, but only if you start it full-screen and never change to windowed mode. Alt+Tab works fine, but F11 locks up (or more correctly it won't redraw).

STANDARD, TWBT, and TWBT_LEGACY all are exactly the same for me except the DFHack GUI problem with TWBT.