FSX Repaint Manager (Version 1.01)
read the License Information before proceeding.
The Flight1 FSX Repaint Manager will allow you to manage FSX Repaints
for many products. It is fairly straightforward in that it is simply a
repackager and installer for aircraft liveries and aircraft.cfg entries.
It will automatically install your aircraft, create folders, and make
necessary aircraft.cfg entries.
document will cover the basic functions of this software. There is additional
information in the FSXRepaint.exe file once you run it.
check for the latest version from www.Flight1.com.
Look in free library
section. And although this product is freeware, if you have trouble,
you can let us know by making a post in our www.simforums.com
Add a Repaint
Remove a Repaint
Create a Package
an RCF File
can find the FSX Repaint Manager in your Start/Programs menu. Look for
the Flight One Software/FSX Repaint Manager entry. There is also
a shortcut on your desktop if you want to use that (you can delete it
if you desire).
to begin, simply press the Select Aircraft button. This will
allow you to browse to a Package (*.pkg) or Repaint Configuration File
(*.rcf). Once loaded you will see the Aircraft title, as well as the
folder path from the FSX root folder that the selected aircraft uses.
You may also see additional information or instructions.
most cases you will load the PKG file, as this will contain all the
information needed to install the new repaint.
for Vista users: If you are using Windows Vista, you may need to
run this program as Administrator. Please read our Vista
Information Page for more instructions on using this and many other
products with Vista.
will use the RCF format if you are creating a first-time Package (you
are packaging a repaint and you had to create the RCF file because none
existed previously in a PKG or RCF file). If you want to create a package
to distribute, and an RCF file does not already exist, see "Creating
an RCF File" below.
data is automatically added to each package when they are compiled so
there is no need to ship an RCF file with your package. You can also
create packages from the RCF data in the package since the RCF data
is embedded in the package. So once you create an RCF file and distribute
your first package, the RCF data migrates itself automatically to every
package created by users (unless a user creates or modifies the RCF
Whenever you load a Package file, there is a corresponding Package.RCF
file created in the same folder as FSXRepaint.exe. You can then view
this data in a text editor if you need to make modifications to it.
After you create modifications to it, you need to reload it in the main
interface for it to be added to your packages.
Add a Repaint
the Add Repaint(s) button. This will open a screen that will
list all the repaint packages (these files end in the .PKG extension)
that exist in your aircraft's Downloads folder. Of course this folder
most likely does not exist by default, so you need to either create
it, or if you already opened the RCF file for the aircraft, then we
have created it for you when you first loaded the RCF file.
you do want to create the Downloads folder yourself, simply browse to
the aircraft folder you are going to use (use Windows Explorer or equivalent
for this), and create a new Downloads folder. An example would
be [YOUR FSX PATH]\SimObjects\Airplanes\YOUR AIRCRAFT\Downloads.
Then, when you download or obtain a repaint package, you would put the
package in the newly created Downloads folder.
will also see a Browse Packages button. This does not require
the Downloads folder above. But the Downloads folder is nice because
you can place many repaints in there at a time and they will all get
automatically listed. Please note that only 1 browsed for package will
appear in the Package List at a time. It will be listed with a preceding
asterisk (*). The browsed for package will also be removed whenever
the list refreshes.
select the packages you want to install, and then press the Install
Package(s) button. Note: Browsed for packages will not get automatically
refreshed in the selection list after installation.
will see a checkbox option that will remove the package file from your
system after installation. Check this if you do not want to retain the
package (PKG) file on your system after installation (it will get deleted).
Remove a Repaint
remove a repaint, simply press the Remove Repaint(s) button.
This will show a list of the selected aircraft's installed repaints
(or liveries). Select which ones you want to remove and the Repaint
Manager will take care of the rest, including removing the associated
Create a Package
Create Package button will take you to the Packager screen. This
will allow you to package a repaint you may have made so you can share
it with others. Use caution here... you do not want to package anything
copyrighted by anyone else. So carefully review the files you decide
to package and make sure you can distribute everything that you package.
package, select the aircraft you want to package from the list. Again,
a PKG or RCF file already needs to be loaded so we know what aircraft
you package an aircraft, all files in the aircraft's texture.xx folder
are listed (xx being a variation)... even non-texture files such as
a Texture.cfg file, as well as a thumbnail.jpg file, will appear. If
you do not want to ship a certain file in your aircraft's texture.xx
folder, you can uncheck it from the box.
is always good, but not required, to include a bitmap image preview
that is 400 x 300 pixels in size. This way, users can preview the package
before installing it.
packaged is information listed in the the Aircraft.cfg file for the
selection. Some information may get slightly changed on the users system
that uses your package (such as a duplicate texture folder or duplicate
aircraft "ui_variation"), but for the most part, everything
is packaged unaltered. Only the fltsim.x section is packaged. No other
aircraft.cfg information is packaged.
system is different from the previous Flight1 Text-o-Matic program for
FS9 and FSX. With the FSX Repaint Manager, all individual textures and
files are packaged, not a single big texture. So, you need to already
have the aircraft painted and configured exactly the way you want it.
Then, a "mirror" of this is unpackaged and configured on the
end users system.
can package either full FSX compliant aircraft, or FS9 style aircraft
imported into FSX.
an RCF File
files, or "Repaint Configuration Files", contain information
required by the Repaint Manager. In many cases you will not need to
create on as the aircraft creator may have done this already. RCF data
is added to the PKG files you create so you do not need to distribute
the RCF file if you are shipping a PKG file. So if you need to create
an RCF file, here is the format. RCF files are all plain text.
need the following lines:
is the title that will appear in the Repaint Manager user interface.
folder is the exact name up from the root FSX folder that your
aircraft exists in.
information is information that may be important, such as any
exclude is if you want an aircraft not to show up in the Remove
Aircraft list. Use the ui_variation field, separated by a vertical pipe
"|" between each aircraft you want to exclude.
is an example.rcf file:
information=Make sure you include a Texture.cfg file. It is required
for each aircraft.
exclude=Aircraft 1 Variation|Aircraft 2 Variation|Aircraft 3 Variation
only the folder is required. But do add at least a title. The
title can be something friendly, and does not have to match anything
in your aircraft.cfg file.
of your Aircraft.cfg file are created just in case you need to revert
to it. These are in your aircraft's folder. Before each installation,
an Aircraft.f1b file is created. This is overwritten after each new
entry is added, so you get constant backups.
you first load a RCF file, the Aircraft.cfg is copied to Aircraft.001.
This is only done one time and not overwritten. This will always be
the original Aircraft.cfg unaltered.
tool will try to keep aircraft.cfg files properly formatted when possible.
This includes removing extra line feeds, and preventing overcrowding
of the various [sections] of the file.
using this software, you agree to the following license agreement for
the Flight1 FSX Repaint Manager (herein referred to as product).
license agreement is between you and Flight One Software, Inc..
this software is free, certain restrictions still apply.
agree that in no event shall Flight One Software, Inc. or its suppliers
be liable for any damages whatsoever (including, without limitation,
damages for loss of business profits, business interruption, loss of
business information, loss of data, or any other pecuniary loss) arising
out of the use of or inability to use this product. Flight1 does not
warrant that this product is bug-free, or that it will work in every
long as the installer does not identify the version as "Beta",
or if the version number of the main FSXRepaint.exe is 1.0 or greater,
you may redistribute the product in its original, unmodified, pre-installed
form as long it is distributed in its original installer that is compiled
by Flight One Software, Inc.. No modifications to any part of the product
itself may be redistributed.
One Software, Inc. does not claim any rights or ownership to unique
works that you package that are not already copyrighted material of
Flight One Software, Inc..
may include any non-beta version of this product in any freeware, shareware,
or commercial application without additional permission from Flight1
as long as you agree to everything above.
software is Copyright 2007 Flight One Software, Inc.
2007 Flight One Software, Inc.