Yeah, the title sums it up.
I’ve tested, with both ‘‘charactermovement’’ and ‘‘floatingpawnmovement’’, they will work fine in the editor. The issue happens only once I package it to be an .exe file.
This is the only warning I get in the Output log.
LogCharacterMovement: Warning: GetSimulationTimeStep() - Max iterations 8 hit while remaining time 0.093056 > MaxSimulationTimeStep (0.050) for ‘Demon_Blueprint_C_0’, movement ‘Walking’
Anyone has a clue as to why it works fine in the editor but not in the client? I don’t use any code, just blueprints.
EDIT: Add movement input is attached to event tick