LordOrion

Here we go again: - Reaper 2 keep orbiting around WP1. - Twister 1 & 2 successfully destroy CItadel but never clear Chevy 2 to attack and RTB - Chevy 2 keep orbiting south of Nest-75 Guys, this campaign is awesome in terms of atmosphere and narration but with huge number of problems: It took me months to do missions 1-12 cause continuous stops waiting for fixes...

Ok, yesterday I've flown (and passed) the mission but I had some trouble with DRYAD: Authentication process was ok: WHISKEY, X-RAY=> BRAVO DELTA, TANGO => WHISKEY However, in the coordinate encryption i got: ROMEO, UNIFORM => NOVEMBER (?) KILO, INDIA, GOLF, UNIFORM, SIERRA, WHISKEY, HOTEL => 57 70'.831 GOLF, CHARLIE => WHISKEY (?) DELTA, ECHO, SIERRA, FOXTROT, TANGO MIKE, WHISKEY => 29 75'.871 Which are obviously not correct... In the end I've passed the mission since I saw the Max flare signal, but I'm curious to understand what I did wrong...

Looks like I've used the wrong encryption too The set letter for "Mike Foxtrot" is Delta, hence, correct sequence for ( 2 4 6 6 2 ) is: QUEBECK, JULIET, CHARLIE, KILO, TANGO

There is something I don't understand in encoding example in Briefing PDF: Shouldn't the correct encrypted sequence ( 2 4 6 6 2 ) be "VICTOR, FOXTROT, BRAVO, OSCAR, UNIFORM"? The example seems to be using the letters int the same reference row of the numbers, but this does not make any sense since it is the same for all reference rows and hence there is no "encryption' in that way... While in mission, should be strictly follow the 'strange' behavior described int he documentation?

10:01: la schermata FLIR sul DDI destro non sembra quella del Litening... E' per caso l'ATFLIR? Also, le nuove nuvole sono stupende.

Well, this indeed make sense :) To me, the effect you are describing seems a wrong target altitude setup... did you double checked it?

I'm only using OB and it worked fine for me

I don't remember any major OB update since the time I've flew this mission: are you using OB or stable version? I've seen the same while training in SLAM usage, and AFAIK active seeker distance is not related since the missile hit without guidance even setting it to 10 or 15nm. Dunno how SLAM works in real life, however it might be that terminal guidance is needed only when you have an approximate position of the target, or it has been mover around. If it is stationary and you have its precise position coordinates, SLAM could be able to hit without any adjustment from the DataLink.

Non so dirti, in genere dopo aver parcheggiato e spento il motore chiudo la missione. Il messaggio a cui ti riferisci comunque l'ho sentito solo quando mi sono mosso mentre era in corso una operazione da parte del personale di terra (riarmamento o rifornimento).

AFAIK no, just be sure to use the same folder name when you install it.

I flew that mission some day ago and all went fine: did you manually set-up targets coordinates? If so, do you have correctly set the target altitude? I saw the same effect when I've used waypoint target designation and WP altitude was not the same of the target, but the idea is the same: weapons compute a fall trajectory using the specified coords and altitude. If altitude is not correct they will miss. I.e.: - If target is a 100ft MSL and you left height to 0 in weapon setup, the JSOW will fall short. - If target is at 100ft MSL and you use the WP altitude (WP TGT designation), with a waypoint set at 15000 ft, the JSOW will fall long. If I'm right your should be the second case.

Dunno how thing goes in real life exactly, maybe you have just one target per plane or maybe wingman can lase one target for you, hence you can setup and launch 2 bombs per pass (just set 2 different laser codes). In any cases, if you are at high altitude (angels 20/25+) you should have enough time to see one bomb hit and move the TPOD to the next target before it goes off FOV. At that point you just need to go more or less 10nm away then turn inbound of the next pass. This is how I use to do in case of multiple targets in the same area.

Ok, in the end, using GBU-24 is the same as GBU-12 (they just add just a couple of fancy menu options) so I've completed the last mission and end the campaign. The overall experience was really good: it just need the author to go on ironing out the "randomness" we (all) already reported himm Nice job, well done! I've notice a couple of strange things with laser pointer of TPOD: usually it should reset the LD master switch to safe after the bomb impact(it uses the impact timer counter) but with GBU-24 this does not seems to occur. To be sure, I have reset and set it again manually prior of every launch and all went ok.

@Bunny ClarkJust completed mission 14 "Praying Mantis". I've never used the AGM-84E SLAM before so I had to train on it a bit before fly the mission. I've successfully completed it at the first attempt, but: Overall It was really fun indeed, but IMHO you should do something to avoid the mission go (almost)SNAFU like in my case. Now, it seems I have to get some training in GBU-24 employment...

AFAIR launchers are outside (in my case tharget was A), use the FLIR zoom to seach for them around: they should be easy to find, just look for a long truck with a missile over it:

Launchers position is random: AWACS will tell you once all flights are in their hold points.

Same here: switch layout from Laser to IR mavericks coupled with SEA radar mode. Hope ED will fix the TGP contrast some day

Mission 3 seems to be random: someone complete it piece of cake at the first attempt, other need to bump their head on it several times. In the end I've completed it successfully at the n-th attempt (I lost the count) but just thanks to a concatenation of positive effects: my wingman that do his job against the first strike group, the CAP that shot down many attackers and my AMRAAMs achieving an 1:1 shot/kill score (wow!) I think the problem is not related to AMRAAMs effectiveness: If shoot under the correct parameters the chances to hit are quite high, just avoid to shoot from too far away or the enemy will notch the missile.

@Bunny Clark Yes, I was right: the trigger zone used in mission 13 to check that all units are in their hold position was too small for 2 separate anchor points. I've fixed this (I hope you don't mind... ) by adding a separate trigger zone (same size) for Dodge flights and modifying the triggers accordingly. That way all worked fine. Here is the modified mission (if you like): https://drive.google.com/file/d/1SX5IkqTjr_F1WiBabgFuf6SNxgGxyb1e/view?usp=sharing Another issue: there are a lot of planes waiting to launch from the carrier at begin. Since the departure order is not specified (or at least I didn't find it) it is possible that player wingman might crash into another AI plane while taxiing (I've seen this a couple of times). This is obviously not your fault (sometime I think we should replace the "I" of "AI" with "S" and call it "Artificial Stupidity" ) To solve this is enough o wait for the bridge to be free from other planes (a couple of messages from the tower might help) but you might also consider to place Dodge flights already en-route to reduce the number of planes taxing on the bridge at the begin.

Double check triggers in mission 13: I've kept "waiting for Godot" (https://en.wikipedia.org/wiki/Waiting_for_Godot) for 20 minutes but Wizard never contact me to notify the target position. Not an editor expert, but I guess the trigger area might be too small for many groups holding over 2 different WP.

You have to escort the strike package and hence deal with SAM and enemy interceptors. You also have a couple of MK-20 rockeye, use them wisely.

thanks!

Hi, any news about release date?

If you mean "Disable Gyro Drift" from Options/Special/M-2000C I already have that option enabled (checked).

I Will check this evening.