Why is there a copy protection system in the graphics, and is it crippling the game?

You all do know that this is being controlled by one .dll (dynamic linking library) that is client side. Disabling this may "correct" many problems we are experiencing... Just thinking out loud...

Wrong, you should've seen Bioshock and Oblivion when they were first released. Talk about getting a little crispy.

Stopped reading here. I've told you approximately 4 or 5 times now that streaming of textures or animations has never been postulated.

Streaming of specific parts of the scene, probably just characters, after having been rendered on the server has been posulated, but is thought to be highly unrealistic and very unlikely.

Streaming of some MODELS from the server to the client, to be 'remote rendered' in the second process has been postulated, and is thought to be the most likely manifestation of the theory if it is in fact true.

Every thing you say continues to harp on about streaming textures and animations, despite the fact that it's never been suggested that these things were streamed.

I'm just going to stop even paying attention every time you start spouting these ridiculously far off the mark bits of nonsense.

Dont be silly, EVAL DRM IZ UBERHEETING MY PC!!!!!!111111

Keep it up.

Mind if I use your last line as my guideline for your topic?

Very good read, would be a bit paranoid of BW to do something like this. I hope that BW will respond to this also.

English, French, German. Each is roughly 7gb. Comes out exactly right. English only is 20gb. Yours (with 2) is 27gb. Beta was 34gb.

That's how SOME of the methods work: they put forth a multitude of methods, of varying levels of difficulty and protection offered. There's a pair of methods suggested of rendering part of a model in software and part of it in hardware, what they call 'hybrid rendering', and then zipping them back together. Even in the paper this is stated to cause a substantial performance hit, particularly regarding a couple of the buffers, and probably requiring special care being taken to integrate the two different parts properly.

A method like that could be used here: The server sends the client the (possibly encrypted) character model, the client sends it to the second process. The second process decodes it if needed, and then software renders the model based on the scene information specified by the client. The finished result is then zipped into the final render of the scene as carried out by the main client.

And the fact that nobody in history has tried to do it and that it's stupid and clunky are actually the entire point.

If it's happening, it needs not to be.

But it's such overkill that it seems highly implausible.

It just fits with some of the problems far too well to just discard without properly evaluating it first.

This...actually makes sense. I'll add it to the OP.

If you run hardware without "safeguards" in the drivers, that's on you. That's the only software at fault, the drivers. Oh and there is all the over-clocking that people do, which chip makers tell you not to do because you need a safety margin in the hardware in case you did a nutty and installed beta drivers without safeguards in them.