RAF Kinloss

[DaleRFU]

am so sorry nick but i downloaded the programme that you said ExcBuilderv2 and i have just tryed it and it works

Thanks anyway Nick was much apeciated

[kungfuman]

Not to worry about the ADE requirements, perhaps one for the future?

I took the liberty of downloading your afcad to take a peek, as I made one myself about a year ago (its on avsim with my Nimrod flightplans). Nice work! It will be even better with the scenery you're making.

May I offer some minor feedback - take it or leave it - about your Comms channels?

There is a bug in FS whereby you can be happily flying along in the UK, then suddenly ATC will hand you over to some distant Approach control on the other side of the country. The controller will be associated with a military airfield, and the frequency will always be 123.3 MHz.

The problem is caused by the fact that Microsoft incorrectly assigned this frequency (123.3) as the primary Approach Control channel for most UK and many Northern European military airfields. All these Approach controllers on the same frequency in the same area seems to scramble the FS ATC "engine".

I have found that the solution is to delete or appropriately modify these offending channels wherever you find them.

With this in mind, I suggest that you go to the Comms list for your Kinloss afcad, and modify the Arrival entry for "LOSSIE" by changing the frequency from 123.3 to 119.35. While you're at it, you may as well delete the "Kinloss Talkdown" channel, as FS will only use one Arrival channel per AFD file. Additionally, you may also want to open your Lossiemouth afcad and again go to the Comms list. Delete the Arrival channel with the 123.3 frequency. You will see that there is already another Arrival channel listed (with freq of 119.35), which will now become the "active" Approach channel for this afcad as well. The end result should be that you will now have both Kinloss and Lossie under the same Approach Control facility (which I believe is the real world situation), while at the same time making your first steps toward eliminating the Microsoft bug.

HTH,

Dan

[DaleRFU]

Thanks for the info about the frequencies. i will try change them.

any feedback would be great

[kungfuman]

The only other things I would say are pretty minor points really:

1.
Your hold-short nodes are unrealistically close to the runway. This means that when your AI are waiting to take-off while another aircraft is on approach, the seperation between the arriving and departing aircraft will be unrealistically close. It can look a bit disconcerting, especially if you are used to seeing real aircraft ops in action. In less developed parts of the world, sometimes this might be realistic, but generally speaking hold-shorts are placed much further from the runway in the real world than in most default FS airports.

However, there is a limit in FS as to how far away from the runway you can place these hold-short nodes. Press "h" on your keyboard to display the hold-short limiting circles. These circles must must touch/cross the edges of the runway. So if this is something you want to address in your afcad, I suggest that you move your hold-short nodes further away from the runway, but make sure the circles still intersect the edge of the runway - so don't move them too far away.

A tip of mine would be to create new nodes instead of moving the current ones. Then, delete the current ones and re-draw the taxiways. This will help prevent odd graphics due to poorly aligned taxiway links, which are sometimes the result of having dragged a node that was part of a straight line section of twy links. But each to their own

2.
You have one or two twy links set to "closed". Unfortunately, this won't stop aircraft from using these links. I have attached my old file to show you how I overcame that problem - and it results in a better look.

AF2_EGQK_DF.bgl

(18.7 KiB) Downloaded 26 times

Check out the point where the two disused runways cross, north of Rwy 26-08. Your afcad definitely looks better overall, but mine still has the odd good point

3.
Naming of parking positions and orientation of parking spots: I understand that the parking stand numbers and orientation of the parking to the South of runway 26-08 in my afcad are correct, so you may want to check your numbers again. I don't know why I marked mine as "Gate", and I don't suggest that you do this either! Strange....

The radius of your Nimrod parking spots seems rather small. These stands are large enough to park visiting VC10s, so you may want to enable this behaviour in your afcad too. I would suggest a radius of at least 31m or more. Appropriate coding of these spots will keep them free of any unwanted visiting aircraft.

4.
This is probably even less important than my other two points, but what the hell...
It might be safer if you close the two disused runways in your afcad file. Currently, they are selectable for both landing and take-off. You need to tick the relevant boxes in their properties menus.

HTH,

Dan

[DaleRFU]

thanks for the info Dan, i never knew about the holdshort node radius so i will sort that out.

as for the other runways i havn't even looked at them yet but i will do.

thanks for the feedback

[kungfuman]

Sorry, I edited my post while you where replying. There are a couple of other points now

Nothing bad, and hopefully it all helps...

[jimrodger]

Just one point to note.

Kinloss main runway is now designated as 25/07.

Flypast just about to take place


Jim

[DaleRFU]

Am sorry dan but i couldn't find the edits you made?

Also with the scenery i am placing so oil rigs for the ai nimrods to fly 2.

[DaleRFU]

here are so pics so far

http://i799.photobucket.com/albums/yy27 ... tled-8.jpg
http://i799.photobucket.com/albums/yy27 ... led3-4.jpg
http://i799.photobucket.com/albums/yy27 ... led4-5.jpg
http://i799.photobucket.com/albums/yy27 ... led1-4.jpg

[kungfuman]

Just one point to note.

Kinloss main runway is now designated as 25/07.

Flypast just about to take place


Jim

Cheers for the info


Looking good, Dale.

You can go ahead and change the Runway designation numbers, as Kinloss doesn't have any approach procedures coded into the FS stock, so it won't cause any problems there. But When you've finished the afcad, you might want to write an ILS approach for it, so that ATC will clear you for an ILS approach when rwy 25 is in use.

However, to do this, you would need ADE9, or someone willing to add this to your file for you.

[Firebird]

Not bad at all.

[DaleRFU]

with regards to the runway, i wont be changing them because if i change the heading of the runway it wont align with the taxiways and buildings. and i dont really want to delete all the buildings and then place them again. so plainly for that reason i wont change it. Sorry.

I will start on the north side of the airfeild tomorrow and see were i end up.

thanks for the feedback guys

[DaleRFU]

with regards to the runway, i wont be changing them because if i change the heading of the runway it wont align with the taxiways and buildings. and i dont really want to delete all the buildings and then place them again. so plainly for that reason i wont change it. Sorry.

I will start on the north side of the airfeild tomorrow and see were i end up.

thanks for the feedback guys

[kungfuman]

Ah, its not the runway heading that has changed. Everything remains in exactly the same position and direction.

It is just the runway name that has changed.

If you wanted to do this with your afcad, you would just open the runway properties menu, and change the "designation". Then select all of the black runway links, and select the new runway name from the drop-down box that sets taxiway designation letters.

Of course, its totally up to you

HTH,

Dan

[DaleRFU]

oh rite, i must have miss understood. i will change it later.

[Firebird]

Yes its all part of the countdown to the next Ice Age. Mike will really moan about the weather in Ohio then.

[bigtam121]

Loaded Kinloss scenery into FS2004 but none of the buildings showing up.

Any advice please.

Thanks

Tom

[Firebird]

Well, in the readme it says that credit for the buildings goes to MAIW. As you have found that there are no libs included which means that you already must have the MAIW libs that have been supplied with various packages, especially the UK ones.

Also by the nature of things the libs MUST be in a folder that is lower down the scenery list, in FS9, than the Kinloss scenery. If not it won't show up.

There could be another reason. If you have any exclude files for EGQK that are in a folder higher up the list than the scenery then they will wipe out the buildings. These should be removed to a safe location.

Does any of this help?