This is not FGear issue but rather, UE4 bug. It manifest itself in condition like this:
Hello again! The FGear orbit camera seems to have some fisheye effect or similar, which increae the âspeed feelingâ quite well. Can you point me to the place where these settings come from to tune it? In the Orbit Camera C++ class itself it seems it is just calculating the positioning, but I do not see the (post process?) effects creating that point of view. Thanks a lot!
we do not alter camera fov at all, epic has changed some camera settings in 5.3 maybe thatâs what you are talking about, check this one : Camera FOV is incorrect in Play mode UE5.3
Okay, thanks, that is still weird but a good hint.
I have another issue which came up today. I tried adding a CollisionResponse to my car. I add it via CustomCollision = CreateDefaultSubobject(TEXT(âCustomCollisionâ)); then set it via CustomCollision->SetStaticMesh(ItemCollision.Object); Seems to work, I can see it in the game as a member of my car, having the static mesh set. Then I disabled the CollisionResponse in the physical Asset we used until now. Still working. But if I drive now, I can collide with objects as guard rails, but will ghost through other cars, which do NOT use UFGearCustomCollision but a ânormalâ physical asset. No flags set, all default. Any ideas? These other cars are working like they should, just not when colliding with âthe other way of doing itâ. This is really confusing me here! Thanks a lot! In addition in the docs for the truck there is this image, which shows the used collision box on it, but layed over the mesh, not the collision mesh. How can I see this? It would help debug for sure.
I recommend you to add your custom collider at design time and try applying the same/similar settings in the sample project. if you check the sample project you can see those wireframe like visuals, the custom collider has a special material that displays it like that.
Any estimation for UE 5.4 support? It will include any update?
the next version is planned to be released next week.
Any physics/driving improvement/fix/addition?
some minor stuff, the update is mostly not about the physics.
here is the updated multiplayer demo with up to date physics and the new client authoritative replication(built with UE 5.4)
Sometimes the skidding (sound and mark) and smoke effects are activated at very low speed, would it be possible to set a minimum speed for these effects to start working?
ps: I mean wheel speed, not car speed, these effects are good in case of a burnout.
And where is the link for the example project with that new cars on the Fgear marketplace page? The link on description is the old example from 4.27. Âż?
Nevermind, they are in a new Sandbox2 level i just saw.
v1.8 is now available
Warning: If you have difficulty running the example project with Unreal5 copy the FGearPlugin folder in Unreal5\Engine\Plugins to FGearExample\Plugins folder.
Notes
Great work as always @lazybitgames will check this out.
Is there a way to unbrick my project after updating?
Thank you for implementing âForward offsetâ and the option to keep the engine sound when the vehicle sleeps!
The plugin is compiling without problems for UE4, however it is necessary to enable the âEnhanced Input pluginâ, otherwise the plugin presents an error and does not load. The âEnhanced Input pluginâ is in Beta and does not have full functionality in UE4, I hope there is no risk of any conflict or loss of performance due to the plugin being loaded.
Still about the effects:
When the vehicle sleeps, the smoke particles disappear suddenly, I looked at the code and you are using âmSmokes[i]->SetVisibility(true / false)â, I am not a C++ programmer, I would like to know if it is safe for me to change it to: âmSmokes[i]->Activate() / Deactivate()â, this way the smoke would appear/disappear smoothly and the visibility would change anyway (in addition to the fact that an inactive emitter consumes less resources than an invisible one).
Activating and deactivating the tire smoke at runtime is essential for my project, since the âmEnableTireSmokeâ variable already exists and using âsetEnableSkidmarksâ as an example, if I create the following lines in FGearEffects.h, it would be possible to activate/deactivate the smoke safely at runtime?
UFUNCTION(BlueprintCallable, Category = FGear)
void setEnableTireSmoke(bool e) { mEnableTireSmoke = e; }
UFUNCTION(BlueprintCallable, Category = FGear)
bool getEnableTireSmoke() const { return mEnableTireSmoke; }
I would like to ask you to reconsider your position regarding improvements to the effects system, it is something that enriches the plugin and was one of the reasons that made me decide to purchase it. My suggestion would be:
Checkboxes to enable and disable engine sound and backfire.
A variable to determine when the wheel effects will start, âminSlipFXVelocityâ.
Two runtime functions: âenable/disable smokeâ and âenable/disable backfireâ.
Good but not essential: âFadeOutâ instead of âStopâ on sounds.
This would be more than enough to make the implementation of the effects much more viable, because at the moment itâs more like âuse all or nothingââŚ
Thanks
Destroyed function is removed in v1.8, using EndPlay instead, replace it and it should work.
it is safe to call activate/deactivate but the effect can be reactivated after sleeping.
I guess it is also safe if you add those functions to enable/disable smoke at runtime(you need to recompile the plugin or use the plugin source as a part of your project or just adding those lines will not make them appear in BP).
effects component was never intended to be used for production, we do some improvements from time to time but a generic implementation can not fit everyoneâs needs, so no promises.
I always need to recompile my plugins with RunUAT to run on UE4 Source.
I would then need a condition to prevent the smoke from activating when the vehicle is sleeping, and if I add â!= mSleepEventsRegisteredâ in the function below, would it work?
If so, which âifâ structure should I put it in? (if you could please rewrite the condition, to avoid mistakes on my part, I am completely new to C++)
//smokes
if (mEnableTireSmoke && cs && physicalMaterial->mSmokeParticle != nullptr)
{
if (mSmokes[i]->Template == nullptr || mSmokes[i]->Template != physicalMaterial->mSmokeParticle)
mSmokes[i]->SetTemplate(physicalMaterial->mSmokeParticle);
mSmokes[i]->Activate();
mSmokes[i]->SetWorldLocation(hit.ImpactPoint);
}
else
{
mSmokes[i]->Deactivate();
}
ps: Thinking better, instead of changing the visibility or activating, changing âmEnableTireSmokeâ to false/true would be easier, right?
Where would I replace it? I canât open the project at all.
