I have just installed Captain Sim 757 base pack (download version) into FSX on my Windows 7 computer.

FSX has the accelleration pack installed and the captain sim installed ok but the aircraft callsigns are not read out or shown in the ATC text.

The callsigns appear in the dropdown menu when selecting an aircraft.

For example instead of ATC saying "Speed Bird 757 heavy" all i get is "757 heavy"

I know this is something with my computer as my daughters boyfriend installed it on his windows 7 computer and it all worked perfectly ok.

The usual attempts of reinstallation made no difference.

Please help

I forgot to mention, it works perfectly ok on my Vista computer but i don't want to use the Vista computer for FSX.

There are several threads in the Forum or the 767 Forum concerning callsigns and ATC. Why don't you try a search using callsign or callsigns and see what you come up with. If that does not work maybe  someone can help you.

Michael Cubine

Do you mean the 757 Base Pack or the 767 Base Pack?

Anyway. To fix it i the 767, change atc_airline= to atc_airline=Speed Bird. Like this:

[fltsim.5]
title=CS 767-300 Captain Paint5
sim=B767-300RR
model=rr5
panel=
sound=RR
texture=british
kb_checklists=
kb_reference=
atc_id=N764A
atc_airline=Speed Bird
atc_flight_number=
ui_manufacturer="Boeing"
ui_type="767-300 RR"
ui_variation="British Airways"
ui_typerole="Commercial Airliner"
ui_createdby="Captain Sim"
description="767-300 Base Pack v1.5\n(c) 2011 Captain Sim www.captainsim.com"
ui_wglts=1

Mark

It is the 757 base pack.
Also i am really sorry but i don't have a clue in how to do the fix that's shown.

philwhite100 wrote on Feb 12^th, 2012 at 1:27pm:

It is the 757 base pack. Also i am really sorry but i don't have a clue in how to do the fix that's shown.

Strange. In v4.6 of the CS757, it is already set correctly atc_airline=Speed Bird. I'll have to do a flight to test it. You edit the aircraft.cfg in the FSX\SimObjects\CS_B757-200 folder. Mine looks like this:

[fltsim.4]
title=Captain Sim 757-200 FSX 4
sim=cs757-200RR
model=RR
panel=
sound=RR
texture=ba
kb_checklists=
kb_reference=
atc_id=G-BPEC
atc_airline=Speed Bird
atc_flight_number=757
ui_manufacturer=Boeing
ui_type=757-200 RR
ui_variation=British Airways
ui_typerole="Commercial Airliner"
ui_createdby="Captain Sim"
ui_wglts=1
description="757 Captain (757-200 Base Pack) v.4.6\n(c) 2011 Captain Sim \nwww.captainsim.com"

Mark

I get exatly that shown on mine too so something must be really messed up somewhere.

I'll take a closer look at the entry. Maybe I missed something important.

This from the FSX SDK:
atc_airline The ATC system will use the specified airline name with this aircraft. This is dependant on ATC recognizing the name. ATC will treat this aircraft as an airliner when this is used in conjunction with atc_flight_number.

If you don't give it a flight number, then the Airline is not mentioned! It must have a Flight Number!

[fltsim.5]
title=CS 767-300 Captain Paint5
sim=B767-300RR
model=rr5
panel=
sound=RR
texture=british
kb_checklists=
kb_reference=
atc_id=N764A
atc_airline=
atc_flight_number=
ui_manufacturer="Boeing"
ui_type="767-300 RR"
ui_variation="British Airways"
ui_typerole="Commercial Airliner"
ui_createdby="Captain Sim"
description="767-300 Base Pack v1.5\n(c) 2011 Captain Sim www.captainsim.com"
ui_wglts=1

So the ones in red test need to be:
atc_airline=Speed Bird
atc_flight_number=767
so that the ATC will call you "Speed Bird 767" and not just "Boeing", or "Boeing 767".

The attached image shows how the ATC responded once I filled in the blanks. ;)

Mark

---

I have tried this but still nothing The whole thing is very strange. I did even totally uninstall FSX and any add ons then reinstall but it made no difference.

Okay. My previous reply was about the 767-300, this reply is for the 757-200. as you can see from the image. It is working for me once I have an atc_airline=Speed Bird and atc_flight_number=757.

Here is the entry (again).

[fltsim.4]
title=Captain Sim 757-200 FSX 4
sim=cs757-200RR
model=RR
panel=
sound=RR
texture=ba
kb_checklists=
kb_reference=
atc_id=G-BPEC
atc_airline=Speed Bird
atc_flight_number=757
ui_manufacturer=Boeing
ui_type=757-200 RR
ui_variation=British Airways
ui_typerole="Commercial Airliner"
ui_createdby="Captain Sim"
ui_wglts=1
description="757 Captain (757-200 Base Pack) v.4.6\n(c) 2011 Captain Sim \nwww.captainsim.com"

Now the interesting part. When I first load the 757-200, with Bristish Airways livery, into FSX, I have the same problem as you (ATC calls me 'Boeing 757"). If I go to Menu > Aircarft > Select Aircaft and then look at the details (Details button) for my 757-200 Bristish Airways, There is no flight number displaying (the spot is blank). Once I add 757 in there and click OK, the ATC starts calling me "Speed Bird 757". I don't know why it isn't reading the aircraft.cfg, but I am having FSX do some strange things every now and then since I last reinstalled FSX. This is one of them and I don't know why it is doing it.

Mark

---

I still can't get this to work but thanks for all your help.
On another note, i have just won an ebay auction for a brand new Saitek Pro Yoke and throttle quadrant with several add ons for just under £100 so i am well chuffed.

Something that has come to mind regarding my issues. The hard drive that it is installed on did have another operating system on it with FSX so all i did was install Windows 7 on it to overwrite the existing operating system and did not format the drive so could this be part of my problem.

thanks.

I have also installed some other third party aircraft add ons and they are also not showing the callsigns. I must have some kind of registry error.

Why not try a repair of FSX? Place the FSX DVD1 in the drive and select REPAIR when given the option. If you have Acceleration, you need to do a repair of that too. If you don't have Acceleration, you will need to reinstall both SP1 and SP2 too. This should help fix the situation.

I guess it is possible, that the error might be in the fsx.cfg, but I don't really know if there is anything in it's settings that deal with that.

Mark

OK i will try a repair and hope it works but i would have thought that when i did a fresh re install of FSX that would have sorted it but it didn't.

philwhite100 wrote on Feb 25^th, 2012 at 7:50pm:

OK i will try a repair and hope it works but i would have thought that when i did a fresh re install of FSX that would have sorted it but it didn't.

I don't see the point of doing a repair of FSX if it wasn't working after a fresh re-installation of FSX. Have you thought of deleting the fsx.cfg so that FSX creates a new one? In case the fault is in there. Or was it a completely new fsx.cfg (in other words you didn't use the old one after re-installing).

Mark

philwhite100 wrote on Feb 12^th, 2012 at 3:28pm:

I get exatly that shown on mine too so something must be really messed up somewhere.

Here is how i got around it, it may work then again maybe not. Windows 7 has FSX permission folders that need to be modified to full control. I am not sure which OP your using but on the search bar type in folders and it should take to the permissions page. WARNING! Doing this will allow you to change the aircraft.cfg. SAVE the original before doing anything.

This gets more confusing all the time. Since i was getting nowhere further i just left things alone and all of a sudden some of the callsigns are working properly with ATC text and voice showing and reading aloud the callsigns.

I am still considering installing a new hard drive in my system and installing windows 7 on it purely for FSX and it's add ons.

ottoramsaig wrote on Feb 27^th, 2012 at 9:24pm:

Here is how i got around it, it may work then again maybe not. Windows 7 has FSX permission folders that need to be modified to full control. I am not sure which OP your using but on the search bar type in folders and it should take to the permissions page. WARNING! Doing this will allow you to change the aircraft.cfg. SAVE the original before doing anything.

I've never had to do that, and I think I would remember having done it. A lot has to do with where on you system FSX is installed.


philwhite100 wrote on Feb 28^th, 2012 at 11:54pm:

This gets more confusing all the time. Since i was getting nowhere further i just left things alone and all of a sudden some of the callsigns are working properly with ATC text and voice showing and reading aloud the callsigns. I am still considering installing a new hard drive in my system and installing windows 7 on it purely for FSX and it's add ons.

When it comes to the installation of FSX when using Vista or Windows 7 (32bit and 64bit):
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X and C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X = BAD
C:\FSX = GOOD
X:\FSX = BEST (X = any drive other than the C: drive)

This has to do with the way that Vista and Win 7 secure the C: drive. Especially Program Files and Program Files (x86).
With Vista and Windows 7, it is recommended that you DO NOT install FSX in its default location because of the restrictions by those Operating Systems.

If you have FSX installed in the default location, I think it would be a smart idea to make FSX always run with administrative rights by Right Mouse Click on fsx.exe (in the FSX root folder) > select properties > Compatibility tab > checkmark Run this program as an administrator (under Privilege Level) > click OK.
Then you need to make sure that you install all your FSX 3rd party addons using Run as administrator (Right Mouse Click on the installer and select Run as administrator from the list).

These things might help you get some things sorted out. I know that it is a real PITA to have to reinstall FSX after having gone through everything to get it where you want it, but the end result would be a lot less headaches. Hopefully the above should make FSX work with less problems.

NOTE: Installing FSX on a drive that is "owned" by you in a previous installation of Vista or Win 7 can end up giving you similar problems (and possibly Win XP, but to a lesser extent). So if, like me, you have other things stored (saved or backed up) on the drive that you install FSX AFTER you have reinstalled the OS, you will have some problems because of the ownership of the drive. I did. I think if I get rid of everything on my J: drive, reformat it and then reinstall FSX, I would fix some minor issues that every now and then rear their ugly little heads in FSX. Somehow retaking ownership of the drive didn't quite fix it. I'm too lazy to do that right now.
And here is me telling you to do just that above ::) So now you know why I understand how much of a PITA it is!

Mark