anything
AirNav RadarBox
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


Author Topic: Error 359  (Read 11264 times)

0 Members and 1 Guest are viewing this topic.

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Error 359
« on: March 16, 2016, 04:27:14 PM »
Hi

I am at my wits end. All of a sudden I am getting a "List index is out of bounds (359)" on Radarbox

I have changed nothing on the settings, maps, logos, etc for over a year so it is not due to a change.

With the help of support I have reinstalled, killed files, etc but to no avail.

I have done some experimenting and have found that the error does not come up if I delete the map file so no map is loaded on startup. If I subsequently load any map (even the default) the error comes back.

The only thing I can now think of is a graphics problem. Any other ideas?


Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 34071
Re: Error 359
« Reply #1 on: March 16, 2016, 04:56:20 PM »
The only thing  I can think of is that it may be a corrupt mylog or database causing the problem

Alan

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Error 359
« Reply #2 on: March 16, 2016, 06:46:07 PM »
Will try with fresh data files

Not much help from Support :(

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 34071
Re: Error 359
« Reply #3 on: March 16, 2016, 07:10:44 PM »
Probably not come across it before

Alan

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Error 359
« Reply #4 on: March 16, 2016, 07:47:15 PM »
Thanks Alan. I did a clean install. Then I copied all my maps across. Still worked. Then I copied all the old data subdirectories across. Still no problems.

Then I copied MyLog and NavData across. Still worked. No need for the other files. Nothing critical resided in them.

After all this I have a vague memory that the L020.dat can get corrupted and cause issues. Wonder if it was this one.

Anyway - all working now. Thank you

Does anyone know which file contains my colour preferences for the lines on the maps. I had these all looking good now I have state borders in blinding white. Not too serious. I can sort that out.,

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Error 359
« Reply #5 on: March 16, 2016, 07:47:42 PM »
Also would like my old polar diagram back. It is also in one of those files.
« Last Edit: March 16, 2016, 07:51:00 PM by Chris11 »

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 34071
Re: Error 359
« Reply #6 on: March 16, 2016, 07:57:00 PM »
Cant help with those Chris, sorry

Alan

neroon79

  • Hero Member
  • *****
  • Posts: 4657
Re: Error 359
« Reply #7 on: March 16, 2016, 08:11:19 PM »
The Polar Diagram  is in file D012.dat.

Ingo
Greetings from northern Germany, Ingo
11.75nm ESE of EDDV

SW: ANRB v5.00.072/6.01.001 on WIN10 64Bit Pro&Home
HW:
Ant.: DPD Productions ADS-B Vertical Outdoor Base Antenna
AMP: Kuhne electr. KU LNA 1090 A TM
Cable: 25m of ECOFLEX 15+
NB: Asus P53E 24/7 op.
PC: 28"4K + 24" Monitor
AirSpy mini @RPi3

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Error 359
« Reply #8 on: March 16, 2016, 08:27:41 PM »
Thanks neroon79

It would be useful if we had a list of the files with details of the file contents

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Error 359
« Reply #9 on: March 16, 2016, 08:32:58 PM »
Well that solves the issue. Copied the old CD012.dat and boom. Back came the error.

I have just deleted it and the system created one on startup. A nice clean new one. No errors

neroon79

  • Hero Member
  • *****
  • Posts: 4657
Re: Error 359
« Reply #10 on: March 16, 2016, 08:38:58 PM »
You can try to manually fix the polar diagramm file by using a text editor.

It shall consist of 360 lines with values that state the maximum reception range in the particular direction.

e.g. line 90 states the maximum reception range in direction 090° (East).

Ingo

Content of D012.dat:

29
29
25
35
189
190
191
192
192
193
32
196
202
204
205
184
182
183
184
205
32
28
188
24
31
27
24
31
27
25
26
26
22
23
26
25
25
26
27
23
23
22
25
26
30
35
33
26
27
28
31
21
21
22
19
28
18
25
26
25
24
23
25
22
25
24
27
32
30
34
31
29
37
37
43
42
41
41
48
31
32
35
40
40
51
41
39
39
33
38
26
38
35
35
41
40
27
29
25
27
32
35
36
36
43
40
42
46
46
48
48
49
45
41
28
30
32
28
29
28
34
25
23
31
22
30
26
22
26
24
19
21
18
18
28
24
19
20
19
17
20
20
20
19
22
21
21
18
20
19
16
20
22
19
16
21
19
17
16
19
18
17
14
15
19
14
14
16
22
15
16
17
14
17
13
20
17
17
16
20
20
21
24
17
26
21
22
19
20
26
27
26
26
23
22
29
23
24
21
20
21
24
19
19
26
19
20
14
20
14
19
21
20
19
20
16
19
18
20
23
22
21
21
19
16
19
17
17
18
18
21
15
19
22
21
23
29
22
23
23
17
18
16
20
20
17
29
23
22
26
34
29
30
32
35
39
24
33
29
47
43
34
36
36
32
34
34
38
40
38
38
36
33
26
36
25
33
30
29
23
43
38
37
31
33
35
34
43
50
37
38
41
42
34
35
32
35
39
33
38
35
31
35
35
35
33
31
33
34
36
31
32
30
34
34
34
26
23
25
27
28
31
27
28
26
30
25
30
26
25
24
29
25
24
28
26
25
25
31
36
33
33
30
30
32
29
34
35
35
36
21
30
31
30
28
26
29
29
31
35
Greetings from northern Germany, Ingo
11.75nm ESE of EDDV

SW: ANRB v5.00.072/6.01.001 on WIN10 64Bit Pro&Home
HW:
Ant.: DPD Productions ADS-B Vertical Outdoor Base Antenna
AMP: Kuhne electr. KU LNA 1090 A TM
Cable: 25m of ECOFLEX 15+
NB: Asus P53E 24/7 op.
PC: 28"4K + 24" Monitor
AirSpy mini @RPi3

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Error 359
« Reply #11 on: March 17, 2016, 06:28:51 AM »
Thanks again