Print

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

[mifki]

Only happens with twbt mode.

But if tileset specified in init.txt is missing, game won't start without twbt as well, or where was the mistake?

[fricy]

Only happens with twbt mode.

But if tileset specified in init.txt is missing, game won't start without twbt as well, or where was the mistake?

Then there's a bug: the FONT and the FULLFONT entries had the typo, and the game just froze - according to the console it happened during twbt (5.28) initialization.

[mifki]

Only happens with twbt mode.

But if tileset specified in init.txt is missing, game won't start without twbt as well, or where was the mistake?

Then there's a bug: the FONT and the FULLFONT entries had the typo, and the game just froze - according to the console it happened during twbt (5.28) initialization.

Yes, but without twbt it would display message box and close anyway.
DF itself displays message box and quits if can't load tileset, for some reason message box hangs when loading tileset from twbt. I'll add some logging but I can only close the game in this case.

[fricy]

Yes, but without twbt it would display message box and close anyway.
DF itself displays message box and quits if can't load tileset, for some reason message box hangs when loading tileset from twbt. I'll add some logging but I can only close the game in this case.

Thx, that'd be helpful.

[HaterSkater]

fricy, i found another issue. It's about grim fortress.
lightrow proposed d_init change — [SKY:250:0:0:2]
d_init of grim fortress in your graphic pack contains lines

Code: [Select]

#[SKY:178:3:0:0]
[SKY:250:0:0:2]but by unknown reason, after installation sky colour reverts back to default 178:3:0:0.
However, it works ok, if commented line is deleted

And also, in his tileset VARIED_GROUND_TILES was set to "no"
upd: oh, i see, PyLNP takes control over this setting

[Pidgeot]

fricy, i found another issue. It's about grim fortress.
lightrow proposed d_init change — [SKY:250:0:0:2]
d_init of grim fortress in your graphic pack contains lines

Code: [Select]

#[SKY:178:3:0:0]
[SKY:250:0:0:2]but by unknown reason, after installation sky colour reverts back to default 178:3:0:0.
However, it works ok, if commented line is deleted

Yeah, PyLNP considers everything between [ and ] to be a tag; there's no special comment syntax right now (other than anything OUTSIDE [ and ]).

It also assumes only one instance of a field name, so it sees the first one before the second one and uses that. It doesn't parse the full file like DF would (at least, not yet...)

[HaterSkater]

fricy, i found another issue. It's about grim fortress.
lightrow proposed d_init change — [SKY:250:0:0:2]
d_init of grim fortress in your graphic pack contains lines

Code: [Select]

#[SKY:178:3:0:0]
[SKY:250:0:0:2]but by unknown reason, after installation sky colour reverts back to default 178:3:0:0.
However, it works ok, if commented line is deleted

Yeah, PyLNP considers everything between [ and ] to be a tag; there's no special comment syntax right now (other than anything OUTSIDE [ and ]).

It also assumes only one instance of a field name, so it sees the first one before the second one and uses that. It doesn't parse the full file like DF would (at least, not yet...)

Interesting. I had thought it just replaces whole file instead of catching tags

[lethosor]

fricy, i found another issue. It's about grim fortress.
lightrow proposed d_init change — [SKY:250:0:0:2]
d_init of grim fortress in your graphic pack contains lines

Code: [Select]

#[SKY:178:3:0:0]
[SKY:250:0:0:2]but by unknown reason, after installation sky colour reverts back to default 178:3:0:0.
However, it works ok, if commented line is deleted

And also, in his tileset VARIED_GROUND_TILES was set to "no"
upd: oh, i see, PyLNP takes control over this setting

I'm not sure if DF would treat that as a comment - an alternative I've seen is replacing "[" and "]" with "(" and ")"

[Pidgeot]

Yeah, PyLNP considers everything between [ and ] to be a tag; there's no special comment syntax right now (other than anything OUTSIDE [ and ]).

It also assumes only one instance of a field name, so it sees the first one before the second one and uses that. It doesn't parse the full file like DF would (at least, not yet...)

Interesting. I had thought it just replaces whole file instead of catching tags

That's what's different about PyLNP compared to the former launchers, and that's what allows it to preserve all the other settings like volume and population cap

[Badger Storm]

I've got the previous version's LNP: Is there a way to "update" it, or do I need to drag my save files out, download this entire pack, put them back into the "new" instance of DF 40.14, and nuke the old stuff from orbit?

[fricy]

/snip
do I need to drag my save files out, download this entire pack, put them back into the "new" instance of DF 40.14, and nuke the old stuff from orbit?

Pretty much, saves are stored in the "User Generated Content".

fricy, i found another issue. It's about grim fortress.
lightrow proposed d_init change — [SKY:250:0:0:2]
d_init of grim fortress in your graphic pack contains lines

Code: [Select]

#[SKY:178:3:0:0]
[SKY:250:0:0:2]but by unknown reason, after installation sky colour reverts back to default 178:3:0:0.
However, it works ok, if commented line is deleted

Once again thx for your help. I'll go check if this affects other packs as well.

[HaterSkater]

Not sure, should i post it here, or in Pidgeot's thread, but anyway. I've already told to dwarf_reform, that 2 of his colour schemes have missing values in them. But what is more important — suddenly i've found that LNP won't load again if said "broken" colorscheme was installed.

Steps to reproduce:
— launch LNP
— load "azure nightmare" or "western rust"
— close LNP
— try to launch it again (now to fix it you need to install working colorscheme in df/data/init manually)


Oh, and thanks for including my sepia

[fricy]

Download MacNewbie 0.9.12 from DFFD
Download MacNewbie 0.9.12 from Dropbox

Spoiler: Macnewbie changelog: (click to show/hide)

version 0.9.12 - for 0.40.15 – Nov. 09, 2014
-df 40.15
-dfhack_40.15-r1
-PyLNP 0.7.a80250a nightly
-IXen's launcher removed
-twbt 5.31
-Wanderlust tileset
-colorblind color profiles
-update to reedit embarks
-misc. bug fixes as usual

Spoiler: DF 0.40.15 Release notes (click to show/hide)

Here's another release with bug fixes and small changes to brighten your day.

Major bug fixes
   (*) Made growing trees update cave-in and light information properly
   (*) Handled stress counter timing properly in adv mode
   (*) Stopped nerve check from bypassing broken parts between thought center and body roots
   (*) Stopped part from being pulped if inner nervous tissue is not detached
   (*) Made pulped parts bleed properly
   (*) Stopped crash from trying to place unit in proper connected component of crowded retired fort
   (*) Fixed reversed inside/outside check for outdoor refuse hauling

Other bug fixes/tweaks
   (*) Animals that can escape from cages no longer brought by traders
   (*) Made reactions try to guess how their containers will be filled to stop problems with brewing large stacks etc.
   (*) Small coin stacks can no longer be stuffed into non-containers
   (*) Small coin stacks no longer pass through opponents
   (*) Stopped tantrum dwarves from checking burrows for fistfights
   (*) Changed tantrum action frequency
   (*) Being in an owned site makes bogeyman not an issue
   (*) Made ballista arrow heads and ballista arrows have edges
   (*) Added ability to trade everything in the depot from either column
   (*) Made column widths even in trade view and abbreviated strings differently
   (*) Added select visible and select category to bring-to-depot menu
   (*) Added totems to crafts tab of bring-to-depot screen
   (*) Added a few categories to the kitchen menu
   (*) Alphabetized stone and kitchen menus
   (*) Added magma-safe indicator to stone menu
   (*) Made encrust jobs respect furniture tools
   (*) Cannot go into specific encrust menus if selected gem not available for encrust
   (*) Dead dwarves removed from burrow count
   (*) Made toggle button update properly when moving unit labor view to non-laborer
   (*) Fixed a problem causing the right edge of the embark world map to disappear, including the cursor
   (*) Fixed location of cursor in minimap for resized windows
   (*) Made DOES_NOT_EXIST exclude creatures from certain lists properly
   (*) Stopped stress reactions from being applied to unintelligent critters
   (*) Stopped stress reactions of hidden creatures from being announced
   (*) Fixed many typos (Gorobay)
   (*) Updated description for pulping so it doesn't say "bruised" etc.
   (*) Fixed broken artifact thought text
   (*) Stopped immortality goal from having a broken display in thoughts
   (*) Properly recognized multiple embark minecarts of the same material
   (*) Slowed down tantrum/mood/etc. indicators
   (*) Stopped zombies from interrupting your sleep to ask if they can help you with something
   (*) Increased default embark points to compensate for more default equipment (stepladder etc.)
   (*) Allowed deletion of first uniform
   (*) Stopped crafts brought by traders from satisfying craft mandates
   (*) Made weather init option clear up weather properly instead of just turning off the global simulation

@HaterSkater: Thanks for the help, I saw something is off, but couldn't figure out what's wrong. Fixed for now.
@Pidgeot: I'm pretty impressed, that the color window in the launcher can tell and show which color scheme a graphic set installs. Nice touch.

[Pidgeot]

@HaterSkater: I'll make sure PyLNP handles broken coloschemes more gracefully.

@Pidgeot: I'm pretty impressed, that the color window in the launcher can tell and show which color scheme a graphic set installs. Nice touch.

Uh, it doesn't do that. It will show the currently installed colorscheme in the preview if you haven't selected anything, but that's only read when the program starts.

I suppose it would probably be a good idea to do that, though... I'll make a note to get that done, shouldn't be too hard.

[fricy]

Uh, it doesn't do that. It will show the currently installed colorscheme in the preview if you haven't selected anything, but that's only read when the program starts.
I suppose it would probably be a good idea to do that, though... I'll make a note to get that done, shouldn't be too hard.

Actually it recognizes and highlights which color scheme is installed by the tileset if that color scheme is in the list of the colors. I noticed this by accident, but it does work.