Search Results
6/28/2025, 8:03:10 AM
REEEEE WHAT IS THIS BUG! Sometimes it works, sometimes it doesn't, including the version before the majority of the latest big update. That would suggest my first portion of the current big update did something. And prior to that there was another big update but the update didn't really do much to that code besides a few minor additions of code.
Well I never even posted the original post I typed up. I started getting sus about what the problem was. I was getting values sent back at some point. Seemed off but were apparently in range in retrospect. Eventually I got negative numbers which in my head were supposed to be impossible, they're not. Then eventually I realized they were in range and moved something to the location it should be occurring at, nothing. Despite using COROUTINES with the yield return feature, not all code was done running. Found this out when I slapped in a for loop to apply a yield return null after the function that ends all the data set up. Made sure it ran a lot to create a gap.
>click play
Suddenly stuff works
>do it again just in case because even before this it would sometimes work, partially ie some data got through
Still working
Seriously? Do I need to add a yield return to each function and not just the outermost function all so it actually truly waits for all the functions to finish running before moving onto the next coroutine? Reeeeeeeee this problem took way too long to figure out. At least I don't have to redo all this code. Maybe the amount of data it processes now makes it so it doesn't send all data back in a timely manner?
Well I never even posted the original post I typed up. I started getting sus about what the problem was. I was getting values sent back at some point. Seemed off but were apparently in range in retrospect. Eventually I got negative numbers which in my head were supposed to be impossible, they're not. Then eventually I realized they were in range and moved something to the location it should be occurring at, nothing. Despite using COROUTINES with the yield return feature, not all code was done running. Found this out when I slapped in a for loop to apply a yield return null after the function that ends all the data set up. Made sure it ran a lot to create a gap.
>click play
Suddenly stuff works
>do it again just in case because even before this it would sometimes work, partially ie some data got through
Still working
Seriously? Do I need to add a yield return to each function and not just the outermost function all so it actually truly waits for all the functions to finish running before moving onto the next coroutine? Reeeeeeeee this problem took way too long to figure out. At least I don't have to redo all this code. Maybe the amount of data it processes now makes it so it doesn't send all data back in a timely manner?
Page 1