Windower 4 - Discussion and Support

[Motenten]

3.4.0.1 pushed to dev (http://update.windower.net/dev/plugins/Timers.dll)

Including 3.4.0.0 changes:
Fix pointer reference which generated target name gibberish (hopefully fixed)
Fix check for whether an action target is a mob
Add Nightingale/Troubadour buff duration gear
Fix Circle buff duration gear for pld/drk
Prevent Vivacious Pulse from generating spurious timers

[Subadai]

3.4.0.1 crashed with 'timers encountered a fatal error and must be terminated. Error: access violation in IncomingChunk method.' This was on my BLM/RDM with six or so buffs up while spamming gas. Windower release, Hook 4.2.7.3.

Edit: rebooted and tried again, happened on my first buff, Refresh. Maybe I just didn't notice it happened on the first cast last time, I was blathering away on voice so wasn't paying close attention.

[Motenten]

I can't replicate the crash. Can you make a crash dump?

[Subadai]

Windower doesn't crash, the plugin just unloads with that error message. Is there a way to get a dump when PoL doesn't crash? The debugger isn't letting me enter the command.

[Arcon]

Windower doesn't crash, the plugin just unloads with that error message. Is there a way to get a dump when PoL doesn't crash? The debugger isn't letting me enter the command.

I don't know if this works (I haven't used WinDbg before) but check if there is an option to catch first-chance exceptions. That will make WinDbg break the execution before Windower unloads Timers with the error message. The downside is that that may crash your POL when it otherwise wouldn't, I'm not sure about that.

[Subadai]

OK, had to Google the windbg commands, hope I got it right. Here is the dump. The windbg docs weren't clear on how to catch all exceptions, but I noticed before that when I cast a buff it was throwing an EH ('(464.8bc): C++ EH exception - code e06d7363 (first chance), (464.e14): C++ EH exception - code e06d7363 (first chance)') so I had it catch EH and produce a dump.

[Trumpy]

Fix pointer reference which generated target name gibberish (hopefully fixed)

That is so weird. I havent updated to this newer version from the previous yet, but all last night names on buffs were perfectly ok. then i read you fixed this and today Haste has bunch of gibberish for when cast on my main character and no name when cast on my mule. Does this stuff just go wacky after a certain amount of time or what? Also were we aware Reraise is not showing up in the buffs duration list still?

[Motenten]

Also were we aware Reraise is not showing up in the buffs duration list still?

It should, if it's been properly set in resources. I'm not sure which of the latest resource corrections have been pushed out, but you can edit windower/res/spells.lua and make sure Reraise has duration=3600.

OK, had to Google the windbg commands, hope I got it right. Here is the dump. The windbg docs weren't clear on how to catch all exceptions, but I noticed before that when I cast a buff it was throwing an EH ('(464.8bc): C++ EH exception - code e06d7363 (first chance), (464.e14): C++ EH exception - code e06d7363 (first chance)') so I had it catch EH and produce a dump.

Ok, added a check to prevent that crash from occurring. However the fact that that -could- crash seems indicative of the type of corruption that could cause the name display issue. Will need to dig deeper into this.

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

[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.

Played with this for a couple hours last night and no problems found. Load/unload/reload all worked just fine. Also tried Ctrl-a, Ctrl-c, Alt-a, Alt-c, etc. All the Ctrl- and Alt- combos worked without a problem.

[Subadai]

It should, if it's been properly set in resources. I'm not sure which of the latest resource corrections have been pushed out, but you can edit windower/res/spells.lua and make sure Reraise has duration=3600.



Ok, added a check to prevent that crash from occurring. However the fact that that -could- crash seems indicative of the type of corruption that could cause the name display issue. Will need to dig deeper into this.

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

I'll give it a try shortly.

[Subadai]

So far so good with 3.4.0.2, I'll report back if I find anything.

[KuKuKaChoo]

3.4.0.2 has been 100% solid for me with a few hours of use.

[geno3302]

Just crashed a few min ago. Been getting very random crashes for the last few months. Nothing ever seems to be the same so this time I launched the debugger to see if I could pull anything from it. I was in port jeuno browsing the AH and then crashed. Here's the assembly if it helps at all:

05A67C80  mov         edx,dword ptr [esp+8]  
05A67C84  push        ebx  
05A67C85  mov         ebx,dword ptr [esp+8]  
05A67C89  push        esi  
05A67C8A  mov         esi,ecx  
05A67C8C  push        edi  
05A67C8D  mov         edi,edx  
05A67C8F  or          ecx,0FFFFFFFFh  
05A67C92  xor         eax,eax  
05A67C94  mov         dword ptr [esi+4],ebx  
05A67C97  mov         dword ptr [esi+8],edx  
05A67C9A  repne scas  byte ptr es:[edi]  
05A67C9C  mov         edi,dword ptr [esp+18h]  
05A67CA0  not         ecx  
05A67CA2  dec         ecx  
05A67CA3  mov         dword ptr [esi+10h],edi  
05A67CA6  mov         dword ptr [esi+0Ch],ecx  
05A67CA9  or          ecx,0FFFFFFFFh  
05A67CAC  repne scas  byte ptr es:[edi]  
05A67CAE  not         ecx  
05A67CB0  dec         ecx  
05A67CB1  cmp         ebx,3  
05A67CB4  mov         dword ptr [esi+14h],ecx  
05A67CB7  ja          05A67CE6  
05A67CB9  jmp         dword ptr [ebx*4+5A67CECh]  
05A67CC0  mov         dword ptr [esi+18h],0  
05A67CC7  pop         edi  
05A67CC8  pop         esi  
05A67CC9  pop         ebx  
05A67CCA  ret         0Ch

Crash happened at 05A67C9A. es:[edi] is zero. Google says the ES register can be used for pointing to video memory and there is hook.dll and d3d8.dll in the call stack if it's accurate, maybe some lua plugin rendering issue?

Call stack

Spoiler: show

 	FFXiMain.dll!05a67c9a()	Unknown
 	[Frames below may be incorrect and/or missing, no symbols loaded for FFXiMain.dll]	
 	FFXiMain.dll!05a67c6f()	Unknown
 	FFXiMain.dll!05a6b040()	Unknown
 	FFXiMain.dll!05a6c216()	Unknown
 	FFXiMain.dll!05aee194()	Unknown
 	atiu9pag.dll!6a903d59()	Unknown
	d3d8.dll!5ea8f913()	Unknown
 	d3d8.dll!5ea7c204()	Unknown
 	Hook.dll!0297e527()	Unknown
 	FFXiMain.dll!05a39f49()	Unknown
 	FFXiMain.dll!05a3adc2()	Unknown
 	FFXiMain.dll!05a3aed2()	Unknown
 	FFXiMain.dll!05a33377()	Unknown
 	FFXiMain.dll!05a6f51f()	Unknown
 	FFXiMain.dll!05940f69()	Unknown
 	Hook.dll!0298053f()	Unknown
 	user32.dll!75d290b9()	Unknown
 	user32.dll!75d2908d()	Unknown
 	uxtheme.dll!72af6e9f()	Unknown
 	user32.dll!75d26381()	Unknown
 	user32.dll!75d162fa()	Unknown
 	user32.dll!75d16d91()	Unknown
 	user32.dll!75d16210()	Unknown
 	user32.dll!75d26cbc()	Unknown
 	user32.dll!75d26c87()	Unknown
 	FFXiMain.dll!05bfe782()	Unknown
 	FFXiMain.dll!05931b4b()	Unknown
 	FFXiMain.dll!059315dc()	Unknown
 	FFXiMain.dll!0594483b()	Unknown
 	FFXiMain.dll!05944077()	Unknown
 	FFXiMain.dll!05943f69()	Unknown
 	FFXiMain.dll!05943d09()	Unknown
 	FFXi.dll!025b4e57()	Unknown
 	kernel32.dll!76bc241b()	Unknown
 	kernel32.dll!76bc2422()	Unknown
 	ole32.dll!7661a5ed()	Unknown
 	kernel32.dll!76bc22f2()	Unknown
 	ntdll.dll!77db7f04()	Unknown
 	ntdll.dll!77db7f04()	Unknown
 	ntdll.dll!77db7f04()	Unknown
 	ntdll.dll!77de4096()	Unknown
 	ntdll.dll!77de3ff9()	Unknown
 	ole32.dll!7663a6c2()	Unknown
 	ole32.dll!7663a1bd()	Unknown
 	ole32.dll!7663a61f()	Unknown
 	ole32.dll!7663a6c2()	Unknown
 	ole32.dll!7663a1bd()	Unknown
 	ole32.dll!7663ab0f()	Unknown
 	KernelBase.dll!76942e44()	Unknown
 	polcore.dll!03bd179f()	Unknown
 	pol.exe!0041320c()	Unknown
 	pol.exe!004140ce()	Unknown
 	pol.exe!00416060()	Unknown
 	ntdll.dll!77d9fbea()	Unknown
 	kernel32.dll!76bc88d2()	Unknown
 	KernelBase.dll!76942f08()	Unknown
 	pol.exe!004061a1()	Unknown
 	pol.exe!0042df28()	Unknown
 	pol.exe!0042df31()	Unknown
 	ntdll.dll!77d9faea()	Unknown
 	ntdll.dll!77dc1092()	Unknown
 	pol.exe!0042a70f()	Unknown
 	pol.exe!0042ce3b()	Unknown
 	pol.exe!004252bd()	Unknown
 	pol.exe!004256a3()	Unknown
 	pol.exe!004256ad()	Unknown
 	pol.exe!00425b34()	Unknown
 	kernel32.dll!76bc338a()	Unknown
 	ntdll.dll!77db9f72()	Unknown
 	ntdll.dll!77db9f45()	Unknown

Code block from hook.dll

Spoiler: show

0297E4FE  int         3  
0297E4FF  int         3  
0297E500  push        ebp  
0297E501  mov         ebp,esp  
0297E503  push        ecx  
0297E504  mov         eax,dword ptr [ebp+14h]  
0297E507  push        eax  
0297E508  mov         ecx,dword ptr [ebp+10h]  
0297E50B  push        ecx  
0297E50C  mov         edx,dword ptr [ebp+0Ch]  
0297E50F  push        edx  
0297E510  mov         eax,dword ptr [ebp+8]  
0297E513  mov         ecx,dword ptr [eax+4]  
0297E516  mov         edx,dword ptr [ebp+8]  
0297E519  mov         eax,dword ptr [edx+4]  
0297E51C  mov         ecx,dword ptr [ecx]  
0297E51E  push        eax  
0297E51F  mov         edx,dword ptr [ecx+0FCh]  
0297E525  call        edx  
0297E527  mov         dword ptr [ebp-4],eax  
0297E52A  cmp         dword ptr [ebp-4],0  
0297E52E  je          0297E53C  
0297E530  mov         eax,dword ptr [ebp-4]  
0297E533  push        eax  
0297E534  call        029632B0  
0297E539  add         esp,4  
0297E53C  mov         eax,dword ptr [ebp-4]  
0297E53F  mov         esp,ebp  
0297E541  pop         ebp  
0297E542  ret         10h

[Sechs]

So far so good with 3.4.0.2, I'll report back if I find anything.

Likewise, didn't notice anything but it has to be said I played on DNC and PUP over these hours. It usually takes a job like BRD (a plethora of AoE and single target buffs over a short amount of time) to see issues in Timers.


Slightly OT:
1) Is the mobcompass Addon outdated? Haven't used it in ages and when I tried yesterday I was getting errors. Nobody mantains it anymore?
2) I seem to recall there was an addon developed by Byrth to track DNC steps, but yesterday I couldn't find it anymore. Did I dream about it or did it really exist?

[Miroku_Asura]

Hey guys- so quick question. I'm unable to take screenshots in windower with the key I have assigned to print screen (f14) for some reason. It's able to take screenshots outside of Windower just fine, but it's not working in game for whatever reason.

Here's my init file:

Spoiler: show

//Bind keys
//Bind syntax is "bind <key> <up> <command>
// ^ represents control- and ! is alt, eg !1 is alt-1
bind !f10 drawdistance set 10
bind ^f10 drawdistance set 1
bind f11 game_forceambientlight
bind f12 showfps
bind sysrq screenshot png hide
bind ^v paste
echo Toggle Lighting = F11 (Bump mapping must be off to work properly)
echo Toggle FPS = F12
echo DrawDistance Lv 10: Alt-F10
echo DrawDistance Lv 1: Ctrl-F10
echo Paste Clipboard = Ctrl-V

[ZetaEpyon]

Hey guys- so quick question. I'm unable to take screenshots in windower with the key I have assigned to print screen (f14) for some reason. It's able to take screenshots outside of Windower just fine, but it's not working in game for whatever reason.

Windower uses a manual keybind for screenshots, you need to change this line:
bind sysrq screenshot png hide

[Sechs]

Some major issues with 3.4.0.2 for me, I'll edit this post and explain better once event is over, had to revert to 3.4.0.1 temporarily.
Everything seemed ok on DNC and PUP yesterday, but major stuff on BRD today.


edit:
Should really test more, these things I'm about to say will probably sound confusing and won't help much =/

1) Getting an error when I log in game, saying Timers encounterd an exceptions and it auto unloads. This happens with 3.4.0.1 as well though.
2) It wasn't tracking all songs. While doing the Balhran fight it was tracking only the first 2 songs sung with horn, not the rest. After that it was a bit random. Some songs just wouldn't appear on timers no matter the order they were sung. (for instance no victory but Advancing was appearing there). It was a bit random, considering both songs got tracked correctly before in the Balrahn fight.
3) It crashed a couple of times (just timers, not the game) with the same error I get when I login


OT1: it seems that lv75 Carnwenhan +duration boost is not calculated into Timers? Not that it matters tbh, just saying lol
OT2: Motenten since I got told you're the one in charge for it now, the Screenshot plugin is giving me a strange message. It does work correctly but whenever I take a screenshot I get two lines. One saying "screenshot was saved as blahblah", and a second line saying "fooo". Other than that it seems to be working fine O.O


Edit2:
Yeah cannot replicate the situation where it starts tracking only 2 songs... it just happens, I can't tell what triggers it.

[Damane]

timers plugin unload itself after I casted warp

error: Access violation in IncomingChunk method.

[Trumpy]

I have accidently hit the screenshot key a couple times and i also noticed the fooo

Yesterday I had gone back to the timers that comes in the release version of windower after a morning full of crashes ( 3.3.0.8 One happened when i hit my sneak attack ws and trick attack ws macros in short succession cause i just plainly hit the wrong one first). So i saw the newest version and decided to try it out last night. It was finally listing reraise in the buff durations but haste wasnt showing who it was cast on. So i was doin dynamis like at 5-6am fighting falling asleep. At one point i engaged a mob and was fighting it for a few seconds when a bst mob ran up. I like to sleep hecteyes cause of dispelga but naturally sleepga doesnt work for them so i have to manually switch to my mule to cast repose on it. So when i alt tabbed to the mule to do so after a few seconds my main crashed. Now i dont think my main was doin anything but meleeing so im not sure what caused it but a friend of mine was talkin to me bout crashes earlier in the day and he said alot of times its when he (He said he isnt using the new timers) switches windows from mule to main or vice versa or even switchin to a internet browser. This crash is the first time i noticed that might have been caused by switching windows.

After the crash i killed the mob on my mule went into the corner to reboot ffxi for both (the previous night's crash caused send to not work between the two so i decided to jsut relog on both to be sure) and also i deleted the new timers and installed the released version again. I never seem to crash at all when i go back to release (I dont play bard either so i dont have those type crashes) So could timers somehow crash due to switchin from one character to the others window? or might that be something else? the only other thing i can think of is i have been using that assistme addon someone posted earlier in this thread but i dunno if that would be the culprit either.

[Motenten]

: Motenten since I got told you're the one in charge for it now, the Screenshot plugin is giving me a strange message. It does work correctly but whenever I take a screenshot I get two lines. One saying "screenshot was saved as blahblah", and a second line saying "fooo". Other than that it seems to be working fine O.O

The only plugin I'm working on is Timers.

it seems that lv75 Carnwenhan +duration boost is not calculated into Timers? Not that it matters tbh, just saying lol

Carn 75 should be accounted for already.

It wasn't tracking all songs. While doing the Balhran fight it was tracking only the first 2 songs sung with horn, not the rest. After that it was a bit random. Some songs just wouldn't appear on timers no matter the order they were sung. (for instance no victory but Advancing was appearing there). It was a bit random, considering both songs got tracked correctly before in the Balrahn fight.

There seems to be a lot of issues with packet info for Timers. Arcon changed it from relying on memory to having it rely on packet data for creating and destroying timers. However the deduplication code in Hook appears to interfere with a significant number of effects (though not all the time), leaving Timers without the data it needs to actually create some of the timers.

I'm still going through and trying to figure out what may or may not be working, and when.