No COMMS in FSINN and/or SB

[Hector Rojas]

Guys,

 

up until 3 weeks ago, I was able to talk/chat with ATC on either COM1 or COM2.

 

Now, suddenly, even though I can connect to VATSIM, I get NO comms with ATC at all.

 

I've tried both FSINN and SB4 to no avail.

 

I've even tried using a restore point when I know the thing worked and still get no comms.

 

Nothing has changed in my FS2004 setup, nothing has been added, nothing removed.

 

What's interesting is that this happens in both FSINN and SB.

 

Does anyone have any ideas or thoughts about what could this be?

 

FS2004

Win XP Home SP3

FSINN 1.3b2

FSCopilot 1.7b2

SB4

[Ernesto Alvarez 818262]

in SB. on the bottom right of it, it should say "Transmitting on 123.45" (or whatever frequency your tuned to)

 

does it say that, or is it just blank?

 

if its blank. you can fix it by restarting SB again. happens to me every now and then. restarting it usually fixes it.

[Larry James 901346]

Guys,

 

up until 3 weeks ago, I was able to talk/chat with ATC on either COM1 or COM2.

 

Now, suddenly, even though I can connect to VATSIM, I get NO comms with ATC at all.

 

I've tried both FSINN and SB4 to no avail.

 

I've even tried using a restore point when I know the thing worked and still get no comms.

 

Nothing has changed in my FS2004 setup, nothing has been added, nothing removed.

 

What's interesting is that this happens in both FSINN and SB.

 

Does anyone have any ideas or thoughts about what could this be?

 

FS2004

Win XP Home SP3

FSINN 1.3b2

FSCopilot 1.7b2

SB4

 

The problem with FSInn can easily be resolved by following the steps presented VIA the please read sticky in the FSInn Help forum.

 

Many problems are described, but when the user takes the time to follow the steps provide the results are always the same.

 

I give this answer for every problem, then if the user tests the steps and continue to have problems, I go over the steps with them and shortly find out which step they skipped. They their issue with FSInn is gone (if they do the steps).

 

The key to success lies in the bold item #3 of the please read sticky. This is where the user makes reference to the steps (as provided in the two messages of the bold item #1) that he actually did. When he does this he either post his followup with what he did to resolve the issue, or by what he posts, I pick out what he leaves out, which turns out to be the culprit.

 

-- L. James

 

--

L. D. James

[email protected]

http://www.apollo3.com/~ljames

[Hector Rojas]

The problem with FSInn can easily be resolved by following the steps presented VIA the please read sticky in the FSInn Help forum.

 

Many problems are described, but when the user takes the time to follow the steps provide the results are always the same.

 

I give this answer for every problem, then if the user tests the steps and continue to have problems, I go over the steps with them and shortly find out which step they skipped. They their issue with FSInn is gone (if they do the steps).

 

The key to success lies in the bold item #3 of the please read sticky. This is where the user makes reference to the steps (as provided in the two messages of the bold item #1) that he actually did. When he does this he either post his followup with what he did to resolve the issue, or by what he posts, I pick out what he leaves out, which turns out to be the culprit.

 

-- L. James

 

If you didnt care to read my problem, then please do not bother posting your template answer.

 

This is not related to installations, and it is not isolated to FSINN, again, just a matter of reading and actually thinking of an answer rather than copying your template.

 

Had you read you would have figured that FSINN and SB4 were working fine, and then one day (today) both of them do not allow for COMMS. Again nothing to do with your template answer.

 

So with this said, anyone has ever seen something like this where COMMS are lost using both FSINN and SB?

 

Thanks in advance.

[Richard Gerrish]

hope there's a better answer for you then this... Had this happen to me as well as a friend a couple months ago ended up having to do a fresh install OS down to solve it. good luck

[Larry James 901346]

The problem with FSInn can easily be resolved by following the steps presented VIA the please read sticky in the FSInn Help forum.

 

Many problems are described, but when the user takes the time to follow the steps provide the results are always the same.

 

I give this answer for every problem, then if the user tests the steps and continue to have problems, I go over the steps with them and shortly find out which step they skipped. They their issue with FSInn is gone (if they do the steps).

 

The key to success lies in the bold item #3 of the please read sticky. This is where the user makes reference to the steps (as provided in the two messages of the bold item #1) that he actually did. When he does this he either post his followup with what he did to resolve the issue, or by what he posts, I pick out what he leaves out, which turns out to be the culprit.

 

-- L. James

 

If you didnt care to read my problem, then please do not bother posting your template answer.

 

This is not related to installations, and it is not isolated to FSINN, again, just a matter of reading and actually thinking of an answer rather than copying your template.

 

Had you read you would have figured that FSINN and SB4 were working fine, and then one day (today) both of them do not allow for COMMS. Again nothing to do with your template answer.

 

So with this said, anyone has ever seen something like this where COMMS are lost using both FSINN and SB?

 

Thanks in advance.

 

Hi, Hector. It’s okay that you’d rather to dwell in the problem rather than the solution. If a template works, why not test it.

 

I read your message very carefully. I wish I could duplicate your problem, then figure out on my machine what is missing from the template that will cause it to fail in your case. It would probably take a lot of work for me to figure out how to produce what you have and are seeing. But since you have it and see it, it might be easy for you to produce the steps in my template.

 

Your message sounds clear that you don’t care about anything and anybody else having the problem, just a resolution for you. But if you would test the template and it fails, even that would be a contribution to the community as a whole.

 

I didn’t mean to aggravate you. I would have been glad to see a flaw in my template if it existed. I would have also been glad to help and spare you downtime.

 

I won’t shove the resolution down your throat since it clear you don’t want to test it. But I would have felt negligent to the community by not making a reference to the resolution that so far hasn’t fail.

 

Have a nice day.

 

-- L. James

 

--

L. D. James

[email protected]

www.apollo3.com/~ljames

[Randy Tyndall 1087023]

Hector,

 

I have something similar which occurs whenever I am on Teamspeak at the same time I'm flying on VATSIM, usually a VA Event Fly-in. If I use the PTT for TS (different from the one I set for VATSIM obviously) it kills my COMMS for VATSIM, both voice and chat. No one can hear/see text from me and I don't hear/see text to me. Otherwise I can hear everything else going on. I know, it doesn't make sense, a freq is a freq is a freq. If I can hear one person talk to another on the frequency I should be able to hear someone talk to me...but I can't after I've pressed the PTT for TS. The controller in KMSP and I tested this for quite awhile the other night. I use F12 for PTT on TS and L-Ctrl for PTT on VATSIM. My interim fix has been to disconnect from VATSIM for a few seconds and then reconnect. Comms work fine again until the next time I try to use TS.

 

Not much help for you I'm afraid, but maybe someone will see this thread and look into both our issues.

 

I use FSInn 1.3/Copilot 1.7/FS9.1/Win XP/USB Logitech Headset-Mic by the way.

[Norman Blackburn]

Hector,

 

How are you starting fs2004? By this I mean how are you selecting your aircraft? This sounds like your aircraft is not powered and is based on a simple fs9 bug.

 

What happens if you load the default flight? Note that this is from the fs menu and is not the same as changing from your broken situation to a Cessna at Meigs.

 

Once you have loaded the default flight do FSInn or SB work?

[Hector Rojas]

Hector,

 

I have something similar which occurs whenever I am on Teamspeak at the same time I'm flying on VATSIM, usually a VA Event Fly-in. If I use the PTT for TS (different from the one I set for VATSIM obviously) it kills my COMMS for VATSIM, both voice and chat. No one can hear/see text from me and I don't hear/see text to me. Otherwise I can hear everything else going on. I know, it doesn't make sense, a freq is a freq is a freq. If I can hear one person talk to another on the frequency I should be able to hear someone talk to me...but I can't after I've pressed the PTT for TS. The controller in KMSP and I tested this for quite awhile the other night. I use F12 for PTT on TS and L-Ctrl for PTT on VATSIM. My interim fix has been to disconnect from VATSIM for a few seconds and then reconnect. Comms work fine again until the next time I try to use TS.

 

Not much help for you I'm afraid, but maybe someone will see this thread and look into both our issues.

 

I use FSInn 1.3/Copilot 1.7/FS9.1/Win XP/USB Logitech Headset-Mic by the way.

 

thanks for your time and approach, but at least in my case, I am not using TS so i'm sure this is not my problem, I can however talk and hear on any rw.liveatc private frequency...just nothing on the ATC frequencies. again, this on both FSINN and SB4, and funny thing is thi was working up until 3 weeks ago (last time I flew).

 

Thanks again

[Hector Rojas]

Hector,

 

How are you starting fs2004? By this I mean how are you selecting your aircraft? This sounds like your aircraft is not powered and is based on a simple fs9 bug.

 

What happens if you load the default flight? Note that this is from the fs menu and is not the same as changing from your broken situation to a Cessna at Meigs.

 

Once you have loaded the default flight do FSInn or SB work?

 

Norman, thanks for your time, as a reminder, I have been using both FSINN and SB4 quite succesfully for a long time without problems, this problem happened suddenly and with no apparent reason. 3 weeks ago Iwas flying and talking fine, 4 days ago, no comms.

 

With that said, I was starting my saved flights as usual. I did however try your approach with almost the same results, meaning, still no voice and no text on ATF freq. using FSINN. (screenshot below)

 

 

and using SquawkBox4 I managed to read and be read on text by ATC, but I could not hear him and he could not hear me, plus, as in the image below, no active COM1 or COM2 are displayed in SB4 as indicated in the screenshot below.

 

[Ernesto Alvarez 818262]

if you look on the bottom right of SB. it sais Voice + text. so it did join the voice channel. why your not able to transmit or recieve on voice is another story.

 

are your running a router? firewall? antivirus?

 

we know youve been using it before with no problems, but stuff happens. its always the little things you skip that end up giving the biggest headaches. so even if something was fine before, you still need to check it again, otherwise you may overlook it.

[Jimmy Settles 902827]

This might not be exactly the same but might be worth a look, I was having trouble with a video driver and was doing some overclocking of the CPU. I reset the defaults in the BIOS until I got the video issue fixed. Next time I was on VATSIM I could hear but not talk. I discovered that when I reset the BIOS to the default values it enabled the onboard sound (in my case I can not use the onboard sound because it is not Vista capable) and Vista set the driver to "Windows default sound device". I could hear sound in my headset but could no longer use the mic. I changed the sound driver back to logitech and it fixed it.