Thank Akka, but I think his issue is just semantic, not about delays.
He thinks the triggers only can be registered with pure forward or backward movements.
But they’re not
The only direction that won’t register with triggers are straight UP and DOWN, precisely because theses direction don’t give any information to the Trainer about orientation.
Pro tips, sweep work just fine with :db: or :df:
Again, it’s a big part of the Manual. If it’s not clear enough, tell me where so I can correct the pdf.
If I set the dummy to do forward SRK on wakeup and use my trigger 1 (Forward+Trigger). The dummy does the inputs backwards. I have to set the dummy to do Backward SRK in order for it to work correctly. Is there something new I’m missing here? This is mainly causing issues with when I try to switch between triggers. If I do one they do the move backwards, and if I do the other trigger it’s correct. I definitely don’t have this issue with ver 1.2
I am trying to download the AHK_TEST_STICK from your google drive link, however when I try and download it says page not found and I am unable to open from your drive.
I already thought of that. Still didn’t work, in fact it didn’t respond at all when I changed custom trigger to the sweep button. It would only work with the pre-populated settings (Forward and fierce, Backward and select according to the stick app) and yes, I pressed activate each time.
I will read the manual again , thanks. I’m sure it works perfect, I just have to figure it out.
The important part is the POV-1. it MUST react and show POVXXXX (XXXX = numbers) when you move the stick. Cause that’s what the Trainer can see. The other data in this line X050 y050 Z050 r050 are useless for the Trainer.
Highlandfireball, Sorry I can’t do any tests right now my Windows’s died, so I need extra time to reinstall one…
I’ll test if I can reproduce these bugs. It seems related to this direction detection part too. So I might release a new version of the Trainer with build in direction test.
Till then and to confirm the app works if we use a basic control, can you try configuring keyboard keys instead of stick triggers ?
Set left and right field below the triggers fields with 2 keyboard keys, and the 3 main triggers with 3 other keyboard keys. Go simple, and avoid using the Trainer reserved keys
Again thanks for your feedback guyz, and sorry if I can’t be arsed to release a freacking stable version of this. Everytime I test it left and right at home, everything I can think about works.
I wonder if these bugs affect “everyone” or it’s specific to some of you.
Ok i got it working. On the Madcatz TE i changed the slide button in the top left to DP instead of LS. Program seems to be working great now. Thank you very much for all the help. This is a great program.
So I reinstalled Win7, and all and couldn’t reproduce any bug with the Trainer, with either the Hori FE, the Madcatz TE R2 Moded, or the single keyboard.
So I’ll wait further feedbacks from you all
Till then, I’ll do that controller direction detection feature for the next release.
Yeah it’s a continuous issue. I basically have to set both triggers for Forward+Trigger otherwise I won’t get the correct responses from the dummy and have to set the action performed as backward. When I load ver1.2 it doesn’t have this issue.
1.3 was relly not that good after all. I found some dumb errors.
I’m still struggling with it but the end is close.
I thought I could finish early but I really need to sleep right now so…
Nah thank you boyz, I would have no may to ping point those bugs alone. Everyone have is own style to use an app.
Next time I’ll think of beta testing before I launch something and maybe put a tracker to have an idea of how is using it, and an update adviser. Ho wait, I have no idea how to do that…
