spetsnaz26

I just replayed this mission three times and finally survivied. Interesting thing is the cloud cover is now almost completely overcast and you'll be IMC on your way to B4. Was it like this back in 2018? Irish peak is around in the middle of the cloud layer.....First time I tried this I wanted to improvise an instrument let-down using the terrain avoidance mode....only to CFIT before reaching the farm because the radar beam apparently was tilted to the horizon rather than along the flight path. I thought the next hill is 10km away but ended up descending into a hill top. The next two attempts I found a large hole in the cloud and rolled to below the deck and scud-ran all the way to the target. The deck was about 5 or 600meters off the flat terrain, and some of the ridge lines are above the ceiling. After some NOE scud running I made it to the target area and had to roll onto the target right at the cloud deck rather than a bit higher and closer. As to the fighter cover the observation is the same. the F-15s are basically an eagle wall protecting our side of the field. The Migs did a number on us...second attempt I was locked by a Mig25 while clearing the last ridgeline before crossing FBEA. My KB was already dry and after some futile turns I got blown away at a few meters AGL by a R40. All other Viggens either flew into terrain or got killed by the Migs. The third time I arrived more or less on time and saved all my KB on my way out and delibrately flew south of B7 to shield myself under other allied aircraft....this worked....While NOE, I could see aircraft on both sides just getting shot out of the sky left right and center....and no way to know who those were....scope finally cleared after leaving the FBEA.... Lesson is try to arrive on time (difficult) and acknowledge that the aircraft simply isn't very survivable under those conditions.

Not sure if the campaign is still being maintained, but i've just started replaying the RF campaign and can't progress past mission 4. I kept getting blown away after popping up for attack. After reviewing the recording in tacview I think what happened was the SA15s around the target airport successfully stopped the F18s from SEAD. In fact, all but one F18 were taken out by the SA15s along with one other SAM to the south. Only the SAM to the south appeared to be destroyed by HARM. With at least two SA15s in the immediate area and no terrain to mask my approach, there is no way to perform the attack. All Viggens were taken out by the SA15s. I guess there must've been some changes to the relative strengths of the aircraft/SAM involved since the campaign was made, and now the mission becomes too difficult?

With unlimited ammo enabled, cycling the weapon safe/unsafe lever does not consistently select the next missile. I tried various things but never found something consistent I can use to make it work. Sometimes the sight picture just went back on by itself. Sometimes the sight came on when I cycled the weapon selector from out of RB75 to RB75, even without unsafing the trigger. The IR quick select button does not reselect the next mav either. Note that this apparently only happens if unlimited ammo is enabled.

Glad to see this reported. In my case I took off without doing any rearming and this happened after I selected the next mav. Looks like the missile is looking sideways. After resetting the view it went back to the center.

I searched and read a dozen or so threads here, read manual, Chuck's guide, and watched a few low drag videos on YT. Can't figure this one out. So, i was playing the Persian Gulf Fast meets Faster mission, and each time I flew close to the release point, i found the steering circle moving downward from my dot symbol. Just before release, it appeared to move rapidly downwards until out of view. I was very hesitant to follow it and the bombs dropped on target anyway (couldn't be 100% sure because by the time I looked back other dudes dropped too and the whole place was on fire). Does this mean I was too high? If I did follow the circle I think it would be a pretty abrupt pitch down, and the release will end up in a negative G push over.

Samsung Odyssey. Seen this haze effect before? Seems to be mostly over the ocean.

haven't been in VR for a while, just noticed that everything in the mid-long distance is covered in a bright, white haze layer, especially over the sea. I am playing the AJS37 beach interdiction mission and it is not supposed to have this weather effect (confirmed when not in VR). This happened in the BK90 FARP mission as well. Is this the result of low graphic settings? Anything there I can tweak with? Really kills the immersion for me. Thanks

odd....I'm using the Odyssesy but didn't notice anything wrong. tried using left eye setting and noticed no difference either...looked in the mirror and confirmed i've got no cross eye problem. Hope it works out for those who do.

Yeah, thought somebody would've posted this already. At least for Viggen is still a problem. For me the symptom is the airplane would pitch up into a loop soon after the replay begins, regardless of what I did in the mission. I tried the harrier and it works fine for several minutes at least.

updated to the latest open beta, and found the replay function acting weird. Saw a few other older posts about similar problems. I used VR and it's strongly disorienting to view a track playback in first person view, without taking control of the view. Is there ANY workaround to view a replay and enable view control? I tried to play a few tracks recorded using older versions (several months old). I was able to press F2 and switch views, for instance, but the control input was totally fubar. Airplane violently pitched up although I did no such thing. To clarify, this happened on AJS-37 but AV-8 seems to be doing fine wrt both view control&replay quality. Any help is appreciated.

I noticed that four enemy tanks simply forded the river, bypassing the bridge, and the mission failed before I landed back the first time... Too difficult...

Thank you. Good thing I didn't submit it as a bug, there's none. I tried again with IRMV selected without interruption and it worked. I always had to switch to other things in a mission, hence the problem.

Hey thanks for the explanation. I'll set up a controlled mission on ground with hot start and see what happens. I'm also concerned it may be a weapon mix problem.

Wait a minute, ready during cool down? I thought they were supposed to show STBY when you first select them. If rdy then you should be able to uncage fine.

Asking me? I've got them in STBY, so I couldn't uncage. This is supposed to go away after the minutes but in my case it never went ready

Tried both. I might be wrong but I am under the impression that the countdown doesn't pause if you don't deserve them?

Initially I suspected the same, but after changing the loadout the problem persisted. E worked fine, but G can't uncage if I follow that campaign mission. Starting from air in a custom mission and I could uncage without any problem.

Maybe I should reinstall the module, repair doesn't do anything

When playing Vulcan forge missions, I couldn't get the irmvs to become RDY and therefore unable to uncage. I selected IRMVs when airborne and waited much longer than 3 minutes (took out half of ISIS convoy with the gun) but missiles still stuck in STBY. Created a test mission with the same load out. Started in the air and could immediately uncage and fire missiles. Load was four IRMVs and two snake eyes outboard. Any help? Edit: this isn't a problem if you keep the missiles selected uninterrupted for three minutes. Also note Zeus note that you can box the Missiles on ACP before going to AG more so they you can prepare before arriving in the AO.

Okay, post June 1st update I still had one mission (#4 the artillery mission, Vulcan forge) where I could not uncage IRMVs, let alone SSS forward. Target is lazed by scripted friendlies, DMT in LST mode. Strangely, in the next mission I had a Target lazed and the uncage, SSS fwd, lock and fire worked perfectly. What's wrong?

.385 version. I see the monocular NVG problem has been solved, but now the radio menu and subtitles are all hidden behind the NVG image, making it awkward to use.

Hey, I tried again. This time I still couldn't drop my 2nd GBU, but after I strafed the BTR the mission continued normally and I was asked to RTB. After reviewing tacview, I think the difference is that this time I arrived on time and the SA8 dropped dead automatically before it could take out the SEAD flight... But thanks anyway

hey Sedlo, congrats on the campaign. One question about mission3: I loft bombed the barracks and when told to bomb the BTR, I had a weird GBU problem that prevented me from release in any mode. I then strafed the BTR to take it out. Then I flew a long time but nothing happened. The CH47s were just waiting on the ground I think. Did I absolutely need to bomb the BTR? Was that the problem? Also the SA8 took out both SEADs...then you know what happened to the SA8...

Had a very frustrating mission 3 of the Vulcan Forge campaign. Was asked to loft a GBU into a building, I did, then it was a BTR, but strangely I could not see the ASL. When I held down the release button, the 'ammo out' hatched pattern appeared and never went away until I put master arm safe and mode to NAV. The reset didn't do any good, as soon as I switched on master arm and mode AG, GBUs were automatically selected and the hatched pattern appeared although I still have bombs left. Target was being steadily lazed by a UAV, I could see target designation box, distance etc, but no time to target or ASL. unlimited ammo was on, not sure if played a role. It didn't happen before. I'm not sure if it's a bug or a 'feature'. see attached screenshot. sorry it's blurry VR. I had to strafe the BTR to take it out but the mission got stuck there (another thread).

here also. [edit] Maybe it's that update that hasn't been pushed to us yet. Out of sequence it appears. 00000.009 STATUS: Initializing... 00000.012 INFO : basedir: C:\DCS World OpenBeta 00000.012 INFO : dcs_variant.txt: openbeta 00000.013 INFO : DCS/2.5.2.17559.377 (x86_64; EN; WORLD,AJS37,A-10C,KA-50,RAZBAM_AV8BNA,NEVADA_terrain,AJS37-REDFLAG_campaign,PERSIANGULF_terrain) 00000.013 INFO : branch: openbeta 00000.013 STATUS: Connecting to update servers... 00001.652 INFO : Got reply from www.digitalcombatsimulator.com 00002.954 INFO : Got reply from srv5update.digitalcombatsimulator.com 00002.958 STATUS: Verifying cached version info... 00003.343 STATUS: Preparing to install FA-18C ... 00003.698 ERROR: Unknown module FA-18C