Jump to content

[1.12.x] NavUtilities continued, ft. HSI & Instrument Landing System

linuxgurugamer

By linuxgurugamer
in KSP1 Mod Releases

 Share

Recommended Posts

Caerfinon

Caerfinon

Posted
Posted (edited)

@linuxgurugamer The debug version does not produce the GUI error. The aircraft approaches the outer marker and everything stays on the screen.  The exceptions related to NavInstruments are no longer present.

There are however, two issues not related to the GUI disappearing issue;

  1. The visual marker indicators work correctly. The audio marker indicators are completely silent.
  2. The purple glideslope indicators on the lower left and right of the display do not change to match the flight of the aircraft. If I change the glideslope to a higher setting, the indicators move to different locations, but again no movement corresponding to the aircraft's flight.

aCAI377.png

Log Files

Edited by Caerfinon
Link to comment
Share on other sites
linuxgurugamer

linuxgurugamer

Posted
  • Author
Posted
2 hours ago, Caerfinon said:

The visual marker indicators work correctly. The audio marker indicators are completely silent.

This is what I expectd.  The audio code is broken, I'll have to work on it.

2 hours ago, Caerfinon said:

The purple glideslope indicators on the lower left and right of the display do not change to match the flight of the aircraft. If I change the glideslope to a higher setting, the indicators move to different locations, but again no movement corresponding to the aircraft's flight.

ok, wasn't aware of them.

And I don't need this log file, so  you can delete it if it's taking space

Link to comment
Share on other sites
The-Grim-Sleeper

The-Grim-Sleeper

Posted
Posted
On 9/23/2021 at 2:57 PM, linuxgurugamer said:

The system slows down to system lock up if the NavUtils compass window is open while the secondary mouse button is held.

 it's something to do with the Linux implementation of Unity.  It would be good to get more people testing this

I am Patient zero of this issue and I just ran a quick test with NavInstuments-0.8.0.5. I still have more or less the same results. That said, I can confirm that reducing system load in minor ways seems to alleviate the issue, and having a lot of GUI elements open (but not NavInstuments Compass specifically) causes a lesser version of this problem with framerate and my system in general. NavInstuments is a big contributor, but that is probably due to the Compass being a bit more graphical than text-boxes used by most mods. It is indeed more a Linux-Unity problem, and is out-of-scope for any mods to fix. I will pursue other solutions to this problem.

Link to comment
Share on other sites
  • 1 month later...
Beetlecat

Beetlecat

Posted
Posted (edited)
5 hours ago, Fletch4 said:

could this work with kk in the future?

How do you mean? It just needs definitions for any KK runways that define the approach and different glideslope angles and marker distances.

Also--speaking of that @Caerfinon -- I think the config for the JNSQ island airfield 270 approach is off-center. It's just the one dirt runway, so it should match the latitude as the 90 approach? but it's off a little bit. This made for quite an exciting night landing when stopping there for some fuel and coffee during an evening flight... ;D
 

Spoiler 
//-------------------------------------------------------------------
// Island Airfield
//-------------------------------------------------------------------
Runway:NEEDS[JNSQ]
{
	custom = False
	ident = Island ILS 09
	shortID = JAO09
	hdg = 90
	body = Kerbin
	altMSL = 483.600006
	gsLatitude = -1.53231275
	gsLongitude = -71.9316483
	locLatitude = -1.53231239
	locLongitude = -71.8958282
	outerMarkerDist = 10000
	middleMarkerDist = 2200
	innerMarkerDist = 200
}
Runway:NEEDS[JNSQ]
{
	custom = False
	ident = Island ILS 27
	shortID = JAO27
	hdg = 270
	body = Kerbin
	altMSL = 483.600006
	gsLatitude = -1.5315907
	gsLongitude = -71.8884811
	locLatitude = -1.53159034
	locLongitude = -71.9243011
	outerMarkerDist = 10000
	middleMarkerDist = 2200
	innerMarkerDist = 200
}

 

 

Edited by Beetlecat
Link to comment
Share on other sites
linuxgurugamer

linuxgurugamer

Posted
  • Author
Posted
1 hour ago, Beetlecat said:

How do you mean? It just needs definitions for any KK runways that define the approach and different glideslope angles and marker distances.

Also--speaking of that @Caerfinon -- I think the config for the JNSQ island airfield 270 approach is off-center. It's just the one dirt runway, so it should match the latitude as the 90 approach? but it's off a little bit. This made for quite an exciting night landing when stopping there for some fuel and coffee during an evening flight... ;D
 

  Reveal hidden contents 
//-------------------------------------------------------------------
// Island Airfield
//-------------------------------------------------------------------
Runway:NEEDS[JNSQ]
{
	custom = False
	ident = Island ILS 09
	shortID = JAO09
	hdg = 90
	body = Kerbin
	altMSL = 483.600006
	gsLatitude = -1.53231275
	gsLongitude = -71.9316483
	locLatitude = -1.53231239
	locLongitude = -71.8958282
	outerMarkerDist = 10000
	middleMarkerDist = 2200
	innerMarkerDist = 200
}
Runway:NEEDS[JNSQ]
{
	custom = False
	ident = Island ILS 27
	shortID = JAO27
	hdg = 270
	body = Kerbin
	altMSL = 483.600006
	gsLatitude = -1.5315907
	gsLongitude = -71.8884811
	locLatitude = -1.53159034
	locLongitude = -71.9243011
	outerMarkerDist = 10000
	middleMarkerDist = 2200
	innerMarkerDist = 200
}

 

 

If someone else could confirm these configs, I'll add them to the mod

Link to comment
Share on other sites
Beetlecat

Beetlecat

Posted
Posted
23 minutes ago, linuxgurugamer said:

If someone else could confirm these configs, I'll add them to the mod

Just to confirm--the ones I quoted are from the JNSQ.cfg already distributed with NavInstruments.  I'm guessing the gsLatitude and locLatitude should be closer to matching the opposite direction since the runway is 100% East-west oriented.

I'll try those other values and report back if I get some KSP time in later this evening. 

Link to comment
Share on other sites
Caerfinon

Caerfinon

Posted
Posted
20 hours ago, Beetlecat said:

I think the config for the JNSQ island airfield 270 approach is off-center

I'll take a look. The  kerbal survey team might have been a little off center as they recorded the information. Each end of the runway is surveyed separately so it can "drift" a bit, especially if the runway provides no ground markings to gauge position. 

Link to comment
Share on other sites
Beetlecat

Beetlecat

Posted
Posted
1 hour ago, Caerfinon said:

I'll take a look. The  kerbal survey team might have been a little off center as they recorded the information. Each end of the runway is surveyed separately so it can "drift" a bit, especially if the runway provides no ground markings to gauge position. 

Oh, that's totally fair, and I don't blame them--considering the fantastic work they've done all across Kerbin. The 27 approach is probably a rarely-used one, especially considering the state of the services there. There's not even a functioning washroom!

Anywho, I did a simulated daytime approach to confirm my suspicions, and it is indeed situated a bit to the right/north of the runway:

Spoiler

alignment.png

I'll try duplicating the latitude #s from the opposite approach (which seems fine).

Link to comment
Share on other sites
Caerfinon

Caerfinon

Posted
Posted
15 hours ago, Beetlecat said:

Anywho, I did a simulated daytime approach to confirm my suspicions, and it is indeed situated a bit to the right/north of the runway:

Definitely something odd going on.  I did a test flight this morning, I'm on JNSQ 10 using the Navinstruments runway files 

Spoiler 
Runway:NEEDS[JNSQ]
{
	custom = False
	ident = Island ILS 27
	shortID = JAO27
	hdg = 270
	body = Kerbin
	altMSL = 483.600006
	gsLatitude = -1.5315907
	gsLongitude = -71.8884811
	locLatitude = -1.53159034
	locLongitude = -71.9243011
	outerMarkerDist = 10000
	middleMarkerDist = 2200
	innerMarkerDist = 200
}

 

My results are these (The green and red waypoints are the gs and loc locations from the runway file):

Approaching Island ILS 27  

vNcu0TD.png

Lining up for landing; 

TjG8yG1.png

I am not experiencing any offset during the flight. 

My list of installed mods 

Spoiler 
Airplane Plus (AirplanePlus 26.5)
Antenna Helper (AntennaHelper 2:1.0.7.5)
AtmosphereAutopilot (Fly-By-Wire) (AtmosphereAutopilot v1.5.17)
Breaking Ground (BreakingGround-DLC 1.7.1)
ClickThrough Blocker (ClickThroughBlocker 1:0.1.10.17)
CommNet Antennas Info (CommNetAntennasInfo 3.0.3)
Community Resource Pack (CommunityResourcePack 1.4.2)
Contract Configurator (ContractConfigurator 1.30.5)
Craft Import & Upload (CraftImport 1:0.9.0.1)
Craft Manager (CraftManager 1.2.0)
Custom Barn Kit (CustomBarnKit 1.1.21.0)
Custom Pre Launch Checks (CustomPreLaunchChecks 1.8.1.1)
Distant Object Enhancement Continued (DistantObject v2.0.3.0)
Distant Object Enhancement Continued default config (DistantObject-default v2.0.3.0)
Environmental Visual Enhancements Redux (EnvironmentalVisualEnhancements 3:1.11.3.1)
Final Frontier (FinalFrontier 1.10.0-3485)
Firespitter Core (FirespitterCore v7.17)
Firespitter Resources config (FirespitterResourcesConfig v7.17)
Harmony 2 (Harmony2 2.0.4.0)
JNSQ (JNSQ 0.10.0)
JNSQ Ribbon Pack (JNSQ-RibbonPack 0.9.0)
JNSQ-KSRGAP  (JNSQ-KSRGAP v1.0.1)
JX2Antenna (JX2Antenna 2.0.5)
Kerbal Alarm Clock (KerbalAlarmClock v3.13.0.0)
Kerbal Konstructs (KerbalKonstructs v1.8.3.0)
Kerbalism (Kerbalism 3.14)
Kerbalism - Default Config (Kerbalism-Config-Default 3.14)
Kopernicus Expansion Continued - Common (KopernicusExpansionContinued-Common release-1.7.1-5)
Kopernicus Expansion Continued - EVA Footprints (KopernicusExpansionContinued-EVAFootprints release-1.7.1-5)
Kopernicus Planetary System Modifier (Kopernicus 2:release-1.12.1-59)
Kramax Autopilot Continued (KramaxAutopilotContinued 0.4.0.1)
Kronometer (Kronometer v1.12.0.1)
KSC Extended (KSCExtended 3.0.2)
KXAPI (KXAPI 1.2.0)
Making History (MakingHistory-DLC 1.12.1)
ModularFlightIntegrator (ModularFlightIntegrator 1.2.10.0)
Module Manager (ModuleManager 4.2.1)
NavHud (NavHudRenewed 1.4.0.5)
NavUtilities Updated (NavUtilitiesUpdated 0.8.0.5)
Omega's Stockalike Structures: No Textures Required (StockalikeStructures 0.0.12)
PlanetShine (PlanetShine 0.2.6.3)
PlanetShine - Default configuration (PlanetShine-Config-Default 0.2.6.3)
Rational Resources (RationalResources 1.19.1)
REPOSoftTech-Agencies (REPOSoftTech-Agencies V1.5.9.0)
ResearchBodies (ResearchBodies 2:V1.12.0)
scatterer (Scatterer 3:v0.0772)
Scatterer Default Config (Scatterer-config 3:v0.0772)
Scatterer Sunflare (Scatterer-sunflare 3:v0.0772)
SpaceTux Library (SpaceTuxLibrary 0.0.6.1)
Strategia (Strategia 1.8.0)
TextureReplacer (TextureReplacer v4.5.2)
Toolbar Controller (ToolbarController 1:0.1.9.6)
TrimIndicators (TrimIndicators 0.1.0.3)
Tundra's Space Center (TundraSpaceCenter 2.0.2)
VesselMover Continued (VesselMoverContinued v1.12.0)
Waypoint Manager (WaypointManager 2.8.3.1)
Zero MiniAVC (ZeroMiniAVC 1:1.1.1.1)

 

 

Link to comment
Share on other sites
Beetlecat

Beetlecat

Posted
Posted (edited)
8 hours ago, Caerfinon said:

Definitely something odd going on.  I did a test flight this morning, I'm on JNSQ 10 using the Navinstruments runway files 

  Hide contents 
Runway:NEEDS[JNSQ]
{
	custom = False
	ident = Island ILS 27
	shortID = JAO27
	hdg = 270
	body = Kerbin
	altMSL = 483.600006
	gsLatitude = -1.5315907
	gsLongitude = -71.8884811
	locLatitude = -1.53159034
	locLongitude = -71.9243011
	outerMarkerDist = 10000
	middleMarkerDist = 2200
	innerMarkerDist = 200
}

 

My results are these (The green and red waypoints are the gs and loc locations from the runway file):

Approaching Island ILS 27  

vNcu0TD.png

Lining up for landing; 

TjG8yG1.png

I am not experiencing any offset during the flight. 

My list of installed mods 

  Hide contents 
Airplane Plus (AirplanePlus 26.5)
Antenna Helper (AntennaHelper 2:1.0.7.5)
AtmosphereAutopilot (Fly-By-Wire) (AtmosphereAutopilot v1.5.17)
Breaking Ground (BreakingGround-DLC 1.7.1)
ClickThrough Blocker (ClickThroughBlocker 1:0.1.10.17)
CommNet Antennas Info (CommNetAntennasInfo 3.0.3)
Community Resource Pack (CommunityResourcePack 1.4.2)
Contract Configurator (ContractConfigurator 1.30.5)
Craft Import & Upload (CraftImport 1:0.9.0.1)
Craft Manager (CraftManager 1.2.0)
Custom Barn Kit (CustomBarnKit 1.1.21.0)
Custom Pre Launch Checks (CustomPreLaunchChecks 1.8.1.1)
Distant Object Enhancement Continued (DistantObject v2.0.3.0)
Distant Object Enhancement Continued default config (DistantObject-default v2.0.3.0)
Environmental Visual Enhancements Redux (EnvironmentalVisualEnhancements 3:1.11.3.1)
Final Frontier (FinalFrontier 1.10.0-3485)
Firespitter Core (FirespitterCore v7.17)
Firespitter Resources config (FirespitterResourcesConfig v7.17)
Harmony 2 (Harmony2 2.0.4.0)
JNSQ (JNSQ 0.10.0)
JNSQ Ribbon Pack (JNSQ-RibbonPack 0.9.0)
JNSQ-KSRGAP  (JNSQ-KSRGAP v1.0.1)
JX2Antenna (JX2Antenna 2.0.5)
Kerbal Alarm Clock (KerbalAlarmClock v3.13.0.0)
Kerbal Konstructs (KerbalKonstructs v1.8.3.0)
Kerbalism (Kerbalism 3.14)
Kerbalism - Default Config (Kerbalism-Config-Default 3.14)
Kopernicus Expansion Continued - Common (KopernicusExpansionContinued-Common release-1.7.1-5)
Kopernicus Expansion Continued - EVA Footprints (KopernicusExpansionContinued-EVAFootprints release-1.7.1-5)
Kopernicus Planetary System Modifier (Kopernicus 2:release-1.12.1-59)
Kramax Autopilot Continued (KramaxAutopilotContinued 0.4.0.1)
Kronometer (Kronometer v1.12.0.1)
KSC Extended (KSCExtended 3.0.2)
KXAPI (KXAPI 1.2.0)
Making History (MakingHistory-DLC 1.12.1)
ModularFlightIntegrator (ModularFlightIntegrator 1.2.10.0)
Module Manager (ModuleManager 4.2.1)
NavHud (NavHudRenewed 1.4.0.5)
NavUtilities Updated (NavUtilitiesUpdated 0.8.0.5)
Omega's Stockalike Structures: No Textures Required (StockalikeStructures 0.0.12)
PlanetShine (PlanetShine 0.2.6.3)
PlanetShine - Default configuration (PlanetShine-Config-Default 0.2.6.3)
Rational Resources (RationalResources 1.19.1)
REPOSoftTech-Agencies (REPOSoftTech-Agencies V1.5.9.0)
ResearchBodies (ResearchBodies 2:V1.12.0)
scatterer (Scatterer 3:v0.0772)
Scatterer Default Config (Scatterer-config 3:v0.0772)
Scatterer Sunflare (Scatterer-sunflare 3:v0.0772)
SpaceTux Library (SpaceTuxLibrary 0.0.6.1)
Strategia (Strategia 1.8.0)
TextureReplacer (TextureReplacer v4.5.2)
Toolbar Controller (ToolbarController 1:0.1.9.6)
TrimIndicators (TrimIndicators 0.1.0.3)
Tundra's Space Center (TundraSpaceCenter 2.0.2)
VesselMover Continued (VesselMoverContinued v1.12.0)
Waypoint Manager (WaypointManager 2.8.3.1)
Zero MiniAVC (ZeroMiniAVC 1:1.1.1.1)

 

 

Nice. Thanks for helping me do some SCIENCE here -- I've not done a great deal of flying around yet, so it remains to be seen if I somehow have a mis-aligned JNSQ Kerbin. The KSC values seem spot-on, so it's not just a simple global shift.

I didn't think to drop waypoint markers at the actual marker locations like you illustrated, so I'll do that next to better visualize what's going on. 

 

[Edit/Update/Etc.]
So I'm not at all sure what was happening, but I'm not going to rule out pilot error. Plopping down the lat/lon markers show them lined up exactly centerline on the runway.  Manually adjusting the #s to match the 90 approach, even made me come in slightly *south* of intended.

It's entirely possible that the tighter tolerance of the short runway (plus lack of visual distance as with the KSC runway) makes it easier to drift off of center.

Doesn't seem like NavUtils is doing this to me! :D

Edited by Beetlecat
Link to comment
Share on other sites
Galland1998

Galland1998

Posted
Posted

I am running into an issue with this mod where when I make a custom runway/approach it will work just fine for that entire session.  All the saved runways will always show.  However, when close out KSP and come back in the "custom runways" no longer load and I have to create them all over again.  What is odd is that the file created by the mod with the custom runway info is in the mod folder but it does not load.   The custom file is titled "customRunways.cfg".  I looked in the settings.cfg file and it had a line that says "loadCustom_rwyCFG = True"  

I am running KSP 1.10.1 with an RSS/RP-1 install. 

 

I even tried putting the custom runway data in the defaultRunways.cfg file and that didn't do anything.  

Is the problem due to running in 1.10.1 or is  there somthing else going on.

Link to comment
Share on other sites
  • 2 months later...
610yesnolovely

610yesnolovely

Posted
Posted (edited)

Love this mod. Makes flying/landing so much easier. Just installing 1.12.3 again (using CKAN), and this is a must have mod.

Couple of minor bug fixes for @linuxgurugamer which may cause NavUtils to not load or warn, if you're not paying close attention (downside of CKAN):

  • netkan / CKAN is missing depends:
    • Click Through Blocker
    • ToolbarController
    • SpaceTuxLibrary
  • The NavInstruments.version file might need a KSP_VERSION_MAX with 1.12.99
Spoiler 
{
  "NAME": "NavInstrumentsContinued",
  "URL": "http://ksp.spacetux.net/avc/NavInstruments",
  "DOWNLOAD": "https://github.com/linuxgurugamer/NavInstruments/releases",
  "CHANGE_LOG": "https://raw.githubusercontent.com/linuxgurugamer/NavInstruments/master/CHANGE_LOG.md",
  "CHANGE_LOG_URL": "https://raw.githubusercontent.com/linuxgurugamer/NavInstruments/master/CHANGES.md",
  "VERSION": {
    "MAJOR": 0,
    "MINOR": 8,
    "PATCH": 0,
    "BUILD": 5
  },
  "KSP_VERSION": {
    "MAJOR": 1,
    "MINOR": 12,
    "PATCH": 2
  },
  "KSP_VERSION_MIN": {
    "MAJOR": 1,
    "MINOR": 12,
    "PATCH": 0
  },
  "KSP_VERSION_MAX": {
    "MAJOR": 1,
    "MINOR": 12,
    "PATCH": 99
  }
}

 

 

Edited by 610yesnolovely
Link to comment
Share on other sites
linuxgurugamer

linuxgurugamer

Posted
  • Author
Posted
4 hours ago, 610yesnolovely said:

Love this mod. Makes flying/landing so much easier. Just installing 1.12.3 again (using CKAN), and this is a must have mod.

Couple of minor bug fixes for @linuxgurugamer which may cause NavUtils to not load or warn, if you're not paying close attention (downside of CKAN):

  • netkan / CKAN is missing depends:
    • Click Through Blocker
    • ToolbarController
    • SpaceTuxLibrary
  • The NavInstruments.version file might need a KSP_VERSION_MAX with 1.12.99
  Reveal hidden contents 
{
  "NAME": "NavInstrumentsContinued",
  "URL": "http://ksp.spacetux.net/avc/NavInstruments",
  "DOWNLOAD": "https://github.com/linuxgurugamer/NavInstruments/releases",
  "CHANGE_LOG": "https://raw.githubusercontent.com/linuxgurugamer/NavInstruments/master/CHANGE_LOG.md",
  "CHANGE_LOG_URL": "https://raw.githubusercontent.com/linuxgurugamer/NavInstruments/master/CHANGES.md",
  "VERSION": {
    "MAJOR": 0,
    "MINOR": 8,
    "PATCH": 0,
    "BUILD": 5
  },
  "KSP_VERSION": {
    "MAJOR": 1,
    "MINOR": 12,
    "PATCH": 2
  },
  "KSP_VERSION_MIN": {
    "MAJOR": 1,
    "MINOR": 12,
    "PATCH": 0
  },
  "KSP_VERSION_MAX": {
    "MAJOR": 1,
    "MINOR": 12,
    "PATCH": 99
  }
}

 

 

I've  updated CKAN, thanks.  These issues are usually caught fairly early, unusual for it to be missed this log.

Version file does NOT need to be updated, I did tell Spacedock that it was compatible with 1.12.3

Link to comment
Share on other sites
  • 2 months later...
610yesnolovely

610yesnolovely

Posted
Posted (edited)

I did a forum search but I don't think anyone has done a KSRSS (possibly RSS might be good enough) configuration?

From what I can tell from @Caerfinon's totally outrageous detailed KSR Gap configs (and Flight Plans for KK) the best technique is to use the in-game Create Runway and derive MM scripts from that. Possibly setting waypoints via Waypoint Manager to help debug?

Edited by 610yesnolovely
Link to comment
Share on other sites
Caerfinon

Caerfinon

Posted
Posted
6 hours ago, 610yesnolovely said:

to use the in-game Create Runway and derive MM scripts from that

Visiting each  site and using the tool to grab the coordinates from the end of the runway worked well. But always copy the results from the custom runway file and put it into your own file in a separate directory. This does the trick. 

(for KK Flight Plans, I had to use python script to create the approaches to each runway, and then test fly them all to ensure the glideslope didn't fly into a hill or something).

Link to comment
Share on other sites
610yesnolovely

610yesnolovely

Posted
Posted (edited)
1 hour ago, Caerfinon said:

Visiting each  site and using the tool to grab the coordinates from the end of the runway worked well. But always copy the results from the custom runway file and put it into your own file in a separate directory. This does the trick. 

(for KK Flight Plans, I had to use python script to create the approaches to each runway, and then test fly them all to ensure the glideslope didn't fly into a hill or something).

Yup, (un)fortunately KSRSS only has the GSC (in Korou, Guiana, S America) and TSC (Vandenberg). I did as you say, copy-pasta from the customRunways.cfg, after making it in game (using HyperEdit and VesselMover to put the plane at either end), into my own MM patch. My assumption is the location you put the plane at is the centre of the threshold markings (end of runway). Works great.

I saw unfortunately because I _really_ miss GAP, Kerbinside GAP, and all the airports. I found 600 airports for RSS but it's no match for your work. Hint. Hint. KSRSS GAP. :P

Here's the MM patch, anyone can use, no rights reserved, free for all, etc.

Spoiler

// -*- conf-javaprop -*-
// Navigation Utilities support for KSRSS

//-------------------------------------------------------------------
// fr_kourou (GSC - Guinana Space Centre)

Runway:NEEDS[KSRSS]
{
    custom = False
    ident = GSC 09
    shortID = GSC09
    identOfOpposite = GSC 27
    hdg = 90
    body = Earth
    altMSL = 109.0
    gsLatitude = 4.96888971
    gsLongitude = -52.9183769
    locLatitude = 4.96888876
    locLongitude = -52.8800354
    outerMarkerDist = 10000
    middleMarkerDist = 2200
    innerMarkerDist = 200
}
Runway:NEEDS[KSRSS]
{
    custom = False
    ident = GSC 27
    shortID = GSC27
    identOfOpposite = GSC 09
    hdg = 270
    body = Earth
    altMSL = 109.0
    gsLatitude = 4.96906567
    gsLongitude = -52.8246803
    locLatitude = 4.96906471
    locLongitude = -52.8630219
    outerMarkerDist = 10000
    middleMarkerDist = 2200
    innerMarkerDist = 200
}

//--------------------------------------------------------------------------------
// Vandenberg (TSC) - Kerbal Konstructs
// 
Runway:NEEDS[KSRSS]
{
    custom = False
    ident = TSC 09
    shortID = TSC09
    identOfOpposite = TSC 27
    hdg = 90
    body = Earth
    altMSL = 764.0
    gsLatitude = 34.4581757
    gsLongitude = -119.500839
    locLatitude = 34.4580917
    locLongitude = -119.454514
    outerMarkerDist = 10000
    middleMarkerDist = 2200
    innerMarkerDist = 200
}

Runway:NEEDS[KSRSS]
{
    custom = False
    ident = TSC 27
    shortID = TSC27
    identOfOpposite = TSC 09
    hdg = 270
    body = Earth
    altMSL = 764.0
    gsLatitude = 34.4581833
    gsLongitude = -119.399033
    locLatitude = 34.4582863
    locLongitude = -119.445358
    outerMarkerDist = 10000
    middleMarkerDist = 2200
    innerMarkerDist = 200
}
 

 

Edited by 610yesnolovely
Link to comment
Share on other sites
Galland1998

Galland1998

Posted
Posted

I was working on doing a config to support the RSS-CanaveralHD mod that is used in RSS/RO builds.  In the config files there is a config for "ident" and "shortID" what are the two used for?  If you build a custom approach the name you give it shows up in the "ident" tag but defaults the shortID tag to "sID4"  

What should be info should be in the two slots?

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...