-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to start stream: error code -1 #66
Comments
please upload your log to pastebin go settings->enable debug log->connect->if got error, close app and upload |
Thanks, connection_stage_starting - stage: 1 Its strange because its working on my iOS devices P.S. Greetings and thanks for the help :) |
oops.. i forgot add to log... |
please check with this |
Initializing platform...connection_stage_starting - stage: 1 |
please retest with this please paste to http://pastebin.com/ :) |
and can you share info about modified GFE? that sound is interesting :) |
Thanks. and the modification is from the good people of XDA :) |
No Problem, have a good night :) the Log: |
ok. i guess that's tcp socket problem of vita. i'll make more small test set for this. thanks :) |
Thanks for the help, i will not be available the next week, but i will check after i come back from vacation. |
thanks, and here is the log :) |
@d3m3vilurr This definitely looks like a bug in the sockets implementation. Moonlight-common-c places TCP sockets in non-blocking mode using FIONBIO to allow the connect() operation to timeout out if necessary, however it sets the sockets back to blocking mode before returning from connectTcpSocket(). See the code here: https://github.com/moonlight-stream/moonlight-common-c/blob/master/src/PlatformSockets.c#L229 The socket appears to still be in non-blocking mode when recv() is called, which is certainly the cause of the failure. |
I made non-block socket
anyway, current build config not set i'll try rechecking socket and socket options at tonight. PS. it's little strange issue, other sockets are working.(eg. libcurl) :( |
@d3m3vilurr Do you have that socket code somewhere that I can look at? In a proper BSD/POSIX sockets implementation, sockets must start in blocking mode for correct application behavior. If they're starting in non-blocking mode, that's a serious bug that would break most applications running on that implementation. If FIONBIO isn't defined, that's okay - it just won't enable the connection timeout. Libcurl may work because it tries to enable non-blocking sockets itself, so it expects the EAGAIN return value and uses select() or poll() to wait for data. |
ok. i found problem. @cgutman you are right. vita-newlib's setsockopt is wrong. i'll make patch newlib or moonlight-common-c. (but i guess it probably newlib's problem.) @cgutman i was wrote wrong before. i expect socket open |
@bam2000 please check this build. sorry i'm late :/ |
Hey, no problem :) |
i'll attach newer vpk to release page asap ;) |
Could you please give me the download address of GFE 2.2.3 ? My GPU is GT750M. And I am use the way like @bam2000 to open the gamestream. However, I could not find the Geforce Experience version2.2.3, |
Please provide the following info.
NVidia Geforce Experience version: 2.2.3
Moonlight Embedded version: 0.1.0
Moonlight Embedded running on: Vita, iOS 10
Output of Moonlight Embedded:
What is the expected result?
Stream starting
What happens instead of that?
Failed to start stream: error code -1
failed stage: rtsp handshake
(Error code -1)
First of I have to use a old version of GeForce experience since my gt650m is not supported native.
So i use a modified version 2.2.3
With moonlight Alpha 6 while installing everything i got a connection with my vita and it worked.
Since 0.1.0 I get the error above, and when i downgrade to Alpha 6I also get the error message.
I have also installed moonlight on my iPad and it's connecting just fine no error. So I have to assume that's a problem with the vita version of moonlight.
I really hope someone can help me find the problem.
The text was updated successfully, but these errors were encountered: