Windower 4 - Discussion and Support

[Buffy]

Go to Timer's settings file and use <graphicalMode>false</graphicalMode> to reduce the frequency of those crashes.

Byrthnoth, since you are involved in that, I assume someone is looking into fixing it? The regular timer is fine, but the graphic mode one is prettier XD

[Byrthnoth]

I'm not actually involved in that. That's Ihm's ball of wax!

The last time I saw him respond to a post about it, he said that it's actually a fundamental problem with the Windower hook. Apparently every time windower tries to do something graphical (something something primitive), there's a chance of a crash like that. The difference is that most plugins generate 0-1 primitive the entire time they're on, while Timers in graphical mode generates 7 per timer (1 per timer in non-graphical mode). So even if it's something that won't happen 99.9% of the time, in graphical mode you're would hit it every 143 casts. In non-graphical mode, every 1000 casts.

So that's what is happening, and Aureus and Ihm are collecting crash dumps and trying to figure out why it happens/how to fix it.

[Fake]

I know there can be performance issues with spellcast if you have lots of rules/variables.

I had a number of spellcasts working on 3.4 that had little/no performance loss when using triggers/JAs/spells, however on 4 even my more simple spellcasts seem to have a large fps drop (from 29 to 26-23 and down to 20 with repeated use) with the more extensive spellcasts causing the game to lock up very briefly.

Is this a known issue on 4 or is there an easy fix to this?

[Byrthnoth]

I'd recommend swapping between 3.4 and 4 to convince yourself of this while doing the same spellcast, but there's no functional difference between 3.4 and 4.0's Spellcast. If you are noticing a difference, it's because of something else (like interactions with your video drivers). If that's the problem, I don't really know the fix. Some people have had luck upgrading their graphics drivers with Windower 4.

The biggest source of spellcast lag is variables. Eliminate as many of them as you can and you'll be fine.

[Fake]

Restarted my PC and it seems to have cured the problem mostly, seems odd though unless I was running out of memory or something (doesn't make sense though since I was on 3.4 and 4 at the same time running the same xml and there was a huge difference).

[chichicha]

sorry, I haven't been following this thread, has LightLuggage been fixed?
It crashed game occasionally. idk why...
Window 7 , Windower 4, and Game configuration Set to Manual.

[Buffy]

You sure it's LL and not timers? The timers issue appears fairly confirmed at this point.

[Fake]

Last issue I'm having with windower4 is for consoleBG, attainment, infobar, pricer(xiutil) the majority of the text is glitching and not displaying. For infobar its usually the first 1/3 of the text that disappears when I'm not targeting anything or targetting a mob (beginning displays when I'm targetting NPCs/PCs), similar for attainment. For consolebg/pricer, all but the last 1-2 lines at the bottom aren't displaying. I have a picture from a while back of what I mean

[Suteru]

Yeah, something is definitely going on with the way text is drawn to the screen. I've been getting that with attainment and the console. Timer seems unaffected though.

[sfchakan]

Got an idea for an add-on: Reive timer. Sometimes you run just inside the range of one or are forced to walk through a lair to get somewhere. Wouldn't this be pretty easy to do?

[Reg]

i'm having a weird problem where my game "freeze" so my screen is staying on the same image, but in reality it's still going on because if i'm staying next to that character it's still doing something (in this case using sc loop for skillups) any idea how to fix it or what's causing it?

[Eldelphia]

i'm having a weird problem where my game "freeze" so my screen is staying on the same image, but in reality it's still going on because if i'm staying next to that character it's still doing something (in this case using sc loop for skillups) any idea how to fix it or what's causing it?

Think that's a known issue, seen others report the same thing.

[Reg]

ok thanks for the answer i'll wait for a fix then!

[chichicha]

You sure it's LL and not timers? The timers issue appears fairly confirmed at this point.

ok, i'll check again, next time it crashed. hopefully like you said it's only timers causing.

[Obsidian]

I'm curious, is anything being done to fix the weird texture compression on aura effects? Lights look 8-bit and having just been on SMN for the first time, I noticed it affects avatars too. I tried changing the texture compression in FFXI config, but it seems to just get forced to High every time the game launches.

[Corkadile]

Interesting, mine gets forced to Low and then maps get forced to Compressed.

[TacoTaru]

Tried setting up binder to use with my Blackwidow Ultimate, but I can only get it to recognize my Naga. I made sure the profile was set to default and tried relaunching, but it's still only recognizing my mouse. Am I doing something wrong?

[Draylo]

Any idea why the light effect doesn't extend past mobs/characters/objects like normal? It doesn't light the area up, just those specific things.

[Jem]

Not sure if anyone will be able to help because I can't provide a crash dump atm and I doubt details are enough to troubleshoot with. Gonna throw it out there anyway just in case someone can though.

Fresh install of Windower 4 on the wifes laptop, nothing changed whatsoever (although did get the same result after tinkering too). POL Crashes directly after hitting launch.

Process is: Boot up Windower 4 > Hit launch > Crash error message for POL before any POL screen displays.

I don't think it's a POL issue as it boots up just fine with Windower 3.4 (maybe 3.3 she uses, I'm not 100% sure). Any idea what could be causing it / how to fix it? This is on Vista if that makes a difference.

[Arcon]

Process is: Boot up Windower 4 > Hit launch > Crash error message for POL before any POL screen displays.

I don't think it's a POL issue as it boots up just fine with Windower 3.4 (maybe 3.3 she uses, I'm not 100% sure). Any idea what could be causing it / how to fix it? This is on Vista if that makes a difference.

If the crash happened in the launcher, there should be a crash.log file in the Windower directory.