Jump to content

Recommended Posts

Posted

Thanks for this MOD. I will test it in the next days.

**************************************

DCS World needs the Panavia Tornado! Really!

**************************************

  • 2 weeks later...
Posted

I've released v1.1.5. This is a small bugfix update:

- Fix a bug that caused the GCI's voice to play 8% faster/higher pitched than intended (oops!)

- When a hostile aircraft disappears, the bot will wait a short while to see if other hostile aircraft also disappear so it can provide a combined FADED call for multiple aircraft in a group disappearing at around the same time. In some cases where players got "killstreaks" this would chain for a long time and a long wave of FADED calls would then be sent all at once. Adjusted the "killstreak timer" to reduce the occurrence of this.

- Updated to Go 1.24 (https://go.dev/blog/go1.24); a couple of the new features are being used for development, but this is otherwise an invisible upgrade for users.

https://github.com/dharmab/skyeye/releases/tag/v1.1.5

  • Like 3
Posted

The voice change caught me by surprise!

This is a genuinely useful bit of software and I'm surprised it isn't used on more public servers.

  • Like 1
  • 2 weeks later...
Posted (edited)

I've released 1.2.0.

New feature: SkyEye supports optional file-based locking to support a use case for some squadrons where multiple SkyEye instances are running on the same CPU. This allows each instance to use the CPU one-at-a-time during the processes' heaviest bottlenecks which is a better user experience than multiple instances flooding the CPU at the same exact moment. Learn more: https://github.com/dharmab/skyeye/blob/main/docs/ADMIN.md#multiple-instances-experimental

Bugfixes:

- Further improvement to the FADED call chaining issue mentioned in my last message.

- Fix a bug where the controller would call "merged" when players flew near certain stationary hostile aircraft on the ground.

Edited by intruder11
  • Like 1
  • Thanks 1
Posted

Hi,

First, many thanks for your work in this project. I wanted to try the bot. Following the instructions I tried to install it in an Ubuntu Linux server, and everything worked fine but the service didn't install due to this fatal error:

FTL failed to load whisper model error="stat ggml-small.en.bin: no such file or directory"
 

I double checked that the model is in /opt/skyeye/models, with all the permissions set as the instructions. ¿Any idea?

[sIGPIC][/sIGPIC]

  • 2 weeks later...
Posted
On 3/9/2025 at 12:27 PM, astiles said:

Hi,

First, many thanks for your work in this project. I wanted to try the bot. Following the instructions I tried to install it in an Ubuntu Linux server, and everything worked fine but the service didn't install due to this fatal error:

FTL failed to load whisper model error="stat ggml-small.en.bin: no such file or directory"
 

I double checked that the model is in /opt/skyeye/models, with all the permissions set as the instructions. ¿Any idea?

Hi, as mentioned in the Getting Help section of the admin guide, please open issues on GitHub rather than using social media. This is important for 2 reasons:

1. The GitHub issue tracker has a form which collects data I need to troubleshoot, such as the full log file and information about your deployment.

2. I don't monitor social media/the forums, I only come here when I have something to say.

  • Like 1
Posted

I've released v1.2.3.
* Prior to this release, Discord tracing was enabled by a `tracing` config option, but documentation and examples referred to a non-existent `enable-tracing` option. The code now accepts either `tracing` or `enable-tracing`.
* Controller now omits HIGH/LOW fill-in if a STACK has only two contacts, since 1 HIGH 1 LOW is implicit in that case
* Added missing data for the Tu-160 to SkyEye's internal aircraft database. Controller no longer considers the Tu-160 a potential threat to friendly aircraft, and will use the reporting name "Blackjack"
* The fact that SRS must have External AWACS Mode configured is now documented and SkyEye will emit error messages if it detects EAM has been disabled by the server.
* Minor internal code improvements.

https://github.com/dharmab/skyeye/releases/tag/v1.2.3

  • Like 1
  • Thanks 1
Posted

I've released v1.3.0, with two new features:

- SkyEye now supports directing threat and merged calls to flight rather than individually, if players conform to USAF-style callsign formats. Where before your flight might have heard "Chevy 11, Chevy 12, Chevy 13, Chevy 14, group threat..." they can now hear "Chevy 1 flight, group threat...". For more details, see the documentation on Strict Callsigns.

- Added support for the GPT4o and GPT4o-mini STT models available through OpenAI's platform. However, I don't recommend using them yet. SkyEye uses some features in the API that are not yet available for these new models, so in practice the current Whisper model works better at this time.

- Other documentation updates.

  • Like 2
  • Thanks 1
Posted

Love the latest update, awesome. Getting better all the time.

SkyEye has been running great on our Public Server for a few months now without issue. I would like to try and run another instace on that box for a second AWACS on another server instance. Apart from the Admin documentation on second instance limitations and possible load managment switches is there a guide somewhere on how best to install a second instance?

  • Like 1
Posted

Also noticed with the latest update 1.3.0, the bot is ignoring the auto-picture: false config.yaml setting. It is still broadcasting at the set auto-picture-interval:

I have tried a few restarts of the bot without effect.

Posted (edited)
On 4/2/2025 at 2:47 PM, PeneCruz said:

Also noticed with the latest update 1.3.0, the bot is ignoring the auto-picture: false config.yaml setting. It is still broadcasting at the set auto-picture-interval:

Thanks for pointing this out. This actually regressed all the way back in v1.2.1: https://github.com/dharmab/skyeye/pull/523/files#diff-243ebed2765f75e6a54f57167212fefb08c3b2a85967ad2acbc0eb78919019c1L129, I'll fix it when I have a free moment. In the meantime you can work around it by setting the auto picture interval to a long time like "24h".

On 4/1/2025 at 3:03 PM, PeneCruz said:

SkyEye has been running great on our Public Server for a few months now without issue. I would like to try and run another instace on that box for a second AWACS on another server instance. Apart from the Admin documentation on second instance limitations and possible load managment switches is there a guide somewhere on how best to install a second instance?

What OS are you running on?

On Linux, I'd use the existing skyeye.service systemd unit as a starting point and change it into a "service template" (https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#Service Templates). That's a systemd-native way of running multiple instances of a background service. You could then have each instance of SkyEye point at a different config file in `/etc/skyeye/`.

On Windows, the easiest way is probably to make a second copy of the skyeye-service.exe and skyeye-service.yml files (e.g. skyeye-instance-2-service.exe and skyeye-instance-2-service.yml), edit the YAML file to change the id, name and arguments fields, and repeat the install steps from the admin guide using this second copy. See also the reference docs for WinSW v2: https://github.com/winsw/winsw/blob/v2.12.0/doc/yamlConfigFile.md

Edited by intruder11
  • 3 weeks later...
Posted

I've released v1.4.0

SkyEye's macOS build has been fully overhauled in this release and is no longer marked as experimental; indeed, the macOS version of SkyEye is now the best version of SkyEye. I recommend you hop on the Flashpoint Levant server, which is already using the macOS version, and check out the near-instant speech recognition, and the new AI voice that is nearly indistinguishable from a human voice.

Unfortunately the macOS build is not easy to install or deploy yet; you can currently manually run it through Terminal, but my eventual goal is to provide an easy installation through Homebrew. That's currently held up because the build process currently itself has a dependency on Homebrew, which creates a circular dependency... I may need to think of a creative solution, haha!

Changelist:

* The macOS version of SkyEye now supports GPU acceleration using Apple Silicon and the Neural Engine. In my benchmarks, the macOS version recognizes speech 3-10x faster than OpenAI's API, and about 50-100x faster than my Windows/Linux PCs.

* The macOS version of SkyEye can now use Apple's Speech Synthesis Manager to speak with realistic AI voices. This requires some additional setup; if this additional setup is not completed, SkyEye falls back to the classic Siri voice from the iPhone 4S/iPhone 5/iPhone 6.

* Fix the `auto-picture` flag not being respected.

* Fix a bug where unarmed aircraft triggered threat callouts.

* Improvements to speech recognition accuracy.

* Other minor internal code improvements.

https://github.com/dharmab/skyeye/releases/tag/v1.4.0

  • Like 3
  • intruder11 changed the title to SkyEye - AI Powered GCI Bot - Talk to your AWACS over SRS!
  • 2 weeks later...
Posted (edited)

I've released 1.4.3, fixing an issue where sometimes broadcast calls in situations where some, but not all, of a flight's members were the target had the callsigns out of order ("2 3, EAGLE 2 1" instead of "EAGLE 2 1, 2 3")

https://github.com/dharmab/skyeye/releases/tag/v1.4.3

(1.4.2 was a small dependency update for a very niche use case far off the beaten path, so I didn't bother telling anyone except the one person who reported the issue)

Edited by intruder11
  • Like 2
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...