Not a Fan. I'm an enjoyer
And that's when you remember why you have been an average AMD enjoyer.
So for me what you want sounds either like magic or like nonsense.
Ray casting is part of physics processing and therefore need a physics body. Using physics body actually should reduce performance impact since you can reduce the geometry of those making calculation less extensive as when you use the full Mesh geometry with al the details.
So for me just creating an auto generated physics body for ray pickability or using the actual mesh geometry sounds like the same thing. But maybe I'm missing something here.
I think in general this problem exist on Reddit as well having multiple subreddits focused around the same stuff it's just like you cannot have the exact same name twice. But I don't know in how many game Dev subs I am on Reddit 😁
There is a opened feature wish for this https://github.com/LemmyNet/lemmy/issues/3071
However I think with all the other (maybe more important) stuff on the line I think it will take a while.
Big Part of my daily business is explaining people what they should code... People aren't reliable as well.
I'm sure in a few years from now nobody will code anymore and you will just tell the AI what you want to see implemented.
Same as nobody writes actual machine code anymore and everyone only uses higher languages.
Thanks for mentioning this. I will definitely check this out
Pro Tip:
Don't just watch other people doing stuff in a video and replicate it. Make your own project, think about what needs to be done and then explicitly search for answers to your questions.
Game Dev is even more about identifying tasks then it is about solving them.
I cannot explain the exact details but I remember during the first great Twitter exodus some people discovered a drawback in the ActivityPup protocol that seems to cause performance issues when very influencial users post on a small/under powered instance.
Because communicating all that stuff to many other instances is more costly than spreading it only to people on the same instance. So technically speaking large instances have a performance advantage and must just scale accordingly to the user number.
Everyone agreed that this need to change in oder to ensure a healthy federated ecosystem but I don't think it was be fixed by now.
Actually, I don't think there is a technology some could recommend that will magically boost your career. Because this will highly depends on what will be required in upcoming projects and no one can know this. So just go with whatever you want and what your interested in.
However, one skill that many technical people are missing is the ability to communicate with other people outside of their own skill spectrum. In my eyes this is the most important thing if we talking about career, because in the end the money never comes from technology it comes from humans and in many cases non technical people decide about you promotion.
So I don't think there is a blueprint for learning such skills, but I guess best thing to do would learning by doing. Go start communicating more with people outside of a technology bubble, try to organize events with other people or maybe even get politically active. Learn to know when people know what you are talking about and when not. Good example would be the use of the abbreviation LOE in your original comment. People seam not to understand what this actually should mean. Here it doesn't hurt much but doing this stuff to often when explaining a concept to a college maybe end up in false Implementation because of misalignment.
To much is always to much.
My advice would be to implement it first and try to optimize if you need to. I think disabling object outside of a range what the player can currently interact with would probably be a good start to save performance.