Keep in mind that to keep the onscreen damage be placed in the correct position, the oversampling needs to be in a 1:1 format.
It has to be a square, not a rectangle like, typically, all other resolutions are.
Using a rectangular oversampling will still produce nice results graphically, but the position of onscreen damage will be a bit out of place.
Most people don't even notice this tbh, so it's probably not a big deal.
hmm I did turn surpersampling on, it had it set to 2, log on, /shutdown, set it to 0.5, launch windower and it deleted it again! I guess I'll wait and hope it get easier to use or I somehow figure what I did wrong at some point !
Ok.... So is there any news on when the older version will be fixed soon? Because I cant stand 4 anymore..... Had it three days and its done nothing but *** up my game. None of my scrips work now *yes I moved them* My Resolution is *** terrible now. I cant move the new recast from covering my battle menu, and it freezes all the time when loading. Please tell me we can go back to the old one soon.
Your scripts not working are your own fault, you obviously haven't moved them correctly or something.
You can EDIT the resolution settings... v4 won't make your game look worse -_-.
You CAN move timers, its only been discussed about 5 million times in this thread, just edit plugins/settings/timers.xml.
Do you want to be a drama queen a little more, sheesh.
If you don't like it, then just don't use it.
You can also change the <slimmode> tag to true in the plugins/settings/timers.xml and they take up about half as much space.
So I downloaded windower4 yesterday and it works amazingly well!
<3 all the work you guys put into it.
The only thing I haven't been able to get working is the scripts; I copied/pasted the old 3.4 scripts file into windower4 file, and I still get a "pathway cannot be found" or "file does not exist" message.
I read through the last 10 pages and it seems like scripts are working for people, I'm just not sure what to change. I moved the windower4 file onto desktop; was completely empty when I first downloaded it so I created a "scripts" folder and transfered everything from 3.4. I can't actually launch windower4 from this file; only from the start menu or a shortcut on desktop (possible I'm looking at the wrong windower4 file or is this normal?).
So far commands like bind !1 input "hello"; and such work great, I just haven't been able to exec any file without the "cannot be found" message.
Let me know if you all have ideas, thanks in advance :)
EDIT: finally found the right file!! It wasn't showing up under a start menu search; I found a different windower4 file when I selected the shortcut to start the game and clicked "open file location". Scripts working now ^-^
first off, windower 4 beta seems great everything seems to work just fine.
But I have a question about binder/windower input commands. Does it only exec. direct targets such a <t> and <me>, the <stpc> command does not seem to work correctly, it will bring up the select target for me, but it cast the spell before I can choose who to target. Then when I let the spell cool down and hit enter <stpc> works as normal but it always cast the spell first. it does the same exact thing if I type the command directly into the game. Such as //input /ma "Cure" <stpc> it will cast cure then leaving the select target arrow up to cast cure again.
first off, windower 4 beta seems great everything seems to work just fine.
But I have a question about binder/windower input commands. Does it only exec. direct targets such a <t> and <me>, the <stpc> command does not seem to work correctly, it will bring up the select target for me, but it cast the spell before I can choose who to target. Then when I let the spell cool down and hit enter <stpc> works as normal but it always cast the spell first. it does the same exact thing if I type the command directly into the game. Such as //input /ma "Cure" <stpc> it will cast cure then leaving the select target arrow up to cast cure again.
alias g11_m2g1 input /ma "Curaga III" <stpc>;
alias g11_m2g2 input /ma "Curaga IV" <stpc>;
alias g11_m2g3 input /ma "Curaga V" <stpc>;
alias g11_m2g4 input /ma "Auspice" <me>;
alias g11_m2g5 input /ma "Refresh" <stpc>;
alias g11_m2g6 input /ma "Haste" <stpc>;
alias g11_m2g7 input /ma "Cure" <stpc>;
alias g11_m2g8 input /ma "Cure II" <stpc>;
alias g11_m2g9 input /ma "Cure III" <stpc>;
alias g11_m2g10 input /ma "Cure IV" <stpc>;
alias g11_m2g11 input /ma "Cure V" <stpc>;
alias g11_m2g12 input /ma "Cure VI" <stpc>;
alias g11_m2g13 input /ma "Viruna" <stpc>;
alias g11_m2g14 input /ma "Erase" <stpc>;
alias g11_m2g15 input /ma "Esuna" <me>;
alias g11_m2g16 input /ma "Cursna" <stpc>;
alias g11_m2g17 input /ma "Paralyna" <stpc>;
alias g11_m2g18 input /ma "Poisona" <stpc>;
It broke after the major update. I think they are working on fixing it. I appreciate everything the windower team does to make this game enjoyable. This is something important to fix however =x my SMN XML file (motes) uses it. I get some locking up everytime i hit a macro.. lol
Ever since the 2013 update and changing to windower 4 i've had this odd problem with some graphic elementals in the game simply disappearing as i get close to them.
Notice how the signposts and even the balcony around the windows vanishes. Has anybody else come across this problem before ?
I've looked about on a few FFXI forums for anybody with similar problems to no avail, I've tried older and newer gcard drivers, and various different resolutions, I'm completely stumped to be honest.
Everything was working fine before the update and before switching to windower 4.
Since the update attainment seems slightly broken, it records exp and limit points fine but lights in abyssea and time remaining in abyssea and dynamis aren't being recorded.
It broke after the major update. I think they are working on fixing it. I appreciate everything the windower team does to make this game enjoyable. This is something important to fix however =x my SMN XML file (motes) uses it. I get some locking up everytime i hit a macro.. lol
The XML lag and the <stpc>/<stnpc> bug are two different things. The lag was happening with Windower4 before the FFXI patch but the st stuff didn't break until after.
As for the lag, I noticed it mostly in Dynamis for whatever reason.
Ever since the 2013 update and changing to windower 4 i've had this odd problem with some graphic elementals in the game simply disappearing as i get close to them.
It broke after the major update. I think they are working on fixing it. I appreciate everything the windower team does to make this game enjoyable. This is something important to fix however =x my SMN XML file (motes) uses it. I get some locking up everytime i hit a macro.. lol
The XML lag and the <stpc>/<stnpc> bug are two different things. The lag was happening with Windower4 before the FFXI patch but the st stuff didn't break until after.
As for the lag, I noticed it mostly in Dynamis for whatever reason.
I had some really bad lag like that awhile back. The game would skip for a sec every time I hit a macro. And would lag again when I confirmed an st target. It got way worse in dynamis. Tried various solutions, like making my XML more efficient. Or dumbing down some game settings.
Ultimately, the way I fixed it was by getting a better processor. -.-;
It broke after the major update. I think they are working on fixing it. I appreciate everything the windower team does to make this game enjoyable. This is something important to fix however =x my SMN XML file (motes) uses it. I get some locking up everytime i hit a macro.. lol
The XML lag and the <stpc>/<stnpc> bug are two different things. The lag was happening with Windower4 before the FFXI patch but the st stuff didn't break until after.
As for the lag, I noticed it mostly in Dynamis for whatever reason.
I had some really bad lag like that awhile back. The game would skip for a sec every time I hit a macro. And would lag again when I confirmed an st target. It got way worse in dynamis. Tried various solutions, like making my XML more efficient. Or dumbing down some game settings.
Ultimately, the way I fixed it was by getting a better processor. -.-;
I don't know very much about computers but I'm running on an i7 CPU 860 @ 2.80 GHz w/ 16.0 GB of RAM. I'm still getting the lock up every time i hit a macro. Its just more defined w/ my <stnpc> in erroring out in my xml file. The slight lock up was bearable before, but after stnpc broke (and something is up w/ my file) the lock ups are pretty intense now.
Ever since the 2013 update and changing to windower 4 i've had this odd problem with some graphic elementals in the game simply disappearing as i get close to them.
Notice how the signposts and even the balcony around the windows vanishes. Has anybody else come across this problem before ?
I've looked about on a few FFXI forums for anybody with similar problems to no avail, I've tried older and newer gcard drivers, and various different resolutions, I'm completely stumped to be honest.
Everything was working fine before the update and before switching to windower 4.
I don't know very much about computers but I'm running on an i7 CPU 860 @ 2.80 GHz w/ 16.0 GB of RAM. I'm still getting the lock up every time i hit a macro. Its just more defined w/ my <stnpc> in erroring out in my xml file. The slight lock up was bearable before, but after stnpc broke (and something is up w/ my file) the lock ups are pretty intense now.
running a i7 only at 3.2 gig >> does this happen on all your xmls ? may be time to clean some xmls up as your pc is fine
I don't know very much about computers but I'm running on an i7 CPU 860 @ 2.80 GHz w/ 16.0 GB of RAM. I'm still getting the lock up every time i hit a macro. Its just more defined w/ my <stnpc> in erroring out in my xml file. The slight lock up was bearable before, but after stnpc broke (and something is up w/ my file) the lock ups are pretty intense now.
running a i7 only at 3.2 gig >> does this happen on all your xmls ? may be time to clean some xmls up as your pc is fine
Just Motenten's XMLs. MNK and SMN....but they are the only jobs I play. I mean, I think that XML's w/ includes always ran with slight lag. This just feels different. A complete lock up for a split second, as Martel said its like a skip or maybe a very small stutter. Has anyone figured out why Motes SMN files bypasses the <stnpc> and still fires immediately and don't wait until confirmed target? ; ; thats a big problem for me
i try to change my <supersampling>2</supersampling> to <supersampling>0.8</supersampling> (supersampling on on win4) but when i restart my profile, i check the setting.xml and the <supersampling>0.8</supersampling> is no more here.
Each time i change <supersampling>2</supersampling> to any new value, windower delete the line. I can change setting.xml, but all time rewrite then the value is not 2.
i try to change my <supersampling>2</supersampling> to <supersampling>0.8</supersampling> (supersampling on on win4) but when i restart my profile, i check the setting.xml and the <supersampling>0.8</supersampling> is no more here.
Each time i change <supersampling>2</supersampling> to any new value, windower delete the line. I can change setting.xml, but all time rewrite then the value is not 2.
if help : Bordeless windows, 1680*950 size
plz help me,
Set your window size to 1344*760 and turn off Super Sampling. You get the same number of meaningful pixels as 0.8 Super Sampling, but you lose the aliasing problems.
Well, soon as I open my mouth on the Tip about the weather effects, it crashed on me lol Seems like I'm having issues with the KERNELBASE.dll file. Keeps crashing the POL. I have done the check files and turned off the weather effects. Also did troubleshoot Compatibility Option for POL.exe and I always get that issue. Anything else I can do to keep Windower4 Running?
shadows also off? tried on w3.4 or it works ok ? how about without any windower? what driver you use - and have you got the same driver now as pre update?
You can find a current copy of WinDbg from the first link here: http://www.codemachine.com/resources.html (Please download the 32-bit version even if you are on a 64-bit machine. If you don't the crash dump is useless.)
We've released a fix for Windower 4. If you use the Windower 4 Beta, just re-run the launcher and it will automatically update. If you haven't moved to v4 yet, we encourage you to do so here. We are working on backporting the fix to 3.4, and will be posting an update when a fix is available.
It's a hook update, so make sure you close the game before updating :).