may be substepping works fine and we are not yet able to utilize it.
but regardless chaos has many more issues and without proper physics, who can use this engine for production, so they need to fix it eventually.
What officials say? Didn’t touched 5.0 for year, i thought since then they fixed at least most issues with chaos.
tried that the delta times seems fine but the physics response is worse. still looking into it.
2 Likes
I believe what he means is chaos physics has different feeling and response compared to UE4’s Physx.
1 Like
What negative effect it would have? Can it be used without substepping?
I would like to be released anyway, because without that I cannot even start working to porting the game to UE5.
good news, some more tidying up and v1.6 will be available soon for both ue4 and ue5.
3 Likes
Is this with Chaos? have you fixed the issues you had with this?
yes, most of the known issues are worked out but the overall driving feel is a little bit different though.
2 Likes
Even with Substepping? It’s great!
Great work Yunus, look forward to testing
v1.6 is available now
CHANGELOG v1.6
Unreal5 support
Custom gravity option
Custom gravity sample map
Better hard contact implementation
Ability to offset casting origin
Improvements and bug fixes
Warning:
-To use the example project with Unreal5 copy the FGearPlugin folder in Unreal5\Engine\Plugins to FGearExample\Plugins folder.
Additional Notes:
-Due to unsolved/undiscovered issues with chaos the overall driving behavior might be different then UE4.
-Without substepping you can get ensure fails in the log with chaos.
-Use custom gravity with chaos or your vehicles can freeze/stop in air for no reason.
-All sample vehicles are set to use custom gravity.
-Convex casting used to generate lateral suspension forces, they are eliminated for correct behavior.
-Blocking hits are forced for all raycasts/sweeps.
-The sphere used in custom gravity map does not match its collider so wheels can penetrate the sphere.
-Added an option to override collision channel for custom colliders.
Somehow default WorldDynamic channel does not collide with the world with chaos so we set it to WorldStatic in the samples.
-New hard contact scale parameter can behave jumpy with high values, use a reasonable value like 0.2-0.3.
-The order of brake/engine torque generation is swapped.
If engine torque is more then brakes then the wheels will spin. This will make it easier to make burnouts.
-All force/torque/impulses are accumulated and applied at the same time now.
-If your wheels get stuck under the ground when the vehicle falls from height then you can use the cast offset parameter.
A positive value will offset the origin of the casts along the suspension normal.
Use a reasonable number to keep the origins inside the vehicle hull. You can activate the telemetry gizmo to view the origins.
-High friction engines could generate negative torques and the vehicle could travel backwards, this is fixed now.
-4.25 support is dropped, epic do not allow more then 3 versions to be uploaded.
2 Likes
Excellent.
Just went to install to UE5 - said it was queued, nothing happened and now cant find in my vault or engine/plugins weird will check again tomorrow as late here.
thanks for the warning, i’ve also checked and i think they’ve uploaded the wrong files, sent a mail to support.
1 Like
Morning, just tried and indeed still says 4.27 for me, will check later also to see if that has been updated at all before I install the plugin and embark on my HUGE migration to UE5 for my project.
1 Like
the issue is fixed, you can grab the latest files now.
2 Likes
“The order of brake/engine torque generation is swapped.”
Is possible to know where is this code? and what was the original one? (previos version)
I had my own burnout system and other stuff that with this ner version the overall behaviour is wrong, so wonder if maybe is this, so want to test and set like in the previous version to see if fixes for me.
drop a mail and i’ll send you the previous version.
Hi Yunus, hope your all good.
I’ve been testing quite a lot lately with my project conversion to UE5, I was really hopeful but performance is real shocking to be honest, real buggy in general and crashes quite a lot. Most likely not all related to Fgear so I’ve been working through to clear things up.
Just wondered did you still have further plans for Fgear UE5 version on the horizon? potential improvements you know are still to be made etc. as currently when I compare the two from 4.27 to 5.0 - 4.27 hands down is a winner.
Appreciate your efforts and time you invest into this, please do let us know if there is more to come from Fgear or indeed if you are awaiting any issues with Chaos/Epic in general for future engine versions.
1 Like
we’ll wait for 5.1 and see what happens.
a maintenance update may be released depending on the feedback, we’ve only detected a single crash case in multiplayer yet.
1 Like
Yes, I think I’ll do the same, still much to do for myself (but so little time) but hey its all fun and the main reason I’m still at it.