Geforce experience audio failed to initialize nvvad audio resources error 602

Describe the bug
Mouse cursor extremely small on extremely high DPI panels (4K, 23», ex), regardless of DPI scaling factor or mouse cursor size settings

Steps to reproduce
Using any very high-resolution panel with small footprint (i.e., high pixel density/DPI); has always been an issue

Screenshots
Will add

Affected games
N/A, this affects the desktop mouse cursor.

Other Moonlight clients
Only aware of this issue with Windows, though I’d imagine it exists on Linux as well, which barely supports high DPI outside modern Gnome

Moonlight settings (please complete the following information)
Default settings with the exception of dragging bitrate slider to max (native resolution)

Gamepad-related issues (please complete if problem is gamepad-related)
N/A

Client PC details (please complete the following information)

• OS: Windows 10 19043 (21H1)
• Moonlight Version: 3.1.1
• GPU: NVIDIA GeForce GTX 965M

Server PC details (please complete the following information)

• OS: Windows 10 19043 (21H1)
• GeForce Experience version: Will provide
• GPU: NVIDIA GTX 1660 6 GB
• Nvidia GPU driver: 466.63
• Antivirus and firewall software: Windows Defender and Windows Firewall

Moonlight Logs (please attach)
Will provide

Describe the bug
[Nvidia streaming server component] GPU footprint reaches over 30%

Steps to reproduce
I just connected mstsc and didn’t do anything else

Screenshots

Affected games
Not a game

Other Moonlight clients

• Does the issue occur when using Moonlight on iOS or Android?
  Yes, this will happen

Moonlight settings (please complete the following information)

Client PC details (please complete the following information)

• OS: Windows 10 21H2 19044.2006
• Moonlight Version: 4.2.1
• GPU: Nvidia GTX 750

Server PC details (please complete the following information)

• OS: Windows 10 21H2 19044.2075
• GeForce Experience version: 3.26.0.131
• Nvidia GPU driver: 516.94
• Antivirus and firewall software: Windows Defender

Moonlight Logs (please attach)
Moonlight-1663895275.log

Whenever I attempt to launch a 4K stream via Moonlight, it initiates and attempts to connect, but ends up terminating the connection. On the PC side, the screen ends up completely black for a bit and then reboots and becomes stuck in a boot loop, unable to boot Windows until I go into safe mode and uninstall the Nvidia Graphics driver, at which point I can boot the PC normally again. This is only an issue with my Apple TV 4K, as I can stream just fine at 4K (and HDR) via Moonlight on my Chromecast with Google TV, which leads me to believe it’s an issue with the iOS/tvOS app itself. 4K streaming also works fine on tvOS via Steam Link and Rainway. I can stream at lower resolutions to the Apple TV just fine, only when I set the Moonlight resolution to 4K does it crash. I’ve also tried completely reinstalling windows fresh several times but that hasn’t fixed the issue either.

It’s also worth mentioning that I didn’t really have issues with this when I was on a GTX 980 Ti (aside from it not being a great card for 4K gaming). I upgraded to a RTX 3080 a month ago and started having this issue after that.

Just noticed this, I am sure this worked in the past.

1. start stream to Windows 11 client via mstc.exe
2. open a youtube video / stream in Chrome
3. maximize the video
4. let mouse idle / not move
5. after a few seconds the stream freezes, though the video still plays on the server (seen on monitor)
6. moving the mouse cursor and the video stream updates randomly
7. minimizing the video and it plays normally again

Is this a bug in GFE?

Been wondering why print screen hasn’t been working over moonlight to take screenshots in games… used keyboardtester.com and on my laptop running moonlight, pressing the print screen button shows up as a comma key. From my desktop the key shows up as print screen appropriately.

Moonlight Version: 3.2
Windows Version: Windows 10 build 19044

Describe the bug
Any game that is utilizing the new FullScreen optimizations in Windows will run into streaming problems if you have vsync applied or capping framerate using NVIDIA Profile settings.
This issue also only applies to 4k streams, it does not apply to lower resolutions.

Steps to reproduce
Play any game that is either DirectX 12, or a game you know personally that uses the new flip model swap chain for low latency borderless windowed/fullscreen gaming.
Enable vsync on game OR apply NVIDIA Max Framerate on GPU Profile
Stream game at 4k resolution

Symptoms
Game will stream fine for a few moments, then stream will drop to around 45fps and will not be smooth, regardless of frame pacing settings.
Changing the streaming resolution to under 4k, appears to resolve this issue.
Streaming at 30fps also does not appear to be affected by this issue.

Affected games
All Direct X 12 supported games
Any game that uses the new swap chain flip model API in Windows for Exclusive Full Screen
If using 22H2 and also enabling the new windowed mode optimization feature, almost all games will be affected.

Additional context
This issue has been reported to NVIDIA.
The cause of this issue is a bug on NVIDIA’s power management mode, which is causing some of the cores used for encoding to be underclocked and not have enough speed to be able to encode at 60fps in this scenario.

Workarounds

It is NOT recommended to disable the new windowed mode optimization as it has a significant reduction to input latency, instead it is suggested to workaround this issue.

Only one of the workarounds mentioned below have to be done, you can pick and choose which works best for you.
I’ve ordered them in the order I feel is best, but you may think otherwise.

1. Disable VSYNC in game and remove NVIDIA Max Framerate setting on game if applied; Then, apply Framerate cap using RTSS via MSI Afterburner.
2. Set performance mode to maximum performance in GPU Profile for game, although this can more than double the power usage on some cards.
3. Lower the resolution of the stream to something under 4k

Client is using Moonlight 4.1.0 on macOS 12.4 on a macbook Pro 16′ M1 Pro.
Host is a Windows 10 Home 64bits 21H2 with a RTX 3080. GFE 3.25.1.27. Drivers are 516.59. No additional firewall/antivirus.
I have a second screen plugged on the HDMI but not turned on.

I use a 802.11ax connection and have a stable 700 Mbps bitrate.
I’m also using Moonlight default setting but tried every options there was to see if it improved anything, it doesn’t. I’m usually streaming at 1440p/120hz.

My issue is that when I use moonlight is that after few minutes (could be 1, could be 40- The stream and the remote application close themselves. It’s not a disconnection issue, both machines can ping internet while this happens.
I have Windows 10 device disconnection sound just before the stream crash.

Moonlight log is like that:

00:26:24 - SDL Info (0): Requesting IDR frame on behalf of DR
00:26:24 - SDL Info (0): IDR frame request sent
00:26:24 - SDL Info (0): Waiting for IDR frame
00:26:24 - SDL Info (0): Waiting for IDR frame
00:30:15 - SDL Info (0): Server notified termination reason: 0x80030023
00:30:15 - SDL Error (0): Connection terminated: 0
00:30:15 - SDL Info (0): Quit event received
00:30:15 - SDL Info (0): Global video stats
00:30:15 - SDL Info (0): ----------------------------------------------------------

And gamestream logs always give me that :

Termination reason = SERVER_TERMINATED_DISPLAY_TOPOLOGY_CHANGED (SRC_DisplayTopologyChanged)
...
<Fbc7FrameProvide> Capture failure, reported capture resolution is 0 x 0 pitch 0. Writing a black frame.
<Fbc7FrameProvide> Capture resolution is now 1280 x 720 pitch 0.
<Fbc7FrameProvide> Failed to grab frame as the session was invalidated.
<Fbc7FrameProvide> FBC session invalidated with internal error code 0xfbce0004.
<Fbc7FrameProvide> Attempting to recreate FBC session.
<Fbc7FrameProvide> Driver reports that device was lost.
<Fbc7FrameProvide> Recreate the pipeline to recover from this situation
<Fbc7FrameProvide> Failed to grab frame: -3 (NVFBC_ERROR_INVALIDATED_SESSION).

I’ve attached a log when it happens with mstsc (but it also happened with Hitman III, I can give the log if necessary)
NvStreamer_mtsc.log

Other than that it works flawlessly and it’s a shame, especially because the application is killed so I lose my game if I didn’t save prior to that.

Describe the bug
Sometimes I get black screen (no video) when trying to stream any game or desktop. Sound and input still work, but video does not. Rebooting client machine does not help, only rebooting host machine makes it work again. It does not happen during stream.

Steps to reproduce
I don’t have exact steps to reproduce. It seems to happen randomly at some point (not during streaming) and then the issue remains until I reboot server machine.

Screenshots

Affected games
All

Other Moonlight clients

• Android client — it’s the same. If it works, it works on both.

Moonlight settings (please complete the following information)
I’ve modified settings but also tested with default settings too and it doesn’t change the situation.

Client PC details (please complete the following information)

• OS: Linux Fedora 34
• Moonlight Version: 3.1.3 from flatpak
• GPU: Intel Iris 6100

Server PC details (please complete the following information)

• OS: Windows 10 19042
• GeForce Experience version: 3.22.0.32
• Nvidia GPU driver: 466.63
• Antivirus and firewall software: Windows Defender and Windows Firewall
• 1 HDMI and one DisplayPort monitors. The issue happens no matter whether they are turned on or off (hdmi one is always detected so I usually turn it off when I play).

Moonlight Logs (please attach)
NvStreamerCurrent.log

Additional context

• I sometimes run VirtualBox and rdp client on the host machine. Also it goes into suspend (sleep) from time to time. I’ve tried doing all these right after reboot and it did not make screen go black, streaming was still working fine
• The issue also occured with few past versions of Nvidia driver and GeForce Experience and moonlight — since I started using Moonlight around February this year.

When I rotate my monitor direction to vertical, the cursor’s appearance on my phone/iPad don’t rotate along.
And it keeps moving the wrong direction as if I am using a horizonal screen.
But on my host PC, the mouse cursor looks nothing wrong, it rotate with the monitor direction.
Only the APPEARANCE of the cursor streamed by moonlight goes wrong.

You can see from the screenshot that I made a up-to-down (image direction) movement, and it works nothing wrong on my host PC.
But the streamed cursor goes right-to-left.
This always happens when I use android or ios client. And input methods like mouse or laptop touchpad both have this problem.

The vertical screen streaming used to work well before. The main difference is that I updated windows from 10 to 11.
Do all win11 host PC has this problem? What can I do to fix it?

A few users have reported RTSP handshake error 60 after updating their drivers. The issue is not affecting the majority of Moonlight users (including myself), but it affects some users very consistently. It must be something specific to their client, host, or streaming settings that is triggering the issue reliably.

Error 60 is ETIMEDOUT which would indicate either a connection timeout or a timeout waiting for a reply from the host. In some cases, GeForce Experience will fail to reply to RTSP messages while waiting for NvStreamer.exe to start. Specific invalid streaming settings (such as resolutions below 256×256) are known to cause NvStreamer.exe to crash, so that may be what’s happening here.

Affected users, please provide the following info:

• What was the last driver version to work and the first driver version not to work?
• Do you have «hardware accelerated GPU scheduling» enabled on your host PC?
• Attach your logs from C:ProgramDataNVIDIA CorporationNvStream after trying to stream and getting the RTSP error

After some indeterminate period of time streaming, the video will freeze and the stream will eventually disconnect. This happens when the encoder thread in nvstreamer.exe hangs. It appears to be a driver bug that is encountered when hardware-accelerated GPU scheduling is enabled on the host PC.

NVIDIA is aware of the bug and has reproduced the issue in their lab.

Workaround: Disable hardware-accelerated GPU scheduling on your host PC.

Describe the bug
The connection is definitively disconnected when the mouse pointer is of a certain shape/size.

Steps to reproduce

• In Adobe Photoshop CS6 (I think many programs using brush tool)
• Use Pencil Tool
• Just Zoom In close to 500%

YouTube Video
https://youtu.be/3_bd6Yb-Nxk

Affected games

• Adobe Photoshop CS6

Other Moonlight clients

• Same in iPadOS, iOS.

Client PC details (please complete the following information)

• OS: Windows 10 Pro 21H2
• Moonlight Version: v.4.1.0
• GPU: NVIDIA GeForce GTX 750

Server PC details (please complete the following information)

• OS: Windows 10 Pro 21H2
• GeForce Experience version: 3.25.1.27
• Nvidia GPU driver: 497.29
• Antivirus and firewall software: Windows Defender

Moonlight Logs

• Attached
  Moonlight-1658154593.log

Additional context
The connection is definitively disconnected when the mouse pointer is of a certain shape/size.
The YouTube example video crashes close to 500% when zoomed in on the screen with the 40px pencil tool at 100% size in Photoshop CS6.
500%, but not with other pointer shapes like a magnifying glass or a selection.
When this phenomenon occurs, remote recovery is difficult with Moonlight alone, and you should avoid the screen by reducing it with another remote program or selecting another tool.
It seems to be a new problem after fixing the misalignment of the mouse pointer position.

This might be a «feature»

Win 10 Pro 19043.1055, any DRM-protected stream, for example using the EME API, causes a «connection terminated» error. Connection cannot be resumed until the protected stream is closed.

Places where this might occur include in web browser accessing something like Prime Video or Netflix, or using their respective PWA’s installed to the system.

Just what the tittle says

I’m doing it on a Proxmox VM under Windows 11, lastest drivers:

Thanks for the hard work!

Describe the bug
Mouse Pointer Position Error in Specific Programs.

Steps to reproduce
No Any Condition. Always Wrong Position in some programs.

Screenshots

Affected games

• Host Program: Adobe Photoshop CS 6 64bit, mspaint.exe

Moonlight settings (please complete the following information)
Default

Device details (please complete the following information)

• Host OS: Windows 10 20H2
• Geforce Experience version: 3.22.0.32,
• Nvidia GPU driver: 466.27,
• Client: iPadOS 14.6,
• DeviceModel: iPad Air 4th
• Host Program: Adobe Photoshop CS 6 64bit, mspaint.exe

Server PC details (please complete the following information)

• Host OS: Windows 10 20H2
• Geforce Experience version: 3.22.0.32,
• Nvidia GPU driver: 466.27,
• Client: iPadOS 14.6,
• DeviceModel: iPad Air 4th
• Host Program: Adobe Photoshop CS 6 64bit, mspaint.exe

Describe the bug
I’m experiencing occasional microstutters when streaming game content from my PC desktop to my Mac client. The screen freezes very briefly causing a observable stutter before returning to normal. No frame drop is detected in the stats overlay. See below in the «Additional context» section for some troubleshooting I’ve tried so far.

Steps to reproduce
This happens every once in a while (from couple seconds to couple minutes) when I stream game from my PC to my host.

Affected games

• First observed when playing Genshin Impact.
• I was able to repro later by streaming a 60fps stutter test video on YouTube playing on the host machine (e.g. https://www.youtube.com/watch?v=Ohuqp5AJqaM).

Moonlight settings

• Streaming with 1440p/60fps. I tried lowering resolution all the way down to 720p and lowering bitrate to 10Mbps and this issue still happens.
• I tried with encoder setting set to H264/HVEC/auto, and this issue persists.
• I tried enabling/disabling frame pacing, and this issue persists.
• I tried enabling/disabling V-sync in both game and Parsec, and this issue persists.

Client PC details

• OS: macOS Monterey 12.5
• Moonlight Version: This repros with both release v4.1.0 and a Git build (based on 685136d9)
• GPU: Intel Iris Plus Graphics 655 1536 MB
• Client & server hosts are connected via 1Gbps ethernet directly onto the same switch (TL-SG108E).

Server PC details

• OS: Microsoft Windows 10 Home 10.0.19044
• GeForce Experience Version: 3.25.1.27
• Nvidia GPU driver: 516.59
• Antivirus and firewall software: Just default Windows 10 settings

Moonlight Logs (please attach)

Attached. Log contains some additional debug information I added, including slow frame logs (https://github.com/isundaylee/moonlight-qt/tree/my-custom-changes).

Also attached two packet captures (on host and client respectively) that cover a subset of time period in the log. See «Additional context» below for more info.

moonlight.log
pcaps.zip

Additional context

The game itself is FPS-locked to 60, with the MSI Afterburner perf overlay showing a steady 60FPS when this happens. GPU usage is between 40-50% and CPU usage is between 10-20%. Hardware-accelerated GPU scheduling is turned off (though this repros when it’s turned on too).

I tried the following to debug this issue:

I added some debug logging in FFmpegVideoDecoder::submitDecodeUnit to detect/alert on frames that arrive later than the expected 16-17ms since the previous frame. The microstutter I observe corresponds pretty well to the slow frames detected/logged. e.g.:

00:08:12 - 2022/08/04-23:58:54,494 - SDL Info (0): Slow frame 28913 elapsedTicks 32

^ Note that elapsedTicks is 32 which is much higher than the expected 16-17 for 60fps.

When this happens, Moonlight still receives a steady 60-61 fps. So this doesn’t look like frame dropping — more like weird frame pacing.

To exclude networking as a potential issue, I took two packet captures simultaneously on my host (pc.pcap) and my client (mac.pcap). I’m able to observe the same higher-than-normal delay between frames in both packet captures, which suggests that the frame delay already exists when the host sends out the data packets.

e.g., this line in the log:

00:08:12 - 2022/08/04-23:58:54,494 - SDL Info (0): Slow frame 28913 elapsedTicks 32

corresponds to the 0.031 seconds jump between the frame comprising of RTP seq nums 15879-15882 and the frame starting on RTP seq num 15883 (for port 47998). You can see it in pc.pcap by comparing the timestamps of packet 12317 and packet 12333, and in mac.pcap by comparing the timestamps of packet 14072 and packet 14088. I also confirmed that these two frames have sequential frameIndex (as defined in NV_VIDEO_PACKET), so no frame dropping.

Note on the packet captures: There’s some timestamp drift between the server and the client, but the timestamps in Moonlight log corresponds pretty well to the timestamps in mac.pcap.

Any potential idea/suggestion is appreciated!

Cannot connect to my host pc using the latest version of moonlight under my local area network. I tried with android client and ipad os client. Both of them cannot find the device either automatically or manually. Besieds, when I running the moonlight internet streamming tools, it reported that Testing TCP 47984…Timeout Testing TCP 47989…Timeout.

Can anyone tell me how to work with this problem??

Other Moonlight clients

• I tried with android client and ipad os moonlight client. Both of them cannot find my host pc.

Moonlight settings (please complete the following information)
All the setting are default

Device details (please complete the following information)
Ipad os and android 10

Server PC details (please complete the following information)

• OS: Windows 10
• GeForce Experience version: 3.20.2.34
• Nvidia GPU driver:466.27
• Antivirus and firewall software: Windows Defender and Windows Firewall Already Closed

Describe the bug
Moonlight is stuck at the loading screen after the driver update to 526.98 (Studio Driver). The return error code is 4.

Steps to reproduce

• Try updating to the latest Studio Driver
• Launch the streaming
• Wait for the error

Moonlight settings (please complete the following information)

• Have any settings been adjusted from defaults?: YES
• If so, which settings have been changed?: YES
• Does the problem still occur after reverting settings back to default?: YES

Gamepad-related issues (please complete if problem is gamepad-related)

• Do you have any gamepads connected to your host PC directly?
• Does the problem remain if you stream the desktop and use https://html5gamepad.com to test your gamepad?
  • Instructions for streaming the desktop can be found here: https://github.com/moonlight-stream/moonlight-docs/wiki/Setup-Guide

Client PC details (please complete the following information)

• OS: Windows 11 22H2
• Moonlight Version: v4.3.1
• GPU: Nvidia Geforce RTX 3080 10GB

Server PC details (please complete the following information)

• OS: Windows 11 22H2
• GeForce Experience version: 3.26.0.154
• Nvidia GPU driver: Nvidia Studio Driver 526.98
• Antivirus and firewall software: Windows Defender and Windows Firewall

Moonlight Logs (please attach)
Moonlight-1669420623.log

PC Windows 11 PRO 21H2 GF experience 3.25.0.84 streaming to
Shield 2019 PRO
XBOX ONE S 1914 model controller connected via BT directly to PC windows.
Launching game by open desktop (explorer.exe in moonlight interface), after manually loading game.
Other words — moonlight works like image transfer only.
All moonlight controller supports are disabled (tried with enabled too)

I found strange bug in two games (rest looks good):

1. Star wars Jedi Fallen orders — only left analogue stick works — nothing more
2. God Of War — nothing works (controller blocked)

Same games without streaming working good with same controller.

This issue happens not only Moonlight, but with original Nvidia shield streaming client too.

First time i thought that game using my BT Shield remote control as a promary controller, but i disconnected it, reconnect streaming, nothing changes.

So looks like XINPUT works different during streaming and prevents to use controllers connected to PC directly.

If the controller connected to Nvidia shield — no problems.

READ ME FIRST!
This issue tracker is not the right place to ask for troubleshooting help if you’re not able to connect or stream at all. For those requests, please use the #pc-help channel on our Discord server where there are many more people who can help (or direct you back here if it looks like a Moonlight bug after all). https://moonlight-stream.org/discord

Can’t use it for some reason. I only see read this channel

Describe the bug
A clear and concise description of what the bug is.

Steps to reproduce
Any special steps that are required for the bug to appear.

Screenshots
If applicable, add screenshots to help explain your problem. If the issue is related to video glitching or poor quality, please include screenshots.

Affected games
List the games you’ve tried that exhibit the issue. To see if the issue is game-specific, try streaming Steam Big Picture with Moonlight and see if the issue persists there.

Other Moonlight clients

• Does the issue occur when using Moonlight on iOS or Android?

Moonlight settings (please complete the following information)

• Have any settings been adjusted from defaults?
• If so, which settings have been changed?
• Does the problem still occur after reverting settings back to default?

Client PC details (please complete the following information)

• OS: [e.g. Windows 10 1809]
• Moonlight Version: [e.g. v0.9.0]

Win 10

Server PC details (please complete the following information)

• OS: [e.g. Windows 10 1809]
• GeForce Experience version: [e.g. 3.16.0.140]
• Nvidia GPU driver: [e.g. 417.35]

Moonlight Logs (please attach)

• On Windows, Moonlight-###.log files can be found in %TEMP%. Simply type that into the File Explorer path field to navigate there.
• On macOS, Moonlight-###.log files can be found in /tmp. In Finder, press Cmd+Shift+G, then type /tmp to navigate there.
• On Linux with the Flatpak, logs print to the terminal when running with the command: flatpak run com.moonlight_stream.Moonlight
• On Linux with the Snap, logs print to the terminal when running with the command: moonlight

Additional context
Anything else you think may be relevant to the issue

Describe the bug
When starting a stream, HDR will appear to be too bright. If you toggle the HDR setting off and then on in the Windows Display Settings, HDR will appear correctly. This happens on 2021 Apple TV 4K, iPhone 13 Pro Max, and a Sony Android TV (X900H)

Steps to reproduce
Enable HDR in the Windows Display Settings of the host PC. In Moonlight settings, enable HDR. Begin streaming any application, including mstsc. The brightness will be blown out and too bright. Toggle HDR off then back on in the Windows Display Settings. HDR will appear correctly for the entirety of the stream. When you disconnect and reconnect, HDR will be broken again. Moonlight HDR Launcher’s Toggle HDR option also fixes the issue.

Affected games
Affects all games

Other Moonlight clients
iOS and Android

Moonlight settings (please complete the following information)
HDR and HEVC turned on. 4K 60 stream.

Server PC details (please complete the following information)

• OS: Windows 10 and Windows 11
• Moonlight Version: 4.0.0
• GPU: GTX 1080

Other Details
I have an LG 4K HDR Monitor connected to the host. I have a Sony X900H HDR 4K TV attached to the client (it also acts as a client with its Android TV)

my server pc ( windows7 ) installed with i7 6700K and gtx1650
the moonlight stream is running normally on my both android device and windows 10 laptop
but they can only run on h264 mode.
when i try to force it to h265, it just said my device is not supported.
i’m sure gtx1650 encoder and decoder support h265
my windows 10 laptop using i5 8250U and GTX1050
the android phone using snapdragon 675
why i cant run the stream on h265?

Client PC details (please complete the following information)

• Windows 10 1803
• Moonlight 1.1

Server PC details (please complete the following information)

• Windows 7 SP1
• GeForce Experience version: 3.20.0.118
• Nvidia GPU driver: 431.60

Hi

Lately when using moonlight everytime I launch steam directly status is as follows:

This sounds like a minor annoyance, but has two problems

1. non-steam shortcuts in steam fail to load
2. when you hit stop remote play it tells you it can’t exit because you’re in-game

Describe the bug
Using Moonlight for Mac, trying to connect to gaming PC running Geforce Experience, it throws the error «Failed to initialize nvvad audio resources». It works fine with an older Geforce Experience version. However Geforce Experience auto updates the next time you open it, and streaming will be broken again.

Screenshots

Client PC details (please complete the following information)

• OS: MacOS
• Moonlight Version: v3.1.4
• GPU: M1 Pro

Server PC details (please complete the following information)

• OS: Windows 10
• GeForce Experience version: [e.g. 3.24.0.123]
• Nvidia GPU driver: 497.09
• Antivirus and firewall software: Windows Defender and Windows Firewall

Moonlight Logs (please attach)

00:00:00 - SDL Info (0): Compiled with SDL 2.0.15
00:00:00 - SDL Info (0): Running with SDL 2.0.15
00:00:00 - Qt Info: No translation available for  "en_NZ"
00:00:00 - Qt Warning: qrc:/gui/main.qml:12:1: QML ApplicationWindow: ToolTip must be attached to an Item
00:00:00 - Qt Info: Found "gamecontrollerdb.txt" at "/Users/netstat/Library/Caches/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:00 - SDL Info (0): Loaded 63 new gamepad mappings
00:00:00 - SDL Info (0): V-sync disabled
00:00:00 - SDL Info (0): Using VideoToolbox accelerated renderer
00:00:00 - FFmpeg: [h264 @ 0x135836c00] nal_unit_type: 7(SPS), nal_ref_idc: 3
00:00:00 - FFmpeg: [h264 @ 0x135836c00] nal_unit_type: 8(PPS), nal_ref_idc: 3
00:00:00 - FFmpeg: [h264 @ 0x135836c00] nal_unit_type: 5(IDR), nal_ref_idc: 3
00:00:00 - FFmpeg: [h264 @ 0x135836c00] nal_unit_type: 5(IDR), nal_ref_idc: 3
00:00:00 - FFmpeg: [h264 @ 0x135836c00] nal_unit_type: 5(IDR), nal_ref_idc: 3
00:00:00 - FFmpeg: [h264 @ 0x135836c00] nal_unit_type: 5(IDR), nal_ref_idc: 3
00:00:00 - FFmpeg: [h264 @ 0x135836c00] Format videotoolbox_vld chosen by get_format().
00:00:00 - FFmpeg: [h264 @ 0x135836c00] Format videotoolbox_vld requires hwaccel initialisation.
00:00:00 - FFmpeg: [h264 @ 0x135836c00] Reinit context to 1280x720, pix_fmt: videotoolbox_vld
00:00:00 - SDL Info (0): FFmpeg-based video decoder chosen
00:00:00 - Qt Info: Found "gamecontrollerdb.txt" at "/Users/netstat/Library/Caches/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:00 - SDL Info (0): Loaded 63 new gamepad mappings
00:00:00 - Qt Debug: Current Moonlight version: "3.1.4"
00:00:00 - Qt Info: Gamepad mappings are up to date
00:00:00 - Qt Info: "DESKTOP-R1BE03Q" is now online at "192.168.1.2"
00:00:00 - Qt Info: Discovered mDNS host: "DESKTOP-R1BE03Q.local."
00:00:00 - Qt Debug: Found update manifest match for current platform
00:00:00 - Qt Debug: Latest version of Moonlight for this platform is: "3.1.4"
00:00:00 - Qt Debug: Update manifest version equal to current version
00:00:00 - Qt Info: Latest supported GFE server: "99.99.99.99"
00:00:00 - Qt Info: Resolved "DESKTOP-R1BE03Q.local." to QHostAddress("192.168.1.2")
00:00:00 - Qt Info: Resolved "DESKTOP-R1BE03Q.local." to QHostAddress("fda8:8fa4:3a27:1:a50a:b63f:5ca0:c1a8")
00:00:00 - Qt Info: Resolved "DESKTOP-R1BE03Q.local." to QHostAddress("fda8:8fa4:3a27:1:5505:ad67:b495:1a31")
00:00:00 - Qt Info: Resolved "DESKTOP-R1BE03Q.local." to QHostAddress("fe80::a50a:b63f:5ca0:c1a8")
00:00:02 - Qt Info: Ignoring ULA: QHostAddress("fda8:8fa4:3a27:1:a50a:b63f:5ca0:c1a8")
00:00:02 - Qt Info: Ignoring ULA: QHostAddress("fda8:8fa4:3a27:1:5505:ad67:b495:1a31")
00:00:02 - Qt Info: Processing new PC at "192.168.1.2" from mDNS QHostAddress("")
00:00:02 - Qt Info: Executing request: "http://192.168.1.2:47989/serverinfo?uniqueid=0123456789ABCDEF&uuid=3494815321a543909f4b71c6a6e10573"
00:00:02 - Qt Info: Executing request: "https://192.168.1.2:47984/serverinfo?uniqueid=0123456789ABCDEF&uuid=2f60ef9a83f248a7808922b0c724b81d"
00:00:03 - Qt Info: Found "ModeSeven.ttf" at ":/data/ModeSeven.ttf"
00:00:03 - Qt Info: Server GPU: "NVIDIA GeForce RTX 3070"
00:00:03 - Qt Info: Server GFE version: "3.24.0.123"
00:00:03 - SDL Info (0): Video bitrate: 150000 kbps
00:00:03 - SDL Info (0): Audio backend: CoreAudio
00:00:03 - SDL Info (0): Selected audio device: MacBook Pro Speakers
00:00:03 - SDL Info (0): Native layout: Stereo (2 channels)
00:00:03 - SDL Info (0): Audio buffer size: 0.030000 seconds
00:00:03 - SDL Info (0): Audio latency: 0.000000
00:00:03 - SDL Info (0): Audio channel count: 2
00:00:03 - SDL Info (0): Audio channel mask: 3
00:00:03 - SDL Info (0): V-sync disabled
00:00:03 - SDL Info (0): Using VideoToolbox accelerated renderer
00:00:03 - FFmpeg: [hevc @ 0x13492a000] nal_unit_type: 32(VPS), nuh_layer_id: 0, temporal_id: 0
00:00:03 - FFmpeg: [hevc @ 0x13492a000] nal_unit_type: 33(SPS), nuh_layer_id: 0, temporal_id: 0
00:00:03 - FFmpeg: [hevc @ 0x13492a000] nal_unit_type: 34(PPS), nuh_layer_id: 0, temporal_id: 0
00:00:03 - FFmpeg: [hevc @ 0x13492a000] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Decoding VPS
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Main profile bitstream
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Decoding SPS
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Main profile bitstream
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Decoding VUI
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Decoding PPS
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Format videotoolbox_vld chosen by get_format().
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Format videotoolbox_vld requires hwaccel initialisation.
00:00:03 - FFmpeg: [hevc @ 0x13492a000] Output frame with POC 3.
00:00:03 - SDL Info (0): FFmpeg-based video decoder chosen
00:00:03 - SDL Info (0): Audio backend: CoreAudio
00:00:03 - SDL Info (0): Selected audio device: MacBook Pro Speakers
00:00:03 - SDL Info (0): Native layout: Stereo (2 channels)
00:00:03 - SDL Info (0): Audio buffer size: 0.030000 seconds
00:00:04 - SDL Info (0): Audio latency: 0.000000
00:00:04 - Qt Info: Found "gamecontrollerdb.txt" at "/Users/netstat/Library/Caches/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:04 - SDL Info (0): Loaded 63 new gamepad mappings
00:00:04 - SDL Info (0): V-sync disabled
00:00:04 - SDL Info (0): Using VideoToolbox accelerated renderer
00:00:04 - FFmpeg: [hevc @ 0x114893200] nal_unit_type: 32(VPS), nuh_layer_id: 0, temporal_id: 0
00:00:04 - FFmpeg: [hevc @ 0x114893200] nal_unit_type: 33(SPS), nuh_layer_id: 0, temporal_id: 0
00:00:04 - FFmpeg: [hevc @ 0x114893200] nal_unit_type: 34(PPS), nuh_layer_id: 0, temporal_id: 0
00:00:04 - FFmpeg: [hevc @ 0x114893200] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:04 - FFmpeg: [hevc @ 0x114893200] Decoding VPS
00:00:04 - FFmpeg: [hevc @ 0x114893200] Main profile bitstream
00:00:04 - FFmpeg: [hevc @ 0x114893200] Decoding SPS
00:00:04 - FFmpeg: [hevc @ 0x114893200] Main profile bitstream
00:00:04 - FFmpeg: [hevc @ 0x114893200] Decoding VUI
00:00:04 - FFmpeg: [hevc @ 0x114893200] Decoding PPS
00:00:04 - FFmpeg: [hevc @ 0x114893200] Format videotoolbox_vld chosen by get_format().
00:00:04 - FFmpeg: [hevc @ 0x114893200] Format videotoolbox_vld requires hwaccel initialisation.
00:00:04 - FFmpeg: [hevc @ 0x114893200] Output frame with POC 3.
00:00:04 - SDL Info (0): FFmpeg-based video decoder chosen
00:00:04 - Qt Info: Found "gamecontrollerdb.txt" at "/Users/netstat/Library/Caches/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:04 - SDL Info (0): Loaded 63 new gamepad mappings
00:00:06 - SDL Info (0): Found host supported resolution: 1920x1080
00:00:06 - Qt Info: Executing request: "https://192.168.1.2:47984/launch?uniqueid=0123456789ABCDEF&uuid=56beb92f220d4dc69725ddb4f559b16e&appid=291312&mode=1920x1080x0&additionalStates=1&sops=1&rikey=987a653d5bc67fe4008c2a20766ae255&rikeyid=-554096707&localAudioPlayMode=0&surroundAudioInfo=196610&remoteControllersBitmap=0&gcmap=0"
00:00:09 - Qt Warning: Request failed: 602 "Audio: Failed to initialize NvVad audio resources"
00:00:09 - Qt Info: Found "gamecontrollerdb.txt" at "/Users/netstat/Library/Caches/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:09 - SDL Info (0): Loaded 63 new gamepad mappings

I started playing with this for touchscreen support on moonlight-embedded, but have run into some odd behavior when the host computer has multiple monitors. Instead of mapping the mouse position from the reference size to the monitor being streamed, the coordinate is being mapped to the entire area covered by all screens.

For example, if I have two screens (same resolution) side by side and I send a coordinate in the middle of the client’s screen (referenceWidth / 2), the mouse cursor will be placed on the right edge of the host screen being streamed. However, moving past that point does not actually put the mouse cursor on the other monitor. This leads me to suspect it’s not intentional behavior.

Describe the bug
I have the iCloud Keychain extension for Chrome installed on the server. Whenever you go to a site that asks for a password, you have to enter a 6-digit verification code first that pops up on screen. After that you can select the saved password. I connected to my server using mstsc so that I would have full remote desktop functionality, but when the verification code pop-up appears the stream is disconnected and it is impossible to reconnect until you physically close the pop-up on the server.

Steps to reproduce

• Install iCloud application for Windows on server
• Enable iCloud Keychain
• Install iCloud passwords Chrome extension
• Connect to server
• Go to website with a saved password
• Click the iCloud Keychain extension to access passwords

Screenshots
https://user-images.githubusercontent.com/80333845/141130070-f5b0bfa6-7f6e-4f84-93d6-b1005b8b2924.mov

Other Moonlight clients

• Does the issue occur when using Moonlight on iOS or Android? Yes

Moonlight settings (please complete the following information)

• Have any settings been adjusted from defaults? Yes
• If so, which settings have been changed? Bitrate lowered to 30Mbps, inverted scrolling enabled
• Does the problem still occur after reverting settings back to default? Yes

Client PC details (please complete the following information)

• OS: macOS 12.0.1
• Moonlight Version: 3.1.4
• GPU: Radeon Pro 555X

Server PC details (please complete the following information)

• OS: Windows 10 20H2 Build 19042.1288
• GeForce Experience version: 3.23.0.74
• Nvidia GPU driver: RTX 2060 Super driver version: 496.49
• Antivirus and firewall software: Windows Defender and Windows Firewall

Moonlight Logs (please attach)
Moonlight-1636403467.log
Moonlight-1636410637.log
Moonlight-1636412929.log
Moonlight-1636413324.log
Moonlight-1636413358.log
Moonlight-1636413579.log
Moonlight-1636413864.log
Moonlight-1636414396.log
Moonlight-1636414904.log
Moonlight-1636470244.log
Moonlight-1636481395.log
Moonlight-1636552396.log

Additional context
Anything else you think may be relevant to the issue

For some reason, when starting a stream using H.265, I get output that seems to look like it’s running at a lower resolution with a fuzzy, almost interlaced-like look

View post on imgur.com

the same image using H.264

View post on imgur.com

Is this a problem what the client (Shield TV Pro) or my host PC? What’s strange is it only happens randomly.

Describe the bug
I have 2 monitors, the primary is connected by DP and I expect it to disconnect when turned off (which it does) and for moonlight to use the second monitor because my pc considers it the primary (which it does). However, the stream shows a black screen unless i am streaming a full screen game. If the game is in any type of windowed mode, or if I try to stream my desktop, it is blank. I am sure this is related to having 2 monitors because unplugging my second monitor and plugging it into the other HDMI port in my gpu resolves the issue until I turn the other monitor back on, as if the pc «realizes» there are 2 which breaks it again for whatever reason. Unplugging the primary (DP) monitor does not change this behavior by itself.

Steps to reproduce
Have one monitor connected by DP, and one by HDMI. Turn off the DP one and try to stream. In my case this leads to the situations described.

Affected games
Any game if it is not fullscreen.

Other Moonlight clients
Occurs on IOS

Moonlight settings (please complete the following information)
No settings have been changes

Client PC details (please complete the following information)

• OS: MacOS 10.14.5
• Moonlight Version: v3.2.0
• GPU: Intel HD Graphics 6000

Server PC details (please complete the following information)

• OS: Windows 10 Pro 21H1
• GeForce Experience version: 3.24.0.126
• Nvidia GPU driver: 497.29
• Antivirus and firewall software: Windows Defender and Windows Firewall

Moonlight Logs (please attach)
Moonlight-1642885432.log

Steam’s controller remapper simply is not functioning when streaming in Moonlight. Any binding I change does not matter as it always uses the default Xinput controls. I suspect the games are taking input directly from the controller instead of the Steam API. When the Steam BPM overlay is opened it’s supposed to block inputs to the game, but they go right though to it instead. These things are happening only when streaming using Moonlight with a gamepad. Steam gamepad functionality works as expected when playing directly on the desktop.

I’ve run DDU and wiped GFE. Clean installed drivers, GFE and Steam. Toggled every controller support option on Steam and Moonlight. It still happens. I haven’t been able to find a single thing about this on the internet, so I thought I’d post this. Seems like it could be an issue with my configuration but IDK what it could be on my end at this point. Moonlight has worked perfectly fine for me in this aspect for a long time. Apologies if it turns out to not be a Moonlight issue but it kind of seems like it so yeah.

Any help is appreciated.

Host: Windows 11, Version 21H2 (22000.434)
Client: Rog Phone 2 (A11) Moonlight (9.10.1)
Gamepad: RoG Kunai 3
GFE: 3.24.0.126
Nvidia Driver: 511.23

It seems that if the server (Windows PC) has multiple monitors, Moonlight gets very confused and is almost impossible to use.

Also, seems like an easy fix. Is this possible. System works well as far as I can tell, but it can’t properly set the resolution or location of the display it is trying to stream.

Thank you

I’m really confused why I can’t post an issue on the internet hosting page.
I have 5 computers, I wanted to access all of them from one Domain.

This is what I get:
https://imgur.com/a/gr53C6E
it tells me that since I already paired one device then all other devices are in conflict uninstall and reboot the router….

Port forwarding a single port would solve most of the issues here, this feels more like a spray ‘n pray methode

Hi guys,

I ran Moonlight pretty well on my iPhone before. Stopped using for a while and tried to use it today but got error 544 saying cannot configure streamer.

I do received at least 2 GameReady Driver updates between last time when I used Moonlight and now. Not sure if it’s because of that?

Anything I can provide for you to look into the issues?

BTW, Moonlight on my MacBook also receives this error…

Thanks.

As in the title.

I am running games on a computer with dual monitors. One of them is vertical, in case it is important.

When launching a game through the client, the game launches properly, and on the correct (primary) monitor of the host. However, what is streamed to the client is the secondary, vertical monitor.

Is there a way to force Moonlight/GeForceExperience to stream the correct monitor? My main monitor is set as primary both in windows and in GeForce settings.

The only way to make it work is to shut down, physically unplug the second monitor, reboot, and then naturally it works.

Any and all help appreciated!

Describe the bug
Moonlight cannot connect to Gamestream without opening Geforce Experience. Test network in Moonlight will say everything looks fine. Wake PC does not work.

Steps to reproduce
Booting Windows, opening Moonlight will show no connection (offline) to PC. Must open GeForce Experience and navigate to Settings->Shield. After a short while, Moonlight will when then show connected. Previously this step was never needed and opening Moonlight would always automatically connect.

Other Moonlight clients
nVidia Shield on local network will not show connected until the steps above to reproduce are done.

**Client PC details

• OS: Windows 11 Pro 22H2
• Moonlight Version: Latest (as of 10-28-2022)
• GPU: RTX 4090

**Server PC details

• OS: Windows 11 Pro 22H2
• GeForce Experience version: Latest (as of 10-28-2022)
• Nvidia GPU driver: Latest (as of 10-28-2022)
• Antivirus and firewall software:Windows Defender and Windows Firewall

00:00:00 — SDL Info (0): Compiled with SDL 2.24.0
00:00:00 — SDL Info (0): Running with SDL 2.24.0
00:00:00 — Qt Info: No translation available for «en_CA»
00:00:00 — Qt Warning: qrc:/gui/main.qml:12:1: QML ApplicationWindow: ToolTip must be attached to an Item
00:00:00 — Qt Info: Found «gamecontrollerdb.txt» at «C:/Users/#/AppData/Local/Moonlight Game Streaming Project/Moonlight/cache/gamecontrollerdb.txt»
00:00:00 — SDL Info (0): Loaded 465 new gamepad mappings
00:00:00 — SDL Info (0): V-sync disabled
00:00:00 — SDL Info (0): Detected GPU 0: NVIDIA GeForce RTX 4090 (10de:2684)
00:00:00 — Qt Info: Found «d3d11_vertex.fxc» at «:/data/d3d11_vertex.fxc»
00:00:00 — Qt Info: Found «d3d11_overlay_pixel.fxc» at «:/data/d3d11_overlay_pixel.fxc»
00:00:00 — Qt Info: Found «d3d11_genyuv_pixel.fxc» at «:/data/d3d11_genyuv_pixel.fxc»
00:00:00 — Qt Info: Found «d3d11_bt601lim_pixel.fxc» at «:/data/d3d11_bt601lim_pixel.fxc»
00:00:00 — Qt Info: Found «d3d11_bt2020lim_pixel.fxc» at «:/data/d3d11_bt2020lim_pixel.fxc»
00:00:00 — SDL Info (0): Using D3D11VA accelerated renderer
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] nal_unit_type: 32(VPS), nuh_layer_id: 0, temporal_id: 0
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] nal_unit_type: 33(SPS), nuh_layer_id: 0, temporal_id: 0
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] nal_unit_type: 34(PPS), nuh_layer_id: 0, temporal_id: 0
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Decoding VPS
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Main 10 profile bitstream
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Decoding SPS
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Main 10 profile bitstream
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Decoding VUI
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Decoding PPS
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Format d3d11 chosen by get_format().
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Format d3d11 requires hwaccel initialisation.
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Decoder GUIDs reported as supported:
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {86695f12-340e-4f04-9fd3-9253dd327460} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {ee27417f-5e28-4e65-beea-1d26b508adc9} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {6f3ec719-3735-42cc-8063-65cc3cb36616} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {1b81bea4-a0c7-11d3-b984-00c04f2e73c5} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {1b81bea3-a0c7-11d3-b984-00c04f2e73c5} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {32fcfe3f-de46-4a49-861b-ac71110649d5} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {d79be8da-0cf1-4c81-b82a-69a4e236f43d} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {f9aaccbb-c2b6-4cfc-8779-5707b1760552} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {1b81be68-a0c7-11d3-b984-00c04f2e73c5} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {5b11d51b-2f4c-4452-bcc3-09f2a1160cc0} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {107af0e0-ef1a-4d19-aba8-67a163073d13} 104 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {20bb8b0a-97aa-4571-8e99-64e60606c1a6} 104 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {15df9b21-06c4-47f1-841e-a67c97d7f312} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {efd64d74-c9e8-41d7-a5e9-e9b0e39fa319} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {ed418a9f-010d-4eda-9ae3-9a65358d8d2e} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {9947ec6f-689b-11dc-a320-0019dbbc4184} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {33fcfe41-de46-4a49-861b-ac71110649d5} 103 106 107
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {463707f8-a1d0-4585-876d-83aa6d60b89e} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {a4c749ef-6ecf-48aa-8448-50a7a1165ff7} 104 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {dda19dc7-93b5-49f5-a9b3-2bda28a2ce6e} 104 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {b8be4ccb-cf53-46ba-8d59-d6b8a6da5d2a} 103 104 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {6affd11e-1d96-42b1-a215-93a31f09a53d} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {914c84a3-4078-4fa9-984c-e2f262cb5c9c} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] {8a1a1031-29bc-46d0-a007-e9b092ca6767} 103 106
00:00:00 — FFmpeg: [hevc @ 000002A43AA340C0] Output frame with POC 3.
00:00:00 — SDL Info (0): FFmpeg-based video decoder chosen
00:00:00 — Qt Info: Found «gamecontrollerdb.txt» at «C:/Users/#/AppData/Local/Moonlight Game Streaming Project/Moonlight/cache/gamecontrollerdb.txt»
00:00:00 — SDL Info (0): Loaded 465 new gamepad mappings
00:00:00 — Qt Debug: Current Moonlight version: «4.3.0»
00:00:00 — Qt Info: Gamepad mappings are up to date
00:00:00 — Qt Info: Latest supported GFE server: «99.99.99.99»
00:00:00 — Qt Info: Discovered mDNS host: «DESKTOP-2IVNSH0.local.»
00:00:00 — Qt Debug: Found update manifest match for current platform
00:00:00 — Qt Debug: Latest version of Moonlight for this platform is: «4.3.0»
00:00:00 — Qt Debug: Update manifest version equal to current version
00:00:00 — Qt Info: Resolved «DESKTOP-2IVNSH0.local.» to QHostAddress(«192.168.137.170»)
00:00:00 — Qt Info: Resolved «DESKTOP-2IVNSH0.local.» to QHostAddress(«fe80::6823:52b4:3af4:2bec»)
00:00:00 — Qt Info: «DESKTOP-2IVNSH0» is now online at «192.168.137.170:47989»
00:00:01 — Qt Warning: Aborting timed out request for «https://192.168.137.170:47984/applist?uniqueid=0123456789ABCDEF&uuid=6a818a3a9b454bf1a78d95df4f74e05f»
00:00:01 — Qt Warning: «applist» request failed with error QNetworkReply::OperationCanceledError

As in the title. I have a dual monitor set up.

Unless I disconnect the second monitor and reboot my PC, moonlight will prefer the wrong monitor.

Games launch on the correct monitor, on the host PC, as this is set as my Primary Display in windows.

In case it is relevant:

• I have a GTX 970
• The secondary monitor is oriented vertically
• The secondary monitor uses a HDMI connection
• The primary monitor uses a DVI connection
• Both monitors are 1080p
• This is true for any game (or manually added executable) launched through moonlight

It’s really inconventient needing to get behind my PC to connect/disconnect my HDMI cable any time I want to stream, and the wear and tear on the port makes me nervous in this economy!

Any help or suggestions would be deeply appreciated, and just let me know if I can provide any further info.

Thanks!

Describe the bug
When using the mouse mode on a gamepad, the mouse cursor doesn’t display when a Windows UAC prompt appears. However, it is still functional (i.e. I can move the cursor over buttons and click them). I just can’t see the cursor. The cursor appears fine before and after the UAC prompt.

Steps to reproduce
Open up any game/application that requires UAC and observe that the cursor disappears. I’m generally streaming my Windows desktop.

Gamepad-related issues (please complete if problem is gamepad-related)
My gamepad is connected to the Shield TV using Bluetooth. It’s an Xbox One controller.

Device details (please complete the following information)
I’m using Moonlight Android on a Shield TV.

Server PC details (please complete the following information)

• OS: Windows 10 Home 19042.867
• GeForce Experience version: 3.22.0.32
• Nvidia GPU driver: 466.11
• Antivirus and firewall software: Bitdefender, Windows Firewall

Additional context
This has been a problem since I started using Moonlight (~4-5 months ago), not a recently introduced issue.

Sometimes, the mouse cursor actually does show up. But it’s very rare and I can’t seem to get it to do that consistently.