Hello,
With last night's update (June 24, 2015 22:00 PDT to 23:30 PDT), Windower is now reporting in the console log:
CRITICAL ERROR: FAILED TO FIND TargetArray
The console log from that time frame:
01:47:13 > Toggle Lighting = F11 (Bump mapping must be off to work properly)
01:47:13 > Toggle FPS = F12
01:47:13 > DrawDistance Lv 10: Alt-F10
01:47:13 > DrawDistance Lv 1: Ctrl-F10
01:47:13 > Paste Clipboard = Ctrl-V
01:48:24 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:48:24 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:48:24 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:48:24 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:48:24 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:49:43 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:49:43 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:49:43 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:49:43 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:49:43 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:50:28 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:50:28 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:50:28 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:50:28 > CRITICAL ERROR: FAILED TO FIND TargetArray
01:50:28 > CRITICAL ERROR: FAILED TO FIND TargetArray
03:04:07 > findall rem's
03:18:39 > CRITICAL ERROR: FAILED TO FIND TargetArray
03:18:39 > CRITICAL ERROR: FAILED TO FIND TargetArray
03:18:39 > CRITICAL ERROR: FAILED TO FIND TargetArray
03:18:39 > CRITICAL ERROR: FAILED TO FIND TargetArray
03:18:39 > CRITICAL ERROR: FAILED TO FIND TargetArray
03:21:23 > Unloaded all addons.
09:41:15 > Toggle Lighting = F11 (Bump mapping must be off to work properly)
09:41:15 > Toggle FPS = F12
09:41:15 > DrawDistance Lv 10: Alt-F10
09:41:15 > DrawDistance Lv 1: Ctrl-F10
09:41:15 > Paste Clipboard = Ctrl-V
09:41:38 > CRITICAL ERROR: FAILED TO FIND TargetArray
09:41:38 > CRITICAL ERROR: FAILED TO FIND TargetArray
09:41:38 > CRITICAL ERROR: FAILED TO FIND TargetArray
09:41:38 > CRITICAL ERROR: FAILED TO FIND TargetArray
09:41:38 > CRITICAL ERROR: FAILED TO FIND TargetArray
09:50:44 > exit
09:50:45 > Unloaded all addons.
NOTE: In the ase of the 09:41:15 to 09:50:45 session. I was in Bastok Mines, setup up two equipment sets (#1 and #20). I didn't do this, though during the 01:48:24 to 03:18:39 session.
Additional issue:
Before I left for 7 months, Windower would abend when I shutdown FFXI and the solution was to exit / quit from the command box. Now, Windower is abending even when exiting and / or quiting. The termination seems to be in LUA, even if I unload all addons before quitting / exiting.
NOTE: I realize this only occurs once (at exit/quit time) and thus is low priority. I would like to give a reason for it to be a higher priority issue, though. I use a System Monitoring tool to look at the stabilty of my system and Windower always crashing at the end is messing up the numbers making the system look bad. Yeah, I should some how get it to ignore Windower, but have yet to find a way for IOLO's System Mechanic to irnore Windower. Anyway, any thoughts on getting Windower ignored by SM OR Windower to not crash at exit?
Thanks! :-)
============================================================================
UPDATE: I just noticed the addon / plugins:
- Distance
- FFXIDB
- PetTP
- Scoreboard
are not working correctly. While they all load Distance, PetTP, and Scoreboard fail to appear on the screen. While FFXIDB displays the position is correct, it fails to show anything more (e.g. PC, monsters, NPC, etc). (Just a comment/FYI/request: I'd love to see FFXIDB expanded to be an OK version of ApRadar.)
Thank you for working on this issue! I know you have main lives that pay the bills, etc! I appreciate your help and Windower very much.
Edited by IBHalliwell, 26 June 2015 - 08:56 AM.