Are there some useful keyboard macros I could make use of in this game?

[EbonHawk]

Just got a macro-enabled Logitech G710+ mechanical keyboard a few days ago and I'm loving it. What I want to know though, is the software that comes with it downloaded a "The Witcher 3" profile to use with it. I can't for the life of me figure out anything about what this profile is supposed to do, other than it lists a bunch of game-specific commands to use. I was thinking a profile would give me access to some ready-made macros.

I can't find anything in the documentation online about what the game Profiles are supposed to do. It goes through a bunch of steps on how to create macros but doesn't get into how to set them up for specific games.

Has anyone used macros with The Witcher 3 and would like to share their insight on this? After playing around with different macros for a few days now, I'm at a loss as to what I could get out of them that would be useful. Is that all a Profile for a game does is just give you the ability to access certain functions in the game? If so, I think that's kind of a letdown, if you ask me.

Potions like Swallow and Tawny Oil don't stack, so I'm not sure how a macro would help with the healing process, so that seems like it's out. Combat is so quirky, wail-y that I don't see how a macro could help. I haven't really come across anything in the game that would benefit from a macro really. I was kinda hoping someone had come up with some that were useful, or just handy or fun really. Something I might've missed.

I experimented with an early macro recording utility many years ago so I know a little bit about setting them up. I've already got several that will come in very handy with the mIRC program I use quite a bit. Makes some of the repetitive stuff a lot easier.

[EbonHawk]

Alright, so none then. Good to know.

I'll just stick to building macros to try and make the rest of Windows more efficient then. G'day, gents.

[Nerd]

I have the exact same keyboard and was using non delay macros for the debug console menu for taking screenshots etc.
Sadly though... CDPR messed up the AHK scripts in 1.07 so you can no longer use non delay macros.
Which kind of makes macros useless now. Not sure what else you could use macros for in TW3 though.

[Ivar]

Explain macros please. I've got a Corsair mechanical KB and I want to use the softawre to be able to quick cast with signs, but bloody hell it's hard to figure out.

[Nerd]

Originally posted by Ivar:

Explain macros please. I've got a Corsair mechanical KB and I want to use the softawre to be able to quick cast with signs, but bloody hell it's hard to figure out.

Sounds like you want to do a non delay multi key macro. If thats the case, you can't with TW3 as macros now need a delay until they fix it that is. I think its 0.20 second delay, don't quote me on that though.

[EbonHawk]

Originally posted by Ivar:

Explain macros please. I've got a Corsair mechanical KB and I want to use the softawre to be able to quick cast with signs, but bloody hell it's hard to figure out.

What's the difference between quick casting signs and whatever the "normal" is?

[Ivar]

Originally posted by EbonHawk:

Originally posted by Ivar:

Explain macros please. I've got a Corsair mechanical KB and I want to use the softawre to be able to quick cast with signs, but bloody hell it's hard to figure out.

What's the difference between quick casting signs and whatever the "normal" is?

To simply cast with a hot key without having to select the sign first. You could do it with the last two games but not this one. There's a mod on Nexus that enables it but it's a static setup.

[Ivar]

Originally posted by MrPixel:

Originally posted by Ivar:

Explain macros please. I've got a Corsair mechanical KB and I want to use the softawre to be able to quick cast with signs, but bloody hell it's hard to figure out.

Sounds like you want to do a non delay multi key macro. If thats the case, you can't with TW3 as macros now need a delay until they fix it that is. I think its 0.20 second delay, don't quote me on that though.

Well ♥♥♥♥. I hate not having hotkeys for signs. Thanks for the info.

[EbonHawk]

Macros work for me for quick casting, but hitting macro keys (the ones situated vertically along the left edge of the keyboard isn't very intuitive for casting signs during fast-paced combat).

Might try mapping them to the F-keys on the top row of my kb. Those would make more sense to me.

Setting the macro to record the number needed (5 for Igni, for example), then pressing the Cast Sign key (Q) and saving the macro works fine. You do have to tweak the delays though, so setting the thing to record the delays as you press them gives you some numbers to edit. Just input 25ms (for 0.025s) for each of the delays works fine as far I can tell.

[Nerd]

Originally posted by EbonHawk:

Macros work for me for quick casting, but hitting macro keys (the ones situated vertically along the left edge of the keyboard isn't very intuitive for casting signs during fast-paced combat).

Might try mapping them to the F-keys on the top row of my kb. Those would make more sense to me.

Setting the macro to record the number needed (5 for Igni, for example), then pressing the Cast Sign key (Q) and saving the macro works fine. You do have to tweak the delays though, so setting the thing to record the delays as you press them gives you some numbers to edit. Just input 25ms (for 0.025s) for each of the delays works fine as far I can tell.

If you use AHK script, its more or less instantanious as it only requires a 0.20 sec delay for the whole script to run. For example:

dlghide
dlgshow
testunpause
testpause

is a 0.20second delay which hides the HUD & freezes the game within 0.20. Makes for taking screens easier. Hopefully when 1.08 comes along, AHK will not require a delay again.

[EbonHawk]

Originally posted by MrPixel:

Originally posted by EbonHawk:

Macros work for me for quick casting, but hitting macro keys (the ones situated vertically along the left edge of the keyboard isn't very intuitive for casting signs during fast-paced combat).

Might try mapping them to the F-keys on the top row of my kb. Those would make more sense to me.

Setting the macro to record the number needed (5 for Igni, for example), then pressing the Cast Sign key (Q) and saving the macro works fine. You do have to tweak the delays though, so setting the thing to record the delays as you press them gives you some numbers to edit. Just input 25ms (for 0.025s) for each of the delays works fine as far I can tell.

If you use AHK script, its more or less instantanious as it only requires a 0.20 sec delay for the whole script to run. For example:

dlghide
dlgshow
testunpause
testpause

is a 0.20second delay which hides the HUD & freezes the game within 0.20. Makes for taking screens easier. Hopefully when 1.08 comes along, AHK will not require a delay again.

I thought you had to use a command like 'sleep 20' to get it to delay AHK like you're talking about. Has that changed?

I might give AHK a shot since it sounds like it's even more powerful than Logitech's macro software, which is kinda limited if you can't bind "macros" to any key you want. It would be MUCH MUCH more useful to be able to just keep the default keys for the signs and make them auto-cast like this!

Here's the code I found in case anyone else is interested:

This would be for Yrden

*4:: 
send {4} 
sleep 50 
send {Q} 
return

this for Igni

*5:: 
send {5} 
sleep 50 
send {Q} 
return

Someone at gog.com's forums suggested 50ms because they had had issues using anything around 25 or lower on rare occasions, so 50ms was their personal cutoff point.

[EbonHawk]

The links are broken at AutoHotkey.org, and I can't get AutoHotkey.exe to install, it just runs instead and says "AutoHotkey.ahk" script not found. It never "installs".

I created an AutoHotkey.ahk text/script file but it refuses to work in Witcher 3. I think it is truly broken at this point, unless I'm just missing something obvious.

The macro (quick-key) scripts I create work just fine in notepad and in npp just fine, the proper letters are displayed correctly, but they just won't work in W3.