gba emulation
- Thread starter metbot
- Start date
SirDaShadow
New member
> what is the best emulator out there besides visual boy
> advance Im fed up with the problems i dont care if i have to
> have seperate emus for color AND advance
>
what problems do you have with vba? try no$gba since it's freeware to play games now...
let me guess...you can't play the NES classics on it or fed up with the battery detection problems?
<P ID="signature"></P>
> advance Im fed up with the problems i dont care if i have to
> have seperate emus for color AND advance
>
what problems do you have with vba? try no$gba since it's freeware to play games now...
let me guess...you can't play the NES classics on it or fed up with the battery detection problems?
<P ID="signature"></P>
> what problems do you have with vba? try no$gba since it's
> freeware to play games now...
> let me guess...you can't play the NES classics on it or fed
> up with the battery detection problems?
>
allright
1.cant save games
2.cheats dont work
3.some games dont work
4.savestates always ,ALWAYS makes games unplayable
5.static sound
6.every game is to slow no matter what the frame skip /throttle is
i want something that has some features maybe alot
ill try no$GBA
<P ID="signature"></P>
> freeware to play games now...
> let me guess...you can't play the NES classics on it or fed
> up with the battery detection problems?
>
allright
1.cant save games
2.cheats dont work
3.some games dont work
4.savestates always ,ALWAYS makes games unplayable
5.static sound
6.every game is to slow no matter what the frame skip /throttle is
i want something that has some features maybe alot
ill try no$GBA
<P ID="signature"></P>
SirDaShadow
New member
> 1.cant save games
get the .nfo file and see the savetype then select it accordingly...the auto function doesn't work with new games because (wild guess) the emulator uses crc32 to detect what rom it uses and adjusts the save type accordingly (think of a looooooong list with all gba game names and save type and the emu looking it up). New games after the current version are not included so....
> 2.cheats dont work
I'm not sure about this one. You sure you are modifying ram and not rom?
> 3.some games dont work
Well, nothing much you can do about that. Prolly the NES series. Then again, just get the PC emulator and play the original!!!
> 4.savestates always ,ALWAYS makes games unplayable
I found savestates are VERY reliable. Just don't close the emu just right after you save state, it won't work
> 5.static sound
Your computer is less than 700MHZ. VBA requires at least 700MHZ to run decently.
> 6.every game is to slow no matter what the frame skip
> /throttle is
Your computer is less than 700MHZ. VBA requires at least 700MHZ to run decently.
> i want something that has some features maybe alot
What the hell other features you want? VBA is very complete...
> ill try no$GBA
Prolly your best bet, altough playing it with a small window doesn't appeal me.
<P ID="signature"></P>
get the .nfo file and see the savetype then select it accordingly...the auto function doesn't work with new games because (wild guess) the emulator uses crc32 to detect what rom it uses and adjusts the save type accordingly (think of a looooooong list with all gba game names and save type and the emu looking it up). New games after the current version are not included so....
> 2.cheats dont work
I'm not sure about this one. You sure you are modifying ram and not rom?
> 3.some games dont work
Well, nothing much you can do about that. Prolly the NES series. Then again, just get the PC emulator and play the original!!!
> 4.savestates always ,ALWAYS makes games unplayable
I found savestates are VERY reliable. Just don't close the emu just right after you save state, it won't work
> 5.static sound
Your computer is less than 700MHZ. VBA requires at least 700MHZ to run decently.
> 6.every game is to slow no matter what the frame skip
> /throttle is
Your computer is less than 700MHZ. VBA requires at least 700MHZ to run decently.
> i want something that has some features maybe alot
What the hell other features you want? VBA is very complete...
> ill try no$GBA
Prolly your best bet, altough playing it with a small window doesn't appeal me.
<P ID="signature"></P>
The 9th Sage
New member
> Your computer is less than 700MHZ. VBA requires at least
> 700MHZ to run decently.
My laptop is 2.2 Ghz and it doesn't run well.
> > ill try no$GBA
> Prolly your best bet, altough playing it with a small window
> doesn't appeal me.
Well, you can resize the window so that it's quite big.
<P ID="signature">http://www.xanga.com/ZeldaDD
</a></P>
> 700MHZ to run decently.
My laptop is 2.2 Ghz and it doesn't run well.
> > ill try no$GBA
> Prolly your best bet, altough playing it with a small window
> doesn't appeal me.
Well, you can resize the window so that it's quite big.
<P ID="signature">http://www.xanga.com/ZeldaDD
The 9th Sage
New member
> works best on the 501
> but still crappy
The strange thing is this 2.2 Ghz laptop that in every way is better than the 667 mhz PC I used to use is slower with VBA than the 667 mhz PC. I don't undestand it at all.
<P ID="signature">http://www.xanga.com/ZeldaDD
</a></P>
> but still crappy
The strange thing is this 2.2 Ghz laptop that in every way is better than the 667 mhz PC I used to use is slower with VBA than the 667 mhz PC. I don't undestand it at all.
<P ID="signature">http://www.xanga.com/ZeldaDD
I have a 2.4GHz computer, and VBA is still rather slow. This is what works for me: Turn off any kind of throttle...disabled auto frame skip and set your frameskip to 2. There aren't as many FPS as I'd like, but it runs in real time and is very playable...even with the 2xSaI filter on.
<P ID="signature">
!</P>
<P ID="signature">
!</P>SirDaShadow
New member
> I have a 2.4GHz computer, and VBA is still rather slow. This
Something's wrong...what resolution, which video card and what bitdepth are you running VBA on?
Also MOVE THE MOUSE AWAY FROM THE VBA SCREEN. It kills performance.
<P ID="signature"></P>
Something's wrong...what resolution, which video card and what bitdepth are you running VBA on?
Also MOVE THE MOUSE AWAY FROM THE VBA SCREEN. It kills performance.
<P ID="signature"></P>
> The strange thing is this 2.2 Ghz laptop that in every way
> is better than the 667 mhz PC I used to use is slower with
> VBA than the 667 mhz PC. I don't undestand it at all.
>
probably cause the newer processors dont support these type of programs as much as older processors
<P ID="signature"></P>
> is better than the 667 mhz PC I used to use is slower with
> VBA than the 667 mhz PC. I don't undestand it at all.
>
probably cause the newer processors dont support these type of programs as much as older processors
<P ID="signature"></P>
> You have no idea what you're talking about.
>
*sigh*older processors have special "instructions" that most processors dont have today.VBA is probably designed for an older type of process (why do you think you cant run DOS 6.22 on a AMD athlon XP 2400+?)
<P ID="signature"></P>
>
*sigh*older processors have special "instructions" that most processors dont have today.VBA is probably designed for an older type of process (why do you think you cant run DOS 6.22 on a AMD athlon XP 2400+?)
<P ID="signature"></P>
Lenophis
New member
> > You have no idea what you're talking about.
> >
> *sigh*older processors have special "instructions" that most
> processors dont have today.VBA is probably designed for an
> older type of process (why do you think you cant run DOS
> 6.22 on a AMD athlon XP 2400+?)
Because you are using windows XP... <img src=smilies/upeyes.gif>
<P ID="signature"><img src=http://www.cpinternet.com/~norwin/lenophis/sig.png>
"For lovers of irony; I'll just say one thing...wishes do come true." - Lobster Cowboy. Jade</P>
> >
> *sigh*older processors have special "instructions" that most
> processors dont have today.VBA is probably designed for an
> older type of process (why do you think you cant run DOS
> 6.22 on a AMD athlon XP 2400+?)
Because you are using windows XP... <img src=smilies/upeyes.gif>
<P ID="signature"><img src=http://www.cpinternet.com/~norwin/lenophis/sig.png>
"For lovers of irony; I'll just say one thing...wishes do come true." - Lobster Cowboy. Jade</P>
Reaper man
Member
> *sigh*older processors have special "instructions" that most
> processors dont have today.VBA is probably designed for an
> older type of process (why do you think you cant run DOS
> 6.22 on a AMD athlon XP 2400+?)
.....
it's because you're running an NT environment
NT OSes don't run "under DOS" like win 9x does
dude, before you make such claims, perhaps you should do reasearch first. Y'know processor history, how operating systems work etc...
<P ID="signature"><center>
sig not found...</center></P>
> processors dont have today.VBA is probably designed for an
> older type of process (why do you think you cant run DOS
> 6.22 on a AMD athlon XP 2400+?)
.....
it's because you're running an NT environment
NT OSes don't run "under DOS" like win 9x does
dude, before you make such claims, perhaps you should do reasearch first. Y'know processor history, how operating systems work etc...
<P ID="signature"><center>
sig not found...</center></P>
I think you just prooved his point
> *sigh*older processors have special "instructions" that most
> processors dont have today.
If anything... new processors have extra instructions that old ones don't... not the other way around. You can't just cut an instruction from a processor line or else all the programs that use it will crash and burn when you try to run them.
> (why do you think you cant run DOS
> 6.22 on a AMD athlon XP 2400+?)
DOS is an archaic OS. There are built in limits... once your machine surpasses those limits, the OS won't work. You can't run Win95 with 1GB of RAM.... that doesn't mean modern RAM is different from older RAM... just that Win95's limit is lower. And DOS is way older than Win95... and the limits are a lot more restricting.
<P ID="signature"></P>
> *sigh*older processors have special "instructions" that most
> processors dont have today.
If anything... new processors have extra instructions that old ones don't... not the other way around. You can't just cut an instruction from a processor line or else all the programs that use it will crash and burn when you try to run them.
> (why do you think you cant run DOS
> 6.22 on a AMD athlon XP 2400+?)
DOS is an archaic OS. There are built in limits... once your machine surpasses those limits, the OS won't work. You can't run Win95 with 1GB of RAM.... that doesn't mean modern RAM is different from older RAM... just that Win95's limit is lower. And DOS is way older than Win95... and the limits are a lot more restricting.
<P ID="signature"></P>
MegaManJuno
New member
> I have a 2.4GHz computer, and VBA is still rather slow. This is what works for me: Turn off any kind of throttle...disabled auto frame skip and set your frameskip to 2. There aren't as many FPS as I'd like, but it runs in real time and is very playable...even with the 2xSaI filter on.
Yeah I've noticed some major "issues" with the throttle settings here as well...
Auto framerate is a *little* better, but I agree with Narvick that your best bet is likely to manually set the frame skip value for the best performance for your system (i.e.: trial & error).
Luckily, I seem to be able to run it with 0 frameskip even with most of the filters on my box. <img src=smilies/thumb.gif>
<P ID="signature"></P>
Yeah I've noticed some major "issues" with the throttle settings here as well...
Auto framerate is a *little* better, but I agree with Narvick that your best bet is likely to manually set the frame skip value for the best performance for your system (i.e.: trial & error).
Luckily, I seem to be able to run it with 0 frameskip even with most of the filters on my box. <img src=smilies/thumb.gif>
<P ID="signature"></P>
> it's because you're running an NT environment
> NT OSes don't run "under DOS" like win 9x does
> dude, before you make such claims, perhaps you should do
> reasearch first. Y'know processor history, how operating
> systems work etc...
I know that! windows dropped DOS long ago and with that SOME(NOT ALL) processors dropped the instructions too.
If you want dos then get it! your best bet is DOSbox a Pentium 4 dosent have thesame instructions as a 286 AND a newer processors have more stages then older processors. (I'm not even gonna try VBA on a AMD 64 FX-52 when it comes in the mail
oh, and ive only got xp on one machine. all the rest are 9.x
<P ID="signature"></p><P ID="edit"><FONT class="small">Edited by metbot on 07/18/04 02:27 AM.</FONT></P>
> NT OSes don't run "under DOS" like win 9x does
> dude, before you make such claims, perhaps you should do
> reasearch first. Y'know processor history, how operating
> systems work etc...
I know that! windows dropped DOS long ago and with that SOME(NOT ALL) processors dropped the instructions too.
If you want dos then get it! your best bet is DOSbox a Pentium 4 dosent have thesame instructions as a 286 AND a newer processors have more stages then older processors. (I'm not even gonna try VBA on a AMD 64 FX-52 when it comes in the mail
oh, and ive only got xp on one machine. all the rest are 9.x
<P ID="signature"></p><P ID="edit"><FONT class="small">Edited by metbot on 07/18/04 02:27 AM.</FONT></P>