this post was submitted on 14 Jun 2023
230 points (100.0% liked)
Technology
37740 readers
776 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I work as a game developer and a programmer. There are a lot of possibilities for people to be wrong. Especially when it comes to design or usage. A lot of misinformation in programming is like "Yeah this answer is technically correct" with this specific case but when you scale it, it breaks entirely. Like https://forums.unrealengine.com/t/stealth-based-mechanics/6992/6 is a great example where yeah a trace will work, your data will be inaccurate a bit, you won't be able to scale it and it won't work with a lot of edge case lighting. The better solution is to use a grey-colored mesh and a scene capture to get information consistently about both the baked and dynamic lighting. You might even have a better way, like getting the data from lumen or shadow maps.
So even with things you think won't have misinformation, you get misinformation, and people are guessing while presenting they are right.