Custom UI Overlay

Dozens of different changes related to Custom UI and code editor. The most significant is the feature that allows you to open code editor in a separate window, which is much more convenient if you have mid-large project opened and much faster, because it will use its own processor core.

• added C# autocompletion
• major performance improvements
• code editor could now be opened in a separate window
• code editor is not loaded by default to improve overall responsiveness
• added new option - Enable browser hotkeys, which enables/disables standard hotkeys like F12, F5, etc.

UI Performance improvements

All overlays and some popups (image effects editor, for example) are now rendered by a separate processor core which should make UI much more responsive. The migration to this tech is still in progress, but current results look very good.

Self-Protection

Added few additional protective layers which should make detection by different anti-cheats harder. This affects application startup-time (especially when Security Measures option is enabled), but should not affect runtime performance

Bugfixes/Other

• Updated Telegram.Bot package to v19
• Network/Telegram messages are now printed in event log
• SendInput - fixed a bug with editor resetting to an incorrect mode (Keyboard rather than Mouse w/ Location)
• SendSequence - improved drag'n'drop support

• [Custom UI] A LOT of changes in overlay that allows you to write your own UI. At this point it could be considered usable and you can try it out. There will be some guides later in May.

  • Editor changes - code completion, highlighting, etc. The same editor will be later used for C# scripts as well
  • Added CSS/JS support - you can include your own scripts and stylesheets and the system will automatically connect them to your UI
  • Added a new API which differs from one used in C# scripts. This API has built-in backward compatibility and replace existing one in a few weeks.
  • Few fun examples - TicTacToe written in Blazor or plain JavaScript. Update to the latest version before importing these! Or write your UI on top of this animated JS background.
  • UI example of some Lineage bot
  • I will include examples which will show how to integrate your new custom UI with existing Eye Auras infrastructure a bit later. Basically, you can use anything - image search, AI search, all kinds of triggers and actions right from your custom UI code

• [New feature] Safe-Mode - when the app crashes or fails to load, you'll be asked to switch to Safe-Mode, which will disable most features of EyeAuras and will focus on one thing - loading the app, which will allow you to fix your broken Aura or update to the newer version without some newly discovered bug. You can enforce this mode manually by adding “--safeMode” or “-s” switch

New overlay - Custom UI - alpha

This is a new type of overlay which allows you to use HTML + CSS + C# to develop a fully custom user interface which will look whatever you like while maintaining full control over auras, triggers and actions. It is still in early stages of development, so there will be a lot of changes in API in the nearest future. There will be a separate Wiki page with examples and stuff soon. Meanwhile, here are some documents for technology that is used - ASP.NET Core Razor components | Microsoft Learn

New - Aura Library

This is a new way of sharing your aura packs. By default, shared aura packs are Unlisted, which means that they are not part of Library. All “old” aura packs are currently set to Unlisted, btw that is ~17000 packs uploaded by all of you in scope of last two years! As in many other similar domains, 10% of Eye Auras users are responsible for generating about 40% of content, I hope that by having public library these authors will be able to gain some visibility in the future.

By accessing URL given to you during Export (e.g. https://eyeauras.net/share/S2023040514233383FuBZ1tqR1A) you can change visibility to Public, amend name and write some meaningful description.

• [SendInput/Sequence/Text] Key presses are now logged in Event Log
• [PlaySound] Audio notifications are now logged in Event Log
• Added Dependencies Graph as a separate tab, currently it shows links of selected aura/folder
• [Bugfix] Fixed crash when system locale is not related to UK/US/RU

• Default Properties are now publicly available - https://wiki.eyeauras.net/en/default-properties

• [New Feature] Added “Import into EyeAuras” functionality which is available on the website. Clicking on link will activate EyeAuras and open up Import dialog.

• [Performance improvements] Config serialization/deserialization should now take less time and put less strain on your SSD (ssd… right ?)
• [SendInput] [TetherScript] Reworked device lookup algorithm - should be more stable on systems with a lot of input devices
• [SendInput] [Usb2Kbd] Changed initialization algorithm - should fix problem on some systems where initialization failed with no reason

• [Bugfix] [Volume Level Trigger] A bunch of fixes related to stability, wave form being not rendered correctly, etc

• [Volume Level Trigger] Is now able to capture audio stream of a single process. Note that volume level depends on a lot of different options so will different wildly across devices/games/etc

New trigger - Volume Level

This trigger allows you to configure reaction to loud sounds (or presence of sound at all) by setting volume level threshold (will be in decibels eventually, currently it's a decimal number [-1;1]

• How it works?

  • It allows you to select specific audio device (input/output), captures audio and measures Min/Max/Average value of played audio samples. In most cases analysis in done in 50ms "frames". If peak value in some frame is high enough ( ≥ Min Level) then the trigger is switched on. As soon as peak level decreases it automatically switches off.

• Is it able to detect a specific sound like click, footsteps or alarm?

  • No, this requires some fancy algorithms which I do not have time to research/implement atm. Maybe at some point in the future if demand will be high enough.

• Is it able to capture audio output of a specific application?

  • No, API that I am using does not support this feature. If you are interested - ping me in Discord with your use case description and I'll think about switching to another one if there will be enough requests and it will be more useful than other features on the roadmap.

• [SendInput] UI improvements
• [Bugfix] Usb2Kbd settings Reset was not working correctly