Search Issue Tracker
Fixed in 0.3.0
Votes
0
Found in [Package]
0.2.1-preview
Issue ID
1138249
Regression
Yes
[Scripting] The "duration" value, when read from callback function for Input Actions, is not correct.
Repro:
1. Download package and project at: https://github.com/Unity-Technologies/InputSystem
2. Go to scene at: Assets -> Demo ->SimpleDemo -> SimpleDemo
3. Enter Playmode
4. Hold down left mouse button for a short time, then let it go
5. Observe how long the shooting lasts
Actual: The "duration" value is much longer than the actual time
Note: When using callback function like this:
controls.gameplay.fire.performed +=
ctx =>
{
if (ctx.interaction is SlowTapInteraction)
{
StartCoroutine(BurstFire((int)(ctx.duration * burstSpeed)));
}
else
{
Fire();
}
m_Charging = false;
};
The value for duration is calculated though time and startTime. However, the startTime for callback function is always 0, which makes the duration value much larger than it is.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment