Search Issue Tracker
Not Reproducible
Votes
2
Found in [Package]
1.9.0
1.10.0
Issue ID
ISXB-1002
Regression
No
The new Input System does not register the "Delta Time Scale" Processor coming from the Cinemachine package when Input Action asset is assigned as the "Project-wide Input Actions"
How to reproduce:
1. Open the “DeltaTimeRepro“ project
2. Open the “Max“ scene
3. Enter the Play Mode
4. Observe the Console window
Expected result: No errors thrown
Actual result: “No InputProcessor with name 'DeltaTimeScale' (mentioned in 'DeltaTimeScale') has been registered“ errors thrown
Reproducible with: 1.8.1, 1.8.2 (2022.3.41f1), 1.9.0, 1.10.0 (2022.3.41f1, 6000.0.14f1)
Could not test with: 1.8.1, 1.8.2, 1.9.0, 1.10.0 (2021.3.42f1) (Must downgrade Cinemachine package and the “Delta Time Scale” functionality is not present)
Reproducible on: macOS 14.5 (Intel), Windows 11 (User’s)
Not reproducible on: No other environments tested
Notes:
- Errors are thrown when the “Delta Time Scale” Processor is added to either the Binding or the Action
- Not reproducible when rebuilding the issue from scratch
-
Mixality_KrankyBoy
Sep 18, 2024 04:16
It appears to be fixed in input System 1.11.0 - as of Sept 17th, 2024 it is not in package manager. You have to manually add it to the manifest.json
-
Mixality_KrankyBoy
Sep 18, 2024 03:34
Same error message here. When I made the CinemachineDefaultInput to global.
No InputProcessor with name 'DeltaTimeScale' (mentioned in 'DeltaTimeScale,ScaleVector2(x=0.1,y=0.1)') has been registered
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes (System.Type[])Unity 6.000.0.19f1
Input System 1.10.0
Cinemachine 3.1.1 -
unity_LvdTGwgj0IIAqA
Sep 03, 2024 06:38
I still had to fight with issue in Unity 6 but thanks for the answer on this topic.
Removing it from the project wide Actions fixed the problem.
It seems all predefined processors have the same issue (DeltaTimeScale, scaleVector) etc. cant be registered.
Hope this gets fixed anytime soon.Unity 6.0.16f1
Input System 1.9 -
nratcliff
Aug 17, 2024 10:37
This is the only google result I could find for this issue with regards to custom user InputProcessor registration. Despite registering the InputProcessor using both `[UnityEditor.InitializeOnLoad]` and `[RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.BeforeSceneLoad)]` I was getting multiple "No InputProcessor with name" errors on enter playmode. Removing my Input Action Asset from the "Project-Wide Input Actions" field fixed the errors.
Unity 2022.3.27f1
Input System 1.10.0
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Not reproducible with Input system version 1.11.2