Windower 4 - Discussion and Support

[Motenten]

In case I select creation, if I overwrite a buff, it stays where the original was, correct? Whereas with Duration even overwrote buffs get dynamically sorted according to how much time is left, right?

It -should- work like this:

Edit: First time I was wrong. Overwritten buffs do indeed stay in their original slot

Creation:

> Valor Minuet (duration 3:45)

• Valor Minuet 3:45

> Haste (duration 3:00)

• Valor Minuet 3:40
• Haste 3:00

> Blade Madrigal (duration 3:45)

• Valor Minuet 3:35
• Haste 2:55
• Blade Madrigal 3:45

> Valor Minuet (duration 3:45)

• Valor Minuet 3:45
• Haste 2:50
• Blade Madrigal 3:40

Duration:

> Valor Minuet (duration 3:45)

• Valor Minuet 3:45

> Haste (duration 3:00)

• Haste 3:00
• Valor Minuet 3:40

> Blade Madrigal (duration 3:45)

• Haste 2:55
• Valor Minuet 3:35
• Blade Madrigal 3:45

> Valor Minuet (duration 3:45)

• Haste 2:50
• Blade Madrigal 3:40
• Valor Minuet 3:45

[pancakesandsex]

Thanks mote, but keep in mind the stuff I wrote in my first post was found out with previous versions of timers (the one Arcon posted on the previous page).
The last 2 posts were made with 3.3.0.3 in mind instead (the one you posted on this page)

Will try 3.3.0.4 asap, but first I'll "reset" my xml just like you suggested.


The "duping" thing described in my post above (wasn't in Arcon's version, as far as I can see it started from 3.3.0.3) still happen, still on Advancing March for me. But now it only happens if I cast Advancing March one after another without other songs in between.

The sorting seems much better for "Buffs", but I noticed something strange that I found how to reproduce, since it doesn't happen always. Basically when you refresh some songs (overwrite a song with the same) it goes to the bottom of the list (as it should) but at first it displays ~10 seconds left. Once it reaches 0 it starts displaying the right timer.
Once you start swapping and overwriting different songs this effect ceases to exist, but I found out how to reproduce it 100% of the times, follow these steps.
1) Start with no songs up
2) Victory March (Horn)
3) Advancing March (Horn)
4) Blade Madrigal (Daubla)
5) Sword Madrigal (Daubla)
6) Victory March (Horn)
7) Advancing March (Horn)
8) Blade Madrigal (Horn)
9) Sword Madrigal (Horn)

If you follow these steps after zoning and without any other songs up, it will always happen, at least for me. It starts on step 8. When you finish casting that Blade Madrigal it will overwrite the old one, move to the bottom of the list, but start at around ~11 seconds left, when it reaches 0 it will let you see the correct timer.

Still about sorting, there's something strange in the Recast window. While doing this trick, I noticed that for all these songs, the sorting order was "inverted" (songs expiring last on top, expiring next on bottom). This doesn't seem to be happen on other, longer cooldowns, which correctly display next on top and last on bottom. /shrugs


Providing a screenshot to explain better, btw
http://s30.postimg.org/cztiu3n8d/pol...2_05_47_87.jpg


Also if you get a chance try to give a read to my 2 posts above, especially about the Song Overwrite matter.
tl;dr I don't think the system behind timers can be made any smarter than it already is, but there should at least be an option to turn it off if you wish so.

What super rad minimap plugin is that?

[Johnblaze]

What super rad minimap plugin is that?

FFXIDB

[Motenten]

3.3.0.6 update (http://update.windower.net/dev/plugins/Timers.dll)

Fixed the overlapping timer bars (overwriting a shorter duration buff with a longer duration one, but having the remaining time appear to be much lower).

Fixed the issue of duplicate timers (victory>advancing>advancing, etc).

Reworked code for timer replacement. Fixes:

1) If single-target buffs (pianissimo songs) had hit multiple individuals, and then an AOE buff hits more than one of those, it will properly clear all relevant individual timers.

2) When creating an AOE buff that replaces an existing single-target buff timer, it properly updates the target name to "AoE".

3) When casting a single-target buff on someone who had previously been hit by an AoE, properly separates them out into a new timer (existing functionality).

4) Possible leak fixed.

[Terravcota]

Downloaded 3.3.0.6 and I can only seem to have 4 BRD buffs tracked. Am I setting something wrong with the new type of timers plugin? Marchx2 Minuetx2 on a DD set (mules) and then ballads on myself (nothing pianissimo) and I end up with only tracking 2 DD songs and 2 ballads. If this is part of the "smart logic" for songs, is there a way to turn it into a setting we can turn off to avoid this?

[Motenten]

OK, the problem there has to do with automatic clearing of buff tracking when buffs wear off (nothing specific to songs, and there's no "smart logic" toggle). Since you did March, March, Min, Min, Ballad, Ballad, by the time you finished the second Ballad, both Marches had been dropped, so they got cleared from the list.

This is a side effect of the normal behavior of, say, Stoneskin wearing off, and when it does, the timer gets dropped. However, it -shouldn't- be removed, because the buff that got dropped was one where there were multiple targets (which Timers tracks), so it dropping from -you- should only remove your entry from the target list, but leave the timer as a whole still active.

I'll work on getting that fixed shortly.

[Subadai]

Beta Plugin: DelayMeNot
https://www.dropbox.com/s/jcuq9uv1mh...DelayMeNot.dll

Removes delay on ALT/CTRL macro menu's popping up. Not tested very much, would appreciate if someone could load / unload and provide crash dumps if it crashes on load / unload.

Feedback also appreciated.

I will try to test this tomorrow, right now I'll be working on the latest Timers. This would be a handy plugin, the macro menu delay is seriously annoying.

[Motenten]

Ok, 3.3.0.7 should fix the issue with buffs wearing off yourself while tracking AOE timers. (http://update.windower.net/dev/plugins/Timers.dll)

[Motenten]

Also: yes, there's a crash. Working on it. (Put 3.3.0.6 back on the server)

[Subadai]

Just got a crash on 3.3.0.6 with hook 4.2.7.3. Crash dump. I was on the teleporter in the chocobo circuit and decided to select "No" to the prompt to use the device.

[Motenten]

3.3.0.8 should fix the crash. (http://update.windower.net/dev/plugins/Timers.dll)

[Subadai]

3.3.0.8 didn't crash after a quick sanity test, I'll report back in a couple hours.

[Sechs]

Reworked code for timer replacement. Fixes:
[cut]

Ossom ^^

is there a way to turn it into a setting we can turn off to avoid this?

Eh... yeah, it's what I asked myself too, but now I'm not sure anymore.
(aside from the fact that lately I seem to hardly rotate between pts anymore)
At least up to until a while ago my typical situation of stuff to track was:
1) 4 songs on PT1
2) 3x Ballads on PT1's WHM
3) 4 songs on PT2

When there is no logic at all to handle overwrites, simply everything would be listed in there, no matter if the song got overwrote or not.
Yes, it created quite a big clutter in the Buffs window, but I kinda got used to it.
With the current system stuff will be cleaner, and that's good.
In the above example I would end up having displayed:
1) 3 Ballads on PT1's WHM
2) 4 songs on PT2
Which... is not a big deal. I know that around ~30 seconds before song1 of PT2 is about to expire, I need to recast songs on PT1, so in a way that should be enough I guess.
It's just a matter of me getting used to this new system maybe.


Honestly I think if the crashes are gone, all the small things/bugs have been fixed.
Only thing "missing" would be turning TextColouring on/off individually for Buffs/Recast/Custom but Arcon said he doesn't want to split it so I'll deal with it (not a big issue anyway).

Think I'll start hunting the missing duration enhancements from now on and open individual tickets for them when I find them, so that Mote, Arcon and the rest of the crew can track them more easily.
I already spotted a few on BRD.

[Motenten]

With the current code, it 'should' show all 11 of those timers, since each version of the AOE songs would have different targets.

Duration enhancements have been added for Nightingale/Troubadour, and fixed for Circle abilities for pld and drk. These haven't been pushed to dev yet, as I was waiting for feedback on version .8.

[Subadai]

3.3.0.8 didn't crash after a quick sanity test, I'll report back in a couple hours.

No crashes or other problems found after around 3 hours of play.

[Sechs]

Mote did you happen to find out this bug?

http://s16.postimg.org/tmyz8ne29/pol...0_14_37_44.jpg

I tried to describe it HERE.
The screenshot was taken from another error actually, but it was just a visual example to explain what I've seen from time to time, even if just for a nanosecond.

It's not a real "problem" for me don't get me wrong, was just trying to provide input to help solving what *might* be an issue in the code.
If it's not then no big deal, doesn't really bother me.


Can't wait to be home and test .8

[Terravcota]

Just wanted to say thanks, Mote! I really appreciate all the work you've been putting in.

[Sechs]

Tested for a few hours, no crash on the horizon and everything seems pretty smooth. The new sorting order by Duration is fantastic!

I still see BRD debuffs though. The only one I don't see is Requiem.
Also I had this nasty bug appear on screen several times
http://s23.postimg.org/nfo39kphz/pol...2_03_14_96.jpg

No clue how to reproduce it. It usually happens once I start pianissimoing stuff but I cannot reproduce it at will.

[Cream Soda]

Is there a find plugin for keyitems?

[Motenten]

Edit: Nevermind, apparently quoting made it show up properly.