GithubHelp home page GithubHelp logo

Fast Execution about fceux HOT 5 CLOSED

tasemulators avatar tasemulators commented on June 17, 2024
Fast Execution

from fceux.

Comments (5)

bbbradsmith avatar bbbradsmith commented on June 17, 2024

I don't know how you're automating things, but if using lua there is emu.speedmode("turbo") in the interface, at least. If you're modifying the source directly you might look into how the turbo mode is implemented? (By default activated with the Tab key, I think.)

from fceux.

Kautenja avatar Kautenja commented on June 17, 2024

Indeed, I'm using a lua script that sets up the interface for the automated agent. I've been using emu.speedmode("maximum") which seems to net better performance than emu.speedmode("turbo") (around 120fps vs 45fps, with no frameskipping). My initial thought was to increase the maximum bound of the maximum speed mode from 3200% to 128000% in the source, but that seemed to have no additional effect. Perhaps overclocking the PPU would speed things up? But, I am unsure of how to accomplish this when launching fceux from a Unix shell.

from fceux.

bbbradsmith avatar bbbradsmith commented on June 17, 2024

I think there should be a configuration file that applies all the settings, so it shouldn't matter if you can't interact with the GUI after launching? (Is it still "fceux.cfg" on the SDL version?)

I don't know much about overclocking the PPU, but the Old PPU is significantly faster code vs. New PPU, at the expense of lower accuracy. Old PPU is still the default setting, I think, but just in case you might see if it's set.

from fceux.

Kautenja avatar Kautenja commented on June 17, 2024

ah, i do see a fceux.cfg in the .fceux directory with all the options listed. Looks like the old PPU is still in effect. Are there any other options I should check to boost emulation speed in this config file?

from fceux.

zeromus avatar zeromus commented on June 17, 2024

overclocking the PPU does the opposite of what you want. If the maximum speed mode was 3200% and you were only getting 120fps, then changing it to 1 zillion % isn't going to help any; it's clearly not the limit.
set SDL.Vsync to 0. Or even better, hack BlitScreen in sdl-video.cpp to return immediately

from fceux.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.