RafaPolit

Thanks for the insight. And AI wingman is not affecting by the same problems? It's weird. I'll try to provide a track video.

Good afternoon friends! I am having issues with BVR in the F-14. I have done the Marianas BVR - Hunting the Jeff mission about 30 times. I turn NW, I either stay at Angels 30 or climb to Angels 40 or 45 (no difference in the outcome). When I get TWS track on the enemies, I shoot the Phoenixes at around 60 miles (have done so further away, I have done so at 40 and even less). Of the 4 bogies, I hit usually 1, never more, sometimes none. This is not in STT, I get the timers on each foe correctly, they are, in theory, being targeted. Obviously, I have my wingman next to me. If I instruct HIM to fire, co-alt, co-speed with me, he calls the fox threes one at a time and, like an ace, "Splash 1", "Splash 1", "Splash 1", "Splash 1". He gets all 4 with very high consistency. What am I doing wrong? Is it just that "human fired" AIM-54s are less precise than AI Phoenixes? It's good to cooperate with them, but it would be great to get at least one foe myself! Thanks in advance, Rafa.

ED cc @NineLine . There are some cosmetic bugs like several tails that are OK if they linger longer as they are just "inconvenient", but not game-breaking. This fueling bug really could be the end of your run, mission, or MP game. If your engine is on, you can "cheat" your way out of being stuck on by moving and "resetting" the ground crew, but if your engine stopped (for example, due to being out of fuel), you are simply paperweight on the ground: your crew will never finish fueling, so you cannot call for inertial starter, therefore never start up and move. You are simply done for. Also, if you are in need of repairs and need to shut down your engine and don't do it on the "correct (bugged) order", you could also end up no longer being able to start. This has happened to me in several MP games and it just completely spoils hours of work towards your objectives. Just like the Dora engine blowing up bug, this should really be a priority, and, I can assume, not that hard to "trigger" the right procedures. This is, in certain scenarios, unrecoverable from. Please bump this to a higher level priority?

I'm on the fence on this one: - it really helps the time to input the CMs and TGs to "plan" out the mission - it gives the time you need to spool up the engines and wait for the oil pressure, etc. But, once you have done this a couple of times for a particular mission, all the setup process becomes a bit repetitive and it now provides "little" additional benefit or input. So a "cheat" F10 menu of: I am already familiar, start me up and set my points of interest, would be a good solution as well. I am really on the fence.

Yeah, or changed the phase to ATK.

It happened to me in one or another attempt at the route, that the wingman, instead of doing a vertical take off, goes for a rolling start and has to navigate the entire taxi way to take off. I think it depends on how you take off yourself. By the way, thanks so much for looking into these and improving them. They really are very enjoyable missions. Thanks @Hangar200

Thanks! Yeah, or your copilot / wingman saying: hey, seems like we got them all! It doesn’t need to be something “official”, just some normal radio talk within the flight but that gives the non-military trained pilots like me a sense of “hey, you’re done, good job”.

I've never gotten to actually return to base. I can confirm I have destroyed all 8 SCUDS with no confirmation whatsoever. I mostly wait for the confirmation message, but not circling the assembly area, but moving slowly through the way points so as to not take too long.

I have actually done a ctrl+F11 trajectory all the way through the route, they are not there either. Maybe I just need to jump out as quick as possible, but starting the Apache takes time with the alignment and what-not, waiting for the PSI to drop to 70, you cannot just start flying away. So if that is happening, that is also an issue with the mission, IMHO.

I've reached WP03 and moved into the zone where you are supposed to rendezvous with the convoy, the convoy is never there. I cannot seem to even start the "mission" part of this mission. But I have never experienced your sudden death (and I have left my wingman going all the way back to the runway as well).

Thanks very much for this mission. Really interesting, and is nice to have to cooperate with the ground forces. I like the dynamic very much. I have encountered so far two issues, one very minor, the other prohibits the mission to complete: - Upon reaching the "antenna" in front of the helipad, apparently having cleaned all the ground enemy forces (the 'defending' ground units in the antenna are all in "stand down" attitude and the convoy of tanks we were escorting stops a few meters before the antenna), the Mi-8 starts to circle the helipad, apparently trying to land, but never accomplishing it. I have moved further away with my wingman, even gone to the next town... nothing. Waited until run out of gas. I then landed on the helipad and the Mi-8 just turned back. So it looks like it really is trying to land, never accomplishing it. Not sure if anyone else has seen this issue? Here's the Mi-8 just circling the pad - The other issue is very minor: it's a typo on the kneeboard on the coordinates of the WRS FARP coordinate... the first two digits are reversed, it's not 1049, but 0149. Here's the other issue with the wrong WRS coordinate: Thanks again, the mission is interesting. Rafa.

Actually, I enjoy it quite a bit. Yeah, I reach the hold area more or less when the F16 are shooting, but the "all air defenses down, proceed" message comes some 5 minutes AFTER the last "kill" report from the F16s... maybe it's waiting for the Hi-8 to do their thing? One additional thing I like to see in missions is: once you get all the MRMBs, it would be nice to hear a message saying "All SUCDs are down, good job!", something to let you know you have finished... something a flight member or copilot will "share with you" on the excitement of a successful mission. Also, perhaps, award 50 pts to that moment, and another 50 when you return safely? I believe the UN campaign for the Huey follows this and I find it useful to, at least, get "something" if you (like me! ) get shot by a missile on the way back once you have already taken out EVERYTHING in the base with your flight. Still haven't seen a "successful mission" here, but I'm getting close. Thanks again, Rafa.

Great to know! Thanks for the mission. It really is a fun mission. Hard enough to get it to try several times, but seems doable (not yet completed). Maybe the wait is a bit too long, but OKish. At initial setup weight the Apache will just NOT hover above a few feet, so I have resulted to reducing a bit of fuel and changing the rockets for another set of missiles. Not sure if this was intended (to have the helo heavy on startup). Again, thanks!

I believe this is a "quality of life" improvement that should be done. I have changed and deleted pilot settings trying to configure the CPG. This is true for the F-14 as well if you enter as RIO. I agree that, if you go into controls from the CPG, it should default to H-64 CPG.

If you are doing a cold start, you need to increase the volume of the radio.

The thing is, I believe, that those knobs have a "pull to disable" feature, that is bound to the LMB. So, you need to use the Mouse Wheel MW on those to rotate them.

You can move the cursor from one screen to the other in two ways: - As mentioned a specific button in the collective that can be bound, but... more useful for me to remember less bindings, - If you move the cursor to the right limit of the left MFD it will stop at the border. If you double-tap in the same direction (like you were "hitting" the border) the cursor will jump to the other screen. This can be done the other way around as well and bring it back to the left. Hope this helps, Rafa.

Actually, this is a bit confusing, but you will find that the LCtrl+V is bound to THREE different bindings: - The one in AH-64 George you are configuring - One inside the George "specific" area for the Pilot - One inside the George "specific" area for the CPG You need to actually bind all 3 to the same binding, in order for, when you are the pilot, to bring the George UI to show. You need to do the same in the CPG controls. I am actually not sure you "need" the one you are configuring, but I bound it nonetheless. Hope this helps, Rafa.

Thanks for the answers. I came here because I thought there was a problem with the CPG IHADSS. Reading this, I found out that it is "independently" true for the CPG. So, after doing the procedure for the Pilot, if you move to the CPG position, you ALSO need to up the light level in order to see the IHADSS concentric circles.

Hello! Thanks for already having some missions in at launch. I was prepping for the SCUD Busters mission, but the kneeboard waypoints are, partially, wrong. The second point HA52 is, probably, 0313 8941 (instead of 3013), as that correctly follows the other kneeboard map image with symbols included (and matches the height perfectly, so I think this is a typo on the kneeboard and probably really easy to fix). Both TG points have KN coordinates. This, to me, appears to be Caucasus map coordinates. Not anything that would be useful in this map. Changing to CA or CV coordinates, they are still a little out of bounds of what is probably useful. Point MBM is unclear to me if it should be a CM or a TG point, but it correctly registers as "red" so this is probably just cosmetic? Other than that, doing a "cheat" autostart on the mission only starts engine 1. Maybe this is a general bug and not specific to this mission? Thanks again, Rafa.

+1 Here! There are many "unrealistic" compromises due to the nature of our control surfaces. Like second detents being allowed without first a "first" detent. Here, this is a must in order to have any idea of where you are "trim neutral" with a joystick that just centers himself automatically.

I think there is a lot of "George Actions" missing completely from the dials and results: - "Search". If, for example, on Hellfires, you "Georuge-up", it will search where you put your LOS crosshair and present you with a list of found targets. This "George UP" is not documented in the dial, so it took me quite a while to actually attempt to do this. - After you are presented with the list of results, it is in no way evident that you need to "George Right" to confirm the target - The "permission to fire" is also an "obscure" concept that could be more evident As a final note, I understand that limited Missiles would require a new acquiring process, but something like the Gun should just move to next target in the region instead of you having to re-instruct George on a new target. So, to the OP, you don't want to "slave" unless you have your acquisition source, you want George to slew the aiming point, and that is done with "George UP" and then selecting the desired target from the list that appears ON THE COMPLETE OPOSITE SIDE of the screen. Which is easy to miss. I also wrote on this "eye parkour" issue on Wags video about George, he said it becomes a muscle memory soon enough. That may be right, still, not necessarily the best solution here. The module is great though, I'm having a lot of fun. Rafa.

Hahahaha... looks like a good approach!

This mod is seriously great! Fun to fly, moderately easy to learn, great looking without a doubt. Honestly, very nice experience! For those like me that are mostly plane pilots but wanted a taste of what a Helicopter can look like, it's simply mind-blowing that you can get this for free! Thanks so much for this mod. Best, Rafa.

On training: Lesson 9 - Air-Air ACM and HMCS You go through the motions, and after you get the missile, there is no further communication with the coach. No: "Good job, that's it", no: "Great, land at Gaudata", no: "Move on to waipoint 4 for extra encounters", nothing. You are left hanging. Also, since the addition of the radar modes, some instructions like : "click the button twice" now requires three clicks, which is something that should get updated when new things are implemented.