Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
2. 2008 Macbook Unibody, Intel C2D 2.0 Ghz, NVIDIA Geforce 9400M 256 MB, 8GB DDR3, Wireless
3. 30 fps
4. Yes, in most games.
5. Cinamatic scenes dropped in fps greatly, but game play wise, it seems like encoding and decoding might be factors, my latency looks fine.
6. Somewhat, but it only occurs briefly.
7. There was a little bit of lag in input here and there, but nothing to major.
2. Laptop, Core i5 3437U, Intel HD 4000, 8GB RAM, Connected Via Wifi (BT HomeHub 5 Router)
3. Crysis 2: "Automatic" to all settings = nigh unplayable (avg: 16fps), "Unlimited Bandwidth/30FPS/Desktop Resolution" = 32FPS, very playable. 60FPS = crash/fail
4. 30 - very playable, 60 - crash/fail
5. Maintained framerate at 32FPS (approx) no issue. However when set to automatic fluctuates between 11-16FPS.
6. No
7. Latency was "noticable" yet no worse than playing Killzone2 or an online game with 100/150 latency
So far tried Trine 2 and Path of Exile. Both are rock solid playable at 30fps 1080p (external laptop connected to laptop)! Control lag is less noticable than streaming Via NVIDIA's Shield. Absolutely excellent work folks! This is totally playable on a laptop that is otherwise perfectly useless for gaming.
The automatic setting selects 30fps, the lock to 60fps setting murders the laptop (red line on stats graphs jumps all over the place), I imagine thats a decoding issue, as the framerate is good on PC still. I will try wireless next. Thanks!
EDIT: On wireless Streaming, same setup as above, but with Wireless G and 720p now. Input latency is a bit worse, but image quality holds up surprisingly well, even far from WAP. Sound quality is poor though, a lot of skips and pops. Its not as good as Nvidia Shield, which can hit 60fps at 720p, but thats on wireless N, and on much newer hardware. Another thing, the automatic framelock setting is going to 60fps I think (because of the lower resolution?); however, the laptop can't decode that even at 720p, so locking it to 30 gave much better results. Might want to rethink were the cutoff is at on the automatic setting.
RANDOM POINT: Doesn't seem to be a way to disable 3dvision from the client, also its not obvious that 3dvision is active when playing on the client, so you're taking the performance hit without seeing 3d. Maybe pop a warning that 3d is on, or disable it somehow when streaming? Thanks again!
assetto corsa failed to run
1. i5 760 3.3ghz, asus p7p55d, corsair xms3 4 x 2gb, 2 x msi nvidia 660ti in sli, creative xifi titanium, netgear wnr834bv2, cat 5 cables less than 5 meters in length, in game streaming latency above 100ms, ping only 1-2ms
2. samsung r530 laptop, i3 2.13ghz, intel graphics media accelerator
3. automatic - when frame rate remains above 50fps. but if frames drop below 40fps it locks to 30fps automatically and doesnt climb again
4. 30fps - even though it reads almost 30fps graphics very jerky
60fps - between 50 - 60fps but controls feel sluggish
5. when i open the stats graph the red line shoots up and causes massive lag, blue line stays steady. i have to disable hardware coding as game runs at about 4fps when enabled
6. no
7. sometimes
2. i5-3210M, Intel HD4000, same network at the running computer.
3. Automatic. For all games.
4. The game ran at the desired framerate for both 60FPS and 30FPS settings.
5. Mainly the network.
6. The game did not play smoothly when the framerate dropped below the selected setting, but light visual tearing was noticable when the framerate spiked higher.
7. Latency was mainly based on my network, but input latency was never an issue, and was not linked to framerate loss.
1. Intel Core i7 3770, GTX 680, 10mbps netspeed.
2. Intel Core Duo E6300, GTX 210, 10mbps netspeed.
3. Automatic settings for Trine 2, Audiosurf & Left 4 Dead 2.
4. 60 fps option gives something about 27-58 fps. 30 fps option - 27-29 fps. Good enough, I think.
5. Looks like all my small lags comes from network speed. All the games were playable, but Audiosurf sometimes stutter for a bit, ~0,3 sec (but still playable). Left 4 Dead 2 (shooter!) was almost perfect and Trine 2 looks pretty similar to L4D2.
6. Yep, smooth enough.
7. Yes, games are fully playable, latency was just fine, something about 30-50ms.
Well done Valve! I'll starting to build third computer to another room.
OS : 1# Linux 3.12 (Mint 16), driver nvidia 331.20
2# Windows 7 (can't remember driver version but at least 1 year old)
Client : Laptop Asus N53J (on wifi)
OS : Linux 3.12 (Mint 15), driver nvidia 331.20
Game tested :
That's all I've tested for now. Hope this will help. Btw great work ! :)
2. CPU: T5800 | GPU: HD3470 Mobility | NET: Realtek (from Toshiba A300-1LT)
3. Poker Night - max, War Thunder - lags on every settings, DOTA2 - max (all games 720p)
4. 30FPS and 60FPS works fine
5. decoding
6. no
7. yes
2. Client Hardware: Surface Pro 2, i5-4200U @ 1.6GHz, Integrated Graphics
Both computers on 802.11n Wifi, tested game was Runner 2 at 1920x1080 (native resolution for both systems)
3. The 60FPS lock seemed to be the most stable and smooth looking in presentation and responsiveness. 30FPS lock was similar, but with some occasional stutters and an (obviously) lower framerate, and Automatic was realy bad, with terrible stuttering and an even lower FPS than either 60 or 30 (19FPS vs 33FPS and 29FPS, respectively).
4. 30FPS lock was able to keep its framerate lock, 60FPS lock wasnt (33 instead of 60), but it kept very stable at the FPS it managed to hit.
5. It looks like most of the issue was the decoding (which makes sense, a 1.6Ghz i5 isnt a lot to work with) and some caused by network stuttering
6&7. At Automatic settings, the erratic framerate made Runner 2 somewhat playable. The game would be alright on easy, but any thing over normal difficulty, expecially later in the game, would be almost impossible with the stutter and lag issues. Stutter in the framerate seemed to also effect the input at the same rate, so you wouldnt be able to dodge an obstacle in the game even if you could see it.
Keep up the good work, guys. I look forward to seeing more!