San Patricio

Just bumping this to say I have a similar problem after the update and can't seem to find a way to revert.

Ok, I understand, thanks. So once you switch to COOP and the CPG designates a target, the LOS cross will always show the relative longitudinal distance between your aircraft and the steering cue/I-beam regardless of where you look. Not the most intuitive GUI but I get it!

Thanks! That does track with my experience but I'm still not sure I understand the logic. When in COOP, I can still move my head around and it moves the LOS cursor. If the target is fixed by the CPG, why does aligning the I-beam with the LOS crosshair (which can move anywhere!) produce a good targeting solution? I'm not doubting it does, just not sure I understand the underlying logic.

So I've watched both Cosmo and Wags videos on this and I have got the hang of firing using the P-HMD. I still don't entirely understand COOP mode though. Specifically, what am I supposed to align with the I-Beam when in COOP? I would think it would be the TADS marker (dashed cross) but that seems to produce very poor results. It seems to work better when I align the I-beam with the LOS cross (non-dashed) but that makes little sense since George is doing the designating in COOP and it shouldn't matter where I look.

Having the same "listening suspended" problem with the F-14B. Not using DiCE or other mods and the fixes suggested above do not seem to help. Oddly it seems to work fine with an in air start but not when cold starting. Edit: Can confirm it has something to do with cold starts. Starting from warm on the runway and it works fine. Same mission but change to cold start and I get the "listening suspended" thing even when trying to talk to Jester or ground crew.

So I've been using Liberation for ages but for some reason today when I launched 4.1.1 the map screen in the center was blank. Tried reinstalling 4.1.1, creating a new campaign, and even rolling back to 4.1.0 and nothing works. It launches fine but the map in the center display won't show up. Any suggestions? Thanks!

Ah, that was my problem, thank you! I had assumed I didn't need a target point since I was using Bx8 as the target. When I entered the assumed release point (B3) as a target point (M3) it gave me the countdown as expected. Thanks again!

So I'm at the mission in the campaign where you are supposed to hit the Russian surface ships with RB-15s and use a particular TOT for the missiles (07:13). I've followed the procedure from the manual (and a YouTube video) which is to go into Tid, input, type in the TOT (071300), then Bx and 8. When I go back to output, however, the Tid is blank and I never get a countdown to take off. Confusingly, the notes in the briefing saying to enter the TOT in Takt, which conflicts with the manual. I tried that as well but no luck there either. Anybody have any suggestions for how to get TOT working with the RB-15s?

Ah! That did it. Thanks much!

Yes, I did and I realized that the export profile for AIRIO does contain the new command to use F10 markers to make waypoints but does not contain any of the other new commands. There are four commands listed when I use the exported AIRIO VAP: Radio tune, TACAN tune, F10 map markers, and link tune. I was able to add the F10 map markers command that way but none of the other new ones (like ground stab or commands to switch to RWS/TWS) are in the exported VAP and they don't work in the game.

I've got AIRIO 2.53 installed along with VAICOMPRO 2.5.11. I'm following the instructions to import the new commands from 2.53 but when I export the profile and then go to edit it, the only commands listed are the ones added in 2.52 (Link tune, etc.) and the new ones from 2.53 don't appear. I manually downloaded 2.53 again and deleted old versions of the export file but I can't seem to get the new commands to show so any help would be appreciated. Thanks!

So those exports work well but when using multimonitors I find that the Jester wheel gets stretched over out across my displays making it hard to use. Is there a way to configure Jester to only display on the main monitor?

I have no way of judging if it is more realistic or not, but after breaking the muscle memory habits of doing CASE I's under the old flight model, the changes definitively makes it easier to control the aircraft on approach. I don't know if it's just the revised drag numbers of whether they've also tinkered with something else, but the plane now seems much less liable to sink like a stone when banking into the short final and it just generally seems easier to control the rise/sink rate than it used to be.

So I try to practice a Case I ot two every day using the Instant Action mission. I noticed a couple changes right off today: the TACAN is now on 74X (and not 55X) and the ZTOD is now projected on the HUD at mission start. More importantly, it seems like the aircraft handles a little differently at low speeds now. Before, I had to keep the engines at somewhere between 91-95% RPM on the turn into short final to avoid sinking too much and then somewhere around 91% on the final (depending on where I was on the glide slope). After today's patch its SEEMS (and this may just be small sample size or my own error) that the gear down produces less drag (takes longer to slow down after dropping them) and that less power is required to keep up a good descent rate on the turn into final and then the short final. After coming in too high repeatedly, I found that somewhere in the 87-88% rpm was all I needed. Anybody else notice this or am I imagining things?

So I've watched the various videos and read Chuck's guide and I'm getting better at my Case I recoveries, but there's one thing that I'm still not sure about. When I hit 250 kts during the break turn, I drop my gear and put flaps to full. The issue is that as soon as I drop the flaps, the aircraft wants to pitch up hard and start gaining altitude. What's the best way to counter this? If I try to just maintain on speed AoA with pitch trim after dropping flaps, I manage to gain a couple hundred feet on the downwind leg before the speed comes down enough to level out and start dropping, which puts me too high. If I counter the pitch up by reducing throttle I still end up gaining altitude because of the delay between the throttle change and the effect on the aircraft (and as a bonus I usually cut throttle too much and then sink like crazy right after). My most reliable way of dealing with it is just holding the stick down to keep the aircraft pitched level after dropping flaps and waiting for the speed to come down, at which point I can let go of the stick, adjust AoA with pitch trim, and manage altitude with throttle as the various guides suggest. Is this the correct way to deal with the flap-induced pitch up? Or do I just need to get better at managing the throttle?

Is there any way to get your wingman to engage or communicate on this mission? On channel 1 on both radios and hear his calls but he will not accept any orders and just circles around the bandits until he gets shot down.

Flying mission 12 (2.5.2 OB update 5), I can't get my wingman to engage bandits or otherwise acknowledge my commands. Both red and green radios are set on channel 1 and I can hear both scripted banter and my wingman's "wheels up" call so I don't think it's a radio issue. I've tried giving commands to both flight" and "wingman 1," "wingman 2" but have never received an acknowledgment and during the fight with the Mig-31s and the Fulcrums poor Teeter just spins around without engaging until he gets shot down. Any help would be appreciated! Thanks for a great campaign.

Good work! Previously, exporting the DDIs to your MFDs with the standard DCS monitor config files caused them to be blank on both the main screen and second/third monitors. Was this fixed in the last patch or does this profile work around the current export bugs in the early access version? I have two Liliputs that I usually use for MFDs and haven't used Helios much in the past, but if it allows us to get around the current problems with exporting the DDIs I'll give it a try.

I'm not sure exactly what is intended, but looking at the Tacview, two L-39s peeled off and returned to base while another two stuck with the transport. I shot down the transport and the two escorts and around that time I got a radio message from Chevy 1-1 that he had splashed two. Since I didn't see anything on my scope, I assumed they were all down and it wasn't until I checked the Tacview that I realized that two had actually RTB'd. None of the L-39s got a shot off, but that may be because I downed the two remaining escorts very quickly. One other thing that may or may not be a bug: After the engagement Chevy 1-1 says he's going to come join me but he never did. I had to fly to him to trigger the next radio message and RTB. I'm attaching the .acmi file here (note that I renamed the mission to FINAL so I could drop it into the campaign folder). Hope this helps. Tacview-20180531-212532-DCS-Mission 10 FINAL.zip.rar

Can confirm that the fixed version above worked fine for me. Got through the engagement with no CTD this time. Thanks and I hope this helps with the Red Flag progress. One small issue: I did not get a mission complete upon landing at Varzani as I usually do. Tried taxing around but stayed stuck at 50% results.

Quick work! I'll test it out tonight and let you know. Thanks!

Really enjoying the campaign! I've had an issue recently though with mission 10 (OB 2.5.2). After intercepting and engaging the L-39s, I get a DCS hard crash. The first time I wrote it off as a random issue on my end, but I just tried it again and got a hard crash in almost exactly the same spot (right after firing on the L-39s). Log files is attached. Thanks for all your good work! dcs.pdf

Thanks for checking. I'm loving the campaign and will try the work around.

I started Mission 7 (Hotel 5) in 2.5.1 this evening but while the radio check and call in to wingman seems to work fine, none of the other active aircraft at Vaziani seem to want to take off. I got clearance to taxi and found the path to the runway blocked by another pair of M2000Cs that seem ready to take off but would not move. Nor would my wingman leave the hanger. I eventually worked my way past the planes blocking the taxiway and took off to see if that broke the log jam but nothing happened (and my wingman remained planted in the hanger the whole time). Seems like a busted start trigger and I'm wondering is this is new in 2.5.1.