4.33 Issues (Known or not)
-
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?
-
What do you mean by your HUD range? The HUD in nav mode displays several ranges. Horizontal range to the selected steerpoint, and slant range to the target/SPI…
There is terminology to describe the HSD settings, too. Your HSD was depressed, decoupled and with 8NM range ring.
Tis possible your SPI was closer than the steerpoint position in the HSD. However, I thought the steerpoints should slew in the HSD in that circumstance. Interesting.
-
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.
You don’t want Local Control because that disconnects IVC from Falcon entirely. If the problem is that a 2D person’s jet seat is too far from a 3D person’s jet seat (i.e. AWACS too far away) then the solution is to change the Outsiders setting so people in 2D are always 0.0nm from people in 3D regardless of their seat’s jet’s position.
-
You don’t want Local Control because that disconnects IVC from Falcon entirely. If the problem is that a 2D person’s jet seat is too far from a 3D person’s jet seat (i.e. AWACS too far away) then the solution is to change the Outsiders setting so people in 2D are always 0.0nm from people in 3D regardless of their seat’s jet’s position.
Yep, there are different settings for the outsiders config (i.e. awacs, seat, etc…).
You definitely can use local control if you want to be the human AWACS. It just makes it so that when you launch into 2D the game code doesn’t take over and it allows you to manually change frequencies.
-
Here’s a little bug I’ve noticed while going through the HARM training mission.
Notice the wrong callsigns Weasel91 … :rolleyes: -
Searched but didn’t find anything. I was coming back and all of the sudden the tadpole and the diamond that marks a steerpoint on the ground didn’t match.
INS was aligned before flight and working. It was right when I got to the target for sure, I don’t know when it started drifting. There weren’t any fault in the PFL.
Is this some real life misalignment modeled into the sim perhaps?
-
This was a mission to strike a ground target, perhaps? You had to slew the cursors at some point in the flight, perhaps?
You also slew all steerpoints when you do that, not just the target.
-
Searched but didn’t find anything. I was coming back and all of the sudden the tadpole and the diamond that marks a steerpoint on the ground didn’t match.
INS was aligned before flight and working. It was right when I got to the target for sure, I don’t know when it started drifting. There weren’t any fault in the PFL.
Is this some real life misalignment modeled into the sim perhaps?
Read the -34 sec. 3.1.3 (pages 142-143) and you will have your answer and see how to get cues lined back up w/ the STPTs.
-
Yesterday I flew a DEAD mission in a campaign (First day, Tiger Spirit) and T/O was 17:11…
Things didn’t work well, so I wanted to start again, so ‘ESC’ and ‘e’, and time was 16:51.
I double checked my flight, and yes, I surly know, that I had my Take Off at 17:11 and it was the correct flight…
What happens there?And…also yesterday (same mission only later again) I asked AWACS where my target is (AAA)…
AWACS: 310 20miles
Flying some seconds, and asking AWACS again…
AWACS: 325 40miles
What happens there?
My thought is: Ok, AAA is moveable, but so fast? (And yes, I had only one target…)TIA
Greeting
Earlybite -
And…also yesterday (same mission only later again) I asked AWACS where my target is (AAA)…
AWACS: 310 20miles
Flying some seconds, and asking AWACS again…
AWACS: 325 40miles
What happens there?
My thought is: Ok, AAA is moveable, but so fast? (And yes, I had only one target…)TIA
Greeting
EarlybiteI would say it was you moving away from the target.
-