This thread is to make 1964 have a better ini, so people, put your mind to this, and put the entries needed changing from the orignal ini release of 0.7.0
This thread is to make 1964 have a better ini, so people, put your mind to this, and put the entries needed changing from the orignal ini release of 0.7.0
I Run This
A small bug, when you a rom, the 1964 backgrond stays with the last rendered frame when viewing 1964 without the rom browser.
I Run This
Also rice, can you put FPS instead of V/I's, less people know what V/I's are than FPS. Just a small suggestion.
I Run This
Any way to make it crash proof against bad roms? i tried to load up 1080 (JU) and 1964 crashed.
I Run This
Illegal Opcode Request On A Bug's Life (U)
80000180: Illegal Opcode Request
I Run This
When switching out of fullscreen, videoupdate almost always fails. And also it would be cool to have a function to auto full screen once a romis done loading
I Run This
I know i been posting alot on this same forum, but in a ini, since the CF increases speed by fooling the timers, why not put all games at cf8 and up to a automatic sync (60 or 50 V/I's) ? since its the fastest? whats the downfall? there has to be one
I Run This
You fool the timer too much, then the timer will fool you by freezing and/or skipping frames. You can not get the skipped frams back by using AutoSync.
You will see what I mean if you try to use large CF, like 8 for most games.
Setting the CF in game option is actually not to fool the game, but to try the best timer out because we are not sure what the timer should be.
CF=2 or 3 is always the best value in 1964 .
- Rice
http://1964emu.emulation64.com
Its kind of hard testing, when evenon cf1 it goes 60fps :-)
I Run This
??A small bug, when you a rom, the 1964 backgrond stays with the last rendered frame when viewing 1964 without the rom browser.
- Rice
http://1964emu.emulation64.com