A quest to stream from mobile Kepler

Search This thread

Character Zero

Senior Member
Aug 22, 2010
847
112
Mine fully works.
Core i7
Geforce 750M

Just played some Batman Arkham City, Dishonored, etc. Mercenary Kings doesn't see the controller though.

---------- Post added at 03:44 PM ---------- Previous post was at 03:42 PM ----------

I really hope Nvidia doesn't take this "hack" away!
 

cgutman

Senior Member
Aug 14, 2010
485
430
OMG!!!! It works. Credit to @cgutman!!!!!
Used the registry entry you provided. I am using a Lenovo Y400, that has the intel GPU disabled. It freaking works!!

So that definitely suggests it's something to do with Optimus specifically, since the 750M in your Y400 and the 650M that I tried are both based on GK107 (possibly different silicon revisions though).

The reason i suggested what i did was because after using the reg entry from this post I have got a pc with
i3-something dual core
GT620
8gig ram
to connect for streaming, it just does not show any games atm.

The GT 620 is a rebadged Fermi GPU so it doesn't have the hardware onboard to do the encoding.
 

Character Zero

Senior Member
Aug 22, 2010
847
112
I was pretty blown away because I assumed it would not work. I took a gamble and it paid off. Thanks for your work on this!!!
 

cgutman

Senior Member
Aug 14, 2010
485
430
In theory, this also means that GK107-based (probably GK208 too) variants of the GT 630 and GT 640 desktop GPUs should also work.

It looks like all Kepler-based GPUs have the hardware to do this. On the desktop side, I'm not aware of anything that would interfere with it working. It might require the DisableStreamingCheck hack for lower-end/unsupported cards but it should work.

On the mobile side, it's a bit more complex. It seems to work for laptops without Optimus that have Kepler-based GPUs using the registry hack. For us Optimus users, it seems like there is a technical limitation in the current version of the software that prevents it from working. At least we know where the problem is, so I'll try messing around with Optimus when I get home from work today.
 

Character Zero

Senior Member
Aug 22, 2010
847
112
In theory, this also means that GK107-based (probably GK208 too) variants of the GT 630 and GT 640 desktop GPUs should also work.

It looks like all Kepler-based GPUs have the hardware to do this. On the desktop side, I'm not aware of anything that would interfere with it working. It might require the DisableStreamingCheck hack for lower-end/unsupported cards but it should work.

On the mobile side, it's a bit more complex. It seems to work for laptops without Optimus that have Kepler-based GPUs using the registry hack. For us Optimus users, it seems like there is a technical limitation in the current version of the software that prevents it from working. At least we know where the problem is, so I'll try messing around with Optimus when I get home from work today.

Yeah like I mentioned upthread on Geforce Forums someone asked about their X51 desktop that had Optimus. The response was they were working on it. I assume once they get that done, it should work on mobile too. I guess they didn't announce support for mobile GPUs due to the likelyhood of Optimus. Pretty cool it works though, gives hope!

Just as an FYI, I have a Asus R65 router and was streaming with the Shield connected 5GHz and the laptop 2.4GHz.
 

cgutman

Senior Member
Aug 14, 2010
485
430
Then how come I can connect to the PC, popup to connect. My shield connects to the pc, it just says "No supported PC games available".
please explain that.

Screenshot 1
Screenshot 2

I don't have an explanation for that one.

You can enable logging using the by creating a DWORD value at HKLM\SOFTWARE\Nvidia Corporation\NvStream\EnableLogging with the value set to 1.

Restart the streaming service, then try to replicate the error. The log should be in C:\Windows\System32\config\systemprofile\AppData\Local\NVIDIA Corporation\nvstreamsvc, but you'll may need to traverse that manually due to permission issues.

See my first post for more info on this.
 
I have a gtx675mx in my asus G75vx. No optimus, and 3630qm core I7. I ran the reg file and restarted the nvidia streaming service. the experience software still says im not ready to stream with a circle and slash on the gpu. Does the stream capability in the status menu change? Or should i just expect it to work? I get my shield delivered tomorrow, so in my excitement watching this thread update with awesome news, i wanted to set it up. Thanks dudes!

edit: driver version is 325.71 if thats relevant. Asus is lame about driver updates, so i dont know if i have a new enough driver to even do it...
 
Last edited:

Character Zero

Senior Member
Aug 22, 2010
847
112
I have a gtx675mx in my asus G75vx. No optimus, and desktop core I7. I ran the reg file and restarted the nvidia streaming service. the experience software still says im not ready to stream with a circle and slash on the gpu. Does the stream capability in the status menu change? Or should i just expect it to work? I get my shield delivered tomorrow, so in my excitement watching this thread update with awesome news, i wanted to set it up. Thanks dudes!

edit: driver version is 325.71 if thats relevant. Asus is lame about driver updates, so i dont know if i have a new enough driver to even do it...


Mine still has the circle and slash symbol but works.

Why do you have to rely on Asus for GPU drivers? If its totally dedicated then you should be able to get your updates straight from Nvidia (I do but I have a Lenovo). I think you have to have the latest beta driver.
 

Character Zero

Senior Member
Aug 22, 2010
847
112
funny you should say that, right after i posted, i went and downloaded the latest beta, and it installed and worked fine. Glad to hear the indicator isn't an indication for my chances at success ;). I can't wait until my toy arrives tomorrow!

Just an FYI, you need to install the first OTA to get streaming to work. I was trying before I got the OTA and it wasn't working and I thought that it just wasn't working. But then I got the OTA and it said it enabled streaming, so after that it started working.
 

wrc1010

Senior Member
Jul 27, 2012
94
8
1) Can Lenovo Y400 can be use to force to stream the pc game now because i want to buy it?

2) Will the Lenovo Y400 meet the requirement for streaming the pc game from laptop in future when announce by nvidia because Lenovo Y400 have GT750M and the minimun requirement for laptop is GTX660M?
 
Last edited:

Character Zero

Senior Member
Aug 22, 2010
847
112
1) Can Lenovo Y400 can be use to force to stream the pc game now because i want to buy it?

2) Will the Lenovo Y400 meet the requirement for streaming the pc game from laptop in future when announce by nvidia because Lenovo Y400 have GT750M and the minimun requirement for laptop is GTX660M?

Yes! I am using the Y400 with the GT750M with the forced streaming registry entry provided in this thread.

Now the newer Y410p, I am not sure if that would work because I think the Intel GPU in enabled. I can't be sure.
 
Last edited:

l_JC_l

New member
Aug 10, 2013
4
0
Yes! I am using the Y400 with the GT750M with the forced streaming registry entry provided in this thread.

Now the newer Y410p, I am not sure if that would work because I think the Intel GPU in enabled. I can't be sure.

11.08.13 20:33:53:532 ] LOGGER.CREATE
[11.08.13 20:33:53:532 DEBUG] Creating IPC Server
[11.08.13 20:33:53:532 DEBUG] Running IPC Server
[11.08.13 20:33:53:535 DEBUG] SSAU.EntryPoint
[11.08.13 20:33:53:535 INFO] StreamServiceAsUser constructed
[11.08.13 20:33:53:536 DEBUG] Restoring taskbar if the taskbar is hidden.
[11.08.13 20:33:53:539 DEBUG] ConfigUtil::StreamingSessionControl(STREAMING_SESSION_CONTROL_DEACTIVATE)
[11.08.13 20:33:53:572 DEBUG] useGfeOpsManager = 1
[11.08.13 20:33:53:593 DEBUG] GfeOpsManager: streaming data for "Steam" is available at "C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam"

[11.08.13 20:33:53:598 DEBUG] GfeOpsManager: streaming data for "Steam" is available at "C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam"

[11.08.13 20:33:53:602 DEBUG] GfeOpsManager: streaming data for "Borderlands 2" is available at "C:\ProgramData\NVIDIA\Updatus\StreamingAssets\borderlands_2"

[11.08.13 20:33:53:609 DEBUG] GfeOpsManager: streaming data for "Left 4 Dead 2" is available at "C:\ProgramData\NVIDIA\Updatus\StreamingAssets\left_4_dead_2"

[11.08.13 20:33:53:613 DEBUG] GfeOpsManager: streaming data for "Metro 2033" is available at "C:\ProgramData\NVIDIA\Updatus\StreamingAssets\metro_2033"

[11.08.13 20:33:53:618 DEBUG] GfeOpsManager: streaming data for "The Elder Scrolls V: Skyrim" is available at "C:\ProgramData\NVIDIA\Updatus\StreamingAssets\skyrim"

[11.08.13 20:33:53:618 DEBUG] SupportedApps =
[11.08.13 20:33:53:618 DEBUG] {
[11.08.13 20:33:53:618 DEBUG] {
[11.08.13 20:33:53:619 DEBUG] Title=Steam
[11.08.13 20:33:53:619 DEBUG] ExeName=steam.exe
[11.08.13 20:33:53:619 DEBUG] ExeDir=I:\Steam\
[11.08.13 20:33:53:620 DEBUG] CmdLineArgs= -bigpicture
[11.08.13 20:33:53:620 DEBUG] KeyFramePath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam\keyframe.dat
[11.08.13 20:33:53:621 DEBUG] AssetsPath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam\steam-big-picture-box-art.png
[11.08.13 20:33:53:621 DEBUG] AssetsDir=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam
[11.08.13 20:33:53:621 DEBUG] KeyFrameTimeout=60
[11.08.13 20:33:53:621 DEBUG] AppId=48358832
[11.08.13 20:33:53:621 DEBUG] MainWindowClass=CUIEngineWin32
[11.08.13 20:33:53:622 DEBUG] MainWindowTitle=Steam
[11.08.13 20:33:53:622 DEBUG] AutomationLaunch=false
[11.08.13 20:33:53:622 DEBUG] }
[11.08.13 20:33:53:622 DEBUG] {
[11.08.13 20:33:53:622 DEBUG] Title=Steam
[11.08.13 20:33:53:623 DEBUG] ExeName=steam.exe
[11.08.13 20:33:53:623 DEBUG] ExeDir=Q:\Steam\
[11.08.13 20:33:53:623 DEBUG] CmdLineArgs= -bigpicture
[11.08.13 20:33:53:623 DEBUG] KeyFramePath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam\keyframe.dat
[11.08.13 20:33:53:623 DEBUG] AssetsPath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam\steam-big-picture-box-art.png
[11.08.13 20:33:53:624 DEBUG] AssetsDir=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\steam
[11.08.13 20:33:53:624 DEBUG] KeyFrameTimeout=60
[11.08.13 20:33:53:624 DEBUG] AppId=48260528
[11.08.13 20:33:53:624 DEBUG] MainWindowClass=CUIEngineWin32
[11.08.13 20:33:53:624 DEBUG] MainWindowTitle=Steam
[11.08.13 20:33:53:625 DEBUG] AutomationLaunch=false
[11.08.13 20:33:53:625 DEBUG] }
[11.08.13 20:33:53:625 DEBUG] {
[11.08.13 20:33:53:626 DEBUG] Title=Borderlands 2
[11.08.13 20:33:53:626 DEBUG] ExeName=C:\Windows\system32\cmd.exe
[11.08.13 20:33:53:626 DEBUG] ExeDir=Q:\Steam\SteamApps\common\Borderlands 2\
[11.08.13 20:33:53:627 DEBUG] CmdLineArgs=/c start steam:" -applaunch 49520 -nolauncher"
[11.08.13 20:33:53:628 DEBUG] KeyFramePath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\borderlands_2\keyframe_negative.dat
[11.08.13 20:33:53:628 DEBUG] AssetsPath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\borderlands_2\borderlands-2-box-art.png
[11.08.13 20:33:53:628 DEBUG] AssetsDir=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\borderlands_2
[11.08.13 20:33:53:628 DEBUG] KeyFrameTimeout=60
[11.08.13 20:33:53:628 DEBUG] AppId=82838976
[11.08.13 20:33:53:628 DEBUG] MainWindowClass=LaunchUnrealUWindowsClient
[11.08.13 20:33:53:629 DEBUG] MainWindowTitle=Borderlands 2
[11.08.13 20:33:53:629 DEBUG] AutomationLaunch=false
[11.08.13 20:33:53:629 DEBUG] }
[11.08.13 20:33:53:629 DEBUG] {
[11.08.13 20:33:53:629 DEBUG] Title=Left 4 Dead 2
[11.08.13 20:33:53:630 DEBUG] ExeName=C:\Windows\system32\cmd.exe
[11.08.13 20:33:53:630 DEBUG] ExeDir=Q:\Steam\SteamApps\common\left 4 dead 2\
[11.08.13 20:33:53:630 DEBUG] CmdLineArgs= /c start steam://rungameid/550
[11.08.13 20:33:53:630 DEBUG] KeyFramePath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\left_4_dead_2\keyframe_negative.dat
[11.08.13 20:33:53:631 DEBUG] AssetsPath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\left_4_dead_2\left_4_dead_2-box-art.png
[11.08.13 20:33:53:631 DEBUG] AssetsDir=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\left_4_dead_2
[11.08.13 20:33:53:631 DEBUG] KeyFrameTimeout=60
[11.08.13 20:33:53:631 DEBUG] AppId=2532608
[11.08.13 20:33:53:632 DEBUG] MainWindowClass=Valve001
[11.08.13 20:33:53:632 DEBUG] MainWindowTitle=Left 4 Dead 2
[11.08.13 20:33:53:632 DEBUG] AutomationLaunch=false
[11.08.13 20:33:53:632 DEBUG] }
[11.08.13 20:33:53:632 DEBUG] {
[11.08.13 20:33:53:634 DEBUG] Title=Metro 2033
[11.08.13 20:33:53:634 DEBUG] ExeName=C:\Windows\system32\cmd.exe
[11.08.13 20:33:53:634 DEBUG] ExeDir=Q:\Steam\SteamApps\common\metro 2033\
[11.08.13 20:33:53:634 DEBUG] CmdLineArgs= /c start steam://rungameid/43110
[11.08.13 20:33:53:634 DEBUG] KeyFramePath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\metro_2033\keyframe_negative.dat
[11.08.13 20:33:53:635 DEBUG] AssetsPath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\metro_2033\metro_2033-box-art.png
[11.08.13 20:33:53:635 DEBUG] AssetsDir=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\metro_2033
[11.08.13 20:33:53:635 DEBUG] KeyFrameTimeout=60
[11.08.13 20:33:53:636 DEBUG] AppId=15742176
[11.08.13 20:33:53:639 DEBUG] MainWindowClass=_uengine_
[11.08.13 20:33:53:640 DEBUG] MainWindowTitle=Metro 2033
[11.08.13 20:33:53:640 DEBUG] AutomationLaunch=false
[11.08.13 20:33:53:640 DEBUG] }
[11.08.13 20:33:53:640 DEBUG] {
[11.08.13 20:33:53:640 DEBUG] Title=The Elder Scrolls V: Skyrim
[11.08.13 20:33:53:641 DEBUG] ExeName=C:\Windows\system32\cmd.exe
[11.08.13 20:33:53:641 DEBUG] ExeDir=Q:\Steam\SteamApps\common\skyrim\
[11.08.13 20:33:53:641 DEBUG] CmdLineArgs= /c start steam://rungameid/72850
[11.08.13 20:33:53:641 DEBUG] KeyFramePath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\skyrim\keyframe_negative.dat
[11.08.13 20:33:53:641 DEBUG] AssetsPath=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\skyrim\skyrim-box-art.png
[11.08.13 20:33:53:642 DEBUG] AssetsDir=C:\ProgramData\NVIDIA\Updatus\StreamingAssets\skyrim
[11.08.13 20:33:53:642 DEBUG] KeyFrameTimeout=60
[11.08.13 20:33:53:642 DEBUG] AppId=92423008
[11.08.13 20:33:53:642 DEBUG] MainWindowClass=Skyrim
[11.08.13 20:33:53:642 DEBUG] MainWindowTitle=Skyrim
[11.08.13 20:33:53:643 DEBUG] AutomationLaunch=true
[11.08.13 20:33:53:643 DEBUG] }
[11.08.13 20:33:53:643 DEBUG] } // SupportedApps
[11.08.13 20:33:53:643 INFO] Creating Mongoose Http listener
[11.08.13 20:33:53:695 DEBUG] NVIDIA GPU's = {
[11.08.13 20:33:53:695 DEBUG] {
[11.08.13 20:33:53:695 DEBUG] FriendlyName=GeForce GTX 670
[11.08.13 20:33:53:696 DEBUG] IsStreamingSupported=1
[11.08.13 20:33:53:696 DEBUG] }
[11.08.13 20:33:53:696 DEBUG] {
[11.08.13 20:33:53:697 DEBUG] FriendlyName=GeForce GT 430
[11.08.13 20:33:53:697 DEBUG] IsStreamingSupported=0
[11.08.13 20:33:53:697 DEBUG] }
[11.08.13 20:33:53:697 DEBUG] }
[11.08.13 20:33:53:698 INFO] Starting MDNS Responder Thread
[11.08.13 20:33:53:699 DEBUG] HandleRequestsLoop started
[11.08.13 20:33:53:700 INFO] Registering Service JC-PC._nvstream._tcp on port 47989

[11.08.13 20:33:53:700 INFO] MDNS Responderdnssd_clientstub: connecting to port 0

[11.08.13 20:33:53:701 INFO] ExitMonitor thread started

[11.08.13 20:33:53:713 INFO] Create window: 130c2c (0)

[11.08.13 20:33:53:741 WARN] MDNS Responder: bound to 56814
[11.08.13 20:33:53:742 INFO] MDNS Responder: Running service directly

[11.08.13 20:33:53:790 INFO] MDNS Responder: Finished Service Registration attempt

[11.08.13 20:33:53:870 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:54:273 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:54:526 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:54:527 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:33:54:701 INFO] MDNS Responderdnssd_clientstub: connecting to port 56814

[11.08.13 20:33:54:780 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:54:887 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:55:38 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:55:38 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:33:55:303 INFO] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:55:304 INFO] MDNS Responder: ProcessResult
[11.08.13 20:33:55:304 INFO] Service now registered and active

[11.08.13 20:33:55:557 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:33:56:52 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:33:56:567 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:33:57:893 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:33:58:66 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:34:02:75 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:34:06:925 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:34:10:76 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:34:26:90 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:34:33:991 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:34:58:93 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:35:01:608 INFO] UI ask is server streaming supported

[11.08.13 20:35:01:609 INFO] Sending Is Server Streaming Supported: 0

[11.08.13 20:35:55:165 ] Received Query from 192.168.0.2 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:36:02:106 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:37:36:173 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:36:173 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:36:297 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:37:36:396 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:36:397 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:36:616 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:36:617 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:36:962 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:37:976 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:38:942 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:39:948 ] Received Response from 192.168.0.11 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:37:40:959 ] Received Response from 192.168.0.11 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:37:46:171 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:46:247 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:37:46:394 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:46:619 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:51:166 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:51:270 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:37:51:391 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:51:614 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:56:162 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:56:239 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:37:56:404 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:37:56:612 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:38:01:203 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:38:01:255 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:38:01:393 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:38:01:616 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:38:06:166 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:38:06:225 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:38:06:392 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0
[11.08.13 20:38:06:443 INFO] Start broadcasting unpairing all for 20000 ms.
[11.08.13 20:38:06:444 INFO] Start broadcasting SERVICE_UNPAIR_ALL
[11.08.13 20:38:06:445 ] Received Response from 192.168.0.2 addressed to 224.0.0.251 on 0000000006A19EF0
[11.08.13 20:38:06:615 ] Received Query from 192.168.0.11 :5353 to 224.0.0.251 :5353 on 0x0000000006A19EF0

Any idea for my problem? In my shield dont see my pc :(

Q6600 670 GTX Windows 7 ultimate 64bits.
 

mustardseed

New member
May 13, 2011
1
0
Just wanted to chime in and say the registry patch works splendidly on my Macbook Pro with the 650m and Intel HD 4000. Only hangup was I has my resolution zoom set to 150% which caused Steam to not work for streaming. After changing that, it works great! Thanks!

Sent from my Nexus 4 using xda app-developers app
 

1wayjonny

Senior Member
Jan 3, 2007
466
1,197
Mine fully works.
Core i7
Geforce 750M

Just played some Batman Arkham City, Dishonored, etc. Mercenary Kings doesn't see the controller though.

---------- Post added at 03:44 PM ---------- Previous post was at 03:42 PM ----------

I really hope Nvidia doesn't take this "hack" away!

This is because of rxinput.dll not being loaded, it hook into the Win32 API. It is because of one of two issues see below.

1) https://forums.geforce.com/default/...-no-input-in-games-uefi-amp-secureboot-only-/

2) https://forums.geforce.com/default/...le-to-use-shield-controller-once-game-starts/
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Enable Game Streaming on mobile kepler (GT750m)

    Great idea! It worked. Using NvFBCEnable and spoofing the requests made to http://gfwsl.geforce.com I managed to enable Game Streaming on a GT750M with the latest GeForce Experience.
    You must first install python 2, but everything else you will need should be here.
    I'll try to list the steps required to make Game Streaming work:

    1. Enable frame buffer capture. It should remain enabled, even after restarting.
    NvFBCEnable.exe -enable from an Admin prompt

    2. Copy patch.py to %PROGRAMFILES%\NVIDIA Corporation\NvStreamSrv
    3. Get Nvidia GPU devid from Device Manager (Properties, Details tab, Hardware Ids dropdown, DEV_xxxx, xxxx is the id)
    4. Run "python patch.py xxxx" (xxxx is the devid) to patch the gpu devid whitelist from nvstreamsvc.exe

    5. Add a redirect from gfwsl.geforce.com to localhost in %SystemRoot%\system32\drivers\etc\hosts
    You can also use the hosts file that I have provided
    6. Start server.py
    Beware of other processes listening on the 80 port (Skype is one of them - go to Tools, Options, Advanced, Connection and untick "Use port 80 and 443....")
    7. Profit

    If processes start crashing or using the entire CPU you should rename
    C:\Program Files\NVIDIA Corporation\NvStreamSrv\rxinput.dll
    and
    C:\Program Files (x86)\NVIDIA Corporation\NvStreamSrv\rxinput.dll
    to whatever you want.

    I haven't tested this on any other machines, so please provide feedback.
    5
    Game streaming via GFE is only officially supported for GTX 600 series desktop GPUs. I want to see what we can do about that. I'll be detailing a bunch of things I've tried and learned during my experience messing with getting this to work.

    Update for GFE 2.x.x
    p1gl3t has developed a new hack for modern GFE versions. I was able to stream with GFE 2.2.3 from a GT 650M laptop with Optimus - something I couldn't do with my original hack because Optimus was unsupported at the time. I followed the steps from this and this. In addition to what the tutorial said, I had to "net stop nvstreamsvc" and "net start nvstreamsvc" after starting the server for it to work but YMMV.

    Update for GFE 1.6.1
    GFE 1.6.1 added countermeasures for the original registry hack that broke it for machines that had it working with GFE 1.6.0. Fortunately they were not difficult to work around and I've developed another registry hack that works on GFE 1.6.1+. This supersedes the original registry hack and works for both GFE 1.6.0 and 1.6.1. I've updated the link in this post to point to the new hack. Note that laptops with Optimus still don't work with Shield Streaming http://xdaforums.com/showpost.php?p=45599322&postcount=66

    Update
    For those running Kepler-based desktop and mobile GPUs without Optimus, the DisableStreamingCheck hack enables streaming to the Shield (the attachment from this post). Note: Not all 600/700 series GPUs are Kepler-based.
    For Optimus users, it's still not working.

    General Info on Executables

    First, the GFE game streaming code lives in C:\Program Files\NVIDIA Corporation\NvStreamSvc. The 2 main executables are NvStreamSvc.exe and NvStreamer.exe.

    NvStreamSvc.exe is installed as a Windows service set to auto-start. It is responsible for several (known) things:
    - Enumerating installed games via GFE Ops Manager
    - Enumerating the NVIDIA GPU hardware
    - Registering _nvstream._tcp with the MDNS responder that allows Shield to see the computer.
    - Handling incoming streaming requests and starting NvStreamer.exe

    NvStreamer.exe is the streaming program used to broadcast the game to the Shield.

    There's also another file rxinput.dll which appears to be loaded by every process on the machine, presumably to do input injection for the controller.

    Reverse Engineering
    To gain some initial insight into GFE, I downloaded and started Process Explorer. I limited the events to those from nvstreamer.exe and nvstreamsvc.exe, while concentrating on registry events. I found that there is definitely some enumeration of video adapters going on, particularly interesting was that it was querying the HardwareID value, presumably to check against a blacklist/whitelist.

    I also noticed a peculiar little registry query that piqued my interest. I saw nvstreamsvc.exe do a query on HKLM\SOFTWARE\Nvidia Corporation\NvStream\DisableStreamingCheck. Could it be too good to be true? Yes and no.

    When I created a DWORD value there, set it to 1, and restarted the NVIDIA streaming service, my Shield now could see my computer and browse my library of Steam games. Sadly, I was still unable to start streaming them. When I tried, my Shield displayed "Cannot launch the game because NVFBC is not supported".

    I continued looking at registry accesses and stumbled upon another curious one: HKLM\SOFTWARE\Nvidia Corporation\NvStream\EnableLogging. When I created that DWORD value, set it to 1, and restarting the NVIDIA streaming service, nvstreamsvc.exe began writing a log file which I found after looking at disk accesses in Process Explorer. The log is located in: C:\Windows\System32\config\systemprofile\AppData\Local\NVIDIA Corporation\nvstreamsvc. Note: You may have to manually traverse this path because several folders are only browsable with admin permissions which prevent explorer from going directly to that path (it will say it doesn't exist).

    The log file gave some insight into the problem, but not enough to make much headway. I've pasted some relevant portions:

    Code:
    [05.08.13 23:25:35:64 DEBUG] NVIDIA GPU's = {
    [05.08.13 23:25:35:66 DEBUG] 	{
    [05.08.13 23:25:35:69 DEBUG] 	FriendlyName=GeForce GT 650M
    [05.08.13 23:25:35:71 DEBUG] 	IsStreamingSupported=0
    [05.08.13 23:25:35:73 DEBUG] 	}
    [05.08.13 23:25:35:75 DEBUG] 	{
    [05.08.13 23:25:35:77 DEBUG] 	FriendlyName=INTEL(R) HD GRAPHICS 4000
    [05.08.13 23:25:35:79 DEBUG] 	IsStreamingSupported=0
    [05.08.13 23:25:35:81 DEBUG] 	}
    [05.08.13 23:25:35:83 DEBUG] }
    
    ....
    
    [05.08.13 23:36:40:538  INFO] HTTP LOG Entering s_handleAppLaunch 14
    
    [05.08.13 23:36:40:541 ERR0R] ServiceUtil::EnableNvFBC() failed since NvAPI_D3D9_NVFBC_GetStatus() failed with RET=0xfffffffa
    [05.08.13 23:36:40:544 ERR0R] Failed to enable FBC
    [05.08.13 23:36:40:546  INFO] StreamerProcessWrapper::FindAndKillStreamer
    [05.08.13 23:36:40:563  INFO] StreamerProcessWrapper::StartStreamerProcess
    [05.08.13 23:36:40:567  INFO] Streamer path: C:\Program Files\NVIDIA Corporation\NvStreamSrv\nvstreamer.exe
    
    [05.08.13 23:36:40:574  INFO] Failed to find management Ip address. Reverting to default
    
    [05.08.13 23:36:40:577  INFO] NvSCI Server IP=192.168.56.1
    
    [05.08.13 23:36:41:115 DEBUG] Streamer thread started
    [05.08.13 23:36:41:121  INFO] Event: NOP: NOP
    
    [05.08.13 23:36:41:121  INFO] StreamerWrapper thread started.
    [05.08.13 23:36:41:126 DEBUG] NvFBC NOT Supported
    [05.08.13 23:36:41:132 DEBUG] session=1375770993&appid=56731104 response:
    [05.08.13 23:36:41:140 DEBUG] <?xml version="1.0" encoding="utf-16"?><root protocol_version="0.1" query="launch" status_code="529" status_message="Cannot launch the game since NVFBC is not supported."><gamesession>1375770993</gamesession><winlogon>0</winlogon></root>
    [05.08.13 23:36:41:148  INFO] HTTP LOG Exiting s_handleAppLaunch 14


    This is the point where I'm now stuck. I can't figure out how to get that NvFBC unsupported error solved. Hopefully we can figure this one out and liberate the Shields! :D
    4
    I was reading another forum and someone was asking if his Alienware X51 desktop would work. It has Optimus (for some reason, doesn't really make sense for a desktop) and the response was that Optimus was unsupported on desktops right now. So I wonder if there is a similar issue for laptops since most would have Optimus. Looks like from that log it is picking up both GPUs. And I wonder if one (like the Intel HD4000) returns a 0 for supported streaming, if returns 0 for all. In my case I have a Lenovo that has the intel IGP disabled, so I am only running a 750M, all they would need to do is whitelist it.

    That's an interesting point. AFAIK, Optimus copies the frame buffer from the discrete GPU to the integrated GPU, which may be unsupported for NvFBC right now (although in theory the data should still be in the discrete GPU's frame buffer too).

    If you're not running Optimus, the DisableStreamingCheck hack may work for you. Just run the reg file and either manually restart "NVIDIA Streaming Service" or reboot your machine.

    EDIT: GeForce Experience will still say your configuration unsupported but that expected. It doesn't have any effect on whether the hack works or not.
    3
    Driver version 358.50 for Windows 10 confirmed working with a GT640M! The host unit is an Acer Aspire V3-571G-9686 laptop. It is an i7, 16GB RAM, 256GB SSD, GT640M, Steam runs from an external 1TB USB 3.0 drive I have. The workstation I had used to test from is an older Dell 4700 upgraded to a Q6600 CPU, 6GB RAM, and a 9800 PCIe card.

    I have so far only tested from the laptop (gb LAN) to the workstation (WiFi) and as I am at work the test was performed remotely using TeamViewer (a session to the host and workstation).

    This was possible with the help of this post along with some minor edits and tweaks. I'm going to outline my steps in hopes it might help someone else.

    1) So I download and clean installed the latest non-beta Nvidia drivers for my model card. I may try those beta drivers at some point as I understand they add 4k?
    2) From the post linked above I downloaded the NvGE.zip that user posted.
    3) Downloaded and installed Python 2.7.1.0 using default path it wanted to be installed in.
    4) Enabled frame buffer using provided exe from the link NvGE.zip "NvFBCEnable.exe -enable"
    5) From the NvGE.zip I copied the patch.py to "%PROGRAMFILES%\NVIDIA Corporation\NvStreamSrv" This file also needs to be edited for this item but I also found in the latest drivers from Nvidia some files are named differently. So after a little trial and error I also edited this line

    SRV = 'nvstreamsvc.exe'

    to be this instead

    SRV = 'NvStreamUserAgent.exe'

    6) Then I ran the edited patch script from CMD while in the "%PROGRAMFILES%\NVIDIA Corporation\NvStreamSrv" location like this 'C:\Python27\python.exe patch.py 0FD2' (replace '0FD2' with your device ID, you can see how get this from step #3 in post #123)
    7) From 'services.msc' I disabled the 'NVIDIA Network Service'. This was needed to keep GFE from fixing itself via updating.
    8) Edited my "C:\Windows\System32\drivers\etc\hosts" to add these two lines. Again making sure GFE can't talk to Nvidia for updates as that will break the patch.

    127.0.0.1 gfwsl.geforce.com
    127.0.0.1 services.gfe.nvidia.com


    9) From post #123 I did not need to run the "server.py" to use Moonlight at this point. Everything was just working. Can anyone tell me what that is for exactly?

    I hope I have everything and it makes sense.

    thanks!


    EDIT: opened ports per instructions on Moonlight setup guide and was able to pair and stream from my home to my Shield tablet at work no problem (other than I have a pretty slow upload from home with my Internet provider).

    EDIT #2: Played a couple various games last night, Bastion and Mirror's Edge, from my Shield TV. Bastion did hang the Shield TV a couple times (still was running on the laptop) but to tell the truth my laptop has been having some odd issue with the LAN port. It works fine then all of sudden loses its IP address. I've yet to have real time to resolve this. I think the Shield TV simply lost connectivity. I switched to WiFi and that seemed to resolve that problem. After switching I fired up Mirror's Edge and played for nearly an hour without any issue at all. I appear to be able to use GameStream or Moonlight no problem. GameStream the first time I fired it up did make NvStreamSvc crash but without making any changes at this point it is now working fine. No idea what was the issue there?

    EDIT #3: OK I resolved my goofy LAN card issue by forcing it to 100 half duplex. Apparently the driver that comes with Windows 10 (I assume this is the fault as on Windows 8.1 it never did this) for my particular LAN card when set to auto negotiate causes that problem but also the driver doesn't give me a choice of 1000, whatever. It is working great now, seems just as fast as before, and no more weird disconnects due to the assigned IP suddenly failing. Every game I've tried to this point works really well.

    Big thanks to all those that came up with the parts needed to make this happen. I have been wanting to gamestream 'properly' really bad for some time. Just a feature I really wanted. I was on the edge of buying a new laptop even. This totally saved me. :)
    2
    Gamestream does not show up as an option under preferences in GeForce experience. I also am on 2.1.2, could that be an issue? I cannot for the life of me figure out why this isn't working, but my computer shows up whether I do the hack or not.

    EDIT:
    Updated my GeForce experience, now works flawlessly. Thanks for you solution this is way awesome, and WAY better than splashtop was!