Print

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

[0ink3r]

Im still having problems getting my logitech mouse profile for DF to load up with LNP. If i set the profile to persistent in the logitech software, the profile then works within DF perfectly. Unfortunately this is not a great solution as it then locks and uses this same profile in everything in windows from thereon in.

I downloaded and ran the vanilla DF with the very same profile pointed at the Dwarf Fortress.exe in that folder and it had no issue whatsoever with recognizing and attaching the profile to that.

So...

It seems to me that perhaps dfhack (or something else) is running as some sort of overlay which takes precedence over any executable i have tried to attach this profile to, though i cant for the life of me find it. I have tried attaching the profile to every .exe within the LNP folder (aside from the ones in the utilities subfolder) these include:

dfhack-run.exe
binpatch.exe
Starter Pack Launcher (PyLNP).exe
Dwarf Fortress.exe
optipng.exe

Still no work...

I then used comodo killswitch to see if it was hooking into anything which was no so apparent and found DF hooking into C:\Windows\System32\conhost.exe it was a long stretch, but i was running out of ideas, so i also tried including this, but still no joy.

Im all out of ideas, does anyone know why the profile is not loading with LNP, or perhaps what file i should be getting the profile to attach to ?

(ill add that i had no problems with the profile loading with "Dwarf Fortress 40_13 Starter Pack r5" it just seems to be these newer ones)

[terko]

You got owned by Toady, again. Starter Pack .16 out, .17 released. I really think someone is really evil here!

[Sebastian2203]

You got owned by Toady, again. Starter Pack .16 out, .17 released. I really think someone is really evil here!

Might be Toady trying to prove that he is always step ahead and no one can rival him?
Not really.

[Pidgeot]

Im still having problems getting my logitech mouse profile for DF to load up with LNP. If i set the profile to persistent in the logitech software, the profile then works within DF perfectly. Unfortunately this is not a great solution as it then locks and uses this same profile in everything in windows from thereon in.

The right executable is indeed Dwarf Fortress.exe - that's the one PyLNP launches.

Since I have a G510 keyboard, let me just check if I can reproduce...

Spoiler: Profile window (click to show/hide)

*clicks Play Dwarf Fortress in launcher*

Profile Activated
Dwarf Fortress 0.40.16

...nope, works perfectly here.

Are you sure you've picked the right Dwarf Fortress.exe? The profile window only shows the filename, but it checks the full path, so you need to add new executable paths manually.

[0ink3r]

Yep, i am definitely pointing it to the Dwarf Fortress.exe in the correct folder. Just for completeness's sake i just tried deleting the profile and creating a fresh one from scratch, still does not work.

Its strange that it works with the older version of LNP and vanilla DF but just not these newer ones ??

edit: FYI, I'm pretty sure the logitech profiler checks the binary of the linked exe anyway, because if you replace the exe in the folder, the link in the profile it was attached to will disappear, forcing you to re-link it to the newer replacement exe file anyway.

Also, ill add that i am using the latest setpoint software from logitech.

[Pidgeot]

Also, ill add that i am using the latest setpoint software from logitech.

Ah, well, I'm referring to the Logitech Gaming Software (the G510 is a gaming keyboard, after all). That one only looks at the path (there's no other information in the profile).

I can't say anything about SetPoint; that's for "ordinary" mice, and I don't have one

[0ink3r]

G700 is a 'gaming mouse'

[Pidgeot]

G700 is a 'gaming mouse'

It is, but this is the first time you said anything about using that particular model, or indeed any sort of gaming mouse (you've only mentioned using a Logitech mouse).

Anyway, for gaming mice, you ought to be using Logitech Gaming Software - and if you are, then I don't understand why you're mentioning SetPoint.

If you are indeed using LGS and you simply misspoke (fair enough), I would suggest checking the XML configuration used by LGS (right-click the profile and select Export), and there you can see the exact path it's looking for. You can then compare it with the one shown when you right-click the Dwarf Fortress process in Task Manager and select Properties.

The point is, there is nothing in PyLNP, the Starter Pack, DFHack, or DF itself which interferes with this; I'm pretty sure they *can't*.

[Probe1]

Heads up

When I launch Starter Pack Launcher (PyLNP).exe (40_16_r1) it pops up and says there is a new version available (version 42_16_r2).  The download link takes me
to 40_16_r1). 

[Laggy]

There is something odd with 40.16 r1. When downloaded and started it claims there is an r2 version available, but when accepting to download it brings up the r1 download page. Downloading again still claims there is an update. The archive claims the version it contains is r2, so I suspect whatever checks latest version vs starting version does a string check and find an r2 posted somewhere, but an r1 internally, leading to a constant claim a new version exists.
And everyone is eager to get their hot little mitts on the very latest version of this very useful pack!

Disregard, the version string on dffd has not been updated properly, there's no r2. Yet.
I expect it to be fixed once Perx takes a look here.

Yep, this is exactly the problem.  I wrote the version checking code that notifies you when there's a new version for download, but the only reasonable way to do it was to pull the "New Version" information directly from DFFD.  Since there is the typo on DFFD, then the notification will always pop up

[PeridexisErrant]

There is something odd with 40.16 r1. When downloaded and started it claims there is an r2 version available, but when accepting to download it brings up the r1 download page. Downloading again still claims there is an update. The archive claims the version it contains is r2, so I suspect whatever checks latest version vs starting version does a string check and find an r2 posted somewhere, but an r1 internally, leading to a constant claim a new version exists.
And everyone is eager to get their hot little mitts on the very latest version of this very useful pack!

Disregard, the version string on dffd has not been updated properly, there's no r2. Yet.
I expect it to be fixed once Perx takes a look here.

PE could bump the version number in the pack, and everything would fix itself.  And some future archeologist is going to beat his head against the wall trying to figure out where the improvement was that justified a new version number.

Or I could just fix the version number on DFFD, which I just did.  Sorry everyone!  (and it would be changelogged, ofc)

You got owned by Toady, again. Starter Pack .16 out, .17 released. I really think someone is really evil here!

Might be Toady trying to prove that he is always step ahead and no one can rival him?
Not really.

We'll probably skip 40.17 entirely, since .18 fixes a critical bug.

I made a couple Consolas font tilesets for TWBT, in case anyone wants to try a modern monospaced font. I think it looks great.

Thx, added as text_16x20 and text_18x22.

Yay!  I'm currently finalising a pull request for the PyLNP, the (relevant, it's a big one) result of which will be the images for the graphics pack, vanilla DF, and the Tilesets folder all get added.  Useful for TwbT and anything else where you want an image in every graphics pack.

[0ink3r]

G700 is a 'gaming mouse'

It is, but this is the first time you said anything about using that particular model, or indeed any sort of gaming mouse (you've only mentioned using a Logitech mouse).

Anyway, for gaming mice, you ought to be using Logitech Gaming Software - and if you are, then I don't understand why you're mentioning SetPoint.

If you are indeed using LGS and you simply misspoke (fair enough), I would suggest checking the XML configuration used by LGS (right-click the profile and select Export), and there you can see the exact path it's looking for. You can then compare it with the one shown when you right-click the Dwarf Fortress process in Task Manager and select Properties.

The point is, there is nothing in PyLNP, the Starter Pack, DFHack, or DF itself which interferes with this; I'm pretty sure they *can't*.

Setpoint/LGS... Same thing, different era... Semantics... Anyway NVM...

I finally managed to get the profile to work, i tried extracting LNP to the default folder of 'Dwarf Fortress 40_16 Starter Pack r1' and the profile now loads up with the Dwarf Fortress.exe file as it should. No idea why this folder works and the previous folder of 'Dwarf Fortress' does not. Even when using the same profile on each of the installs...

Thanks for your help though, seems that .18 has just been dropped on us anyway =]

[mndfreeze]

hey what happened to the scripts make_legendary and elevate_physical?  I understand why the elevate_mental went away when the big switcharoo happened but not sure why these others just dissapeared this version?  Also armoks_blessing and at least one more that I cant remember the name off the top of my head.  All were related to raising/adjusting physical or mental stats or the level of a skill like mining or woodcutting.

[lethosor]

Those are Vjek's scripts. I'm not sure if they work with recent versions of DFHack or not, but you're welcome to test them.

Also, PeridexisErrant: The versions of some of my scripts you're bundling are out-of-date (particularly load-screen and settings-manager). I'm not sure how best to inform you of updates, other than watching the repo, but I've seen a few reports of problems with load-screen that I've fixed.

[mndfreeze]

Those are Vjek's scripts. I'm not sure if they work with recent versions of DFHack or not, but you're welcome to test them.

Also, PeridexisErrant: The versions of some of my scripts you're bundling are out-of-date (particularly load-screen and settings-manager). I'm not sure how best to inform you of updates, other than watching the repo, but I've seen a few reports of problems with load-screen that I've fixed.

Thanks for the info and link.  I know they all worked or mostly worked (I can't say I've used every possible variable and option with all of them) in .14. 

I thought that since they dissapeared maybe they were just redundant and there was some other script included that did the same sort of things but I don't see a one, so I'll just install these back in manually.  Thanks!