L & R buttons don't seem to work.

Pixel Brady

Veteran
Veteran
Joined
Jun 8, 2012
Messages
46
Reaction score
4
First Language
English
Primarily Uses
Totally baffled here, the L/R functions do nothing I can see at the best of days and now I'm trying to make a common event to check whether they're bein' pressed to set it up to cycle through weapons, but every time the L button gets pressed I get a buzzer, not with R though, but neither will do anything with the common event; it just ignores the commands.

Not sure where I'm brickwalling it here, so any suggestions/ideas would be great, cheers.
 

Des

timefantasy.net
Veteran
Joined
Mar 2, 2012
Messages
1,370
Reaction score
508
First Language
American
Primarily Uses
N/A
Are you pressing the "L" and "R" keys on your keyboard, or are you using the corresponding keys? It doesn't actually mean "L" and "R". By default they are assigned to "Q" and "W".
 
Last edited by a moderator:

Pixel Brady

Veteran
Veteran
Joined
Jun 8, 2012
Messages
46
Reaction score
4
First Language
English
Primarily Uses
Aye, the buzzer comes with Q/PageUp and doesn't with W/PageDn. They don't seem to be doing anything for me at all, much less with my common event.
 

Des

timefantasy.net
Veteran
Joined
Mar 2, 2012
Messages
1,370
Reaction score
508
First Language
American
Primarily Uses
N/A
Show us a screenshot of your common event.
 

Rapu

One foot in grave, the other in hell.
Member
Joined
Mar 13, 2012
Messages
46
Reaction score
6
First Language
Finnish
Primarily Uses
Are you sure you haven't somehow messed up your keybinds? I just created a conditional branch that checks if L or R button is being pressed and it worked, as it should have.

In any case, two things which can cause problems comes to my mind: One, your keybinds are messed up. Two, your script(s) causes an error.
 

Pixel Brady

Veteran
Veteran
Joined
Jun 8, 2012
Messages
46
Reaction score
4
First Language
English
Primarily Uses
One thought is about the ABS I'm using, would it be possible that's affecting it? I see no reason for it, but I guess...

EDIT: @Rapy possible I suppose, but I wouldn't even know how to change them anyways, so if they're messed up i'vw no way to know. Mind , I'm thinking they're right because (at least one of them) buzzes.

EDITEDIT: Just realised that I forgot to have the par.proc checker to set the other two weapons to "0" while setting the equipped to "1", but I can't see that causing the problem, especially since in my test I only equipped one anyways.

Anyhoo, the commons:

There's 5 versions of three different weapons. the first par.proc checks what you have, sets a variable, then checks which button is presssed and turns on a switch for that "button". each button script is an auto start, checks the variable weapon, equips the "next one along" of the best version available, then switches back off, leaving the par.proc to wait until you hit L/R again.

At least, that's the intention.

 
Last edited by a moderator:

Mr. Bubble

Makes stuff.
Member
Joined
Mar 1, 2012
Messages
853
Reaction score
163
One thought is about the ABS I'm using, would it be possible that's affecting it? I see no reason for it, but I guess...
Yes, it would be possible. That or some other custom script you're using.

The best way to check is to test your event in a clean project without custom scripts and see if it works.
 
Last edited by a moderator:

Pixel Brady

Veteran
Veteran
Joined
Jun 8, 2012
Messages
46
Reaction score
4
First Language
English
Primarily Uses
Problem is two-fold, apparently.

In the ABS project, it happens as described above, doesn't work, probably because of the ABS.

In a clean project, the autoruns lock up, so I've obviously screwed up the events somewhere to prevent it turning the switch off at the end.
 

Rapu

One foot in grave, the other in hell.
Member
Joined
Mar 13, 2012
Messages
46
Reaction score
6
First Language
Finnish
Primarily Uses
Try to use a less complex event to see if the problem lies to your event. Something like this:



If this doesn't work, then your script(s) causes problem.

EDIT: Another solution would be to change the order of your scripts. Probably not much help in this situation though.
 
Last edited by a moderator:

Pixel Brady

Veteran
Veteran
Joined
Jun 8, 2012
Messages
46
Reaction score
4
First Language
English
Primarily Uses
Excellent idea there, never even occured to me. Just tested it out and it worked absolutely fine, so I guess it's time to go over my events and see where I've gone wrong.

Cheers :)

EDIT: Okay, I've tried everything I could think of, including leaving the commons as a par.proc instead of waiting for the autorun switch but it's still just going back to the L-buzzer, R-nothing routine. It must be the way in which I've set the conditionals, but I'm honestly at a total loss, I've no idea what's causing the trip up, and no idea why it thinks there's a difference between the two because they look the same to me.

Any assistance would be grand!

Cheers
 
Last edited by a moderator:

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Latest Threads

Latest Posts

Latest Profile Posts

Work on Yanfly's MZ plug-ins is coming along nicely. Looking forward to getting them: http://www.yanfly.moe/wiki/Core_Engine_VisuStella_MZ
so uh variables can only be used for num lol? I guess I gotta fix that once MZ come out lol
I didn't think I'd spend the evening jamming out to the battle theme of a Hole Punch.
Welcome back to the dark era, where everything is in dark mode!
.
.
.
I'm not complaining! :o

Forum statistics

Threads
100,726
Messages
978,827
Members
132,353
Latest member
BM_ANDERSON
Top