Yep. It's my understanding that it's no longer a "priority" but he's not going to snub things like that- to not support the OS is to cut one's nose off to spite one's face. Moreover, if he wants any "in" on the Netbook/Handheld/Mobile Phone market, he's going to have to still "do" Linux stuff because WinCE isn't there. You want to target, you have to deal with iPhone/Android/Limo/OpenEmbedded. Seriously.Seriously though, I remember reading/hearing somewhere that he was indeed very fond of DX11 but that he would continue to release his games on Linux for now. This is supported by this article.
Doom3, Quake4, QuakeWars, and soon QuakeLive. Someone's trolling and not doing a very good job of it.You don't know if Doom 3 was ever released for Linux? What kind of gamers are you guys?
It's people doing the sky is falling, the sky is falling at the drop of a hat because it's in vogue- they misconstrue ONE thing the man says and run with it.Here I give you something to think about:
- Every ID game since Quake had been released on Linux with a native installer and in most cases without support. Why would they stop now?
- The Linux game market always has been crap compared to the Windows game market. However it is at it's all time best right now. Why would they stop now?
- If they don't like to support Linux any more, how come they are still porting Quake Live to Linux?
Heh... I'm one of the honest advocates and evangelists for Linux gaming and have been for quite a long time.EDIT: Heh, I just noticed Svartalf in the slashdot comments on the article.
what kind of epic networking does unigine boast?
Massive MMO stuff's going to be "fun" though. It's not a simple, easy thing to do- and it's the reason behind why I said that the bunch preaching that the games can be local to the company and served across the net to itty-bitty set-top boxes and special clients on PC's and Mac's were selling snake oil.
An example of what I'm talking about- I explained this to someone in private while I was out on holiday:
frank@frank-laptop:~$ traceroute www.phoronix.com
traceroute to www.phoronix.com (184.108.40.206), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 5.184 ms 7.231 ms 7.371 ms
2 10.91.176.1 (10.91.176.1) 23.188 ms 25.024 ms 26.316 ms
3 66-169-205-97.ftwo.tx.charter.com (220.127.116.11) 26.752 ms 27.098 ms 30.150 ms
4 so-6-0-0.edge4.Dallas1.Level3.net (18.104.22.168) 30.427 ms 30.856 ms 31.150 ms
5 ae-34-89.car4.Dallas1.Level3.net (22.214.171.124) 32.730 ms ae-14-69.car4.Dallas1.Level3.net (126.96.36.199) 32.039 ms ae-24-79.car4.Dallas1.Level3.net (188.8.131.52) 32.399 ms
6 THE-PLANET.car4.Dallas1.Level3.net (184.108.40.206) 31.486 ms 22.229 ms 17.638 ms
7 et1-1.ibr02.hstntx1.theplanet.com (220.127.116.11) 27.592 ms 29.284 ms 31.746 ms
8 et1-3.ibr02.hstntx2.theplanet.com (18.104.22.168) 31.842 ms 34.555 ms 33.647 ms
9 po2.car02.hstntx2.theplanet.com (22.214.171.124) 34.365 ms 40.392 ms 41.184 ms
10 ev1s-209-62-40-52.theplanet.com (126.96.36.199) 41.929 ms 42.539 ms 46.734 ms
This means I experienced roughly a 45ms latency to Phoronix from the hotel. That's a fairly clean link there, especially for a hotel ISP one. I was pleasantly surprised.
You have to cope with a lot of 45-150ms or worse latencies for the traffic you're processing. If your timing atom is larger than 200ms, you feel the drag on a FPS or similar type game. Some games actually have smaller atoms- 100ms. At 100ms, you have precisely 55ms to address all interactions that the player just made with the world in toto, along with all the other players in toto, before the next timing frame if you use the connection from the hotel as your example. You have 85ms in the case of a link like mine (which is NOT the norm right at the moment- not even close...). If your ping time plus the time you need to process everyone's interactions exceeds the atom timing size, you start losing stuff, lagging stuff, or both depending on the design you chose for things. Motion estimation compensates for some of this, but it doesn't fix as much as many make it out to. Streaming RUDP does as well- it's part of why Q3:A plays as nicely as it does online over the Internet. But, it's not going to make doing an MMO easy or nice in that regard.
Last edited by Svartalf; 05-26-2009 at 12:54 AM. Reason: Expanded on my remarks... :-D
isnt latency the reason they strategically place servers at certain locations. eg, Chicago or Dallas. Or Germany for Europe representation.
Looks like your trace-route doesn't even leave Texas. Most people dont game in a hotel room they do it at home with purchased internet connections.
I have a stable 55.5 MS to Phoronix.com from Toronto. My ISP eats up 13 MS of that.
Heres a distance representation.
obviously, that would be a really stupid airplane route. Your packets may go around the world if you are on HE or Cogent. Heck if i want to connect to chicago using cogent it takes it to new york first.... But any decent network is going to get you from A to B with few hops.
1 192.168.0.1 (192.168.0.1) 0.365 ms 0.356 ms 0.346 ms
2 * * *
3 xxxx.xxxx.rnc.net.cable.rogers.com (66.185.xxx.xxx) 9.673 ms 9.676 ms 9.768 ms
4 xxxx.xxxx.phub.net.cable.rogers.com (66.185.xxx.xxx) 9.368 ms 9.499 ms 9.492 ms
5 xxxxxxxxx.wlfdle.phub.net.cable.rogers.com (66.185.81.xxx) 37.751 ms 37.863 ms 37.856 ms
6 188.8.131.52 (184.108.40.206) 27.045 ms 23.850 ms 23.829 ms
7 eqix.asbn.twtelecom.net (220.127.116.11) 24.315 ms 24.553 ms 24.538 ms
8 hagg-03-ge-1-0-0-538.hsto.twtelecom.net (18.104.22.168) 52.712 ms 52.436 ms 52.691 ms
9 po1.car02.hstntx2.theplanet.com (22.214.171.124) 53.247 ms 53.514 ms 53.216 ms
10 ev1s-209-62-40-52.theplanet.com (126.96.36.199) 56.665 ms 56.749 ms 57.045 ms
This is not how the internet works. It's a self organizing routing system. Routers can send packages through different routes depending on the current network situation. Furthermore less hops is not always faster. If a hop in between becomes a lagger for one reason or another you might be faster taking a detour using faster and less stressed hops. So it's not that easy as "less hops = faster".
I guess you could say it's like avoiding the freeway during rush hour traffic. Sure, city streets are slower and have traffic lights, but you still got home 2 hours earlier than if you took the freeway.