Known Issues & Limitations - Lailloken/Exile-UI-Legacy GitHub Wiki

Clicking

some mouse drivers/software may cause problems with (long-)clicking UI elements
if issues like these occur on your system, you will have to disable or close your mouse software to continue using this tool

make sure you have extracted the downloaded zip-file correctly
if you launch the tool via any method other than double-clicking the .ahk-file (e.g. any form of CLI), make sure to explicitly include the correct working directory
if you still get an error message, it's possible your AutoHotkey installation is out of date

the script has to read the PoE config-file to determine which windowed mode is being used, but it will always read the current user's config-file instead of a possible alternative user's
to make it read an alternative user's config-file, you have to manually edit the config.ini file found in the scripts ini-folder
- in the [settings] section, add/edit the following line with the desired file-path: PoE config-file="X:\some file path\Path of Exile\production_Config.ini"

the tooltip automatically closes whenever the inventory is closed
if it vanishes even though the inventory is open, the pixel-check for the inventory has to be recalibrated in the "screen-checks" section of the settings menu

this message appears if the script has insufficient write-permissions in the current location
the first possible solution is to move the script to a different folder or to run it as administrator
the 'general' section of the settings menu has a write-permissions test that can be used to trouble-shoot these permission issues
- you can use this to find a folder location that works, or to find out if admin rights resolve the issue

if 'show advanced item descriptions' is not bound to ALT, the omni-key cannot read advanced mod descriptions from items, which affects many item-related features
- v1.27.2 implemented a workaround with which users can specify which key the highlighting is bound to
- open the LLK-UI settings menu (by clicking the LLK-UI panel or typing .llk into chat), go to the omni-key section, click into the text-field next to 'highlight-key', and then type the key name into it (refer to this site for correct spelling: AHK wiki)
if anything other than the character sheet is bound to C, every omni-key press while not hovering items will trigger whatever is bound to C (e.g. inventory)
- v1.27.2 implemented a workaround with which users can specify a secondary omni-key that triggers all item-related features
- open the LLK-UI settings menu (by clicking the LLK-UI panel or typing .llk into chat), go to the omni-key section, click into the text-field next to 'omni-key (items)', and then press the desired hotkey (neither key-combinations, nor modifier-keys can be used)
- from now on, you'll have to use the secondary key to omni-click items and activate related features

an unknown combination of hardware and/or software may cause dramatic frametime spikes while the tool is running
this is most probably related to the script using pixel-checks in the background to determine if a full-screen menu is open in the game
I will try to mitigate the issue by making background pixel-checks optional. However, this means the script will be less smooth, and the user has to toggle overlays on and off manually

it may happen that overlays flash/toggle randomly while moving your character
this issue is due to the fact that 'name-plates' are rendered on top of the realm/instance panel in the top right (which the script pixel-checks in order to tell if the player is on the 'game-screen' or in a menu)
- I cannot fix this behavior, it's up to GGG to change that

these uncommon resolutions caused rather big problems in archnemesis because they are (seemingly) not properly supported by the game-client
using these resolutions will cause inconsistent rendering of icons and certain UI elements, which is problematic for any feature that relies on image recognition/detection
I have thus decided to end official support for these resolutions, i.e. the script refuses to run at these resolutions
though I haven't tested it, it is highly likely that this also happens in custom-sized windowed-mode (i.e. manually resized windows)
the officially-supported vertical resolutions are 720p, 900p, 1080p, 1200p, 1440p, 1600p, 1800p, and 2160p
the script will warn the user about the current resolution when launched and suggest using a custom resolution. You can read a guide HERE

Windows versions older than 10 probably don't have the right snipping tool that this script uses for screen-capping when setting up cheat-sheets or image-checks
every feature that uses the snipping tool has instructions on its wiki page on how to do the setup without the snipping tool