New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ BETA ] Mobility Update v2.11.6-beta #396
base: dev
Are you sure you want to change the base?
Conversation
Chat errors now notify user trying to link legacy objects to new objects. Engine RPM matches gearbox rpm much closer now.
Added double diff to blacklist
Limit feedback torque until I can find a better formula. Boost wheel torque to match old ACF torque x1.5 increase
Add delta time to idle throttle Fix deltatime accuracy
Added button for pasting gearbox ratios into the ACF spawn menu from copy data. Added button to convert legacy ratios to new ratio values and vice-versa
I notice the calcMass test is failing for KEShove, I was told that it was caused from an unrelated change to KEShove. Is there something I need to update or change for this pull request? |
Merge the latest commit from dev and the tests should be good now |
Removed console command for mobility update Removed experimental section Moved mobility update checkbox to the menu for each gearbox and engine Fixed bug when converting ratios that would convert 0 to 0.1
+ Cleaned up code + Fixed bugs related to order of operations in engine logic + Dual Clutch differential fix + Added third clutch variable for engine and transmissions.
Added torque transferring for dual clutch transmissions
I have a couple of suggestions but I wasn't entirely sure with bringing them up because they could certainly end up being controversial. One of the topics that has been brought up in the discord when it comes to mobility components is the inconsistency on the units used by them:
Which makes me think, would it be possible to standarize all these inputs to use a single unit? Changing Throttle and Brake to work with 0-1 would certainly make everything much simpler for the end user, but it'd also break every single old contraption prior this change. |
Yeah I could make them all use a 0-1 value and for brakes to use 0-50 to keep it relative. The input manager for throttle converts 0-100 to a 0-1 value immediately anyways so that would make the code a lot more simple. Not sure how the manager for brake converts but i assume it’s the same. I could make a maximum brake force slider for gearboxes so that the brake input could also default to 0-1. It wouldn’t necessarily break old contraptions, but if they did use say 50 throttle it would be similar to using 100% throttle since the value would be clamped to 1 as a maximum. I do like this update because it would allow users to use nothing but a chair and a wire POD controller for mobility if they don’t have access to ecu codes |
Updated CVT gearbox to use the new ratios and logic. Dual clutch gearboxes have proper torque transferring Dual clutch gearboxes can now receive partial clutching of either side with proper torque transfer between the clutch and non clutched side. Dual clutch inputs are fixed. Old system had flipped Left and Right sides
Updated turbine engines to use new logic added flywheel reaction torque to engines
+Angular Momentum Transferring +Better clutch simulation +Some updates to flywheel masses +Fixed bug with gearbox clutches
ACF MOBILITY UPDATE V1.0.0-beta
This update brings new logic to ACF3 mobility. This update will NOT affect existing dupes that are using the legacy mobility components. Updated components must be spawned new as they do not share the same class as legacy components.
Legacy components cannot be auto updated by using the ACF spawner tool to use the new mobility logic. THEY MUST BE SPAWNED NEW
Legacy Components CANNOT be linked to updated components and vice-versa.
Please view the Other Changes sections for how to enable/disable this update, and to spawn updated components.
**this update is experimental and may have adverse effects to your health
**please be patient as bugs may increase in prevalence to its stage of development
Engine Component Changes
Gearbox Component Changes
Other Changes
- New Client Setting - client setting to spawn updated components- New Client CMD - acf_mobilityupdate can be used to enabled/disable this update- Update Eligibility - notification description added to all engines and gearboxes.!
Future Updates
For Developers
Creating Eligible Components
To create or update existing engine addons, all engines must have the following variables in their registry:
Important Info
Updated mobility components are NOT
acf_engine
acf_gearbox
classes.Updated mobility components are
acf_engine_update
acf_gearbox_update
classes.The reason for this was to create a separation of legacy and updated mobility components to maintain a stable mobility components as changes are made to the mobility update.
The legacy components should be considered
depreciated
.