fceux/help/Troubleshooting.html

131 lines
5.8 KiB
HTML

<html>
<head>
<title>Troubleshooting</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="generator" content="HelpNDoc Personal Edition 3.8.0.560">
<link type="text/css" rel="stylesheet" media="all" href="css/reset.css" />
<link type="text/css" rel="stylesheet" media="all" href="css/base.css" />
<link type="text/css" rel="stylesheet" media="all" href="css/hnd.css" />
<!--[if lte IE 8]>
<link type="text/css" rel="stylesheet" media="all" href="css/ielte8.css" />
<![endif]-->
<style type="text/css">
#topic_header
{
background-color: #EFEFEF;
}
</style>
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="js/hnd.js"></script>
<script type="text/javascript">
$(document).ready(function()
{
if (top.frames.length == 0)
{
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
top.location.href = "fceux.html?" + sTopicUrl;
}
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
{
top.FrameTOC.SelectTocItem("Troubleshooting");
}
});
</script>
</head>
<body>
<div id="topic_header">
<div id="topic_header_content">
<h1>Troubleshooting</h1>
<div id="topic_breadcrumb">
<a href="FAQGuides.html">FAQ / Guides</a> &rsaquo;&rsaquo; </div>
</div>
<div id="topic_header_nav">
<a href="FAQGuides.html"><img src="img/arrow_up.png" alt="Parent"/></a>
<a href="FAQGuides.html"><img src="img/arrow_left.png" alt="Previous"/></a>
<a href="ToolAssistedSpeedruns.html"><img src="img/arrow_right.png" alt="Next"/></a>
</div>
<div class="clear"></div>
</div>
<div id="topic_content">
<p></p>
<p><span class="rvts17">Troubleshooting</span></p>
<p><br/></p>
<p><br/></p>
<p>This section describes potential problems/question that could arise when using FCEUX.</p>
<p><br/></p>
<p><span class="rvts40">Slow emulation / Sound crackle</span></p>
<p><br/></p>
<p>FCEUX may not run well on slow CPUs.</p>
<p>Ensure that you're using the Old PPU, because the New PPU engine is very slow. Check Config -&gt; PPU -&gt; Old PPU.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">Sound crackle</span></p>
<p><br/></p>
<p>If you enable hardware acceleration and Vsync (Wait for VBlank), and your monitor has a framerate different from 60FPS, you may experience minor sound cracle. This is a known issue and will probably be resolved in a future release.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">Emulated picture is blurred (similar to the bilinear filter)</span></p>
<p><br/></p>
<p>Try choosing different options in the "DirectDraw" list in the <a class="rvts18" href="Video.html">Video</a> config dialog.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">Slow savestates when recording movies</span></p>
<p><br/></p>
<p>On slower computers, savestates can be slow with long movies. &nbsp;A small speedup can be done by disabling Config -&gt; Enable -&gt; Backup savestates.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">The colors in game X do not look right!</span></p>
<p><br/></p>
<p>There's no such thing as a universally right palette for NES games.</p>
<p>FCEUX uses the color palette of the old FCEU / FCEUXD branches. Also FCEUX comes pre-packaged with several additional color palettes. For more information see <a class="rvts18" href="Palette.html">Palette config</a> and <a class="rvts18" href="PaletteOptions.html">Palette options</a>.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">I converted a .fcm file to .fm2 but the .fm2 desyncs</span></p>
<p><br/></p>
<p>Depending on what version of FCEU / Game your .fcm was made, there maybe a number of sync issues. &nbsp;These are listed in detail at <a class="rvts18" href="http://tasvideos.org/ConvertFCMtoFM2.html" target="_blank">http://tasvideos.org/ConvertFCMtoFM2.html</a>.</p>
<p><br/></p>
<p>In addition, the .fm2 conversion tool has had some issues on certain operating systems including Vista and Mac.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">Can't find FDS Bios image when I attempt to load a .fds game!</span></p>
<p><br/></p>
<p>FCEUX requires the FDS Bios to be named <span class="rvts32">disksys.rom</span>. &nbsp;It must be located in the root directory (where fceux.exe is stored) or in the folder of the FDS Directory override (see <a class="rvts18" href="Directories.html">Directory overrides</a>).</p>
<p><br/></p>
<p>In addition, there are some bad versions of disksys.rom. &nbsp;The one FDS requires is 8192 bytes in size.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">How can I use Netplay / Where can I get FCEU Server?</span></p>
<p><br/></p>
<p>Currently, the WIndows version of FCEUX is not compatible with the FCEU-server code. This is a known issue and will probably be resolved in a future release.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts40">I have a Game Genie rom, how can I use it with FCEUX?</span></p>
<p><br/></p>
<p>While FCEUX has a <a class="rvts18" href="GameGenieEncoderDecoder.html">Game Genie code converter</a>, you can also use game genie codes with the game genie ROM. &nbsp;It must be named gg.rom and be placed in the root directory (where fceux.exe is stored). &nbsp;You must also check <span class="rvts22">Config-&gt;Enable-&gt;Game Genie ROM</span> in the main menu.</p>
<p><br/></p>
<p><br/></p>
<p><br/></p>
<p><br/></p>
<p><br/></p>
<p></p>
<p class="rvps2"><span class="rvts13">Created with the Personal Edition of HelpNDoc: </span><a class="rvts14" href="http://www.helpndoc.com/create-epub-ebooks">Produce electronic books easily</a></p>
</div>
<div id="topic_footer">
<div id="topic_footer_content">
2013</div>
</div>
</body>
</html>