Mixing
Are NES turbo buttons internal to the controller?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
As you may know, the classic NES controller was not the only NES controller that Nintedo released with the NES. These included the NES advantage, the NES Max, and the Dogbone. All of these new controllers featured turbo buttons (buttons for frame perfect spam). The thing that confuses me about this is that the controllers had no way of knowing when the NES changed frame, so how how did it know when to switch from on to off or vise versa? The reason I don't think the NES communicated this information to the controller is because controllers with turbo buttons came out after the NES, so Nintendo hadn't even thought of the concept yet, and wouldn't have been able to design the NES to work with it.
nes nintendo
asked 29 mins ago
Jack Kasbrack
14814
add a comment |Â
up vote
1
down vote
favorite
As you may know, the classic NES controller was not the only NES controller that Nintedo released with the NES. These included the NES advantage, the NES Max, and the Dogbone. All of these new controllers featured turbo buttons (buttons for frame perfect spam). The thing that confuses me about this is that the controllers had no way of knowing when the NES changed frame, so how how did it know when to switch from on to off or vise versa? The reason I don't think the NES communicated this information to the controller is because controllers with turbo buttons came out after the NES, so Nintendo hadn't even thought of the concept yet, and wouldn't have been able to design the NES to work with it.
nes nintendo
asked 29 mins ago
Jack Kasbrack
14814
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
As you may know, the classic NES controller was not the only NES controller that Nintedo released with the NES. These included the NES advantage, the NES Max, and the Dogbone. All of these new controllers featured turbo buttons (buttons for frame perfect spam). The thing that confuses me about this is that the controllers had no way of knowing when the NES changed frame, so how how did it know when to switch from on to off or vise versa? The reason I don't think the NES communicated this information to the controller is because controllers with turbo buttons came out after the NES, so Nintendo hadn't even thought of the concept yet, and wouldn't have been able to design the NES to work with it.
nes nintendo
asked 29 mins ago
Jack Kasbrack
14814
As you may know, the classic NES controller was not the only NES controller that Nintedo released with the NES. These included the NES advantage, the NES Max, and the Dogbone. All of these new controllers featured turbo buttons (buttons for frame perfect spam). The thing that confuses me about this is that the controllers had no way of knowing when the NES changed frame, so how how did it know when to switch from on to off or vise versa? The reason I don't think the NES communicated this information to the controller is because controllers with turbo buttons came out after the NES, so Nintendo hadn't even thought of the concept yet, and wouldn't have been able to design the NES to work with it.
nes nintendo
nes nintendo
asked 29 mins ago
Jack Kasbrack
14814
asked 29 mins ago
Jack Kasbrack
14814
asked 29 mins ago
Jack Kasbrack
14814
asked 29 mins ago
Jack Kasbrack
14814
asked 29 mins ago
Jack Kasbrack
14814
14814
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
accepted
In the case of the NES Advantage at least, the Turbo rate was adjustable, by turning the dial at the top of each button.
You are right in assuming that the NES does not communicate the start of a frame to the controller. But also, these buttons do not need to know when the frames are. All they need to do is open and close the circuit, which the software will usually treat as singulative button presses.
A similar device exists on modern gaming controllers as well. They include a very simple circuit which just "make it look like" the user is mashing the button.
answered 20 mins ago
Wilson
9,501543117
1
But wouldn't that make it miss a frame every once in a while? Is that a thing that happens?
– Jack Kasbrack
18 mins ago
2
@JackKasbrack sure, but it doesn't matter. Let's say the button fires a bullet of some kind. Use the turbo button and you get a load of bullets. It doesn't really matter if this is frame perfect, so it isn't frame perfect.
– Wilson
15 mins ago
2
That's kind of a crappy answer, but at the same time the best possible one.
– Jack Kasbrack
13 mins ago
Often there were limits on how many fired bullets (for example) could be on screen at once (if they were implemented as sprites) so once you'd hit that limit the autofire wouldn't help you until a previous bullet had either hit something or moved off screen. I found autofire tended to be more of a hindrance than a help
– bodgit
8 mins ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
In the case of the NES Advantage at least, the Turbo rate was adjustable, by turning the dial at the top of each button.
You are right in assuming that the NES does not communicate the start of a frame to the controller. But also, these buttons do not need to know when the frames are. All they need to do is open and close the circuit, which the software will usually treat as singulative button presses.
A similar device exists on modern gaming controllers as well. They include a very simple circuit which just "make it look like" the user is mashing the button.
answered 20 mins ago
Wilson
9,501543117
1
But wouldn't that make it miss a frame every once in a while? Is that a thing that happens?
– Jack Kasbrack
18 mins ago
2
@JackKasbrack sure, but it doesn't matter. Let's say the button fires a bullet of some kind. Use the turbo button and you get a load of bullets. It doesn't really matter if this is frame perfect, so it isn't frame perfect.
– Wilson
15 mins ago
2
That's kind of a crappy answer, but at the same time the best possible one.
– Jack Kasbrack
13 mins ago
Often there were limits on how many fired bullets (for example) could be on screen at once (if they were implemented as sprites) so once you'd hit that limit the autofire wouldn't help you until a previous bullet had either hit something or moved off screen. I found autofire tended to be more of a hindrance than a help
– bodgit
8 mins ago
add a comment |Â
up vote
4
down vote
accepted
In the case of the NES Advantage at least, the Turbo rate was adjustable, by turning the dial at the top of each button.
You are right in assuming that the NES does not communicate the start of a frame to the controller. But also, these buttons do not need to know when the frames are. All they need to do is open and close the circuit, which the software will usually treat as singulative button presses.
A similar device exists on modern gaming controllers as well. They include a very simple circuit which just "make it look like" the user is mashing the button.
answered 20 mins ago
Wilson
9,501543117
1
But wouldn't that make it miss a frame every once in a while? Is that a thing that happens?
– Jack Kasbrack
18 mins ago
2
@JackKasbrack sure, but it doesn't matter. Let's say the button fires a bullet of some kind. Use the turbo button and you get a load of bullets. It doesn't really matter if this is frame perfect, so it isn't frame perfect.
– Wilson
15 mins ago
2
That's kind of a crappy answer, but at the same time the best possible one.
– Jack Kasbrack
13 mins ago
Often there were limits on how many fired bullets (for example) could be on screen at once (if they were implemented as sprites) so once you'd hit that limit the autofire wouldn't help you until a previous bullet had either hit something or moved off screen. I found autofire tended to be more of a hindrance than a help
– bodgit
8 mins ago
add a comment |Â
up vote
4
down vote
accepted
up vote
4
down vote
accepted
In the case of the NES Advantage at least, the Turbo rate was adjustable, by turning the dial at the top of each button.
You are right in assuming that the NES does not communicate the start of a frame to the controller. But also, these buttons do not need to know when the frames are. All they need to do is open and close the circuit, which the software will usually treat as singulative button presses.
A similar device exists on modern gaming controllers as well. They include a very simple circuit which just "make it look like" the user is mashing the button.
answered 20 mins ago
Wilson
9,501543117
In the case of the NES Advantage at least, the Turbo rate was adjustable, by turning the dial at the top of each button.
You are right in assuming that the NES does not communicate the start of a frame to the controller. But also, these buttons do not need to know when the frames are. All they need to do is open and close the circuit, which the software will usually treat as singulative button presses.
A similar device exists on modern gaming controllers as well. They include a very simple circuit which just "make it look like" the user is mashing the button.
answered 20 mins ago
Wilson
9,501543117
edited 17 mins ago
answered 20 mins ago
Wilson
9,501543117
answered 20 mins ago
Wilson
9,501543117
answered 20 mins ago
Wilson
9,501543117
9,501543117
1
But wouldn't that make it miss a frame every once in a while? Is that a thing that happens?
– Jack Kasbrack
18 mins ago
2
@JackKasbrack sure, but it doesn't matter. Let's say the button fires a bullet of some kind. Use the turbo button and you get a load of bullets. It doesn't really matter if this is frame perfect, so it isn't frame perfect.
– Wilson
15 mins ago
2
That's kind of a crappy answer, but at the same time the best possible one.
– Jack Kasbrack
13 mins ago
Often there were limits on how many fired bullets (for example) could be on screen at once (if they were implemented as sprites) so once you'd hit that limit the autofire wouldn't help you until a previous bullet had either hit something or moved off screen. I found autofire tended to be more of a hindrance than a help
– bodgit
8 mins ago
add a comment |Â
1
But wouldn't that make it miss a frame every once in a while? Is that a thing that happens?
– Jack Kasbrack
18 mins ago
2
@JackKasbrack sure, but it doesn't matter. Let's say the button fires a bullet of some kind. Use the turbo button and you get a load of bullets. It doesn't really matter if this is frame perfect, so it isn't frame perfect.
– Wilson
15 mins ago
2
That's kind of a crappy answer, but at the same time the best possible one.
– Jack Kasbrack
13 mins ago
Often there were limits on how many fired bullets (for example) could be on screen at once (if they were implemented as sprites) so once you'd hit that limit the autofire wouldn't help you until a previous bullet had either hit something or moved off screen. I found autofire tended to be more of a hindrance than a help
– bodgit
8 mins ago
1
1
But wouldn't that make it miss a frame every once in a while? Is that a thing that happens?
– Jack Kasbrack
18 mins ago
But wouldn't that make it miss a frame every once in a while? Is that a thing that happens?
– Jack Kasbrack
18 mins ago
2
2
@JackKasbrack sure, but it doesn't matter. Let's say the button fires a bullet of some kind. Use the turbo button and you get a load of bullets. It doesn't really matter if this is frame perfect, so it isn't frame perfect.
– Wilson
15 mins ago
@JackKasbrack sure, but it doesn't matter. Let's say the button fires a bullet of some kind. Use the turbo button and you get a load of bullets. It doesn't really matter if this is frame perfect, so it isn't frame perfect.
– Wilson
15 mins ago
2
2
That's kind of a crappy answer, but at the same time the best possible one.
– Jack Kasbrack
13 mins ago
That's kind of a crappy answer, but at the same time the best possible one.
– Jack Kasbrack
13 mins ago
Often there were limits on how many fired bullets (for example) could be on screen at once (if they were implemented as sprites) so once you'd hit that limit the autofire wouldn't help you until a previous bullet had either hit something or moved off screen. I found autofire tended to be more of a hindrance than a help
– bodgit
8 mins ago
Often there were limits on how many fired bullets (for example) could be on screen at once (if they were implemented as sprites) so once you'd hit that limit the autofire wouldn't help you until a previous bullet had either hit something or moved off screen. I found autofire tended to be more of a hindrance than a help
– bodgit
8 mins ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f8119%2fare-nes-turbo-buttons-internal-to-the-controller%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password