The Xbone

[Zeph]

So this here is pretty neat. Distributed lighting between server and client via the internet. And it uses, wait for it, voxels! This is basically lighting by numbers. Who called it? I called it. Go to hell.

Unfortunately for Xbone, it's running AMD hardware.

Fuck off. You not see that last part of the video or something?
Latency was the reason I said was why you don't render the simulation with data not from the client.
The moment you tie dynamic lighting into something players control is the moment that 100ms latency becomes input lag and you know damn well how much gamers despise input lag.

This has its uses in the LAN, but that's it. On a regular networked game, the latent lighting from a flashlight means you see a player come around the corner before his lighting catches up with him and you can not see around the corner until your flashlight catches up with you.

[Warsaw]

Except it looked pretty good even at those very high latencies, even with the jumpy light. That's what compensatory algorithms can do for you. And how many gamers play with 500-1000 ms latency rates? Anybody serious enough to care about that little bit of lag is not going to be playing on such an awful connection. Not only that, but the direct lighting isn't what this is really about, it's the diffuse. As in, the stuff that's going to actually use up the local resources at a greater rate when it tries to model where the photons are scattering to instead of simply being told where they are and then mapping it. Finally, this doesn't necessarily have to be tied to a player-controlled item, it can be environmental. The goal is offloading some of the work, not making everything controlled remotely.

So get real, you are pulling it out of context and seem to have a narrow idea of what this stuff can and will be used for. You said it wasn't workable and Nvidia just demonstrated that it is.

[Zeph]

Oh yeah, I'm definitely out of context with a narrow idea of what it can be used for even though I've said it's perfectly fine in a LAN setting where latency is low/non-existant while disastrous for interactive things like games where lag is incredibly noticeable.

You're posting in a FUCKING XBOXONE THREAD about something that would be a disaster if implemented on something the console was using while saying I have no clue what I'm talking about. You've admitted that you have no programming experience on this. Not like I've actually coded things reliant on serialization for games or anything oh wai.....


You're worse than 9mm ever was. He even admitted to never reading things he talks about and you haven't gotten there yet.



If you actually did read what you brag about you'd know that this can indeed work with the xbone. Their goal was to see if the hardware environment could support such a thing and it did. However, they've stated that latency is indeed the weak point in the system and they don't expect it should be implemented for anything beyond a few network hops. Do I really need to go over how many hops are likely to take place along the player's home, local ISP, high tier host, the XBL datacenter, and then the compute farm itself?

Seriously, the whole research project just confirmed that the hardware today has enough bandwidth to be a light farm for 50 or so local clients and remain competitive in quality you'd expect for higher-end PC hardware. This is something that would push light from your PC to your nVidia Shield.

[Btcc22]

And how many gamers play with 500-1000 ms latency rates?

Quite a lot if they try this out with the current state of Internet speeds in most of the world. What you saw in that video was using up to 43Mbps.

[Higuy]

I don't see why this is great. Your streaming a crticial part of the engine from a serverbox over a internet connection, just for ligthing. What good possible uses would this have? Maybe some clearer, sharper graphics, but is that really neccessary nowadays? You're getting latency just for maybe a slightly noticable difference if it was all being done local.

[neuro]

So this here is pretty neat. Distributed lighting between server and client via the internet. And it uses, wait for it, voxels! This is basically lighting by numbers. Who called it? I called it. Go to hell.

Unfortunately for Xbone, it's running AMD hardware.

except unreal has been using voxel based lighting ever since lightmass.
it's how all dynamic meshes are lit.

[Zeph]

http://www.youtube.com/watch?v=lbrmAsxJPv4

Stupidest idea ever putting a native wireless receiver on the console.
BRB, going to an MLG LAN and haxxoring the consoles in the middle of matches.

[CabooseJr]

It comes with a sticker, so it's clearly the better console.

[Dwood]

I don't know if this has been mentioned yet, but it would seem that they are using a proprietary connection for the Kinect to XBone. I knew something like that would happen. For shame.

Edit: Here, I found a source:
http://arstechnica.com/gaming/2013/0...t-work-on-pcs/

[Warsaw]

The old Kinect had a proprietary connector. The USB adapter was only there because older Xbox 360s didn't have that proprietary connection port, only USB. They don't want people using the new one on Windows like last time, they want them to pay the $400 for the Windows version. Of course, I'd be willing to bet that some will simply splice a USB connector onto the Xbone version.