Windower 4 - Discussion and Support

[Martel]

As of this morning, Autoexec isn't loading for me, and when I try to load it from console, one of my other plugins crashes with "plugin encountered a fatal error and must be terminated. Error: access violation in Initialize method." The plugin that crashes depends on what I have loaded, apparently. I had TParty plugin loaded, and that crashed, when I deselected it in the launcher, Timers began crashing instead.

I'm seeing the same issue, with one difference.

While it says TParty crashed, it didn't. Even after getting that msg, TParty remained loaded, and functioning. Kinda makes me think it's just referencing the wrong name when dealing with autoexec.

[JSHidaka]

Yea, autoexec isnt loading... and when try to //load autoexec.... faltal errors.

[BahamutRicker]

Is there any way to tell if a mob is claimed to my party or alliance?

Looking at the function windower.ffxi.get_mob_by_id(id), there doesn't appear to be a way.

[Casey_]

This http://files.bluegartr.com/75643c0b5...12f97dbb50.zip

is crash dump for initial CS on https://www.bg-wiki.com/bg/What_Price_Loyalty
I talk to Gentle Tiger, I hear the music change after the fade to black, then I crash.

First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
*** WARNING: Unable to verify checksum for FFXiMain.DLL
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FFXiMain.DLL - 
FFXiMain!DllUnregisterServer+0x103340

Curious.

I'm going to stay on this crashable state for a day or two, I'd like to be able to do the rest of the missions, but in the name of Science I will stay for any attempted debug fix builds.

I do not crash without windower, and I force terminated to leave my mission state alone.

edit: Feel free to contact me for any extraneous info you may want or need.

[Arcon]

I'm going to stay on this crashable state for a day or two, I'd like to be able to do the rest of the missions, but in the name of Science I will stay for any attempted debug fix builds.

Much appreciated

Unfortunately, I don't have much time to devote to this until Tuesday, and I hate to hold you up >< But I'll see what I can do until then.

Also, the dump you provided is a 64-bit dump. Since this is a 32-bit process we either need a 32-bit dump or a 64-bit dump that includes full heap information. Either will work, the latter might be pretty huge (hundreds of MB), but we'll take either one.

[Casey_]

I'll get you a 32bit dump. This week is reasonable, I can just switch nations to do fiat lux anyway. Wonder if that resets campaign op "tags" hmmm...

[Casey_]

Attaching the 32 bit windbg prevents the crash!

Ticket closed, halfass workaround implemented.

But seriously..

I did a .dump /ma in the console on 64bit windbg. Don't know if you wanted that or /f, but here's a link:

https://mega.co.nz/#!oEVDGKRQ!d18J4X...4g_D1BE-OwaSYY

[Arcon]

The crash dump is not very helpful I'm afraid... it indicates an error outside of Windower. It could be a Hook that we messed up, which is not only very hard to debug but impossible to fix, as we don't have the source of the hooking library we use :\

It could be other things, but none of them are very easy to debug. I'm not sure what to tell you, but since you can just skip this one I suggest you do it, and we'll leave it to v5 to fix (which will make a lot of debugging things much easier, if they're even necessary there).

[Casey_]

That's a shame. I tried!

[Casey_]

Update:

When attaching the 32bit debugger I cannot continue in the CS chat. I can press enter, or click and I can hear the sound for accepting the chat and for the next one to print, but it never comes.

edit: What Gentle Tiger says is a HUGE wall of text, I wouldn't be surprised if that may be part of the issue. Timestamp really messed up the chat.



I also captured a .dmp for the infamous click in window and the game freezes but the printout was like this again.

*** WARNING: Unable to verify checksum for FFXiMain.DLL

Makes me think it may not lead anywhere, but here it is:
https://mega.co.nz/#!oMUDlZyS!GhbCcc...XIjJo0RS4VSKEU

[Arcon]

Crash dumps are generally not very useful for game freezes, because we have to sift through all the threads (and there are a lot) and see what's waiting for the mutual resources. It's generally not possible to debug from a crash dump alone unless we get very lucky, which we very rarely are. I've never experienced that myself, is there any way to reliably reproduce it? If so, debugging might be possible.

[Casey_]

There's no one true way of doing it. Sometimes I won't get it all day but other times I'll get it repeatedly in a small time span.

All i'm doing is clicking into a firefox/chrome browser, or into steam, then clicking back in. Eyeballing jokes aside, it seems to happen if I click in and out too many times in a shorter period of time. I imagine an autohotkey script spamming the heck out of the click in/out might be able to produce it quickly. I'll try that later.

[Karizo]

It seems like the bug with gearswap where certain gear slots will be ignored have reappeared. Usually goes away after reloading gearswap or the job lua a few times, but sometimes I don't catch it. Has anyone experienced similar things since the most recent patch?

[Damane]

keyboard lock seems buged/doesnt happen on gearcollector.

[Snprphnx]

gearcollector is working, however, the menus are not opening up. some gear is being skipped over

[Arcon]

gearcollector is working, however, the menus are not opening up. some gear is being skipped over

That may have been due to outdated resources. Does it still happen now?

[Arcon]

keyboard lock seems buged/doesnt happen on gearcollector.

Yeah, as discussed here, this is currently an oversight (I changed some of the code and I wasn't aware that it blocked keyboard input before). I may add an option to enable it, but not really sure why. I'll think about it.

[Martel]

Yeah, as discussed here, this is currently an oversight (I changed some of the code and I wasn't aware that it blocked keyboard input before). I may add an option to enable it, but not really sure why. I'll think about it.

I'd always assumed that blocking keyboard input was somehow necessary to gearcollector 's functionality. If it's not needed, then great. It was annoying to have to type replies via the console while it was running.

[Arcon]

Maybe it originally worked by sending key presses, but even before I worked on it now it was entirely packet-based. Opening the menu is also entirely cosmetic and doesn't do anything, I will disable it by default.

[Trumpy]

I thot it was cause arrow keys can still mess it up when u push up and down or left/right same thing with when you mouse over your item list it sometimes moves the pointer.