ah yes that's quite and old architecture really. Kraft uses Vulkan/Forward+ with MSAA and HDR. maybe later down the line, i'll do some more optimization and also offer quality settings for older hardware. thanks for your feedback anyway!
megariffer
Creator of
Recent community posts
thanks for the feedback! this is most probably a side effect of the top down view. realistic physics seem very weird, it's so easy to underestimate your speed. the tires have realistic grip budget, and quick steering inputs easily overload the tires. try turning back steering assist if you are on the keyboard. it limits your steering inputs so they always try to remain under the limit the tires can still maintain. and if you are seriously interested, press F2 in the game, and try fiddling with the physics, you might be able to tune the simulation better than myself.
it would help me tremendously if you could tell me your GPU, especially since you also said you don't think it's a CPU issue. i have an office grade laptop with an integrated graphics card, and i get steady 60FPS, so it could well be a GPU/driver quirk or Godot simply choosing the wrong GPU on your system. if you are on windows, there is a %APPDATA%\Godot\app_userdata\Kraft\logs\godot.log file which says what GPU the game selected on startup.
thanks! i'm really glad the tuning and the simulation (and of course the racing) felt enjoyable! could you tell me which platform you played, your GPU/CPU, resolution, and whether it was low FPS overall, or occasional stutter? was it while racing the AI with many bots? you see, every AI opponent uses the same complex physics computation as yourself, which means a 60Hz physics tick for the vehicle dynamics, and a 960Hz for the tire model. that could add up. it's an early alpha, and i haven't done much optimization yet, so this information would be helpful to me
