I finnaly Got

[Kaileocomial]

I LOOOOVE that game!

It's damn tough, but it's so good it just keeps you trying and trying again! Usually I have no patience for games that hard, but something about Omega Factor just really makes me love the challange.

I hate how easy it is to 'erase all data' every time I let my son touch the game he accidentally erases my save... EVERY TIME!

Oh well, it runs awesome on the GBA emulator I have in my new PSP, so I'll just play it on there from now on & he can have the GBA version.

[1magus]

I LOOOOVE that game!

It's damn tough, but it's so good it just keeps you trying and trying again! Usually I have no patience for games that hard, but something about Omega Factor just really makes me love the challange.

I hate how easy it is to 'erase all data' every time I let my son touch the game he accidentally erases my save... EVERY TIME!

Oh well, it runs awesome on the GBA emulator I have in my new PSP, so I'll just play it on there from now on & he can have the GBA version.

Emulators just don't run well enough sadly. I really don't get it they can clock up to 155 mhz or more and most of those games barely used 5 mhz in the beginning yet they are still slow, guess that is the bad thing about emulators (:.

[fafner]

Emulators just don't run well enough sadly. I really don't get it they can clock up to 155 mhz or more and most of those games barely used 5 mhz in the beginning yet they are still slow, guess that is the bad thing about emulators (:.

Emulating a game needs to simulate all instructions of the program, because most of the time, processors are not of the them type (and interaction with the hardware may be far from trivial with a direct execution anyway). This is what makes emulators usually slow.
For example, moving a value into a register takes 1 clock tick. For a program to simulate that instruction, it will need a single move too, that is probably 1 tick too. However, recognizing the instruction will need a few tens of ticks. Let's say that 10 ticks will be needed (which is rather low). That means that 50 MHz are needed to emulate 5 MHz. That means that a very good emulator might manage to run GBA games at full speed with 155 MHz.

[CommanderEVE]

thats the Omega Factor game story base like?

[1magus]

thats the Omega Factor game story base like?

BAsicly yeah but very dumbed down since it is GBA.

[1magus]

Emulating a game needs to simulate all instructions of the program, because most of the time, processors are not of the them type (and interaction with the hardware may be far from trivial with a direct execution anyway). This is what makes emulators usually slow.
For example, moving a value into a register takes 1 clock tick. For a program to simulate that instruction, it will need a single move too, that is probably 1 tick too. However, recognizing the instruction will need a few tens of ticks. Let's say that 10 ticks will be needed (which is rather low). That means that 50 MHz are needed to emulate 5 MHz. That means that a very good emulator might manage to run GBA games at full speed with 155 MHz.

That I knew but we could do something more advance like just make the game a executable rather than a emulator running it. Not sure why we can't.

[CommanderEVE]

BAsicly yeah but very dumbed down since it is GBA.

kool... i just thought that the game has a good name i thought it would have a good story line to it... so yeah your right it's a GBA but it's still good

[fafner]

That I knew but we could do something more advance like just make the game a executable rather than a emulator running it. Not sure why we can't.

Dynamically recompiling a program is possible: most Nintendo 64 emulators do it because otherwise it would be waaaaay too slow hmy: But this technic is usually not developped for "slow" hardware such as the GBA, because it is rather hard for a very low advantage Today most hardware (but not all) can emulate very well GBA even with slow emulators.