Welcome to Radarspotting. Please login or sign up.

May 16, 2026, 01:54:35 AM

Login with username, password and session length

New Members

New Members

You should get an activation email when you join.  If not, please use the Contact option.

New Problem with adding Airport Outlines in BaseStation

Started by Davfog, January 23, 2025, 05:51:46 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Davfog

I'm visiting a few South American countries commencing next weekend (March 1st) and have downloaded the following outline files which don't appear on my chart display after I've copied them to my outlines folder.

Viracopos Campinas SBKP.out
Sao_Paulo_Congonhas_SBSP.out and I also tried
Sao Paulo Congonhas.out

I'm running my SBS-1e on a Lenovo laptop running Windows 10 64 bit operating system
Edition   Windows 10 Home
Version   22H2
Installed on   ‎15/‎03/‎2021
OS build   19045.4894
Experience   Windows Feature Experience Pack 1000.19060.1000.0

Basestation software version 1.2.4.184, firmware version SBS-1e build 402
Basestation software runs from Program Files (x86) and works fine.  I also use an add-on, Basestation Analyser from Aerodata

In Display Settings ---> Data Files, all the airport outlines I have installed start with AFB, AFM or AFP followed by an underscore and the airport name.

So, the question is, how do I get these outline files to show?

Thanks in advance.
Dave

Davfog

That should read "February 1st".  The perils of retirement!

Anmer

Have you reloaded the Outlines in BaseStation?

Settings -> Reload -> Outlines

Post back here if you still need help.
Here to Help.

Davfog

I forgot about that, so thank you.

I tried it and got this error. 


App: BaseStation
Version: 1.2.4.184

-----------------------------------------------

Occurred : 11:46:34.700 2025/01/24

Error : EAccessViolation - Access violation at address 004F83B7 in module 'BaseStation.exe'. Read of address 00000000

Last Command : UPDATE Flights SET EndTime = '2025-01-24 11:26:05.516', NumPosMsgRec = 883, NumADSBMsgRec = 2483, NumModeSMsgRec = 12071, NumIDMsgRec = 93, NumSurPosMsgRec = 0, NumAirPosMsgRec = 883, NumAirVelMsgRec = 896, NumSurAltMsgRec = 7809, NumSurIDMsgRec = 27, NumAirToAirMsgRec = 0, NumAirCallRepMsgRec = 1278, HadAlert = 0, HadEmergency = 0, HadSPI = 0, UserNotes = '', FirstIsOnGround = 0, LastIsOnGround = 0, FirstLat = 51.45489, LastLat = 50.53963, FirstLon = -2.30698, LastLon = -0.29201, FirstGroundSpeed = 452.0, LastGroundSpeed = 402.6, FirstAltitude = 16950, LastAltitude = 33025, FirstVerticalRate = 2176, LastVerticalRate = 0, FirstTrack = 90.0, LastTrack = 133.1, FirstSquawk = 6335, LastSquawk = 6335 WHERE FlightID = 5604991

Last Aircraft : 40643C

System Status : 137363456 | 0 | 137363456 | 121566708 | 2918004 | 3.7.11 | 869437042688

Previous : O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo | O-WriteToDebugMemo | I-WriteToDebugMemo

Anmer

Maybe a bad outline file?

Can we have a remote connect session so I can take a look with you?
Here to Help.

Davfog


Anmer

Here to Help.

Anmer

Just to close the thread.

The Outline file (created by Rod Bearden):

Sao_Paulo_Congonhas_SBSP.out

...was "bad".

There was an empty line.  Deleting the line was all it needed.

The corrected file has now been uploaded to the forum.
Here to Help.