test2 and test3 both fail to return the the proper location.
The skill is cast where my cursor is when I press it (or at itās range) and I donāt see the cursor moving at all with that version.
Hmmm, I just downloaded it and tested with this config and it worked in-game for me.
Does it work in Windows with the following config for you?
With title_match_mode=2 you need to put any string that is contained in the name of the window.
Even single letter should work if itās contained in the window name. (not sure if you can make it work on Desktop this way)
[general]
game_window_id=Notepad
title_match_mode=2
[center casts]
cast1=a:1
another idea, maybe itās so fast you donāt see it? And the skill is from native A press?
Then test this in Grim Dawn in game:
[center casts]
cast1=a:1,1,1,1
delay1=1000
I thought it was a normal GDAutoCaster program, so I was just testing it by adding that bit of config (as c:2) to my regular config. I see now that it is actually another test program, sorry.
Okay, with just your simple 2 line config, in game, I can see my cursor jump to my other monitor, jump back to where it was (not centered) and cast. With the longer script in Notepad The cursor jumps to the other monitor, then jumps back, but is invisible (Iām guessing that is an oddity due to Notepad) and reappears when I move it. It is back in the original location.
Okay, I used the 2nd config in while in Notepad. It makes my cursor disappear, but when I then move it slightly, it reappears.
edit- Just to clarify, GD and Notepad were both on my secondary (not main) monitor when I was testing.
no, no, itās GDAutocaster. When itās called GDAutocaster it GDAutocaster
I just wondered if it works in Windows when itās doesnāt seem to work in Grim Dawn.
Iāll prepare some special version of GDAutocaster for you that will log something again
It was working very oddly when in GDAutocaster, sort of like the cursor was bouncing back and forth between the monitors even when not pressing the ācenter castsā key, but I didnāt investigate it further, just restored my previous version.
Can you test the following version of GDAutocaster?:https://mega.nz/file/xNlCFIbR#Acbt1SjiMx77wIW7Y4AyEIlJopmBmazEDv1UeLdNRQE
-
turn off current GDAutocaster.exe just to be sure (although newer instance should replace older?)
-
in Main Menu of the game (of course needs 3s to load up)
-
but press A only when cursor is in about the centre of the screen because Iād like to log coordinates to the file
- at least at the beginning so that I know what are the center coordinates on your monitor
-
and later tell me coordinates from the GDAutocaster.log
-
with this super simple config
[center casts]
cast1=a:1
I got 1-2 things to try still
- Btw Iād like you to test in Main Menu for know because weāre only interested in cursor movement and position now, not whether the skills are cast or not
I think this was pretty close to the center, on my charās forehead on the loading screen : xpos=-1172 ypos=626
edit- I wasnāt sure that one was right, retrying with a new invocation of the program gave: xpos=-1172 ypos=626xpos=-1182 ypos=621
I think it just appended the 2nd set of coordinates to the 1st set.
Negative coordinates thatās new, didnāt think itās possible.
Anyway, Iāll prepare the last version to test with 2 configs
Either it will work with on of them (or some improvement) or Iām dropping this (or at least long break )
Actually just one config.
>> Download GDAutocaster! <<
Please redownload and try this config:
[center casts]
center=-1172,626
cast1=a:1
That almost worked right, it was a little high and a little to the right. I played a bit with the coordinates and the following seemed to be centered (or at least close enough that to my eyes it was centered):
[center casts]
center=-1200,775
cast1=c:2
edit - I suspect my ācenterā in the tests was off. Inside the game center is right on my charās feet and so it is easy to see.
Ok. If you later want, I can add off_center to this
Because Normaly I donāt cast in the center but just a little bit off
and the direction of this off is relative to your initial cursor position.
This is so that you donāt changee orientation.
Because if your character if facing upward
and you cast something in the middle then it will usually change the direction your character is facing.
Or mayble Iāll do it right now (make off_center work with center override), change the documentatioon etc.
Sounds awesome. I know youāve been working on this problem for a very long time and I appreciate it.
-edit- Here I am editing again. lol.
Testing in game, My character isnāt turning when Iām pressing ācā no matter which direction Iām facing.
The power Iām using is Inquisitor Seal.
edit 2 - Iām not using the moving camera stuff.
>> Download GDAutocaster! <<
Ok. Added .With off_center1 option if you circle with coursor aroudn middle of the screen
the cursor will be clicking in a small circle around the true middle of the screen.
I recommend you to use it (no global off_center as of now):
[center casts]
center=-1172,626
cast1=a:1
off_center1=true
Now Iāll read your post.
[edit] Ah, so itās not an error. You actually saying it works.
I added global off_center
This should work now
[center casts]
center=-1172,626
off_center=true
cast1=a:1
Btw betterr way
Just saying that I didnāt seem to need Off_center, since the center cast wasnāt making my character turn. It does still seem like a good thing to have. Iāll test the new version and function shortly. Non-gaming stuff is keeping me somewhat busy right now.
Sure. I also use it to have Inquisitor Seal a bit further so that it works on enemies more not only me.
Although as of know the distance is not configurable.
This should work now
[center casts]
center=-1172,626
off_center=true
cast1=a:1
Aye tqFan!
Kindly refresh my memory.
I want to configure something that hides the loot when Iām attacking then shows it when I move. Looks like it should be configured on mouse buttons.
Thank you as always
Hereās a general config. It works well imo and I use it personally while playing.
[hide items]
hiding_buttons=RButton
ingame_hide_button=RAlt
hide_duration=2000
Algorithm is as follows
- when you press one of hiding buttons the state of loot being shown is changed to hidden
- after hide_duration thereās a check if youāre still holding a button
- if so the state is prolonged
- if not, the state is changed back to the starting one (shown)
hiding_buttons can be more buttons, i.e.
hiding_buttons=RButton,A,Space
ingame hide button is from Grim Dawn keybinding
be prepared to use it manually occasionally to fix initial state of items being hidden, I have in on Alt / LAlt too (secondary keybinding)
because it rarely happen, i.e. to to changing locations, that the beginning state might be hidden incorrectly instead of shown
experiment with hide_duration=2000
2 or 3 seconds should be good
unless you hold button continously while fighting than maybe 1 second?
longer means more waiting time after releasing buttons till loots comes up but fewer switched depending on your button press frequency
shorter means possibly more messages about loot shown / which can crate a very long message queue Grim Dawn can show long after battle is finished (thatās why 1s is too short)
Of course I always recommend redownloading the program.