OCC Display

[Harley Glossop 1111828]

Havnt been able to find any information about this plugin, but what does it actually do? and how do i get it to display in euroscope?

[Todor Atanasov 878664]

Yes the info is still missing, will be added very soon. It is a gate management plug-in. You can use it by loading the plugin. After that build empty file using NOTEPAD and call it _occ.asr and fill this in it (change the data according to your needs)

DisplayTypeName:OCC View
DisplayTypeNeedRadarContent:0
DisplayTypeGeoReferenced:0

PLUGIN:OCC view:AIRPORT:LHBP
PLUGIN:OCC view:FINAL:2
PLUGIN:OCC view:LINES:27
PLUGIN:OCC view:TOPEMPTY:120
PLUGIN:OCC view:BOTTOMEMPTY:60
PLUGIN:OCC view:LEFTEMPTY:60
PLUGIN:OCC view:RIGHTEMPTY:120
PLUGIN:OCC view:SEPARATOR1:9
PLUGIN:OCC view:SEPARATOR2:18
PLUGIN:OCC view:SEPARATOR3:27

PLUGIN:OCC view:STAND1:1:S1:0:0:N047.26.37.942:E019.13.26.950
PLUGIN:OCC view:STAND2:2:S2:0:1:N047.26.35.502:E019.13.28.581
PLUGIN:OCC view:STAND3:3:S3:0:2:N047.26.32.773:E019.13.30.298

You have to define every stand with coordinates from your scenery (be advice that if some pilot is not using your scenery they may not show on the plugin, as they stand position can be different).

 

You can move the plane via mouse or can use the following commands:

.occ arr
.occ dep
.occ free
.occ push
gate left
gate right
gate top
gate bottom

 

I'll try to explain it better in the wiki

[Andreas Fuchs]

So, "OCC" stands for? Operations Control Centre?

[Gergely Csernak]

Affirmative Andreas.

[Andreas Fuchs]

Thanks a lot I could have peaked at this at the BETA-forum, too, but thought it might an interesting piece of information for the guys and girls here at this forum.

[David Saunders 818672]

I tried this for heathrow, but didnt find it accurate enough, so aircraft were shwoing up on different stands, small screenshot

 

[Stephan Boerner 945550]

You always have to keep in mind that you create this to match one scenery, and one scenery only. I don't know how if the stand positions in aerosoft EGLL and uk2000 EGLL match, but you will always have standard scenery aircraft that won't match anything. I created some definitions for EDDF and EGLL several months ago, but never finished them. I figured that as soon as the pilot used the correct scenery, the stand detection worked very well. But you will never come across the problem of different sceneries.

[Sascha Fruehwirth 1051824]

You can move the plane via mouse or can use the following commands:

.occ arr
.occ dep
.occ free
.occ push
gate left
gate right
gate top
gate bottom

 

I think thats not correct, it should be:

.occarr <gatenumber> <callsign>
.occdep <gatenumber> <callsign>
.occfree <gatenumber>
.occfree <callsign>
.occpush <callsign> 
.occgate <gatenumber> <callsign>
.occleft <spaceleft>
.occright <spaceright>
.occtop <spacetop>
.occbottom <spacebottom>

[Todor Atanasov 878664]

Well I'm writing what it says in the code of the plug-in, but I haven't looked at the release one.

[Gergely Csernak]

Sascha is right. All commands need the .occ prefix.

[Felix Musselmann]

I have a question. What can i do if i have an aircraft on the ground, but it isn't shown in the OCC.asr? Can i add it manually?

[Gergely Csernak]

Yes, use the .occdep command. That will allocate the gate for the specific AC. May be it will not realize that the AC has departed from the gate. We originally used it in one of Budapest Overloads to allocate the gates prior connecting.

[Felix Musselmann]

I did a file for EDDM. But there aren't any aircrafts although there are 3 on the ground. I add the file to this post, would you have a look please? I don't know what i did wrong.

thanks

Felix

 

DisplayTypeName:OCC View
DisplayTypeNeedRadarContent:0
DisplayTypeGeoReferenced:0

PLUGIN:OCC view:AIRPORT:EDDM
PLUGIN:OCC view:FINAL:2
PLUGIN:OCC view:LINES:58
PLUGIN:OCC view:TOPEMPTY:30
PLUGIN:OCC view:BOTTOMEMPTY:60
PLUGIN:OCC view:LEFTEMPTY:60
PLUGIN:OCC view:RIGHTEMPTY:120
PLUGIN:OCC view:SEPARATOR1:15
PLUGIN:OCC view:SEPARATOR2:19
PLUGIN:OCC view:SEPARATOR3:30


PLUGIN:OCC view:STAND1:101:101*:0:0:N048.21.29.628:E011.46.58.241
PLUGIN:OCC view:STAND2:102:102:0:1:N048.21.27.524:E011.46.58.575
PLUGIN:OCC view:STAND3:103:103:0:2:N048.21.25.418:E011.46.58.901
PLUGIN:OCC view:STAND4:104:104:0:3:N048.21.23.313:E011.46.59.237
PLUGIN:OCC view:STAND5:107B:107B*:0:4:N048.21.19.101:E011.46.59.904
PLUGIN:OCC view:STAND6:108:108:0:5:N048.21.16.996:E011.47.00.239
PLUGIN:OCC view:STAND7:109B:109B:0:6:N048.21.14.890:E011.47.00.573
PLUGIN:OCC view:STAND8:110:110*:0:7:N048.21.12.785:E011.47.00.894
PLUGIN:OCC view:STAND9:111B:111B:0:8:N048.21.10.743:E011.47.01.223
PLUGIN:OCC view:STAND10:112:112:0:9:N048.21.08.669:E011.47.01.547
PLUGIN:OCC view:STAND11:115B:115B:0:10:N048.21.04.425:E011.47.02.220
PLUGIN:OCC view:STAND12:116:116:0:11:N048.21.02.353:E011.47.02.560
PLUGIN:OCC view:STAND13:117A:117A:0:12:N048.21.00.280:E011.47.02.873
PLUGIN:OCC view:STAND14:118:118:0:13:N048.20.58.206:E011.47.03.214
PLUGIN:OCC view:STAND15:119:119*:0:14:N048.20.55.875:E011.47.03.614
PLUGIN:OCC view:STAND16:131:131:0:15:N048.21.14.437:E011.46.49.362
PLUGIN:OCC view:STAND17:132:132*:0:16:N048.21.12.590:E011.46.49.669
PLUGIN:OCC view:STAND18:133:133:0:17:N048.21.10.840:E011.46.49.961
PLUGIN:OCC view:STAND19:134:134:0:18:N048.21.09.026:E011.46.50.253
PLUGIN:OCC view:STAND20:141:141:0:19:N048.21.24.641:E011.46.44.758
PLUGIN:OCC view:STAND21:142:142:0:20:N048.21.22.534:E011.46.45.109
PLUGIN:OCC view:STAND22:143:143*:0:21:N048.21.20.397:E011.46.45.454
PLUGIN:OCC view:STAND23:151:151*:0:22:N048.21.14.241:E011.46.46.485
PLUGIN:OCC view:STAND24:152:152:0:23:N048.21.12.396:E011.46.46.793
PLUGIN:OCC view:STAND25:153:153*:0:24:N048.21.10.646:E011.46.47.080
PLUGIN:OCC view:STAND26:154:154:0:25:N048.21.08.832:E011.46.47.383
PLUGIN:OCC view:STAND27:161:161:0:26:N048.21.02.840:E011.46.48.392
PLUGIN:OCC view:STAND28:162:162*:0:27:N048.21.00.733:E011.46.48.736
PLUGIN:OCC view:STAND29:163:163:0:28:N048.20.58.563:E011.46.49.100
PLUGIN:OCC view:STAND30:201:201:1:0:N048.21.31.994:E011.47.30.673
PLUGIN:OCC view:STAND31:202:202:1:1:N048.21.30.471:E011.47.30.925
PLUGIN:OCC view:STAND32:203:203*:1:2:N048.21.28.560:E011.47.31.219
PLUGIN:OCC view:STAND33:204:204:1:3:N048.21.26.713:E011.47.31.518
PLUGIN:OCC view:STAND34:205:205:1:4:N048.21.25.256:E011.47.31.745
PLUGIN:OCC view:STAND35:206:206:1:5:N048.21.23.603:E011.47.32.003
PLUGIN:OCC view:STAND36:207:207*:1:6:N048.21.21.952:E011.47.32.261
PLUGIN:OCC view:STAND37:208:208:1:7:N048.21.20.073:E011.47.32.562
PLUGIN:OCC view:STAND38:209:209:1:8:N048.21.18.389:E011.47.32.825
PLUGIN:OCC view:STAND39:210:210:1:9:N048.21.16.509:E011.47.33.132
PLUGIN:OCC view:STAND40:211:211*:1:10:N048.21.14.889:E011.47.33.380
PLUGIN:OCC view:STAND41:215:215:1:11:N048.21.12.558:E011.47.33.760
PLUGIN:OCC view:STAND42:216:216*:1:12:N048.21.10.872:E011.47.34.014
PLUGIN:OCC view:STAND43:217:217:1:13:N048.21.09.058:E011.47.34.307
PLUGIN:OCC view:STAND44:218:218*:1:14:N048.21.07.730:E011.47.34.518
PLUGIN:OCC view:STAND45:219:219:1:15:N048.21.06.241:E011.47.34.751
PLUGIN:OCC view:STAND46:220:220:1:16:N048.21.04.296:E011.47.35.061
PLUGIN:OCC view:STAND47:221:221:1:17:N048.21.02.482:E011.47.35.354
PLUGIN:OCC view:STAND48:222:222*:1:18:N048.21.00.896:E011.47.35.603
PLUGIN:OCC view:STAND49:231:231:1:19:N048.21.03.551:E011.47.30.737
PLUGIN:OCC view:STAND50:232:232:1:20:N048.21.02.190:E011.47.30.904
PLUGIN:OCC view:STAND51:233:233*:1:21:N048.21.00.605:E011.47.31.201
PLUGIN:OCC view:STAND52:243:243:1:22:N048.21.27.006:E011.47.48.897
PLUGIN:OCC view:STAND53:244:244:1:23:N048.21.25.613:E011.47.49.131
PLUGIN:OCC view:STAND54:245:245:1:24:N048.21.24.219:E011.47.49.356
PLUGIN:OCC view:STAND55:246:246:1:25:N048.21.22.470:E011.47.49.664
PLUGIN:OCC view:STAND56:247:247*:1:26:N048.21.20.883:E011.47.49.928
PLUGIN:OCC view:STAND57:248:248:1:27:N048.21.19.263:E011.47.50.193
PLUGIN:OCC view:STAND58:249:249:1:28:N048.21.17.675:E011.47.50.456
PLUGIN:OCC view:STAND59:250:250*:1:29:N048.21.16.121:E011.47.50.706
PLUGIN:OCC view:STAND60:251:251*:1:30:N048.21.14.534:E011.47.50.977
PLUGIN:OCC view:STAND61:252:252:1:31:N048.21.12.979:E011.47.51.229
PLUGIN:OCC view:STAND62:253:253:1:32:N048.21.11.424:E011.47.51.495
PLUGIN:OCC view:STAND63:254:254:1:33:N048.21.09.998:E011.47.51.729
PLUGIN:OCC view:STAND64:255:255:1:34:N048.21.08.444:E011.47.51.986
PLUGIN:OCC view:STAND65:256:256:1:35:N048.21.06.920:E011.47.52.228
PLUGIN:OCC view:STAND66:261:261:1:36:N048.20.59.729:E011.47.51.844
PLUGIN:OCC view:STAND67:262:262:1:37:N048.20.59.956:E011.47.54.947
PLUGIN:OCC view:STAND68:263:263:1:38:N048.20.59.956:E011.47.54.947

[Gergely Csernak]

Felix,

 

The planes should be quite close (< 0.05 NM) to the point to show up automatically. Can you check if they are so close?

[David Saunders 818672]

best way i found to find the exact coords for common sceniers is to look where the aircraft is actually placed and then use the .sline command and place the cursor in the middle of the aircraft then look to see if it is similar or the same and if necessary change the lat & long to reflect the actual position according to sceneries.

[Felix Musselmann]

Thanks for the answers. I think they are not near enough. But i would add them manually, but it don't work. Here a picture how i try it. After i entered this i press enter, the text disappear, but nothing happens.

http://www.bilder-space.de/show.php?file=17.015uppZffoVgerec4.jpg

Sorry for my bad english, i am 16 years old and still learning .

Felix

[Felix Musselmann]

It seems so that the Coordinates are the problem. If i take coordinate with .sline in Munich there is no aircraft shown. But if i take one of Frankfurt the correct aircraft is shown in the OCC picture.

Felix

[Felix Musselmann]

Has nobody a idea what's wrong?

[David Saunders 818672]

Felix I have tried to create an occ but like you at the moment it is blank, but it didnt help the traffic doesnt stay on the ground connected for long enough to get coords, let me try again later and i will get back to you.

[Stephan Boerner 945550]

I am not sure what OCCs for Frankfurt are actually available for public, but all OCCs I know of are based on the actual MAF AFCAD, so if your coordinates are the problem, you should try to use the GAP AFCAD. That should create matches for all aircrafts using the scenery.

[Felix Musselmann]

I haven't one for Frankfurt. I looked where is an aircraft in Munich, used .sline and put in the coordinate at the gate, but it isn't shown. Then i looked to Frankfurt, .sline on the aircraft and changed only one Gate in the EDDM_OCC to the Frankfurt Coordinates, and then the aircraft was shown.

I hope it wrote it understandable.

Felix

[Sascha Fruehwirth 1051824]

Could you provide the OCC testfile, so we can have a look at it?

 

regards,

Sascha

[Felix Musselmann]

I posted it in this thread on page 1, post 13.

Felix

[Ben Hofer 1042467]

Hi Felix,

I just converted the degree-format of the ASR-file (N048.21.22.534:E011.46.45.109) for stand 21 to the format google accepts (048°21'22.534'',011°46'45.109'') and as you see: The indicated location is not really the place aircraft are normally placed, but on the gate itself (e.g. where the number of the stand is shown as freetext defined in the sector file).

Ensure you have taken the sufficient AFCAD or sectorfile-coordinates in the right format (degree, not "48.356259,11.779197" which would be the decimal coordinate for 21 which the sector file usually provides) and the aircraft are on their correct position.

Scenery offset often is the reason why the OCC-view does not register a plane at the expected stand.

Regards, Ben

[Felix Musselmann]

I took the coordinates out of the sectorfile, but i also try when i see a aircraft on stand 205 for example, .sline on the aircraft to get the coordinates out of Euroscope and add these coordinates. So it should be the correct coordinate.

Felix