On this page we'll try to answer some of the most frequently asked questions. If your question is not answered here or you'd like further elaboration, feel free to reach out to us on Discord.
A: Right now it's hard to say. You can already use Artemis 2 if all you want are simple brushes and animations without any game interaction.
However, the plan is to create some kind of beta release with things like a proper installer and auto-update before work on the workshop starts, early 2021.
A: The core systems, UI and default plugins are developed by Spoinky and I'm also writing this page!
Aside from that Artemis relies heavily on RGB.NET by DarthAffe, who also has done some work on Artemis and provided a lot of behind the scenes feedback.
Many people have helped out over the past few months with feedback and pull requests. An honorable mention being DrMeteor who has been a very early adpoter of the plugin API and Artemis in general.
A big thanks to everyone that has helped out!
A: Maybe. The core is written in .NET Core and can be compiled for Linux with minimal changes.
The UI is a different story, it is written in WPF which is a Windows-only platform. Artemis can function without the UI though and a different UI based on cross-platform frameworks can be put in place as well. I don't currently have any plans to do this but perhaps when Artemis 2 has matured enough and is feature complete, it would be a nice endeavour.
There is also the option of running Artemis in Wine, with which some users on Discord had succes in combination with the OpenRGB plugin.
A: While Artemis and Aurora attempt to solve similar problems, they both do it in very different ways. Many people coming from Aurora may try to use Artemis as if its a new version of Aurora which raises a lot of questions that don't apply to Artemis.
All I can say is, go through the Artemis guides and if at the end of that there's still a feature you're missing, let us know and perhaps we can improve upon that
A: All device support in Artemis is done via plugins. This means that in order to add support for a new device, a plugin has to be updated or created. Right now we do not take requests for plugins but the workshop will feature a request system.
If your device is of a brand already supported by the default Artemis plugins but it does not show up, please create a GitHub issue on the Artemis.Plugins repository.
If you want to add support yourself by creating a plugin, check out the developer guides.
A: This means your device has no layout. For each device we need to create a layout to tell Artemis where the LEDs are precisely. The layout can also contain a device image which Artemis uses in the editor.
You can help with this, even if you're not a programmer! Everything is explained in our layout guide.
A: Just like with devices, support for games is done via plugins. Again, the workshop will be the best source for plugins and right now the focus is on getting the Artemis core systems ready.
A: We hope to provide many easy tools for creating game plugins but in general the more moddable a game is, the easier it will be to create a plugin. Multiplayer games will be harder to support because many ways of reading game data can also be abused by cheats.