4.33 Issues (Known or not)
-
No, in 4.33 it could be also saved in a campaign name.ini file. That’s the difference.
-
No, in 4.33 it could be also saved in a campaign name.ini file. That’s the difference.
Oh, wasn’t aware of that! That’s a change with 4.33? When will it used waypoints from one as opposed to the other?
Checking the ini file for the campaign now though (I haven’t flown any missions since), and it appears to contain just the same coordinates as the pilot.ini file (the correct ones, but not the ones I got in the cockpit). And no precision waypoints I can see there either.
-
Avoid CH13 and prefer one of the Tactical Freq … CH13 (like CH14) is nothing realistic (sort of massive broadcast with heavy traffic).
Apologies for dragging up this old post, but I switched from Ch13 to the tactical frquency and AWACS was still spamming like crazy. It won’t shut up and chatters constantly throughout the sortie unless I detune AWACS completely.
-
Apologies for dragging up this old post, but I switched from Ch13 to the tactical frquency and AWACS was still spamming like crazy. It won’t shut up and chatters constantly throughout the sortie unless I detune AWACS completely.
In the ‘Settings’ section, un-select ‘UI Chatter’ and see if that helps.
-
I had that happen to me I had to clear all targets in the data Cart re did the mission and it worked fine
-
UI Chatter is an option if you listen to the radio while in 2D. AWACS “Radar contact…” type messages are spammed on 307.3Mhz which is ch13. “I switched to the tactical frequency” needs more info. What frequency/ch is tactical?
-
UI Chatter is an option if you listen to the radio while in 2D. AWACS “Radar contact…” type messages are spammed on 307.3Mhz which is ch13. “I switched to the tactical frequency” needs more info. What frequency/ch is tactical?
I think you have to set that up Fred. BMS User Manual, “7.6.2 Radios in the Falcon4 BMS World”. It does not specify which channel guard is or what reference channel should be used, but does specify flight package settings and frequencies. So it looks like you will have to set up (pre flight) your TAC channel.
-
… What frequency does he think “tactical” is.
-
… What frequency does he think “tactical” is.
Ha Ha,
Your guess is as good as mine. :rofl:
You have to set your squads channel(s). The above chapter should help with that.
-
“Tactical” is given in the briefing.
I tried some of the things suggested above and awacs has quieted down.
-
The frequencies given in the briefing are just the same as ch6/7/8/9/10 IIRC. There’s nothing special about them. Those are the default package filter frequencies. I don’t think the ch13 frequencies are in there but it might be. AWACS should only blab in proximity, team, broadcast assuming he also isn’t in your package.
What I find irritating about 307.3 is that is by default the IVC 2D-3D frequency which is neigh unusable with a working AWACS. I’ve changed my “team” IVC frequency to 308.3 in config but that only works when I host and others need to be told.
-
What I find irritating about 307.3 is that is by default the IVC 2D-3D frequency which is neigh unusable with a working AWACS.
BMS Manual p251-252 Radio Filter might help.
-
-
There seems to be an offset in the cabine pressure backlight in the block50/52 compared to the normal gauge faceplate.
-
Hello guys. I’m trying for a new campaign, the au c130. unfortunately they do not attack targets. It is’ a bug?
-
BVRAAM Lod5 shows a Python.
-
The frequencies given in the briefing are just the same as ch6/7/8/9/10 IIRC. There’s nothing special about them. Those are the default package filter frequencies. I don’t think the ch13 frequencies are in there but it might be. AWACS should only blab in proximity, team, broadcast assuming he also isn’t in your package.
What I find irritating about 307.3 is that is by default the IVC 2D-3D frequency which is neigh unusable with a working AWACS. I’ve changed my “team” IVC frequency to 308.3 in config but that only works when I host and others need to be told.
Just curious - What do you mean it is unusable with a working AWACS?
-
I mean if you have a friend sitting in 2D using “F1” (IVC) and you’re in 3D using 307.3 and you try to have a little chat you have to share air time with Johnny Magic who will not shut up. Shift the team frequency to something else:
set g_nF1TeamUiFreq 308300 // Frequency for F1 UI voice comms (for Force on Force type missions) 307300
and you can do the same thing without the constant verbal stream.
-
I mean if you have a friend sitting in 2D using “F1” (IVC) and you’re in 3D using 307.3 and you try to have a little chat you have to share air time with Johnny Magic who will not shut up. Shift the team frequency to something else:
set g_nF1TeamUiFreq 308300 // Frequency for F1 UI voice comms (for Force on Force type missions) 307300
and you can do the same thing without the constant verbal stream.
Yep, was just curious if that’s what you meant. Couple days ago in Balkans we had the issue where if the AI AWACS in 3D is too far away you can’t hear the player in 2D talking to you on F1. Not a sim issue as that is how it is designed but an issue for our flight.
Been meaning to try out Force Local Control which is nice because you can switch channels in the 2D AWACS role to communicate with people in 3D.
-
Ok, I’ve got a small one about the HSD MFD page I noticed in TE 02 Basic Nav. I had my HSD set up the default way with the center of the circle down towards the bottom of the MFD, range displayed was 8 to the outer range ring and my NAV steerpoint was shown outside the 8 nm ring, BUT MY HUD RANGE WAS 7.x nm! I didnt have time to check my HSI for range, couldn’t get there fast enough with my mouse once I noticed it. So which display should I trust, the HUD or the MFD?