You can definitely re-direct specific types of messages to separate text box, but it wouldn't be scrollable like the real game text log.
You can definitely re-direct specific types of messages to separate text box, but it wouldn't be scrollable like the real game text log.
Oh you're right, I've noticed my plugins have updated as well, good catch. I'll attribute it to that until I see otherwise. Thanks!
I was getting those mini-freezes and just set Timers' graphical mode to False. No freezes since.
Confirmed Windower4 ignores the resolution settings (and likely all other settings) that you put into XI-Utils.
I'd really love a solution for this, anything we can do, even manually inside the settings.xml file?
The graphical-but-still-going crash appears to be linked to Timers, yes.
http://forums.windower.net/topic/219...ost__p__219241
btw, unloading timers causes this crash too >.<
There was something I noticed about the last time an update broke a bunch of windower stuff: most of that was remedied by zoning. Might wanna look into that. Perhaps there's a cleanup or initialization or resources thing that's only getting tripped by zoning at least once. Not zoning makes the Timers crash happen almost instantly, when it can take hours otherwise.
Tried moving super sampling to .5 and game still can't run 2 instances over 2 fps, any other ideas on the fps problem?
Running a Intel Core 2 Duo, 3.16 ghz, not sure if that what you asking, but the computer could tribox fine back with 3.4 without any fps lost, figured I'd try to upgrade to 4.0 and try and getting crap results so far...just hoping they get the new 3.4 and get binder fixed...
Transferred all my binds over to windower 4 until windower 3.4 is fixed and send on xiutil seems to be crashing me whenever I use my send binds
Crashed on homepointing from Rala Waterways to Western Adoulin. Timers wasn't loaded. Might have been mid-gearswap like Spellcast didn't detect I was dead or something.
By the way the two incriminated registry Keys are n° 18 and n° 19.
18 has to be to value "2" to be to uncompressed.
19 has to be to value "1" to be uncompressed.
Basically 18 is Texture compression and 19 is On-screen Maps.
Temporary solution to this would be making the Whole FinalFantasyXI key in the registry a read-only folder. That way Windower4 won't be able to write values in there and, hence, change anything.
I have no clue how to do it, but in theory it should work.
Also question about two plugins:
1) WinControl - what is it for? I think I assumed it was for something different
2) Timers - I understood what graphicalMode (true/false) is, but slimMode (true/false)? What does it do?
Some programs really don't like it if you do that. It looked like from the other link that it will be fixed
In the meantime this is safer.
(This is for NA win 7 64 bit... Win 7 32 bit and XP will different)
Copy thatCode:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PlayOnlineUS\SquareEnix\FinalFantasyXI] "0018"=dword:00000002 "0019"=dword:00000001
name ffxi.reg
Launch FFXI with win4
Click ffxi.reg and import
Play normally
I've noticed while on smn mostly, that occasionally I'd get no numerical countown. Normally I wouldn't care but on smn I always glance to make sure my bp gear is getting equipped etc. Any ideas why this could have happened?