I created a component using keyframed movement. It worked great. I posted it on reddit for feedback. 2 days later, I come back after no changes, and it is very jittery, and no longer looks smooth.
No longer looking smooth like the video from my Reddit post. Very jittery. FPS is perfectly fine, and other games on the Fortnite platform work perfectly fine.
When testing, it looks like it is running at 3FPS, even though I am getting over 120FPS.
Platform(s)
Tested on PC, Mobile, And Xbox.
When working and running smooth, it looked great on all platforms. Now it is jittery, it is jittery on all the platforms.
Happy to share code privately with an Epic Games employee.
Very frustrating, especially because I put a lot of time into it already. Makes me not want to use the UEFN and Fortnite platform for game development.
We’ve experienced this too, which is weird because supposedly scene graph runs it’s keyframes on the client side and not server side, so it shouldn’t be limited by any frame rate other than what runs on the client and not TPS.
I agree. Realistically, we shouldn’t need vehicle components, we should be able to create a vehicle with what’s already given to us with scene graph. These bugs and jitter make it impossible to create new experiences on Fortnite
Hello, yes that is correct. Although it was jittery the day before the update. I waited to report it because I knew there was an update coming, and I hoped maybe that would fix it.
Is there anyway I could send over the code I have? I don’t want to post it publicly.
I am also experiencing some weird jittery/hitching behaviour with scene graph keyframed movement. I had made a custom player entity and I observed that there are random intervals where movement is very laggy. I’ve spent hours trying to debug this in 42.10 and 42.20, with different frame rates and devices, so i feel like this is a bug.
I can share a video and my code privately if needed
I’m also experiencing the same issue on one of my projects. It was fine a few weeks ago and now its super laggy and buggy. Exact same issue as reported above here.
