Example #1
0
</p>

<p>
Virtual Boy ROM images must each have an extension of ".vb" or ".vboy" to be recognized as such.  Mednafen versions prior to 0.9.13 allowed ".bin" as well, but this conflicts with the Sega Megadrive emulation module.
</p>

<p>
Due to how the left+right views are transformed into a single image, enabling most of the image filter effects(bilinear interpolation, OpenGL pixel shaders, special scalers, etc.) is not recommended.  However, they will work properly with the "cscope" and "sidebyside" 3D modes, and may work tolerably with the "anaglyph" 3D mode.  This limitation may be corrected in the future by refactoring the 3D mode mixing out to the driver side, post individual filtering for each left/right view; however, this would significantly negatively impact performance.
</p>

<p>
To use the "hli" mode with a "Line Interlaced 3D" monitor, you'll want to set "vb.yscale(fs)" to 1, "vb.liprescale" appropriately, and "vb.xscale(fs)" to 2 multiplied by the value of "vb.liprescale".
</p>

<p>
<b>NOTE:</b> The "hli" and "vli" modes will not work properly in windowed video output mode; you may need to adjust the window's position to get the lines to line up correctly for the 3D effect to work.
</p>

<?php 
EndSection();
?>

<?php 
PrintSettings();
?>

<?php 
EndPage();
?>
Example #2
0
  alter the contents of the primary configuration file, unless a user action occurs that causes new setting values to be generated
  based on the current active setting value(such as toggling full-screen mode inside the emulator, for instance).  Some settings
  currently cannot be overridden properly:
  <ul>
   <li>cd.image_memcache</li>
   <li>filesys.untrusted_fip_check</li>
   <li>&lt;system&gt;.enable</li>
  </ul>
 </p>
<?php 
EndSection();
?>


<?php 
PrintSettings("Global Settings Reference");
?>

 <?php 
BeginSection("Firmware/BIOS", "", FALSE, FALSE, "Section_firmware_bios");
?>
<p>
Some emulation modules require firmware/BIOS images to function.  If a firmware path is non-absolute(doesn't begin with
C:\ or / or similar), Mednafen will try to load the file relative to the "firmware" directory under the Mednafen <a href="#Section_base_directory">base directory</a>.  If it doesn't find it there, it will be loaded relative to the Mednafen <a href="#Section_base_directory">base directory</a> itself.  Of course,
if the "path_firmware" setting is set to a custom value, the firmware files will be searched relative to that path.
</p>
 <?php 
EndSection();
?>

 <?php