Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Pidgeot

Pages: [1] 2 3 ... 19
1
I've made some changes which should hopefully be enough to make this work with version 50.x (50.01-50.05 at time of writing; later versions may require more changes).

However, I don't have the ability to do a ton of testing right now, so I'd appreciate if adventurous people are willing to download and try it out. Feel free to test older versions too; they should still be working, but there's always the risk of subtle bugs popping up.

It should be compatible with the builds from Steam, but you will need to copy it into a folder structure like any other DF version, and there is no attempt to detect Steam itself or the version installed through that. Note that baselines are not available for 50.01-50.03, since these were Steam-only releases, which may impact some functionality; use 50.04 or later for best results.

The build can be downloaded from GitHub. It is Windows-only for now, since DF 50.x is itself Windows-only. This is a pre-release build. Please make sure you test thoroughly before including in any packs.

I would also like to hear suggestions and feedback on whether more interface changes are even relevant for 50.x. Now that there is a proper settings interface in DF itself, a lot of the options that used to be in the launcher may not make a whole lot of sense anymore. Indeed, PyLNP *itself* may not make a ton of sense anymore, especially not if most players are going to be using the Steam version from here on.

2
Yo, thanks for putting in like 9 years of dedication into maintaining this Pidgeot  8)
It Dwarfs my original run for sure (pun intended)

We never really talked except in a very short PM almost exactly 9 years ago... I feel guilty about not checking in!

Hello! And yeah, I guess it has been that long, hasn't it? Crazy how time flies...

Quote
I'm amused that my layout and graphic design have been pretty much maintained through it all. I still have the original asset files btw, though maybe the program could do with an icon update? Would people riot?

I've been tempted to jump in and make some sort of contribution again for the last number of years, let me know if you could use some help somehow...
I'm still not a professional programmer but I've learnt some Python and I still have my crappy photoshop design skills :P
For now... I'll say hi!

Hey, if it ain't broke...  :D

Help is always welcome if you want to jump in.

3
PyLNP 0.14d is released for Windows. This build fixes the DFHack issues introduced in the repacked version of 0.14c by repackaging with a different version of PyInstaller

I've increased the version number to make sure the documentation changes get associated with a proper version number, but there are no actual changes to the PyLNP code.

4
On Windows, there is no special handling of DFHack when launching - there should be no difference in how the application is launched compared with double-clicking, and the console window is completely controlled by DFHack, so it's something on their end that's going wrong.

Please file a bug report with them; I'm happy to change the launcher if there's something I'm overlooking, but this is not something I'm going to be able to investigate myself.

5
No worries! I mostly posted over there to make sure Peridexis sees it too. :)

6
DF General Discussion / Re: PeridexisErrant's DF Starter Pack
« on: October 07, 2022, 07:17:26 pm »
Why am I getting this error with the 0.47.05-r09 when running the Launcher? While the r08 version ran just fine? (Win7)

"The program can't start because api-ms-win-core-path-l1-1-0.dll is missing from your computer." and
"Error loading Python DLL 'c:\Users\[username]\AppData\Local\Temp\_MEI70642\python39.dll'. LoadLibrary: The specified module could not be found."

EDIT: Never noticed PyLNP 0.14a was 2 years old. No wonder it still work for my system.

I already touched on this in the PyLNP thread, but I'll do it here too for good measure:

I upgraded my computer between 0.14a and 0.14b, which meant I ended up on a newer version of Python - one that does not support Windows 7 or earlier.

I've replaced the 0.14c build with one made on slightly earlier version that supports Vista and 7. If you need it, you can download it from the GitHub releases page for PyLNP, but PeridexisErrant may also want to replace the version in the pack.

7
The Windows build of PyLNP 0.14c has been replaced.

0.14b and 0.14c were built with Python 3.9 on Windows, but unfortunately this means they are not compatible with anything older than Windows 8. That was not intentional.

I have replaced the Windows build of 0.14c with one made with Python 3.8, which should allow PyLNP to run on any Windows version starting with Vista; there are no other changes to the build. I recommend any pack maintainers manually replace this in their packages.

Any future version will use Python 3.8 by default.

8
Hm, looks like the Python version I'm using to build these days doesn't work with Windows 7. :\

Nothing that you can do on your end, unfortunately, except downloading the source code and Python yourself and running it that way. I'll look into getting it rebuilt with an older version that'll work, but it won't be before the weekend.

9
PyLNP 0.14c has been released and may be downloaded from the GitHub release page.

This fixes some issues with listbox coloring on a system running a dark theme (contributed by TV4Fun), and prevents an error message that was showing when closing the macOS version.

10
PyLNP 0.14b has been released and may be downloaded from the GitHub release page.

The main change is support for upcoming DFHack changes: the init files are moving from the root DF directory to a subfolder dfhack-config/init. See the associated GitHub issue for more details.

Special note for pack maintainers: Please note that the default PyLNP.json has changed! The DFHack history entry in the import section now references a new placeholder directory, `<dfhack_config>`. Make sure you update modified copies of this files as appropriate.

This also ensures mod installation creates any additional subdirectories it needs.

11
PyLNP 0.14a has been released and may be downloaded from the GitHub release page.

This fixes an issue when the program attempts to import text files from an old pack.

12
PyLNP 0.14 has been released and may be downloaded from the GitHub release page.

The main change here is an upgrade to Python 3 for the builds (specifically Python 3.6 on Linux and 3.7 on Windows and macOS).

This has required setting up entirely new build machines for Linux and macOS, and as such it *is* possible that something has changed that might cause compatibility issues that I have not noticed (as I am not a regular user of either of those operating systems). If you have issues running the latest version, please report them.

In addition to the Python upgrade, this release should improve terminal handling on Linux, and be a bit better about reporting crashes.

13
I've not been able to look at it for a couple of weeks now, but the current state is that I still need to get a Python 3-based build working for MacOS. Because switching to Python 3 is a very major change, I don't want to release until I know this is working for all OSes.

So far my attempts to make the build process work properly has required *far* more hacking that I'm comfortable including in a build process (which is saying a lot :P ). I have thought of some alternative ideas that I hope to try out over the weekend; as long as I can get one of them to work, a new release will follow immediately after.


14

  • With Python 2 approaching end-of-life, I'll be looking into moving all executables to be Python 3-based. The exact details here aren't finalized yet, so I can't say precisely which Python 3 version will be required - it depends on what I'm able to build executables with. Some time after that, the codebase will probably no longer target Python 2 support anymore - it'll probably stay working for a while, in case you want to run from source, but there won't be any guarantees. I'll post more details when I'm able.

This is still being looked at; I've finally managed to get Windows builds working with Python 3, but I still need to verify with the other operating systems. Hoping to get this fully sorted during Easter.

Let me know if I can help with any of this testing.  Mac is my main platform with VMs for windows and linux.  I've run and built PyLNP on all 3 with 3.8 and haven't come across any issues yet but I'm not sure what's needed for testing all the scenarios.

Generally speaking, builds are going to run fine on the same system that built them, but they don't necessarily run on *other* systems. For example, on Windows, you'll want to make sure it's bundling the VC runtime as necessary, but you won't see that problem on the build machine because it will already have the right runtime installed system-wide.

In the case of Linux, my main concern is to end up with executables that have the minimal possible requirements (e.g. minimal glibc version requirements, etc.). Due to the state of the specific VMs I was using, it's not been possible to re-use the existing ones for Python 3 builds, so I'm in the process of spinning up newer ones (...which takes a while, because I need to use Gentoo to achieve that).

For Mac, at the moment it's mainly making sure that I have a way to build it - my normal build VM no longer boots for some reason, so I need to get another one working first.

Some users are reporting crashes when trying to install a graphics pack. One said it fixed the problem when he tried running PyLNP from souce. It seemed like a kind of unusual thing. I think all the user might have Windows 10 in common, but there's definitely lots of Windows 10 users with no problems, so i dunno.

I don't have enough details to really make a good guess at the cause. If this is happening often I might need to build in extra debug output and hope to track it down that way, but first I need to have my build VMs working...

15
A progress update on things I mentioned in a previous post:
  • Bitbucket is removing support for Mercurial repositories in 2020. As PyLNP is using a Mercurial repository, this means it'll have to move. There is already a mirror on GitHub, so I expect to simply switch over to using that as the primary repository, but I have some backend processes that I will need to update first. I'll move over existing issue reports once I'm ready to make the switch.

This has now been fully completed, and as thurin correctly guessed, that involved copying the issues over. Unfortunately the issue IDs had to change, so references in commit messages etc. will no longer match up.

I have also just finished migrating all binaries over to the Github releases page, so they are archived there. All future releases will go here.

The Bitbucket repository is still around for now, and will still contain a mirror of GitHub, but issues and pull requests should not be made there. AFAIK, it will disappear completely on June 1.

  • With Python 2 approaching end-of-life, I'll be looking into moving all executables to be Python 3-based. The exact details here aren't finalized yet, so I can't say precisely which Python 3 version will be required - it depends on what I'm able to build executables with. Some time after that, the codebase will probably no longer target Python 2 support anymore - it'll probably stay working for a while, in case you want to run from source, but there won't be any guarantees. I'll post more details when I'm able.

This is still being looked at; I've finally managed to get Windows builds working with Python 3, but I still need to verify with the other operating systems. Hoping to get this fully sorted during Easter.

Pages: [1] 2 3 ... 19