Windower 4 - Discussion and Support

[Sechs]

I'm still getting the following issue very often since the last patch (delve etc).
Been told "unload and reload Timers when it happens, usually fix it" but it doesn't. When I do that, the console gets crazy (see the screenshots below)

http://imageshack.us/a/img163/4156/timers1.th.jpg
Uploaded with ImageShack.us

First screenshots is what happens when I unload/load Timers, console goes crazy.
Second screenshot is when I get the fullscreen "semitransparent layer" making the screen darker. In this particular screen I had TWO, a fullscreen one and a partial one.
Can also see a blank line on the right (yarnball) and different colours for buffs (grey and white).

How do I solve this, really? Sometimes Timers works so smoothly it's perfect, then after a while it just gets crazy like that

[grevenilvec75]

try unloading consolebg and statustimer

[Sechs]

I don't use statustimer, unloading consolebg did nothing a while ago when I had that situation (second screenshot) but I'll try another time if it happens again. (it totally will >.>)

[Gwynplaine]

Mip mapping is set to 0 (off?), resolution is 1024x768, bg res is the same when sampling is off

Try setting the mip mapping to 3, the thing your describing might be because of the sharpness of the full textures in the distance.

[Carraway]

I'm still getting the following issue very often since the last patch (delve etc).
Been told "unload and reload Timers when it happens, usually fix it" but it doesn't. When I do that, the console gets crazy (see the screenshots below)

First screenshots is what happens when I unload/load Timers, console goes crazy.
Second screenshot is when I get the fullscreen "semitransparent layer" making the screen darker. In this particular screen I had TWO, a fullscreen one and a partial one.
Can also see a blank line on the right (yarnball) and different colours for buffs (grey and white).

How do I solve this, really? Sometimes Timers works so smoothly it's perfect, then after a while it just gets crazy like that

The console bug is independent of the transparency bleeding from Timers. Look for Timers.xml in your windower4/plugins/settings directory and change the bgA, bgR, bgG, and bgB fields to zero.

[Sechs]

The console bug is independent of the transparency bleeding from Timers. Look for Timers.xml in your windower4/plugins/settings directory and change the bgA, bgR, bgG, and bgB fields to zero.

I think there might be a link though, because whenever the transparency thing happens and I start unload/reload timers the console bug (which happened to me a couple of times on 3.4 too) always happen. Usually on the first reload, if not in the next one.

Tried the /unload consoleBG btw, this is what happened (i.e. nothing)
http://imageshack.us/a/img59/7910/timers3.th.png


I swear I had this bug a lot on the first days of windower 4 but it slowly went down. Until the last patch (delve) and successive windower4 updates I was hardly getting it.
Did something break up in my installation? Some of my friends weren't even aware of this bug, meaning it never happened to them.
Seeing how often it happens to me I can't believe it.

[Fake]

Send is back to causing the char commands are being sent to to freeze, and when char is reloaded it won't send to the reloaded char until every char is reloaded.

[grevenilvec75]

//bmn disable/enable doesnt seem to work anymore

[Obsidian]

Game's been very choppy for me since the update today. No idea why.

[TacoTaru]

Nevermind, whatever it was seemed to have cleared itself up.

[Sithel]

Trying to look through some pages here and on windower and not finding info, but Scoreboard randomly quick working. Loads fine but just sits there and says "Waiting for results" //sb reset does nothing and not showing and parsing at all. Ideas?

[noodles355]

For some reason today timestamp isn't working. Nothing's changed since my last log in (no updates either), however today, even though the plugin is loaded, it's not showing in the log. Unloading/reloading doesn't make it appear.

[Arcon]

For some reason today timestamp isn't working. Nothing's changed since my last log in (no updates either), however today, even though the plugin is loaded, it's not showing in the log. Unloading/reloading doesn't make it appear.

There are certain things that can interfere with Timestamp, but they're intermittent and usually fixed upon Timestamp's reload (ffocolor.lua for example, although I don't think you use that). Does it persist after relogging?

[noodles355]

Derp. Don't worry, it's fine. I just ran windower 3 by mistake without noticing >.>

[Buffy]

Haven't played in about a week, was gonna clean up some stuff on mules before accounts turn off.

Any reason my Windower 4 launcher is taking forever to launch?

[Bingbong]

Getting the same thing, www.windower.net isn't responding, so I'm assuming the auto updates aren't loading, hence the hangup

[Fake]

The delay also seems to make freezing when logging in possible. I had to log in 3 times because the first 2 times I would freeze while it was loading all the plugins which got backed up waiting for resources to update.

[grevenilvec75]

Happening to me too.

That whole "disable automatic updates" thing is looking better and better.

[Sechs]

fixed it

[crux]

Had Windower 4 working fine yesterday. Had to reinstall Windows 7 to fix some sound distortion on my new build, and upon reinstalling Windower4 it doesn't want to launch POL. It also isn't downloading the plugins database, though add-ons are accounted for, if that's relevant. I'm stumped. PlayOnline and FFXI boot fine sans Windower.

Here's the crash log:

Spoiler: show

System.TimeoutException: The operation has timed out.
at #=qqAzPRWz$RssPKfk0jUZ$WCjp8nopLLO9t9sTGipaG5Y=.#= qq6o8s_4$CV5qmty7aDpXcQ==(#=qPm9BNL3SiV0sOAYpWtx42 5myfcWJq6lbag6RFwBzBCs= #=qG2SARFf0vXqceHhYVwNoug==, String #=qlo1fBfSYicE$ixwnsC3uWg==, #=qiiAOl5GPj6DXsDvP2Kdi7w== #=q113362DYQ2RlYX3Ca1e7Og==, TimeSpan #=qPg2TgCAk6GOBreydtbq_Rg==)
at #=qqAzPRWz$RssPKfk0jUZ$WCjp8nopLLO9t9sTGipaG5Y=.#= qYiV2gsygzf1MqdSmf_sUiQ==(String #=qXGQR6A2pK4bYx3UIwD9kPQ==, #=qV_vdXJWxFe82jBde5nTWZNpU5N6zKCFTkYVR28Q6PJQ= #=qm$kpPhSY99mSZfKvwcQdtg==, TimeSpan #=qDfv1C4VSYhzJGIXE3L_ZyQ==)
at #=qqAzPRWz$RssPKfk0jUZ$WCjp8nopLLO9t9sTGipaG5Y=.#= qswaxzuXUpRrG1TBx6_ctbA==(String #=q3G6Bu4p7cm89Y1nXoqM4Sw==, #=qV_vdXJWxFe82jBde5nTWZNpU5N6zKCFTkYVR28Q6PJQ= #=qoF8XYRBkEKpZTIfxksI1ag==)
at #=qE_Gmewu1xJSvcdNgw8QTigHdtg9gjRFqivu3anVY95o=.#= qnQCMKMqRLmsGND5_yA3M5Q==()
at #=qAlk$Mw_tywKjs9rd7cyoVByKGVe3vaaXeS_LGtl1hBE=.#= qfyJ2oWactrEI0jMMW5DrEA==(#=qmhNvAyztrFon0QQMItVoE w== #=q$_uA1omHXJgXxHzgfPGREA==)
at #=qmhNvAyztrFon0QQMItVoEw==.#=qav9FVComJWu2k_c7i_y B0A==()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.RunInternal(Exec utionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()