4.33 Issues (Known or not)
-
Pretty sure you messed up your DTC if your INS has been correctly align.
That is of course possible. But what in the DTC would be wrong?
I still have the WDP open from that mission, and in the DTC section it does list the correct coordinates for the target waypoint. And none of the waypoints are precision waypoints.
I could have possibly picked a different mission inside BMS than I thought, and hence got the waypoints for a different mission. But in the debriefing I did get a successful mission for destroying the target I was supposed to, so I don’t think I flew a different mission.
About the wrong coordinates when entering them I’ve tried several times to reproduce with the same location now, and it does work correctly. It’s possible that I may have simply made a typo with coordinates, but can’t say for sure now.
-
What can hapend, is that the DTC saved is not the right one. Depending of the mission type, it could be stored in the pilot.ini file and on the mission.ini file. Then, check both with the WDP when reset the DTC.
-
In short WDP is mandatory and falcon Dtc might cause troubles?
-
Nope, but is more easy to control what is inside the DTC with it. That’s why I use it.
-
What can hapend, is that the DTC saved is not the right one. Depending of the mission type, it could be stored in the pilot.ini file and on the mission.ini file. Then, check both with the WDP when reset the DTC.
It was a campaign mission, so it should have used the pilot.ini file, right? That’s the one I viewed in WDP, no precision waypoints there.
-
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?