Windower 4 - Discussion and Support

[Byrthnoth]

Battlemod wouldn't affect the code I posted, but it would affect exact matching implementations like what you originally tried to do. Just use my code.

[Jem]

This is the crash issue I was talking about



Literally happened ~20 times whilst fighting 3 NMs in Escha-Zi'tah, sometimes instantly as soon as I hit close the window. Didn't happen at all elsewhere which involved running around grabbing CS'es and doing the final Adoulin fights. (The above is obviously just fighting a normal mob though)

It only ever happened tonight when in combat, I can't remember if that is always the case but it could be.

[Byrthnoth]

This is the crash issue I was talking about

Arcon says this is caused by the Update addon (probably in combination with multiboxing). Just unload the update addon and it'll stop.

[Jem]

Ok great, thanks. I don't multibox so can't be that but I'll try unloading that addon and see if it fixes it.

[Trumpy]

A little late but Se added mog safe2 instead of wardrobe 2 cause people wanted to do things with furniture (also all the inventory complaints).

[Nexxus]

Does anyone know how to trigger a "song" or else when certains words appear in the logs (with battlemod addon active) ?
I'd like to know when i learn a new spell as blue as the logs are often spamming with eminence and other stuff, a small sound that trigger when the word "**** learn ****" appears in the logs.

[Trumpy]

Have you tried chatmon? it may be able to do this.

[Nexxus]

Have you tried chatmon? it may be able to do this.

Gonna tried !
I've tried an old Autoexec to input a /tell (so chatmon is triggered), but didn't work, i didn't think at Chatmon itself...

should i put below:
<trigger match="*Myname learns*" notfrom="Tell|Party|Linkshell" sound="Talk" /> ? i dunno with part of the chat log is the learns message.


edit: work fine.

[Sechs]

Been experiencing something strange the last few days, not sure if it depends on some addons/plugins being updated or something else. Strangely enough it only affects FFXI and no other game/software I use.
Basically when I load FFXI the keyboard starts acting wonky. The basic keys (letters etc) work, but all other keys (numpad, enter, esc, -, +, etc) do not work at all.
Of course if I alt tab to another application everything works perfectly.

This doesn't happen all of the times, it seems to be random. Maybe it's not, but then I haven't still found which conditions generate it.


I have a Logitech G19 Keyboard, I use the Logitech Gaming Software, I use the Binder plugin and I'm under Windows 10.
This started happening a few days ago and I've been on this very same configuration (without changing a single bit, minus Windows Updates) since December 2015.



If you guys tell me you're 101% no way this could possibly depend from Windower of any of its components, then I'll have to think about something else, but I'm pretty clueless atm.

[Byrthnoth]

What windows version do you use?

[Trumpy]

If its a keyboard issue first check the config menu. you might have set it to compact or something. there are 3 options, so just make sure its on the correct one. Compact options are for laptop that might not have numpads ect... There was a time where this settin kept gettin set to compact for no reason repeatedly but was eventually fixed

[Sechs]

What windows version do you use?

I said before, Windows 10, or did you mean more specific? It's Windows 10 Professional 64 bit, updated to the latest patches, italian localization.
Again I have no clue if this depends on Windower4 or something else, but it's strange how this happens only with FFXI to me and no other software/game.
I just asked in case there has been some update over the last week that could've interested the keyboard, the binder plugin or anything even remotely connected to these things.


@Trumpy
Not even sure I use config plugin lately (or did you mean the in-game config menu?) but the problem here is that this happens randomly. It doesn't happen all of the times, it's been a random thing that happened to me over the last... I dunno, 4 days, no more than a week I think.
I'll check, but I seriously doubt it has anything to do with that.
I've been using this specific configuration since december and it never happened before, and this PC (with same keyboard, same component) for the past 3+ years and, again, never seen it happen before.

[Byrthnoth]

Someone else on Windows 10 reported strange input device issues after this past Wednesday's patches. Try rolling them back and see if it goes away?

[Sechs]

Ooh... so you say it could be some strange issue depending on Windows 10's last update.
Could be.
Sounds strange that it only affects Windower/FFXI but then again not THAT strange I guess.
Do you have a link to that discussion so I can read?

[Byrthnoth]

https://github.com/Windower/Issues/issues/814

[Maurauc]

Would like to confirm I've been experiencing the same issue. XBone controller. Windows 10. Crash on switch from POL to FFXI.
I can't supply a crash dump atm (Gotta get those WKR runs in) but once the campaign switches over, I'll try and supply one on Github.

[Sechs]

I do use a wireless Xbox One pad but I'm not sure how could that be the cause of my issues. Not like I'm experiencing crashes anyway
Maybe it's two different issues, altough the fact they seem somewhat linked to input systems and the 03 March Windows10 patch is... fishy for sure.

[Isiolia]

I do use a wireless Xbox One pad but I'm not sure how could that be the cause of my issues.

MS did recently break the XB1 controller with a Windows 10 update.

[Sechs]

But my pad works perfectly with FFXI (even when the keyboard problem occurr), with 2D and 3D Beatemups on PCs, with Emulators, with FFXIV, with Blade & Soul, with Black Desert and pretty much anything I can think of D:
I mean, not saying that article you linked says a bunch of lies but still, uuuuh...

There might be a connection though, I'll keep my eyes open for Windows update. Could try using my old X360 wireless controller meanwhile and see if anything changes.

[Trumpy]

yea i meant the in game config menu. And it randomly changed the setting when it happened. but if you checked it, it of course isnt the issue.