I saw this post from a while ago and decided to try out the script Chris gave to help randomise the QTE buttons but i can't really get it to work? I'm not sure what i'm missing here.
https://adventurecreator.org/forum/discussion/10455/quick-time-event-issue
The text for the QTE changes to Down for the first action but then doesnt do anything for the next one.
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
I can't recreate the problem, and I see no issues with the settings.
Does it change to Left if you swap the two QTE Actions around?
What are your AC/Unity versions, and what are your QTE Menu's properties?
My unity version is 2021.3.27f1 and AC is 1.78.2
My "qte" menu is just a simple unity ui prefab menu. Everything is unchecked except Always fit on screen, Appear type is set to Manual, No actionlists when turn on or off and the linked canvas prefab is the one I showed earlier.
I'm not even sure if this is a menu problem or just input problem? because nothing happens when I click the first key. You would think that if it's just the menu not working then clicking Left then Down or vice versa would still give you the "You win" dialogue but it's like I'm not even pressing anything at all. The "Left" text just shows on the screen for 4 seconds and then goes away and normal gameplay continues
Is the issue that the second QTE does not run, or that the label does not correctly update? You can test this by having the second QTE run even if the first QTE fails, which can be done by having the first Action's "If condition is not met" link to the second.
Do you have the inputs Down and Left defined in your Input Manager? Share screenshots showing their definitions if so. If not, they will need to be listed for the QTE to be able to react to them.
Okay, if i link the first action's "If condition is not met" to the second action, they both show up. So Down shows after left and vice versa.
These are my input definitions
https://imgur.com/iwlKIHN
https://imgur.com/fOzrcn0
All looks OK. If you remove the "not met" condition sockets again, but also uncheck Wrong button fails?, what happens?
Your "left" input is mapped to the left-arrow key - not the left mouse button.
If you want to map it to the left mouse button, set the Input's Positive Button to "mouse 0".
If you're pressing the keys, it should work - at least, I can't see any reason why it wouldn't.
You've set to use the Input Manager in your Project settings, as opposed to Input System?
So since "Left" is first, when I press left, the actionlist just ends and doesn't go to "down". It does the same if I connect the left qte action's "if condition is not met" to down. The second action doesn't run, it just ends the actionlist.
I also noticed that if I kept running the cutscene the qte is in over an over, sometimes pressing left would just end the actionlist but sometimes it seems like actionlist just speeds itself up? Like it would show left and then when I press the key, it would show down really quickly for like a second and then the actionlist would just end. That happens like once every 6 tries
This is with "Wrong button fails?" still unchecked?
All sounds very odd. In both Actions, clear the Menu to display (optional) fields, and instead rely on ActionList: Comment Actions to get feedback on which branches get run. Does that alter anything?
If not, I may need to see it for myself, as I really can't reproduce the issue. If you can create a .zip of your Managers, the scene with the Actions, and your project's ProjectSettings folder, PM it to me and I'll take a look.
The issue I described earlier now only happens when I check "wrong button fails". Only the first qte plays no matter what button I press or it just speeds through the rest of the actions in the qte in about a second.
I wasn't sure how to use the " Actionlist comment " so I put one after each qte action to see if anything came up after I pressed a button and it was still the same. Ill pm you a zip of the things you asked for
Thanks, with this I've found the issue.
Open up AC's PlayerInput script, and look for line 1603:
Replace with:
Now to just remember to add this whenever I wanna use qtes in a project unless it gets added in during the next patch. But seriously, thank you!
This is a bug, and will be fixed in the next update. The above is just a temporary fix for you in the meantime.