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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment