Wow, this is so unbelievably unoptimized. The sound of my computer fans makes it so immersive.
The shadow map is being rendered twice with 300+ draw calls and 1M+ triangles. Full resolution GTAO is probably even more expensive with a lot of fetches per texel. I'm sure there are a ton of low hanging optimization fruits and I'm confident claude et. al can fix all those issues, but if you don't know where to look and never profile the app then you get a vibe coded unoptimized mess.
It's a work in progress. I have cut down on the original mesh size by quite a bit but continue to do that. I also fade out the resolution of the map tiles as you approach the horizon so you aren't loading ihgher res satellite images than you need. I've run entire flights on my 2022 mac pro with no issue, but as this is a side project it remains not as optimal as it could be. Any suggestions for order of operations / what should be fixed next are welcome :-)
awesome, I will look at each of these, one at a time. my bigger issue today was that I was not expecting so many people to try the app and have unoptimized bandwidth costs. bringing those down first and then will be looking into optimizations like you have listed. I honestly just built this thing for fun & it was running fine for me. now that others are using it it's time to start thinking about performance more. Appreciate the thoughts.
One thing that really kills this for me is it just takes a straight line flight. It really needs to take flight data and pick a track that performed that flight so that turns occur.
Did the product manager look at this before it was released? We have a lot of work to do here! We need to create a sprint for optimizing it, otherwise no one will like it. Be sure to put the texel fetches in a user story. This should be top priority. Lots of users are very angry.
