Console Video Setting Macros not working

[crowdx]

Hi all,
so I watched Mrai video on the setting up ISBoxer to swap screen and adjust video settings and for some reason I cannot get it to work. I have pasted the macro's below and I have tried just adding a key bind to the key map and it still does not work. When I add the macro's below into a regular in game macro they also seem to work.
Any help would be greatly appreciated.
Patrick McC

HIGH SETTINGS
/console graphicsviewdistance 8
/console graphicsGroundClutter 10
/console graphicsParticleDensity 5
/console graphicsSSAO 5
/console renderscale 1
/console MSAAQuality 1



LOW SETTINGS
/console graphicsviewdistance 2
/console graphicsEnvironmentDetail 2
/console graphicsGroundClutter 2
/console graphicsParticleDensity 1
/console graphicsSSAO 1
/console renderscale .3
/console MSAAQuality 0

[MiRai]

I have tried just adding a key bind to the key map and it still does not work. When I add the macro's below into a regular in game macro

Are the game clients already running when you're doing this? If so, you need to /reload the UI in every window to refresh the ISBoxer add-on. Otherwise, if you want us to look at your profile, then you're going to need to share it.


Also, this...

/console MSAAQuality 1

...is not the command to enable Multisampling. Assuming you want 2X, then it's 1,0.

[WOWBOX40]

Also make sure the isboxer addon is enabled ingame.

[crowdx]

So I have updated my macro and still no joy. I attached my setup file.
Patrick McCabe

[MiRai]

So I have updated my macro and still no joy. I attached my setup file.

First, I just want to say that, when sharing your profile, it's a lot simpler for someone to look at it if you use a paste site, as outlined in the directions on the ISBoxer Wiki.

With that said, you've assigned these macros to F23 and F24, but I'm going to bet that your keyboard doesn't actually have those physical keys on it, and therefore it's not working because of that. So, my suggestion would be to use a key that is actually available on your keyboard, and that will likely fix the issue.

If it doesn't fix the issue, then I will also point out that only your "Monks" Character Set is assigned to use the "SlotSwap" Mapped Key, and if you're testing from a different set, they aren't currently set up to utilize that particular Mapped Key.

[crowdx]

Apologies for sharing the file incorrectly.
So it does seem changing the keybind from F23 and F24 solved the issue of the macro not working. The only issue that remains is that the Jamba Master macro does not seem to be firing off correctly, as not all of my toons start to follow once I swap slots and break follow.
Any thoughts on that piece?
Thanks again for the help.
Patrick McC

[mbox_bob]

There is no specific reason for it not to work. Maybe have it as the first action in the list, and the cvars on self last. The game might not be processing the results of the JambaMaster mapped key while all that other stuff is going on, and changing the order around in the slotswap mapped key may give it a millisecond or two to do something about it.

You could also try changing your CPU Strategy to "Select all CPUs with every window ......" (the last option in the drop down list of the CPU Strategy Wizard). It is generally a better choice on todays CPUs.

[WOWBOX40]

Ive never used any of the built in jamba features in isboxer. But do they still work, IF he is using the EMA addon?

[crowdx]

I actually have EMA disabled as it did not seem to work correctly even with Jamba disabled. I tried it for a few hours but reverted back to Jamba.

[MadMilitia]

Hi.

I had a nasty problem some months ago with key modifiers getting stuck between windows if I included a modifier in my window swap.

It was causing {FTL} modifiers to act up and thus causing follow to not work, among other {FTL} commands like assist.

To test set some mounts with various key modifiers and a mount command. Then do your normal swap rotation and fire off the mount key to see which mount they choose. That's how I identified my key modifier bug. Ideally they should always choose the [nomod] mount but if the bug is present they will mount the ones on the modifier keys.

EDIT: Should have noted that the "fix" was to stop using modifiers in my slot switch. Since switching those keys to nomod all the problems went away. I think what was happening was competing modifiers on some macros were preventing CTRL from registering as up on the recently swapped out of window. So that window would always see CTRL DOWN present until I broadcasted and registered CTRL UP.

EDIT (again!): After thinking about this I revisited the profile.

As it turns out, the Jambamaster macro in the WoW Default macro profile was sending this:

CTRL + SHIFT + F12

My character slot switch was using CTRL + X where X was F1, F2, F3, F5, F5.

The CTRL key was getting double banged. From my physical CTRL DOWN event on the switch and the CTRL DOWN in the WoW macro Jambamaster.

I removed the WoW macro Jambamaster from the slot switch keymap Jambamaster in ISB42 - WoW. Then put CTRL + X as the modifier for slot switch. I moved all the Jambamaster, ctm and renderscale macros to ingame macros so that I could clear up some confusion on the isboxer profile. So now it was just sending (ALT + SHIFT + -) for SLAVE and ALT (+ SHIFT + =) for master.

Voila! Problem fixed. No more double banged CTRL results in everything releasing as expected now. That nasty little bug haunted me for months. Just an FYI if anyone else is seeing weird behavior like this make sure you aren't double banging a keydown event on the slot switch.