Mark Hamil and John Rhys-Davies might have been an easier sell, having been in Wing Commander. For the rest, maybe they were excited to work on something that hasn't been done before. The quality of the characters shown in the trailer is crazy.
Have you checked it out since they added Hurston?
Unedited https://media.discordapp.net/attachments/271503305283338250/...
Watermark edges https://media.discordapp.net/attachments/271503305283338250/...
The grid of noise in the highlighted edges is from the jpeg compression on the screenshot, if we had the full quality original to work from it'd look cleaner.
http://fotoforensics.com/analysis.php?id=9c41c242d475089ea8c...
It's a low-alpha checkerboard, and it's actually quite visible.
Doing it in Gimp is easy. Load the image; Filters->Edge Detect->Sobel
They must've been pressed on time.
At that point, the GPU doesn't care if it's overlaying text or something like a barcode. The main priorities would be resilience to image/video compression, and being large enough that you can't just crop it out of screenshots, while not impeding gameplay. Since it's only for the unstable testing builds, why spend more time than necessary implementing it?
Is there something I'm missing about what's wrong with this approach?
Instead of hiding an image of a text in a layer, they could've encoded the text itself (i.e. the ascii values) into the texture. That's trivial to do and doesn't produce visually-discernible artifacts as per above.
It'd be overkill if they were building this feature from the ground up starting with nothing but a string, but they weren't.
They render ID into rasterized text (blocks of pixels) and blend in these blocks. But they could've just as easily rendered raw 0s and 1s of the ID into blocks the exact same way. It just would've not looked like text, but as a random pattern.
But a rasterized text has a lot more information about each character than the raw ASCII values. If you halve the resolution or add compression artifacts an OCR will still pick it up.
If they rendered raw binary data they would have to add lots of redundant information as well as spreading it out over a large enough area. Maybe that's what you meant but didn't fit the 'trivially to do' part for me. Seems a lot easier to just render the text.
You still get leaks because people take screenshots for their bug reports, upload them somewhere (even with an unlisted URL) for discussion on the bug reports forum, and then other users under the same NDA can download your screenshots and share them (rather than getting busted for leaking their own). So having a screenshot from a bug report leak isn't necessarily actionable for banning people.
But it's still useful to prevent, say, users under NDA streaming the super buggy builds on Twitch. Once they're relatively stable, CIG drops the NDA requirement, opens testing to a wider audience, then eventually push out to the main servers.
Doing this with a disguised UI component is a pretty cute implementation.