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

Well I got yellow used to announce the dev posts, for obvious reasons. Red to try to get people to see the big huge caveat. What color to use to differentiate the rest then, neon green? And technically it's just 'blue' per the forums...I can go lighten it up a bit maybe.

And actually I've been editing the post to try to clarify things to keep people from misunderstanding and jumping to quite so many false conclusions, so that newcomers reading it get a better idea of what's going on. Also adding in whatever plausible bits of explanation I can come up with, but without modifying the text or locking it off until it's confirmed.

Things that are pretty well conclusively proven wrong are closed off in spoiler tags and labeled to that effect within them as well. I'd use strikethrough instead but that doesn't seem to be an option, at least not that I can find.

All that died when publishers decided that mediocre products couldn't possibly be the reason for falling revenue, it had to be pirates.

Oh - and I might as well add:

SWTOR.exe PID 6772 (they main pid I think that is doing all the disk reads, etc) is:

935.220 MB memory / 900,488 private

SWTOR.exe PID 2156 (the secondary process the above guy is doing something with) is:
292,824 MB memory / 197,776 private

That is a heafty primary process, huh?

Agreed

But I just want to play a game that actually works. Turn it on, log in, and go kill something.

Then go pirate it. That's the delicious irony of DRM. No matter how much we want to actually pay for a game, the pirated DRM free version is almost always higher quality. THANKS FOR THAT UBISOFT!

Based on my logs:

The secondary process is only accessing registry information about the entire system, no TCP communication either with local or remote servers.

The only asset it did access was the shaders.bin file.

Should be same for everyone, I'm using retail DVD version, never participated to beta test.
Got 2 32Bit swtor.exe's running, one is taking 270K and other bit over 1Gb RAM.

the 'bnk' in there reminds me of the bink video/audio codecs you used to see being used for cinematics on games all the time. Other than that your guess is as good as mine.

Just scanning the registry? Could very well be our 'warden' if that's the case.

I still type too fast. -.0

I understand that, but on my reading, there's a heck of a lot of hyberbole & speculation still in the white sections - maybe that's just my reading of it. I just would prefer to see it kept to known facts, and leave the speculation for the thread itself. For an equivalent example, you don't go labelling a process a rootkit until you are very very sure of what it does. Even the thread title assumes and implies a copy protection system in place. A newcomer is very much led down a given path of thinking. You still have statements like:

Seriously, what exactly is the news about TOR having two processes? Out of process communication & proxy processes are pretty commonplace. I've written two in the last year for our product; it enables you to do all sorts of things. Please stop with the utterly unhelpful rampant speculation as to what they do. You don't know unless you've looked at the code. A bunch of numbers is frankly meaningless statistics about activity, not what activity they are doing. Of course those two processes are going to communicate - they wouldn't be there if they weren't. Forgive me if I sound perjorative or terse, but as a software engineer I really would prefer to see some hard facts about the code itself. The Wireshark idea is an interesting one.

Has it occurred to anyone at all yet that the words Remote Renderer mean 'remote as in another process' because I'd surely consider calling a remote rendering server that I run next to the main app so as to work around 32-bit address space limitations exactly that.