|
フォーラム » Windower »
News
»
Windower won't start! - Windower v4.3 and the Creators Update
Windower won't start! - Windower v4.3 and the Creators Update
Fenrir.Caiir
VIP
サーバ: Fenrir
Game: FFXI
Posts: 199
By Fenrir.Caiir 2017-05-03 18:48:31
Another update:
A new hook (4.3.0.7) has been pushed to the dev branch. It should correct a few issues, including keys getting stuck while alt-tabbing and reverting to the controller focus behavior of 4.2.
As a nice bonus for controller users, only the last focused FFXI window will now capture controller input while out of focus as long as the "Always Enable Gamepad" is checked in your launcher profile config. Correspondingly, our default for this setting has been updated to "true".
There's currently a known issue where when you switch between windows, the window you switch to may replicate the last button press on your controller. This should be a fairly simple fix, fortunately.
Regarding setkey not working out of focus :
SquareEnix apparently does not poll keyboard input while the game is out of focus, and thus, despite us actually sending the keypress, the game just queues it up and executes it once it's back in focus. I encourage you to not use setkey, as there are much better and cleaner ways to do things. We are currently looking into solutions on our end, though.
The following issues are going to be worked on next, and they are actually the only two issues that specifically relate to 4.3 that we are currently aware of:
* Crashing on minimize (this may actually not happen any more, please let us know).
* Disabling windows key so it can be used in keybinds.
By steelernation 2017-05-03 19:06:20
many thanks for all that you guys do.
[+]
サーバ: Bismarck
Game: FFXI
Posts: 148
By Bismarck.Cloudstrafie 2017-05-03 19:17:48
Bismarck.Cloudstrafie said: »Where can i upload them? i tried on github and it keeps telling me file not supported
nvm i just posted it with dropbox and uploaded it to the issue tracker.Thank you very much
By Nathoo 2017-05-03 19:25:38
Has the launching Playonline issue been fixed?
Ragnarok.Kenshi
サーバ: Ragnarok
Game: FFXI
Posts: 123
By Ragnarok.Kenshi 2017-05-03 19:27:00
Has the launching Playonline issue been fixed?
Yes, I had the launcher hanging issue and its gone.
Edit: minimized and let the game minimized for 2 mins and didn't crash.
Edit2: Dev version (Hook 4.3.0.7)
Carbuncle.Allyzon
サーバ: Carbuncle
Game: FFXI
Posts: 21
By Carbuncle.Allyzon 2017-05-03 19:30:47
Has the launching Playonline issue been fixed?
Yes, I had the launcher hanging issue and its gone.
Mine is still not loading, did you change any of the settings?
Ragnarok.Kenshi
サーバ: Ragnarok
Game: FFXI
Posts: 123
By Ragnarok.Kenshi 2017-05-03 19:32:04
whats the version of your launcher?
Carbuncle.Allyzon
サーバ: Carbuncle
Game: FFXI
Posts: 21
By Carbuncle.Allyzon 2017-05-03 19:38:19
whats the version of your launcher?
It just loaded, thank you so much
Fenrir.Aisaka
サーバ: Fenrir
Game: FFXI
Posts: 17
By Fenrir.Aisaka 2017-05-03 21:05:47
With the new hook, any time the window loses focus, all of my binds are unbound. This includes alt-tab and clicking to another window.
サーバ: Bismarck
Game: FFXI
Posts: 1346
By Bismarck.Kuroganashi 2017-05-03 23:32:49
Windower4 is currently being worked on and with the new update there will be a Windower4 update as well.
issue has been fixed for the most part, Still a few bugs to be delt with.
サーバ: Sylph
Game: FFXI
Posts: 184
By Sylph.Subadai 2017-05-03 23:50:42
With the new hook, any time the window loses focus, all of my binds are unbound. This includes alt-tab and clicking to another window. This is happening for me, too. Launcher v35270, Hook 4.3.0.7, Win10 Home with Creators Update installed (unlike my previous reports where I did not have Creators Update).
By Rife 2017-05-04 03:31:40
Crashing on minimize has stopped with Windows 10 - 64 bit.
However im noticing that the game is in the "darker" mode that makes people flash when you target them.
On 4.2 by default its on "lighter" mode where people dont flash. Wasnt sure if I could turn it back to the lighter mode.
Tried pressing the shortcuts that used to work
Lakshmi.Byrth
VIP
サーバ: Lakshmi
Game: FFXI
Posts: 6191
By Lakshmi.Byrth 2017-05-04 03:48:16
The command probably still works, but now binds are being wiped when the window loses focus for some reason.
Valefor.Psykopat
サーバ: Valefor
Game: FFXI
Posts: 160
By Valefor.Psykopat 2017-05-04 10:45:07
With new version 4.3.6332.35301 updated today I have a crash:
System.ComponentModel.Win32Exception (0x80004005): Accès refusé
à Launcher.Injector.Inject(SafeSystemHandle process, String hook, Settings settings, TimeSpan timeout)
à Launcher.Injector.Launch(String hook, Profile profile, Boolean debug, TimeSpan timeout)
à Launcher.Tasks.LaunchTask.Run()
à Launcher.Tasks.Task.Run(Core core)
à Launcher.Core.Run()
à System.Threading.ThreadHelper.ThreadStart_Context(Object state)
à System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
à System.Threading.ThreadHelper.ThreadStart()
Using Vista
Valefor.Psykopat
サーバ: Valefor
Game: FFXI
Posts: 160
By Valefor.Psykopat 2017-05-04 10:48:35
Using dev version with new hook I have the following error:
System.TimeoutException: Le délai d'attente de l'opération a expiré.
à Launcher.Injector.Inject(SafeSystemHandle process, String hook, Settings settings, TimeSpan timeout)
à Launcher.Injector.Launch(String hook, Profile profile, Boolean debug, TimeSpan timeout)
à Launcher.Tasks.LaunchTask.Run()
à Launcher.Tasks.Task.Run(Core core)
à Launcher.Core.Run()
à System.Threading.ThreadHelper.ThreadStart_Context(Object state)
à System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
à System.Threading.ThreadHelper.ThreadStart()
Valefor.Psykopat
サーバ: Valefor
Game: FFXI
Posts: 160
By Valefor.Psykopat 2017-05-04 10:49:30
Accès refusé means access refused
Le délai d'attente de l'opération a expiré means operation waiting delay expired
Sorry no idea why crash file is in french :)
Fenrir.Caiir
VIP
サーバ: Fenrir
Game: FFXI
Posts: 199
By Fenrir.Caiir 2017-05-04 12:00:04
With the new hook, any time the window loses focus, all of my binds are unbound. This includes alt-tab and clicking to another window. This is happening for me, too. Launcher v35270, Hook 4.3.0.7, Win10 Home with Creators Update installed (unlike my previous reports where I did not have Creators Update).
I pushed as fix to dev to address this. Please let me know if anything unexpected happens. Hook version 4.3.0.8.
By Rife 2017-05-04 12:25:18
Crashing on minimize has stopped with Windows 10 - 64 bit.
However im noticing that the game is in the "darker" mode that makes people flash when you target them.
On 4.2 by default its on "lighter" mode where people dont flash. Wasnt sure if I could turn it back to the lighter mode.
Tried pressing the shortcuts that used to work
messed around with //game_forceambientlighting
on the New version, it makes the screen even darker and disables the flashing when targeting people.
In 4.2 makes the screen darker and toggles people flashing.
So 4.3 is starting out dark and only gets darker, also the colors are a bit washed out
-------------------
Edit, updated my actual windower folder with the dev branch instead of using it in a seperate folder and the lighting is normal again
By Vijara 2017-05-04 12:32:55
With new version 4.3.6332.35301 updated today I have a crash:
System.ComponentModel.Win32Exception (0x80004005): Accès refusé
I believe this error is related to Windower not running with administrative permissions.
Are you sure you're running Windower as an Admin?
Asura.Psylo
サーバ: Asura
Game: FFXI
Posts: 446
By Asura.Psylo 2017-05-04 12:36:15
I have an issue with all the bind since this morning.
And then all the F9-F12 fonction from lua (mote one) don't work at all.
I need to reload gearswap or init.txt to use it and after 1 min, nothing work again.
Any idea ?
By Vijara 2017-05-04 12:37:50
I have an issue with all the bind since this morning.
And then all the F9-F12 fonction from lua (mote one) don't work at all.
I need to reload gearswap or init.txt to use it and after 1 min, nothing work again.
Any idea ?
Caiir just pushed a new hook to -dev.
With the new hook, any time the window loses focus, all of my binds are unbound. This includes alt-tab and clicking to another window. This is happening for me, too. Launcher v35270, Hook 4.3.0.7, Win10 Home with Creators Update installed (unlike my previous reports where I did not have Creators Update).
I pushed as fix to dev to address this. Please let me know if anything unexpected happens. Hook version 4.3.0.8.
Try updating to 4.3.0.8 and see if that continues to happen.
Asura.Psylo
サーバ: Asura
Game: FFXI
Posts: 446
By Asura.Psylo 2017-05-04 12:48:23
Yep, version 4.3.0.8 works ^^ Thks ;)
Thks all for your good work.
[+]
Asura.Farroh
サーバ: Asura
Game: FFXI
Posts: 19
By Asura.Farroh 2017-05-04 13:04:53
any chance you guys can fix the mouse cursor not landing on menu?
i believe game_allowsetcursorpos 1 isn't working
[+]
Valefor.Psykopat
サーバ: Valefor
Game: FFXI
Posts: 160
By Valefor.Psykopat 2017-05-04 14:12:26
Are you sure you're running Windower as an Admin?
Always running as admin yup
Asura.Topace
サーバ: Asura
Game: FFXI
Posts: 771
By Asura.Topace 2017-05-04 14:57:39
Windower keeps giving me "Failure to Initialize 3D" when i'm switching from playonline to FFXI. But it works when I use Ashita or regular POL. I'm not really sure how fix it.
サーバ: Asura
Game: FFXI
Posts: 1
By Asura.Monstah 2017-05-04 15:14:12
Everything working again! Thank you :)
By Vijara 2017-05-04 15:28:45
Are you sure you're running Windower as an Admin?
Always running as admin yup
Then I'm not sure, sorry... leave it to the devs to figure that one out! Good luck man!
サーバ: Odin
Game: FFXI
Posts: 4013
By Odin.Godofgods 2017-05-04 16:43:54
I pushed as fix to dev to address this. Please let me know if anything unexpected happens. Hook version 4.3.0.8 how to i update to that? When i start windower i still get hook 4.3.0.6 Even when i dl new from the windower site.
[+]
Ragnarok.Inx
サーバ: Ragnarok
Game: FFXI
Posts: 371
By Ragnarok.Inx 2017-05-04 17:06:44
Yep, today's pushed dev build fixes the hang launching POL. Have been using without issue for a few hours now.
Asura.Neufko
サーバ: Asura
Game: FFXI
Posts: 236
By Asura.Neufko 2017-05-04 17:49:08
Windower keeps giving me "Failure to Initialize 3D" when i'm switching from playonline to FFXI. But it works when I use Ashita or regular POL. I'm really sure how fix it.
Screenshot in spoiler :
I get the same messsage, same with -dev
That happened just after creator update.
I'm using Nvidia 980 Ti with last drivers (05/04/2017)
Windows 10 64b Creator update
I've tried to disable all plugins and addons, still same error.
I'll update if I figure something out
Edit : Ok, I ended up rolling back Creator's update for now. Everything's ok with -dev
Windower v4.2's hooking uses a very old x86 library known as madchook. For legal reasons, we haven't been able to update madchook since the creator took it private but did have permission from him to use the old version. In order to get around this, Iryoku wrote a new x86 hooking library for Windower v5 (a work in progress).
As it happens, the Creators Update for Windows 10 (roll-out began yesterday) breaks the old hooking library. However, through collaboration with users who downloaded the Creators Update early, we discovered that Windower v5's hooking library had no problems with the Creators Update.
In the last three days, Iryoku heroically backported v5's hooking library to v4 and adjusted everything for it (bumping the version to 4.3). Two nights ago we got it to build and Arcon has been bug squashing for the last day.
There is also a pretty good chance that this Windower update will also fix the compatibility the issues people have had with Windows 8+ and Windower. This extends to the Launcher, where we've switched to software rendering and expect the white screen issues people were having to be fixed.
v4.3 and the new Launcher are both currently on -dev. If you are having problems with the Creators Update and want to log back in, we recommend at least temporarily using -dev. To do this, duplicate your entire Windower directory, then download this Launcher, replace your existing Windower.exe, and log in.
I will update this post when it goes live, but please try it on -dev or we're unlikely to find the last few bugs that are doubtlessly lurking.
|
|