Windower 4 - Discussion and Support

[Fival]

I have 2 characters, named Fiv and Fival, and shortcuts doesn't like me;

If Fival has party lead, "/pcmd leader Fiv" will not work, but thats not all, "/pcmd kick Fiv" doesn't kick Fiv, instead it makes Fival just disband the party himself, only himself not the entire party. This isn't a big issue, not as big as when shortcuts was newer and //warp2 Fiv would make Fival warp himself, thankfully that doesn't happen anymore, but still, i think the predictive names is getting in the way here, when i turn off shortcuts these functions work properly.

[Karizo]

I have 2 characters, named Fiv and Fival, and shortcuts doesn't like me;

If Fival has party lead, "/pcmd leader Fiv" will not work, but thats not all, "/pcmd kick Fiv" doesn't kick Fiv, instead it makes Fival just disband the party himself, only himself not the entire party. This isn't a big issue, not as big as when shortcuts was newer and //warp2 Fiv would make Fival warp himself, thankfully that doesn't happen anymore, but still, i think the predictive names is getting in the way here, when i turn off shortcuts these functions work properly.

This sound like a fix the dev can implement rather easily. Shortcuts just need to prioritize empty space or lack of character before "a", or something like that.

[Trumpy]

A few days ago i was gettin the lag with tells. Chatmon would say i have a tell but i wouldnt get them for up to a minute sometimes. about this time tho i also did some campaign battles. fort kurka or whatever it is called was the worst with like 1 million npcs around. Not only was i gettin lag on tells I wouldnt get LS chat til i moved away from the herd, but i am pretty sure that is jsut standard lag. But i got the tell lag pretty much everywhere without evident lag. But for me at least it has all gone away since then.

[Motenten]

Updated Timers. This doesn't change any of the code, it just intercepts what looks like the point of failure for the crash. If this is in fact where things go bad, you should see a message printed out in the console, and Timers should avoid crashing (though it may mess up the display, and you'd need to reload Timers).

3.4.0.8: http://update.windower.net/dev/plugins/Timers.dll

[Subadai]

Updated Timers. This doesn't change any of the code, it just intercepts what looks like the point of failure for the crash. If this is in fact where things go bad, you should see a message printed out in the console, and Timers should avoid crashing (though it may mess up the display, and you'd need to reload Timers).

3.4.0.8: http://update.windower.net/dev/plugins/Timers.dll

So far so good, I put in about 5 or 6 hours on NIN last night, no crashes or error messages. But then again, it has always taken a long time for me to crash, so I'll report back later this week after I've tried a few other jobs/events. I'll be doing a Dynamis run on THF tonight, that's where I crashed last time, so we'll see how it goes.

[Sechs]

I won't have chances to play extended sessions until thursday, so no testing from me sorry =/

[Suteru]

That version of timers gives me multiple durations of the same ability, known issue? Better than slowly sliding down the screen and blocking chat still, I guess

edit: Did they make it so you don't have to be engaged to WS or is that a Windower thing now?

[Trumpy]

That is a Gearswap glitch/benefit that allows one to WS while not engaged. Obviously just becareful who you do that in front of

[Sechs]

I managed to find a place with a lot of developers experts with Microsoft Windows SDKs and crashdumps. I might be able to solve the issue me and Subadai have been incurring lately (minidumps are too small, 32kbs, and they have only a single thread) but I need to be able to give a correct explanation of the issue.
Can anybody help me out? Maybe Motenten since he's the one who examined mine and Subadai's dumps?

Some more questions: are we the only two people so far who had this issue?
Since Subadai provided many other dumps, some of which have been useful, does this problem happen only with the dumps concerning THAT specific crash?


If anybody can help me come up with a reliable technical description of the problem with our dumps I might be able to solve it.
And if we solve it we will be able to provide meaningful Dumps of that nasty crash.
And if we do that, we're going to 100% solve the issue once and for all!

[Motenten]

Some more questions: are we the only two people so far who had this issue?

Yes, but you're also the only two people who have provided crash dumps (for me, anyway; I know Arcon has gotten more from others).

Since Subadai provided many other dumps, some of which have been useful, does this problem happen only with the dumps concerning THAT specific crash?

The other dumps Subadai provided had the same issue, it's just that there was enough detail provided that I could ferret out what the problem was.


General issue: Only a single thread is captured in the crash dump. Wouldn't be a huge deal, except there's the sense that it's not necessarily the thread that had the exception thrown (and of course is completely unhelpful if it's a cross-threading issue).

[Motenten]

Just a note: New update of times, to 3.4.0.9: http://update.windower.net/dev/plugins/Timers.dll

The debugging stuff from 3.4.0.8 was removed, as there was no indication that it provided any help. The changes for 3.4.0.9 will either do nothing, or will fix stuff. Again. As always, appreciate any testing and feedback.

[Fwahm]

Is it possible to get Windower to do a StatusTimer type of thing, but only for a single specific buff, other than dummying out every single other buff/debuff in StatusData.txt?

[Subadai]

Just a note: New update of times, to 3.4.0.9: http://update.windower.net/dev/plugins/Timers.dll

The debugging stuff from 3.4.0.8 was removed, as there was no indication that it provided any help. The changes for 3.4.0.9 will either do nothing, or will fix stuff. Again. As always, appreciate any testing and feedback.

I'll try it out today and over the weekend, and report back.

[Suteru]

It seems to still show a roll after Busting, and it also ignores that zoning resets the Trust timer.

Is there a place to download the most recent non-dev timers?

[Arcon]

Suteru: All current live plugins can be found at http://update.windower.net/plugins/ and dev plugins at http://update.windower.net/dev/plugins/.

You can also just delete it from your repository and re-select it in the launcher, then it will download from the above links (depending on whether you have the live or dev Windower).

[Fwahm]

I'm having a problem with StatusTimer.

I'm trying to adjust the timer for a certain buff (Aftermath lv. 3, ID 272), but if I put something other than -1 for the duration in the StatusData txt file, it counts down from 1:30 no matter what I put. If I reload the plugin while the buff is active, the duration is switched to the correct one, but it goes back to 1:30 the next time I put the buff on again. Since there seems to be another location with buff duration that is overriding the StatusData file, does anyone know where it is, so I can change it, too?

Also, is it possible to change the positions of the numbers by default, so you don't have to change it every time you load the plugin? If so, how do you do that?

Any help?

[Draylo]

Is the thing where your timers keep creeping to the bottom of the screen a bug? It's been there a while, so just wondering.

[Lyramion]

Not sure if this is a Windower or gearswap issue but I had the SAME crash 3 times in a row now:

1) Fighting CORSE in Rala Skirmish
2) Corse casts DEATH
3) I manually hit my Shadowring + Eihwaz Ring macro
4) I fail to resist and die
5) I reraise or get arised
6) I get up and will crash with a Windower Runtime Error


Did didnt get a screen of the Runtime error yet since my PT was obviously waiting for me.

[Motenten]

Is the thing where your timers keep creeping to the bottom of the screen a bug? It's been there a while, so just wondering.

Yes, that's a bug. It's in the version that's on live, and has been for the last month while the dev version is worked on. The version on dev fixes that, but has crash issues. Unfortunately there's only 2-3 people helping debug it, so it's taking a while to fix all the problems. You can either download the dev version and help test it to hopefully get the issues resolved faster, or wait til it's done.

[Motenten]

Not sure if this is a Windower or gearswap issue but I had the SAME crash 3 times in a row now:

1) Fighting CORSE in Rala Skirmish
2) Corse casts DEATH
3) I manually hit my Shadowring + Eihwaz Ring macro
4) I fail to resist and die
5) I reraise or get arised
6) I get up and will crash with a Windower Runtime Error


Did didnt get a screen of the Runtime error yet since my PT was obviously waiting for me.

Are you on live or dev? Are you using Timers? Are you using a GS file based on my libraries? Are you able to save a crash dump?

You can either follow the instructions here: https://github.com/Windower/Issues/w...ps-with-Windbg for creating a crash dump, or simply save a dump using the Task Manager when a program crashes. If you're on a 64-bit version of Windows, you'll need to use the 32-bit version of the Task Manager, located at C:\Windows\SysWOW64\taskmgr.exe