Print

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

[Putnam]

Your antivirus is overzealous.

[Zanzetkuken The Great]

Your antivirus is overzealous.

It's webroot, so possibly.

[Dirst]

Your antivirus is overzealous.

It's webroot, so possibly.

This comes up fairly often with starter packs, at least on Windows.  Until enough users (of that particular antivirus) explicitly trust the executable, it gets treated as malware.  You can probably exclude-from-scan the parent directory of your DF folders.

[Pidgeot]

PyLNP 0.9.1 is now available. The main additions are improvements to the mods system, and DFFD integration for updates, both courtesy of PeridexisErrant.

I plan to contact DHL tomorrow, arranging to have my CPU shipped to Intel on Monday. I'll try to keep updated via my phone, but expect about a week of downtime on my part once we're past the weekend. I will not be able to make new builds until I receive my replacement CPU, so any urgent bugs requiring an immediate fix needs to be reported before early Sunday evening (UTC+1).

[Zanzetkuken The Great]

Your antivirus is overzealous.

It's webroot, so possibly.

This comes up fairly often with starter packs, at least on Windows.  Until enough users (of that particular antivirus) explicitly trust the executable, it gets treated as malware.  You can probably exclude-from-scan the parent directory of your DF folders.

Thing is, it's getting nuked right out the gate.  It maybe has only a few milliseconds before the Antivirus finds it and then deletes it.

[Pidgeot]

Your antivirus is overzealous.

It's webroot, so possibly.

This comes up fairly often with starter packs, at least on Windows.  Until enough users (of that particular antivirus) explicitly trust the executable, it gets treated as malware.  You can probably exclude-from-scan the parent directory of your DF folders.

Thing is, it's getting nuked right out the gate.  It maybe has only a few milliseconds before the Antivirus finds it and then deletes it.

I've never used Webroot, but I would expect a "disable" switch somewhere that you can use while extracting the pack, then add the file to the exclusion list before re-enabling it. Alternatively, you can probably change the default action taken when it encounters something it (falsely) believes is a threat

Personally, though, I'd probably find myself a different AV program.

[Pidgeot]

Turns out the Linux/OSX issue about encoding detection wasn't *actually* fixed, so I'm currently re-building those with a proper fix. They have been re-uploaded as 0.9.1a.

The Windows build is unaffected, so 0.9.1 is still the newest build for that OS.

[PeridexisErrant]

An important note for pack maintainers upgrading from an earlier version:  0.9.1 requires a few changes in auxiliary files.

1.  There are new fields in the updates dict of PyLNP.json - make sure you have them, even if blank.  The build can handle a broken json, but doesn't check that a valid file has all the required fields.

2.  The baselines spec has expanded slightly.  For best results, re-download baselines.

I'm also having some strange issues with installing graphics packs, which I think can be traced to the new code to update graphics on modded saves.  More on this soon, hopefully.

[Pidgeot]

I'm also having some strange issues with installing graphics packs, which I think can be traced to the new code to update graphics on modded saves.  More on this soon, hopefully.

This should be fixed with 0.9.2, which is now up.

EDIT: Binaries are pulled temporarily pending research of an issue fricy just found. Will upload them once we figure this out.

[Pidgeot]

It took a bit longer than I'd originally hoped, but 0.9.2 is up.

The main new feature is integration of PeridexisErrant's Legend Processor script, as well as several changes and fixes to the graphics and mod systems.

Also, a reminder: I expect to be without a CPU starting tomorrow, so further changes will be somewhat delayed.

[Bearskie]

Hope you dont mind me asking... I've downloaded your launcher, now what?

So far I've got the launcher to load graphics set by creating a folder called 'LNP' in Downloads, and chucking the graphics stuff into subfolder 'Graphics'.  But when I click Install Graphics, the launcher cant find df 0_40_24, which suggests to me that I'm putting my Dwarf Fortress folder in the wrong location (atm it's in Downloads too)... where should I put it then?

[PeridexisErrant]

Hope you dont mind me asking... I've downloaded your launcher, now what?

So far I've got the launcher to load graphics set by creating a folder called 'LNP' in Downloads, and chucking the graphics stuff into subfolder 'Graphics'.  But when I click Install Graphics, the launcher cant find df 0_40_24, which suggests to me that I'm putting my Dwarf Fortress folder in the wrong location (atm it's in Downloads too)... where should I put it then?

I would getting a complete pack from http://lazynewbpack.com - either to use or to have as an example to build your own. The readme also documents the setup in decent detail, under "customisation" (the last third).

[Pidgeot]

0.9.2a is up now with a small fix to pack simplification to make it work properly again. Nothing major, but pack authors probably want to re-simplify before releasing a pack, to cut down on disk consumption.

Hope you dont mind me asking... I've downloaded your launcher, now what?

So far I've got the launcher to load graphics set by creating a folder called 'LNP' in Downloads, and chucking the graphics stuff into subfolder 'Graphics'.  But when I click Install Graphics, the launcher cant find df 0_40_24, which suggests to me that I'm putting my Dwarf Fortress folder in the wrong location (atm it's in Downloads too)... where should I put it then?

As PeridexisErrant also suggested, if you want to set up your own installation, I recommend using an existing pack as a base, or using the readme as a reference, especially the "Directory structure" section. If you still need help after that, feel free to post more specific questions, but from a general perspective, I'm going to have to point to the readme, because it'd get a bit too long to repeat here.

[PeridexisErrant]

0.9.2a is up now with a small fix to pack simplification to make it work properly again. Nothing major, but pack authors probably want to re-simplify before releasing a pack, to cut down on disk consumption.

Before compression, the reduced raw format cut 31 MB (after old simplification) to 14.8 MB for all seven graphics packs.  For mods, which don't have the images, this ratio could be a lot better in many cases.  It's a significant if not massive decrease in filesize to distribute, which means faster downloads.

[Pidgeot]

New CPU arrived this morning, and I inmediately installed it.

Just before 11 AM, it crashed again.

I tried turning off the same two features once again... and it crashed again an hout ago.

One thing I have not tried so far was *replacing* my RAM - I've tried each stick individually, without any luck, but I didn't try replacing it. I've ordered some new RAM which I hope will arrive tomorrow, and then I will just have to hope this finally fixes it - the problem seems to happen during I/O, so maybe this isn't something MemTest could catch... but if that also doesn't work, all that's left is the case and a Blu-ray drive...