Kill the Aircraft/foo path warning.
We probably need a warning for cross-aircraft paths, but leaving that for a separate change since I’m worried it will warn on MP aircraft. Maybe better checked in the Python scripts than in the app?
This commit is contained in:
parent
9e122eaf81
commit
31e933d836
1 changed files with 0 additions and 8 deletions
|
@ -88,14 +88,6 @@ public:
|
|||
const char* aircraftDir = fgGetString("/sim/aircraft-dir");
|
||||
string_list aircraftDirPieces(sgPathBranchSplit(aircraftDir));
|
||||
if (!aircraftDirPieces.empty() && (aircraftDirPieces.back() == pieces[1])) {
|
||||
// disable this warning for release builds
|
||||
SGPath betterPath;
|
||||
for (unsigned int i=2; i<pieces.size(); ++i) {
|
||||
betterPath.append(pieces[i]);
|
||||
}
|
||||
SG_LOG(SG_AIRCRAFT, SG_DEV_WARN, "resolved path:" << aResource << " using /sim/aircraft-dir.\n"
|
||||
"This is legacy behaviour, change to an aircraft relative path:" << betterPath);
|
||||
|
||||
// current aircraft-dir matches resource aircraft
|
||||
SGPath r(aircraftDir);
|
||||
for (unsigned int i=2; i<pieces.size(); ++i) {
|
||||
|
|
Loading…
Reference in a new issue