Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stuck at High Speedup #627

Closed
LilBeanBoi opened this issue Mar 8, 2020 · 3 comments
Closed

Stuck at High Speedup #627

LilBeanBoi opened this issue Mar 8, 2020 · 3 comments
Assignees
@denisfa
Labels
question

Comments

@LilBeanBoi
Copy link

Sorry this is not any technical stuff, but vba seems to be stuck at 200-250% speed and I can't seem to fix it. Any help?
@denisfa
Copy link
Collaborator

denisfa commented Mar 8, 2020

@LilBeanBoi We have had a couple of issues of the speed being stuck at high values. I will assume you have the latest stable version 2.1.4... Also, Windows or Linux?

Has it been like this since you very first try playing a game? Or did it start happening after you tried to do some configuration?

Could you try: help--> factory reset (backup your configuration first). If it works, could you send the vbam.ini that did not work?

@rkitover rkitover changed the title Speedup issues Stuck at High Speedup Mar 8, 2020
@LilBeanBoi
Copy link
Author

@denisfa I have the 2.1.3 version on Windows 10, and this issue started randomly, but I don't think changing video filters might have affected that. I tried to do a factory reset and it worked! Unfortunately I don't know what vbam.ini is but the issue is fixed, thank you

@rkitover rkitover closed this as completed Mar 9, 2020
@rkitover
Copy link
Collaborator

rkitover commented Mar 9, 2020

Glad things are working for you now.

If you have any problems feel free to open an issue and we'll help the best we can.

denisfa added a commit that referenced this issue May 22, 2020
@denisfa
Avoid override of variable throttle for turbo.
174ee3d 
It is not needed to set `throttle` on neither case. There is actually a
bug when using turbo/speedup and closing the emulator. The test case
is the following:

#627

On Windows:

1. use opengl;
2. load GBA game;
3. set throttle to `100%`;
4. set turbo throttle to `200%`;
5. enable turbo on menu;
6. save game;
7. close emulator && open emulator;
8. load GBA game;

==>

throttle is `200%`.

This is definitely not expected.
rkitover pushed a commit that referenced this issue Jun 1, 2020
@denisfa @rkitover
Avoid override of variable throttle for turbo.
8f8c340 
It is not needed to set `throttle` on neither case. There is actually a
bug when using turbo/speedup and closing the emulator. The test case
is the following:

#627

On Windows:

1. use opengl;
2. load GBA game;
3. set throttle to `100%`;
4. set turbo throttle to `200%`;
5. enable turbo on menu;
6. save game;
7. close emulator && open emulator;
8. load GBA game;

==>

throttle is `200%`.

This is definitely not expected.
rkitover pushed a commit that referenced this issue Jun 1, 2020
@denisfa @rkitover
Avoid override of variable throttle for turbo.
6bbdd9b 
It is not needed to set `throttle` on neither case. There is actually a
bug when using turbo/speedup and closing the emulator. The test case
is the following:

#627

On Windows:

1. use opengl;
2. load GBA game;
3. set throttle to `100%`;
4. set turbo throttle to `200%`;
5. enable turbo on menu;
6. save game;
7. close emulator && open emulator;
8. load GBA game;

==>

throttle is `200%`.

This is definitely not expected.
denisfa added a commit that referenced this issue Jun 4, 2020
@denisfa
Avoid override of variable throttle for turbo.
0d84ebb 
It is not needed to set `throttle` on neither case. There is actually a
bug when using turbo/speedup and closing the emulator. The test case
is the following:

#627

On Windows:

1. use opengl;
2. load GBA game;
3. set throttle to `100%`;
4. set turbo throttle to `200%`;
5. enable turbo on menu;
6. save game;
7. close emulator && open emulator;
8. load GBA game;

==>

throttle is `200%`.

This is definitely not expected.
denisfa added a commit that referenced this issue Jun 10, 2020
@denisfa
Avoid override of variable throttle for turbo.
3edf5fc 
It is not needed to set `throttle` on neither case. There is actually a
bug when using turbo/speedup and closing the emulator. The test case
is the following:

#627

On Windows:

1. use opengl;
2. load GBA game;
3. set throttle to `100%`;
4. set turbo throttle to `200%`;
5. enable turbo on menu;
6. save game;
7. close emulator && open emulator;
8. load GBA game;

==>

throttle is `200%`.

This is definitely not expected.
denisfa added a commit that referenced this issue Jun 14, 2020
@denisfa
Avoid override of variable throttle for turbo.
aeb7a0e 
It is not needed to set `throttle` on neither case. There is actually a
bug when using turbo/speedup and closing the emulator. The test case
is the following:

#627

On Windows:

1. use opengl;
2. load GBA game;
3. set throttle to `100%`;
4. set turbo throttle to `200%`;
5. enable turbo on menu;
6. save game;
7. close emulator && open emulator;
8. load GBA game;

==>

throttle is `200%`.

This is definitely not expected.
denisfa added a commit that referenced this issue Jun 17, 2020
@denisfa
Avoid override of variable throttle for turbo.
6b257d5 
It is not needed to set `throttle` on neither case. There is actually a
bug when using turbo/speedup and closing the emulator. The test case
is the following:

#627

On Windows:

1. use opengl;
2. load GBA game;
3. set throttle to `100%`;
4. set turbo throttle to `200%`;
5. enable turbo on menu;
6. save game;
7. close emulator && open emulator;
8. load GBA game;

==>

throttle is `200%`.

This is definitely not expected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@denisfa denisfa

Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rkitover @denisfa @LilBeanBoi