Its a funky order thing when using ViewportTextures, where the size isn't known in time. It should resolve itself after a single frame and you can thus ignore it.
