Reduce severity of a failure to create a marker beacon due to an unknown runway from...

[flightgear.git] / src / Navaids / navrecord.cxx

diff --git a/src/Navaids/navrecord.cxx b/src/Navaids/navrecord.cxx
index 03317a57d3342f62cd68718c36d1cc88e910ae5c..d0549f26b8e1b6797dfa3c3d22abf981171dc827 100644 (file)
--- a/src/Navaids/navrecord.cxx
+++ b/src/Navaids/navrecord.cxx
@@ -39,7 +39,6 @@
 #include <Airports/runways.hxx>
 #include <Airports/simple.hxx>
 #include <Airports/xmlloader.hxx>
-
 #include <Main/fg_props.hxx>
 
 FGNavRecord::FGNavRecord(Type aTy, const std::string& aIdent, 
@@ -51,8 +50,7 @@ FGNavRecord::FGNavRecord(Type aTy, const std::string& aIdent,
   multiuse(aMultiuse),
   _name(aName),
   mRunway(NULL),
-  serviceable(true),
-  trans_ident(aIdent)
+  serviceable(true)
 { 
   initAirportRelation();
 
@@ -60,7 +58,7 @@ FGNavRecord::FGNavRecord(Type aTy, const std::string& aIdent,
   // assign our own defaults, unless the range is not set for some
   // reason.
   if (range < 0.1) {
-    SG_LOG(SG_GENERAL, SG_WARN, "navaid " << ident() << " has no range set, using defaults");
+    SG_LOG(SG_GENERAL, SG_DEBUG, "navaid " << ident() << " has no range set, using defaults");
     switch (type()) {
     case NDB:
     case VOR: