Com1 tune in problem
-
Today I have flown on Vatsim within Greece CTR. During this flight I wasn't able tune in to 129,675. All traffic on that frequency was inaudible for me. Is it me only or something has broken?
-
I'm having the same issue. When tuning the radio to 129.67 for example, the simulator thinks you are tuning to 129.670 instead of 129.675 and so the radio doesn't tune properly. I'm having the same exact problem with ATIS at KSWF 124.575, you can't tune to that frequency.
-
@ethreven Are you sure that COM1 volume was switched on, volume up, and was switched on on the audio panel?
-
@ethreven Have you tried it using the GNS 430 or 530, which are not limited to two decimal points.
I do recall some mention somewhere of the KX170 frequency band being widened so that it would include the 0.005 but I can't recall where I saw that.
(EDIT: Oops, ignore this. I was getting confused with the ADF frequency issue.) -
@ethreven Have you tried it using the GNS 430 or 530, which are not limited to two decimal points.
I do recall some mention somewhere of the KX170 frequency band being widened so that it would include the 0.005 but I can't recall where I saw that.
(EDIT: Oops, ignore this. I was getting confused with the ADF frequency issue.)@sender46 I have, but today it wasn't my first flight in Greece, I flew there before with KX170 and I have never had any issue with a radio communication. I'm going to spawn at different airports and check the radio. Fortunately I'm not lonely with my case
-
I'm having the same issue. When tuning the radio to 129.67 for example, the simulator thinks you are tuning to 129.670 instead of 129.675 and so the radio doesn't tune properly. I'm having the same exact problem with ATIS at KSWF 124.575, you can't tune to that frequency.
@wizardneedsfood You're right, that's what it's doing.
@Sender46 The KX170 shouldn't even be able to tune 129.670. It only supports 25 kHz separation, so tuning anything ending like .X2 or .X7, it's actually .X25 or .X75. It shouldn't have to be artificially widened to include those frequencies. I think what you're remembering is the fractional ADF frequency issue
-
@wizardneedsfood You're right, that's what it's doing.
@Sender46 The KX170 shouldn't even be able to tune 129.670. It only supports 25 kHz separation, so tuning anything ending like .X2 or .X7, it's actually .X25 or .X75. It shouldn't have to be artificially widened to include those frequencies. I think what you're remembering is the fractional ADF frequency issue
@vcapra1 said in Com1 tune in problem:
I think what you're remembering is the fractional ADF frequency issue
Ah yes, you're right. Apologies and thanks for the correction.
-
We'll fix this is the next update. If you contact our support team, they can provide an updated gauge to fix the COM tuning issue which can be used in the meantime.
-
We'll fix this is the next update. If you contact our support team, they can provide an updated gauge to fix the COM tuning issue which can be used in the meantime.
@martyn said in Com1 tune in problem:
We'll fix this is the next update. If you contact our support team, they can provide an updated gauge to fix the COM tuning issue which can be used in the meantime.
Is this present in the other Pipers, as well?
-
@martyn said in Com1 tune in problem:
We'll fix this is the next update. If you contact our support team, they can provide an updated gauge to fix the COM tuning issue which can be used in the meantime.
Is this present in the other Pipers, as well?
-
Does anyone know the status of this bug? I don't think it was corrected in the last update. Can anyone confirm/deny?
Thanks
