Windower 4 - Discussion and Support

[Damane]

My Timers suddenly have jumped to a lower location on my window. Should I just delete the config file? It seems that the duration timers drift downward everytime I do something with the window out of focus, not sure specifically what yet.

this ecxept for me its everytime I do extensiv buffs, especially haste cycles etc.

[KuKuKaChoo]

Yeaaaaaaaars ago I used to have a plugin or program (can't remember which) that allowed XI to go cell shaded.

Any chance of someone being able to make a comeback? I think it'd be pretty cool

Wasn't this a feature of the JP windower? I don't know that I ever saw a program or plugin that did that elsewhere.

[Cream Soda]

Might have been; I don't remember it well tbh. I enjoyed playing around with it when I did though

[Byrthnoth]

There was (the last time I looked) a bunch of stub code for it in hook. It looks like someone started making it for Windower but then decided it was too much effort. It was definitely a feature of JP windower, though.

Iryoku says this would not be possible without more time and an actual copy of FFXI (which he doesn't have):

Only problem is it has a side effect for controller users. It took me a few minutes playin around with it to figure out what was different on controller but i finally did. Normally on controller if i hit my trigger buttons to open the macro menus they stay open til i hit one or my cancel button, which i like so i can open my menu get ready for stun, or open the macro menu put it on what i will need and concentrate on moving my character around and be able to just hit my enter button to activate the macro. But your plugin makes the menu go away upon releasing the trigger buttons (so its more like a hold and not toggle) I mean im sure i could get used to it, but if u could make it an option somehow or make it work like before on controllers and keep the no delay on keyboard. If its not possible to fix for keyboard and keep the delay that is ok, since the plugin is totally optional or one could just try to get used to the different functionality of controller macros.

[Sithel]

I had a POL crash while on the AH looking at items. It's happen before and has a drop down from the crash that says view details. Will posting that help?

[Motenten]

For those testing Timers, can try the new version on dev: http://update.windower.net/dev/plugins/Timers.dll

Hopefully should have fixed the crash issue for brd.

[Prothescar]

while we're on the subject of visual enhancements, was there ever any headway into a plugin/addon to adjust the FPS cap for the game? is it possible at all or are we gonna be stuck using the .exe?

[Rhonda the Sly]

I just took a look at the latest drop in dev and haven't seen any crashes but have noticed the following issues.

If songs are immediately recast, duplicate Timers are created
Cast the following song sequences:
Sequence #1: March1 > March2 > March1 > March2
Sequence #2: Paeon1 > Paeon2 > Paeon1 > Paeon2

Expected Timers:
Sequence #1: Advancing March, Victory March
Sequence #2: Army's Paeon, Army's Paeon II

Actual Timers:
Sequence #1: Advancing March, Victory March, Victory March
Sequence #2: Army's Paeon, Army's Paeon II, Army's Paeon, Army's Paeon II

Occasionally additional Timers are displayed
Cast the following song sequence:
#1 March1 (BAU) Timers: March1
#2 March2 (BAU) Timers: March1, March2
#3 Aubade (BAU) Timers: March1, March2, Aubade
#4 Madrigal (BAU) Timers: March1, March2, Madrigal2
#5 Ballad1 (BAU) Timers: March2, Madrigal2, Ballad1
#6 Ballad2
Expected: March2, Madrigal2, Ballad2
Actual: March2, Madrigal2, Ballad1, Ballad2

Songs are casted without Pianissimo and with the following bonuses:
Aubade with no bonuses
Ballad +3 to Song Family with +41 duration
Madrigal, March, Paeon +4 to Song Family with +51 duration

[bigbomb]

while we're on the subject of visual enhancements, was there ever any headway into a plugin/addon to adjust the FPS cap for the game? is it possible at all or are we gonna be stuck using the .exe?

This should be what your looking for: http://legacy.windower.net/topic/213...e-cap-adjuster

[Sechs]

If songs are immediately recast, duplicate Timers are created
Cast the following song sequences:
Sequence #1: March1 > March2 > March1 > March2
Sequence #2: Paeon1 > Paeon2 > Paeon1 > Paeon2

Expected Timers:
Sequence #1: Advancing March, Victory March
Sequence #2: Army's Paeon, Army's Paeon II

Actual Timers:
Sequence #1: Advancing March, Victory March, Victory March
Sequence #2: Army's Paeon, Army's Paeon II, Army's Paeon, Army's Paeon II

Not sure I get what you mean but the "Actual Timers" line is exactely how Timers should be working?
I.e. it displays timers for all the songs you've cast, wether they've been overwrited or not.
It's actually useful for it to be like that because Timers cannot know exactely which songs got overwrited and just keeping track of the last 4 songs cast might be bad.
For instance think about a situation where you have 2 PTs and you're swapping, you would want to keep track of the songs you cast on pt1 and the songs you've cast on pt2, for a total of 8 songs.
With the way you're suggesting (Expected timers) you would lose track of the first 4 songs, which didn't really got overwrited since they were cast on a different party.


Been testing Timers the last few days on BRD and never had any crash with 4.7.2.3 Hook and the Timers version Arcon posted a couple of pages ago (is it the same Motenten posted on this page?).
The only issues still there as far as I can see are:

1. Timers don't always get sorted by the one expiring first (up) to the one expiring last (down)
2. It seems to be ignoring, for some reason, the limit you set for the Buffs window (I set it to 15, but it displays at least up to 20, maybe more)
3. Sometimes the cooldown window doesn't display the time left for a certain action (happens randomly and only happened to me on songs with small cooldown, never saw it happen for long time stuff or JAs)
4. Sometimes, for a nanosecond, I see a very wide line with an alpha background that displays uhm... something, random numbers, cannot read it since it stays on screen just for such a sort time. It's a line that starts in the middle of the Buff windows and goes all across the screen, it's very wide. I dunno what it is... happens sometimes when I'm casting buffs.
5. With Graphical mode to False and Textcoloured mode On, the colours do not get used as they should (still need to try the 2 new options Arcon created in the last version of timers, which should be able to tell Timers wether you want it to start from the colour set for "Low" and go up to "High" or vice-versa)
6. Sometimes (always?) when a timer is flashing because it expired or that ja/spell is ready again, that flashing line goes "above" the line of another timer which will be "invisible" behind (can't see it because there's the flashing one above). I see this happen all the time in the Cooldown window if I set the Flash timer over 2 seconds. I need to test more to see if it happens in the Buffs window too.
7. Currently while in Graphical Mode FALSE it doesn't display anymore an indicator to tell you if that buff was cast on a specific target or if it was an AoE one.
8. Not a real issue, but it's a new "feature". Buffs window displays debuffs too. I'd love a setting that allows you to turn this thing off, because adding all of the debuffs to the Blacklist might take quite a while and it would be inconvenient.

Edit:
I need to do more tests, but issue 2) might be the same thing as issue 6) actually.

[RalphTheDwarf]

I noticed an issue where the window title bar is intermittently not being updated with the currently logged in character. It seemed to start this weekend.

[Haborym]

Does anyone have recommendations to bypass the limit of 4 pol accounts?

[Karizo]

Another issue I noticed on the LIVE version of timers, not sure if it has been resolved by didn't see anyone post the same issue.

When I have a buff on myself that's also casted on others, all the trackers for said buff disappears as soon as mine wears off.

For example, I am on RDM and casting Haste II on everyone, if my haste II wears off before others, the tracker for other haste II will disappear even though they haven't worn off.

[Motenten]

Another issue I noticed on the LIVE version of timers, not sure if it has been resolved by didn't see anyone post the same issue.

When I have a buff on myself that's also casted on others, all the trackers for said buff disappears as soon as mine wears off.

For example, I am on RDM and casting Haste II on everyone, if my haste II wears off before others, the tracker for other haste II will disappear even though they haven't worn off.

I'm not seeing that problem on the dev version.

[Sechs]

Did some testing with the version Mote posted (3.3.0.3) and noticed something I want to add/change to my previous report.

1. Over the last few versions, songs normally overwrite themselves in the smartest possible way, but I still feel this is not enough. Explaining why in another post, gonna be long.
2. It doesn't work for everything. For some reason Advancing March is not overwriting itself, but keeps on appearing there in the list. The odd thing is that other people are getting the same result, but with different songs. For instance for me Advancing was duping, Victory was overwriting. For Chaulefree it was the other way around. This was NOT happening on the version Arcon posted on the previous page (3.2.0.1 I think?). I get the same happening for Ballad II (duping) and III (overwriting). Happens with Sword Madrigal (dupe) and Blade Madrigal (overwrite) as well.
3. The overwrote songs fuck up the sorting. Normally you have the buffs about to expire on top and those with longer cooldowns on bottom. But if a song about to expire is overwote with a new one, you'll see the new, long timer on top.
4. Buffs do not disappear anymore when you zone (i.e. the buff disappears, for most buffs at least)

Also after downloading Mote's version (3.3.0.3) I had a crash in Einhherjar while buffing. Didn't see any crash over the last few days using the previous version (with 4.7.0.3 hook).
Might be a coincidence of course, /shrug

[Sechs]

About the songs overwriting now, I don't think there is a perfect solution because there is no absolute way to track what-overwrites-what.
I'll describe how things have been working over the last couple of versions for songs, please correct me if I'm wrong.

• If you pianissimo cast a song on a target, you'll get a [nameoftarget] specific timer line
• If you pianissimo on yourself or AoE but hit only yourself, you'll get nothing
• If you AoE song and hit multiple targets, you'll get an [AoE] line
• If in the current pt there are 2 pianissimoed songs on 2 different targets (Ballad [name1] and Ballad [name2]) if you perform an AoE ballad you won't get the [AoE] marker. Instead the timer of the Ballad higher in the list (i.e. the one supposed to wear off sooner) will be replaced. In this example Ballad [name 1]. Ballad [name2] will remain on screen.
• If you cast a song (AoE) on a pt, then drop and go to another pt and cast the same song, the timer will overwrite itself and you will only see the more recent one)

This probably as smart as it can get, but honestly I'd love at least an option to turn this smart overwriting off.
I don't know what other bards think about it, but while there are times when smart overwriting would be blessed to avoid excessive clutter in the Buffs window, at the same time I'd rather have a long list to correctly check the wear time of all the songs I cast, and I don't think anything anybody could program could ever be that smart.

Just my two cents btw.



Oh also, managed to finally take a screenshot of the error I was talking about on number #4 of THIS post.
It looks just like that, stays on screen for a nanosecond, sometimes I think I've seen multiple colours in there, and the bar is probably a bit less wide than that (don't think it takes up the whole screen, but I might be wrong)
http://s16.postimg.org/tmyz8ne29/pol...0_14_37_44.jpg

[Motenten]

It seems to be ignoring, for some reason, the limit you set for the Buffs window (I set it to 15, but it displays at least up to 20, maybe more)

Fixed. Also, in doing so, I found that there was a mismatch between the saved and loaded settings names. You may want to delete your old settings file and let a new one be created, or use the new entries at the bottom of the saved file to replace the misnamed ones.

Timers don't always get sorted by the one expiring first (up) to the one expiring last (down)

Partly fixed.

With Graphical mode to False and Textcoloured mode On, the colours do not get used as they should

I'm not seeing this. The text is colored as expected when I try it.

Sometimes (always?) when a timer is flashing because it expired or that ja/spell is ready again, that flashing line goes "above" the line of another timer which will be "invisible" behind (can't see it because there's the flashing one above). I see this happen all the time in the Cooldown window if I set the Flash timer over 2 seconds. I need to test more to see if it happens in the Buffs window too.

I set the flash timer to 4 seconds, and am not seeing this effect.

Currently while in Graphical Mode FALSE it doesn't display anymore an indicator to tell you if that buff was cast on a specific target or if it was an AoE one.

I see the normal indicator if a spell was cast on a specific target. I know self-buffs don't show a target anymore, since it's implicit. Are you testing something like Protectra cast on yourself, with noone else in the party? Since there's only a single target it's not considered AOE, and since it was cast on yourself it won't show a specific target.

Not a real issue, but it's a new "feature". Buffs window displays debuffs too. I'd love a setting that allows you to turn this thing off, because adding all of the debuffs to the Blacklist might take quite a while and it would be inconvenient.

From what I can tell, this should only apply to Threnodies, Elegies, and Foe Lullaby I/II, as those are the only enemy-targetted spells with durations in resources. The durations in spells.lua resources were directly copied over from a spell durations file, which included those spells.

I'm not sure offhand whether those durations are being used for anything elsewhere, so not going to remove them from resources. However I should be able to exclude them from showing up in Timers.

Fixed.



Can't reproduce or never encountered the other mentioned items.

New version uploaded on dev (3.3.0.4). Can download from http://update.windower.net/dev/plugins/Timers.dll for testing, if you're on live.

[Sechs]

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.

[Motenten]

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

Revised how it filtered mob-targetted buffs. Filtering them from the loaded resources caused a couple problems. They are now filtered at timer creation, for buffs only (recast still shows up normally).

Changed sorting pref: Removed orderAlphabetically, and added a sortOrder pref that can take values of: Creation, Duration, and Alphabetical.

Fixed the remaining issues of sorting by remaining timer duration.

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

This is most likely a side-effect of fixing the crash issue. I'll have to go back into that.

[Sechs]

added a sortOrder pref that can take values of: Creation, Duration, and Alphabetical.

Wow! Awesome change! /chapeau
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?

This is most likely a side-effect of fixing the crash issue. I'll have to go back into that.

Well, as far as I can tell with Arcon's last version (I don't remember, the one on previous page) there were several issues (most of which solved in your updates) but I never crashed in 3 days, with the new hook.
Now I can't tell about 3.3.0.4 and 3.3.0.5, but with 3.3.0.3 I did crash during Einherjar while overwriting daubla buffs with NiTro horn buffs.
Sorry, no crash dump =/