v0.2.8-alpha.5

Warning

If you're using multiple instances to stream multiple different displays simutinuously, disable Advanced display device options!

The upstream implementation for display topology handling and resolution automation doesn't support multi instance well. They may end up messing up everything unexpectedly.

If you only need one Apollo instance, it's still safe to upgrade.

Don't forget to remove display_device.state from Apollo's config dir if it exists.

Change log

• v0.2.8-alpha.1

1. Primary display can now set automatically
2. Preserve previous log when Apollo restarts
3. Adapt display config handling to libdisplaydevice
4. Track upstream

• v0.2.8-alpha.2

1. Revert back to original HDR workaround
2. Update libcurl, fixes #235

• v0.2.8-alpha.3

1. Hash cookies for Web UI
2. Track upstream
   • Inverse polarity for Global Prep Commands for apps (bug from some unnecessary upstream changes)
   • Display config reverting logic refine (not really necessary for Apollo actually, but the new display config handling mechanism caused some display flickering on and off issues on some systems, this change might have fixed the problem)
   • Security patch (but it's already patched in Apollo in another way when I discovered the other security vulnberity long ago)

• v0.2.8-alpha.4 & v0.2.8-alpha.5

1. Fix bug where output_name did not take effect
2. Fix all deactivated display are enabled when quitting virtual display

The inclusion of libdisplaydevice further complicated the display config problem, I hope this version gets all problems with virtual display introduced by libdisplaydevice solved...

Nope, there're more hidden problems...

If you encounter display being toggled on and off constantly while using the latest versions, first quit Apollo (you can access the web UI from another device, by enter https://your.host.ip.address:[webuiPort] to your browser, then in Troubleshooting page tap Quit Apollo), then go to Apollo's install dir, under config dir remove display_device.state.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.7

Happy New Year! 🎆

Change log

1. Fix password is always saved issue (#130)
2. First connection now should respect user settings for encoder capablity announcements (#123)
3. SudoVDA update: peak brightness is now 1671 nits (#164)
4. Track upstream

It's very complicated to explain why HDR is a total mess, and why enabling HDR makes the image appear dark/yellow. If it's your first time got HDR streaming working, and thinks HDR looks awuful, you're right, but that's not Apollo's fault, it's your device that tone mapped SDR content to the maximum of the capability of its screen, there's no headroom for anything beyond that actual peak brightness for HDR. For details, please take a look here.

NOTE: Windows 11 24H2 broke the method for programatically setting primary display, even MultiMonitorTool fails to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.6-alpha.3

Change log

1. Fix error/success couldn't be shown on login page
2. Show alert for checking permissions after pairing
3. Track upstream

PS: Originally I wanted to fix a weird lagging issue I discovered previously with this build, but it turns out to be the AV1 encoder of nVidia behaving strange. It works fine in most cases so it's not a really big deal, but I still suggest use HEVC if you have a good network connection. If you insist of using AV1, try disable Two-pass mode and enable Spatial AQ in NVENC config tab, that would make the problem less noticable. AMD cards doesn't have this kind of issue.

NOTE: Windows 11 24H2 broke the method for programatically setting primary display, even MultiMonitorTool fails to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.6-alpha.2

Change log

1. Fix Working Directory not working in some more cases
2. Fix Find Cover Online
3. Track upstream, removed session count and quit app limit (only clients with Launch Apps permission can terminate a stream)

NOTE: Windows 11 24H2 broke the method for programatically setting primary display, even MultiMonitorTool fails to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.5-alpha.1

Change log

1. Add Intra Refresh for NVENC
2. Fix Working Directory not working in some cases

NOTE: Windows 11 24H2 insider preview broke the method for programatically setting primary display, even MultiMonitorTool fails to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.4-alpha.2

Change log

1. Fix codepage conversion for clipboard upload (resolves #69)

NOTE: Windows 11 24H2 insider preview broke the method for programatically setting primary display, even MultiMonitorTool fails to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.4-alpha.1

Change log

1. Add Clipboard sync (text only)
2. Add permissions for clipboard sync

NOTE: Windows 11 24H2 insider preview broke the method for programatically setting primary display, even MultiMonitorTool fails to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.3-alpha.1

Change log

1. Assign a fixed UUID for each app
2. Allow using app's own identity instead of client's for virtual display creation (for specific display configurations)
3. Try fix display probing for some weird platforms
4. Minor UX improvements

NOTE: Windows 11 24H2 insider preview broke the method for programatically setting primary display, even MultiMonitorTool failes to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?

v0.2.2-alpha.2

This build tries to fix graphics card probing on some weird systems.

v0.2.2-alpha.1

Change log

1. Split Keyboard & Mouse permission into dedicated keyboard and mouse permissions (#45)
2. Update Chinese translation
3. Minor UI improvements

This version split the original combined Keyboard & Mouse Input permission into separate Keyboard Input and Mouse Input, you need to grant existing clients with the corresponding permissions manually.

NOTE: Windows 11 24H2 insider preview broke the method for programatically setting primary display, even MultiMonitorTool failes to do so. You can still set the virtual display to default manually and Windows will remember your configuration.

Warning

It is highly recommend to remove any other virtual display solutions from your system and Apollo/Sunshine config, to reduce confusions and compatibility issues.

Warning

Quit ALL running Apollo instances before upgrading!

Note

VirusTotal scan report for this build

Why Windows always report file as harmful?