Aug 25, 2018 RPG Maker Forums. Home Forums > Support. Ultra Mode 7 Demo Script Script Download FAQ Q: Why does the script not work with canvas? A curiosity: I remember old mode-7 scripts for XP/VX allowed you to make some tile elements like trees 'pop up'. Will this ever be possible, or is too much of a hassle?
Mkxp mkxp is a project that seeks to provide a fully open source implementation of the Ruby Game Scripting System (RGSS) interface used in the popular game creation software 'RPG Maker XP', 'RPG Maker VX' and 'RPG Maker VX Ace' (trademark by Enterbrain, Inc.), with focus on Linux. The goal is to be able to run games created with the above software natively without changing a single file. It is licensed under the GNU General Public License v2+.
Prebuilt binaries by Ali Bindings Bindings provide the glue code for an interpreted language environment to run game scripts in. Currently there are three bindings: MRI Website: Matz's Ruby Interpreter, also called CRuby, is the most widely deployed version of ruby. If you're interested in running games created with RPG Maker XP, this is the one you should go for.
MRI 1.8 is what was used in RPG Maker XP, however, this binding is written against 2.0 (the latest version). For games utilizing only the default scripts provided by Enterbrain, this binding works quite well so far. Note that there are language and syntax differences between 1.8 and 2.0, so some user created scripts may not work correctly. For a list of differences, see: This binding supports RGSS1, RGSS2 and RGSS3. Mruby (Lightweight Ruby) Website: mruby is a new endeavor by Matz and others to create a more lightweight, spec-adhering, embeddable Ruby implementation.
You can think of it as a Ruby version of Lua. Due to heavy differences between mruby and MRI as well as lacking modules, running RPG Maker games with this binding will most likely not work correctly. It is provided as experimental code. Write your own ruby scripts and run them.
Some extensions to the standard classes/modules are provided, taking the RPG Maker XP helpfile as a quasi 'reference'. These include Marshal, File, FileTest and Time. This binding only supports RGSS1. Important: If you decide to use, don't forget to add -lonig to the linker flags to avoid ugly symbol overlaps with libc.
Null This binding only exists for testing purposes and does nothing (the engine quits immediately). It can be used to eg. Run a minimal RGSS game loop directly in C++. Dependencies / Building • Boost.Unordered (headers only) • Boost.Program_options • libsigc++ 2.0 • PhysFS (latest hg) • OpenAL • SDL2* • SDL2_image • SDL2_ttf • • vorbisfile • pixman • zlib (only ruby bindings) • OpenGL header (alternatively GLES2 with DEFINES+=GLES2_HEADER) • libiconv (on Windows, optional with INI_ENCODING) • libguess (optional with INI_ENCODING) (* For the F1 menu to work correctly under Linux/X11, you need latest hg + ) mkxp employs Qt's qmake build system, so you'll need to install that beforehand. Alternatively, you can build with cmake (FIXME: add cmake instructions). Qmake will use pkg-config to locate the respective include/library paths. If you installed any dependencies into non-standard prefixes, make sure to adjust your PKG_CONFIG_PATH variable accordingly.
The exception is boost, which is weird in that it still hasn't managed to pull off pkg-config support (seriously?). If you installed boost in a non-standard prefix, you will need to pass its include path via BOOST_I and library path via BOOST_L, either as direct arguments to qmake ( qmake BOOST_I='/usr/include'.) or via environment variables. You can specify a library suffix (eg. '-mt') via BOOST_LIB_SUFFIX if needed. Midi support is enabled by default and requires fluidsynth to be present at runtime (not needed for building); if mkxp can't find it at runtime, midi playback is disabled. It looks for libfluidsynth.so.1 on Linux, libfluidsynth.dylib.1 on OSX and fluidsynth.dll on Windows, so make sure to have one of these in your link path.
If you still need fluidsynth to be hard linked at buildtime, use CONFIG+=SHARED_FLUID. When building fluidsynth yourself, you can disable almost all options (audio drivers etc.) as they are not used. Note that upstream fluidsynth has support for sharing soundfont data between synthesizers (mkxp uses multiple synths), so if your memory usage is very high, you might want to try compiling fluidsynth from git master. By default, mkxp switches into the directory where its binary is contained and then starts reading the configuration and resolving relative paths.
In case this is undesired (eg. When the binary is to be installed to a system global, read-only location), it can be turned off by adding DEFINES+=WORKDIR_CURRENT to qmake's arguments. To auto detect the encoding of the game title in Game.ini and auto convert it to UTF-8, build with CONFIG+=INI_ENCODING. Requires iconv implementation and libguess. If the encoding is wrongly detected, you can set the 'titleLanguage' hint in mkxp.conf. MRI-Binding: pkg-config will look for ruby-2.1.pc, but you can override the version with MRIVERSION=2.2 ('2.2' being an example). This is the default binding, so no arguments to qmake needed ( BINDING=MRI to be explicit).
0 kommentar(er)
