* Melchior FRANZ -- Sunday 01 February 2009:
Any of the applications are only interested in FG_DATA. And please
not again a fallback from FG_DATA to FG_ROOT/data, because that
just repeats that old mistake.
No, wait! This would actually be ok: If FG_DATA is defined, use
data from
installation. Below that we would have
sensible defaults ... like data/ bin/ scenery/ but these could be overridden
with FG_DATA FG_SCENERY FG_AIRCRAFT, etc.
OK, fine with me. Then let's rename fgfs' --fg-root to --fg-data,
and let it read FG_DATA rather than FG_ROOT. Someone has to adapt
all
directory from $FG_DATA/Aircraft to
$FG_DATA/AI/Aircraft
- Removed any extraneous files/directories (-set.xml, FDM, Panels, sounds),
typically just leaving a Model directory.
- Use ImageMagick to convert any .rgb textures to png.
- Use a text editor to replace all the .rgb references to .png
- Hacked
to bugs and confusion, while not having a *single*
advantage. Or could anyone tell me one, please? Just one?
It might make sense to have FG_DATA which defaults to $FG_ROOT/data/
What for? FG_ROOT shall point to the directory which contains
the data (i.e. the file version). We don't need another
. If
possible, I'd suggest maintaining multiple versions of the download (2.0
compatible and 2.4 compatible), but of course that's more hassle for you.
Fundamentally, we want aircraft to do things they previously did not (work
outside FG_DATA), and without introducing too many hacks, so there has
Hi Clément,
On Thu, Apr 11, 2013 at 1:15 PM, Clement de l'Hamaide wrote:
I'm using a Thrustmaster Hotas-x and I noticed that nasal section on top
of the original file (
$FG_DATA/Input/Joysticks/Thrustmaster/T-Flight-Hotas-X.xml ) is not copied
to the custom file written in $FG_HOME after
contains
the data? Or shall we rename FG_ROOT to FG_DATA, and let
FG_ROOT point to the source, and FG_DATA to the data? In any
case, there should be no assumption that data is in the source
directory. It doesn't belong there.
I think I already explained my thoughts in terms of logical
consistency
understand there's reasons not too.
If possible, I'd suggest maintaining multiple versions of the download
(2.0 compatible and 2.4 compatible), but of course that's more hassle
for you. Fundamentally, we want aircraft to do things they previously
did not (work outside FG_DATA), and without
that with something else now.
Maybe $FG_BASE or $FG_INSTALLDIR for the installation directory?
Agreed, I don't know what the manual says, or the original intent, but every
piece of code we have now, that I've seen, assumes FG_HOME is somewhere like
$HOME/.fgfs - not the FG_DATA location or any
Hello,
I found 2 issues with the ASK13 (fg_data 2.60_rc1-1.1).
1. Immatriculation doesn't work because files from another aircraft which isn't
in the base package are used:
loadxml: Cannot find XML property file 'Aircraft/Grob-G109/Dialogs/immat.xml'.
Nasal runtime error: Dialog class: XML
Hi,
I'm using a Thrustmaster Hotas-x and I noticed that nasal section on top of
the original file ( $FG_DATA/Input/Joysticks/Thrustmaster/T-Flight-Hotas-X.xml
) is not copied to the custom file written in $FG_HOME after modification from
the Joystick Configuration dialog.
This missing nasal
what do you suggest? That FG_ROOT must always point to a
directory containing a directory named data/ which contains
the data? Or shall we rename FG_ROOT to FG_DATA, and let
FG_ROOT point to the source, and FG_DATA to the data? In any
case, there should be no assumption that data
this would provide beyond what we already have with TerraSync
?
However the scenery goes to FG_ROOT in fact it should be split imho to
(Because its a sudo or a patented.m$.runas ie it DONT need root.. ie I
can ad to scenary and override..)..
* FG_AIRCRAFT
* and FG_SCENERY
* and FG_DATA
I'm now
the scenery goes to FG_ROOT in fact it should be split imho to
(Because its a sudo or a patented.m$.runas ie it DONT need root.. ie I
can ad to scenary and override..)..
* FG_AIRCRAFT
* and FG_SCENERY
* and FG_DATA
It wont sing well on windows, because Steve Blamer wont like that. ? am
out of touch
14 matches
Mail list logo
