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.
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.