Quax

Try changing the "_winwing.interval=" value (line #19) in wwtExport.lua to something higher from what it is originally on. Make sure to do it in \SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua as well or the changes will get overwritten on the next start of SimAppPro. That changed helped for me to significantly reduce stutter. The refresh rate of SimAppPro simply was too high (and isn't needed).

Another topic I ran into in this mission: After the "divert" for the special tasking, I was told to continue to the carrier for a CASE III approach. There was a 70kn headwind component and a very strong crosswind resulting in a wind correction angle of about 10 degrees so the birdie was way off the HUD. Is that on purpose? Shouldn't the carrier turn into the wind?

That worked! I tried in M08 and game didn't crash at the regular point (just when feet wet). I was able to complete the mission until going RTB.

Anyone tried to deactivate the F-14 Heatblur Mod? Maybe that causes problems? I constantly keep getting crashes in M08 and didn't try without the F-14 Heatblur yet. Could there be a relation?

Welche Bildschirme benutzt du dort denn für die MFDs?

Ich besitze die F/A-18 Variante des WinWing Sticks und Throttles und bin vollauf zufrieden! Allerdings kann das Synchronisations-Script für die Beleuchtung zu FPS Einbußen führen, die man aber mit einem kleinen Tweak des entsprechenden Scripts beheben kann (in wwtExport.lua den Wert für _winwing.interval erhöhen - bei mir jetzt auf 0.5). Alles in allem top Verarbeitung, super Qualität und Support! Zoll machte auch keine Probleme (wird alles über FedEx geregelt).

Ok, looks like the DCS-BIOS messages aren't related to the crash. However, on my last test I got the following log messages right when the crash happens: 2022-08-06 14:23:29.358 ERROR SOUND: invalid source_params(woLA-16806656:aircrafts/uh-60/enginel): gain 2022-08-06 14:23:29.358 ERROR SOUND: invalid source_params(woLA-16806656:aircrafts/uh-60/enginer): gain 2022-08-06 14:23:29.358 ERROR SOUND: invalid source_params(woLA-16806656:aircrafts/uh-60/rotor): gain 2022-08-06 14:23:29.358 ERROR SOUND: invalid source_params(woLA-16806656:aircrafts/uh-60/distant_flyby_s): gain 2022-08-06 14:23:29.358 ERROR SOUND: invalid source_params(woLA-16806656:aircrafts/uh-60/distant_flyby_b): gain Anybody know what those mean and maybe has a workaround?

Correct. "150 to 5" means fly those 150kts to 5 NM from the boat. In the Hornet that means to trim for an AOA higher than "on speed" because 150kts will be achieved at a lower AOA than "on speed AOA".

@baltic_dragon I understand that it could be difficult to identify the problem but just because that not everyone has the crash is not a proof that it is not related to the campaign but could be something that happens in connection between the campaign (probably/maybe something between a script in a mission) and DCS or a very popular plugin (see my post in the other M08 thread regarding DCS BIOS). In my case, I have never experienced freezes or crashes except in M06 and M08 of the Dominant Fury campaign. Don't get me wrong - I don't want to blame anyone but obviously those crashes are related to the missions in the campaign somehow. So lets try to gather information so that you could reproduce the problem and maybe find a solution. The result could be that you can't do anything to solve the problem but right now the exact problem hasn't been identified so please don't just blame DCS. The campaign is a great piece of work and of superb quality overall but if people can't complete it or continously facing CTDs when playing it, this will probably influence their oppinion somehow.

Ok, guys. Deactivated all my mods except the official ones. Still the mission is crashing right after the BDA confirmation of the Ravens after "feet wet". I checked dcs.log - no error messages Update: I just found two messages in DCS-BIOS.log (which has a timestamp that fits the time of the crash): Util.lua: value 524053.000000 is too large for address 29944 mask 65535 Util.lua: value 1900515.000000 is too large for address 29950 mask 65535 Maybe that has something to do with the crash. I can't test again until tomorrow evening but maybe this info helps you guys.

I finished M07 today without problems after having installed the latest update.

Crash/freeze in DCS in mission 07 just training is aborted. See also https://forum.dcs.world/topic/305643-mission-07-crashfreeze/#comment-5015268

Same for me - but not using VR. Happens just after the intercept started.

Same problem here except that no more comms after the instruction to not attack the civilian traffic that popped up on radar. AI also didn't follow waypoints after the drop anymore and entered a holding pattern in about 23000ft about 45 NM east of the carrier. After having read the briefing for mission 07 I feel I missed some important part of the story as diplomatic tensions are mentioned and I guess those should be rising while still playing mission 06. @Trini86 I would be interested in the fix

Hey guys, I played a bit with that setting. Lowering it actually DECREASES fps (up to freeze with 0.01) so I increased the value to 0.5 in steps - that almost doubled my fps!

As a workaround, select an unused waypoint and copy coordinates from the target waypoint. Then use that one for targeting. This way you won't change the coordinates of the original target waypoint. Mark points work as well.

Dear developer team, I just finished the first mission of the new campaign and I absolutely like it! Although not one shot fired this mission is really exciting and immersive - well done and thank you very much for taking your time in creating such a great experience for us players. However, some minor items I experienced while playing: - Headings, radials etc seem to be referenced to true and therefore are a few degrees off (e.g. first radial to waypoint 1, final bearing etc) - When approaching Akrotiri, approach instruction is to enter downwind runway 28. Although this can be done, as approaching from the south east, a direct approach may be more suitable (especially in a case of emergency). - Later on the missed approach procedure is announced to the player with a RIGHT turn heading 180, which means an about 270 degrees right turn when flying the missed approach runway 28. Maybe it should be a LEFT turn here? - There is a typo in the radio message on ground to STRIKE ("... on on radio...") Don't get me wrong - the quality of the mission and probably the entire campaign is absolutely stunning! That's just minor details and the quality is very, very high. Thank you very much!

That was the solution! Thank you!

See attached picture - that symbol. It is Open Beta. I guess, it is a server load issue but I'd like to start the download (my connection isn't that fast )

Same problem here. I bought the map, downloaded the update but cannot download the map. It is not even listed in the module page of DCS although I have a valid license in my DCS profile...