kaba

It almost sounds like the attackers either got killed or there was some AI bug where they decided not to attack. Not sure if youve got a tacview that i could look at?

Cornflex - Did any of the ground attackers get destroyed? Did you call in all ground attackers? There is a fairly forgiving scoring system to work out if you win based on how many attackers make their attacks.

Thanks - there is a recurring DCS bug where the player aircraft is put on the wrong catapult, so it spawns you on cat 1. I'm unable to work around that so i will just remove the static hornets in a future update.

Might be something to do with how DCS assigns start positions between different players - are you starting on the Cat? Could you try from the ramp, either cold start or hot start?

Sounds like the carrier doesn't have any spawn slots at the time you spawn, so you have to wait for AI to take off. Supercarrier or normal carrier?

there was a CTD on AI CASE II landings. I'd previously reported this to ED and it seems to have been quietly fixed in a recent patch. I've also changed up the weather in the latest campaign version to avoid CASE II's entirely (both to avoid the bug, and also because I find them quite boring vs CASE I & CASE III) So short answer, I'm not aware of any new bugs and nobody else is reporting any. If you do experience some, then please let me know, but you also need to report CTDs to Eagle Dynamics rather than just me.

There should be no issue with changing the loadouts on these missions, but be careful of fuel! This mission is pretty forgiving, you only need to take out one target and they are not hardened. CCRP, CCIP, LGBs, totally up to you. There's nothing preventing you from hitting it with JDAM or even JSOW if you really want, although I don't think they were invented yet...

Thanks, I am glad you are enjoying it. This is the OCA mission, right? Don't worry too much about the wingman - I've intentionally left all objectives complete-able without relying on him, the AI is so shonky!

Thanks for flagging this - I've fixed this internally and sent off the updated files ( with a few other bug fixes). Should be available in an update soon. Afaik it shouldn't happen - SC not supposed to spawn you on top of statics - but at least it doesn't cause damage. Did this happen on the very first time you started the mission, or after restarting? I could only get it to occur after a restart, very odd!

I've had no issues in the latest patch, except for the Case II ATC loudly repeating. I can understand if you'd prefer to wait though.

Hello, this is my campaign. If you go into Campaign > F14 (NOT 'My Campaigns') you should see the Supercarrier version in your campaigns. Let me know if not?

On singleplayer, yes. See https://forums.eagle.ru/showthread.php?p=3732441

I'm experiencing no CTD on landing after today's patch. Can I ask you to please let me know if this still occurs after the update on your side? Edit - actually, a lot of new bugs in this patch. Might want to hold off until a hotfix can help this out...

Hey Razor18 it's very possible. Did you ever submit a bug report and the crash log to Eagle Dynamics? I'm not the best person to be able to help diagnose system crashes I'm afraid.

Hi guys There seems to be a recurring crash on CASE II landings when multiple AI are in the stack. Have you experienced this? If so can you attach your logs to the bug thread I posted here: https://forums.eagle.ru/showthread.php?p=4377154#post4377154 I'll upload a new version of the campaign without CASE II landings this week to avoid this issue for now.

DCS version: OpenBeta v2.5.6.50321 Details of crash: DCS crashes to desktop during a mission when AI try to land on the carrier. This occurs using both Supercarrier and normal Stennis carrier. I have only experienced this CTD on a Case II landing pattern, and only with multiple AI groups in the stack. The crash consistently occurs as the first AI reaches the downwind leg. I have reproduced this crash 4 times. Once on a busy mission I made (with supercarrier) oncec on the same mission (without supercarrier) and twice on a test mission with just the supercarrier and AI. Looking at the crash logs, the error is an ACCESS_VIOLATION in relation to Flight.dll. I've attached an excerpt of one of the crash logs below. Attachments I've also attached the full logs for the 4 instances of the crash. I have also attached a test mission which reliably leads to this crash. The AI are will try to land at the carrier, and when the first aircraft hits the downwind leg I get the crash. To reproduce, just play the mission, and wait for the AI to land. I've attached them to another thread on this issue - here Hope this helps. 2020-06-09 09:18:03.000 INFO EDCORE: try to write dump information 2020-06-09 09:18:03.002 INFO EDCORE: # -------------- 20200609-091803 -------------- 2020-06-09 09:18:03.004 INFO EDCORE: DCS/2.5.6.50321 (x86_64; Windows NT 10.0.18362) 2020-06-09 09:18:03.005 INFO EDCORE: M:\DCS\bin\Flight.dll 2020-06-09 09:18:03.006 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 4977ECDB 00:00000000 2020-06-09 09:18:03.010 INFO EDCORE: SymInit: Symbol-SearchPath: '.;M:\DCS;M:\DCS\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Cal' 2020-06-09 09:18:03.012 INFO EDCORE: OS-Version: 10.0.18362 () 0x100-0x1 2020-06-09 09:18:03.867 INFO EDCORE: 0x00000000000AECDB (Flight): woATC::onMessage + 0x5AB 2020-06-09 09:18:03.868 INFO EDCORE: 0x000000000005244C (Transport): wAirService::getFreeCatapultsNum + 0x52C 2020-06-09 09:18:03.870 INFO EDCORE: 0x00000000000B0170 (Flight): woATC::onMessage + 0x130 2020-06-09 09:18:03.870 INFO EDCORE: 0x000000000004ACBA (Flight): wAirbase::onMessage + 0x2A 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000069DF41 (DCS): woLA::loadNewInputLayout + 0x2AAB71 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000069BA81 (DCS): woLA::loadNewInputLayout + 0x2A86B1 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000069A235 (DCS): woLA::loadNewInputLayout + 0x2A6E65 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000048645B (DCS): woLA::loadNewInputLayout + 0x9308B 2020-06-09 09:18:03.871 INFO EDCORE: 0x0000000000446794 (DCS): woLA::loadNewInputLayout + 0x533C4 2020-06-09 09:18:03.871 INFO EDCORE: 0x0000000000003C04 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x504 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000000040AD (World): wSimCalendar::DoActionsUntil + 0x1FD 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000007033FF (DCS): woLA::loadNewInputLayout + 0x31002F 2020-06-09 09:18:03.872 INFO EDCORE: 0x0000000000714313 (DCS): dDispatcher::InitDatabase + 0xDC73 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000006EAB44 (DCS): woLA::loadNewInputLayout + 0x2F7774 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000006EAF09 (DCS): woLA::loadNewInputLayout + 0x2F7B39 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000015A3B37 (DCS): AmdPowerXpressRequestHighPerformance + 0x9ECB33 2020-06-09 09:18:03.873 INFO EDCORE: 0x00000000008CE98E (DCS): uiAsyncNet::onGameStop + 0x684BE 2020-06-09 09:18:03.873 INFO EDCORE: 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14 2020-06-09 09:18:03.873 INFO EDCORE: 0x000000000006CE51 (ntdll): RtlUserThreadStart + 0x21 2020-06-09 09:18:04.214 INFO EDCORE: Minidump created.

DCS version: OpenBeta v2.5.6.50321 Details of crash: DCS crashes to desktop during a mission when AI try to land on the carrier. This occurs using both Supercarrier and normal Stennis carrier. I have only experienced this CTD on a Case II landing pattern, and only with multiple AI groups in the stack. The crash consistently occurs as the first AI reaches the downwind leg. I have reproduced this crash 4 times. Once on a busy mission I made (with supercarrier) oncec on the same mission (without supercarrier) and twice on a test mission with just the supercarrier and AI. Looking at the crash logs, the error is an ACCESS_VIOLATION in relation to Flight.dll. I've attached an excerpt of one of the crash logs below. Attachments I've also attached the full logs for the 4 instances of the crash. I have also attached a test mission which reliably leads to this crash. The AI are will try to land at the carrier, and when the first aircraft hits the downwind leg I get the crash. To reproduce, just play the mission, and wait for the AI to land. Hope this helps. 2020-06-09 09:18:03.000 INFO EDCORE: try to write dump information 2020-06-09 09:18:03.002 INFO EDCORE: # -------------- 20200609-091803 -------------- 2020-06-09 09:18:03.004 INFO EDCORE: DCS/2.5.6.50321 (x86_64; Windows NT 10.0.18362) 2020-06-09 09:18:03.005 INFO EDCORE: M:\DCS\bin\Flight.dll 2020-06-09 09:18:03.006 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 4977ECDB 00:00000000 2020-06-09 09:18:03.010 INFO EDCORE: SymInit: Symbol-SearchPath: '.;M:\DCS;M:\DCS\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Cal' 2020-06-09 09:18:03.012 INFO EDCORE: OS-Version: 10.0.18362 () 0x100-0x1 2020-06-09 09:18:03.867 INFO EDCORE: 0x00000000000AECDB (Flight): woATC::onMessage + 0x5AB 2020-06-09 09:18:03.868 INFO EDCORE: 0x000000000005244C (Transport): wAirService::getFreeCatapultsNum + 0x52C 2020-06-09 09:18:03.870 INFO EDCORE: 0x00000000000B0170 (Flight): woATC::onMessage + 0x130 2020-06-09 09:18:03.870 INFO EDCORE: 0x000000000004ACBA (Flight): wAirbase::onMessage + 0x2A 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000069DF41 (DCS): woLA::loadNewInputLayout + 0x2AAB71 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000069BA81 (DCS): woLA::loadNewInputLayout + 0x2A86B1 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000069A235 (DCS): woLA::loadNewInputLayout + 0x2A6E65 2020-06-09 09:18:03.871 INFO EDCORE: 0x000000000048645B (DCS): woLA::loadNewInputLayout + 0x9308B 2020-06-09 09:18:03.871 INFO EDCORE: 0x0000000000446794 (DCS): woLA::loadNewInputLayout + 0x533C4 2020-06-09 09:18:03.871 INFO EDCORE: 0x0000000000003C04 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x504 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000000040AD (World): wSimCalendar::DoActionsUntil + 0x1FD 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000007033FF (DCS): woLA::loadNewInputLayout + 0x31002F 2020-06-09 09:18:03.872 INFO EDCORE: 0x0000000000714313 (DCS): dDispatcher::InitDatabase + 0xDC73 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000006EAB44 (DCS): woLA::loadNewInputLayout + 0x2F7774 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000006EAF09 (DCS): woLA::loadNewInputLayout + 0x2F7B39 2020-06-09 09:18:03.872 INFO EDCORE: 0x00000000015A3B37 (DCS): AmdPowerXpressRequestHighPerformance + 0x9ECB33 2020-06-09 09:18:03.873 INFO EDCORE: 0x00000000008CE98E (DCS): uiAsyncNet::onGameStop + 0x684BE 2020-06-09 09:18:03.873 INFO EDCORE: 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14 2020-06-09 09:18:03.873 INFO EDCORE: 0x000000000006CE51 (ntdll): RtlUserThreadStart + 0x21 2020-06-09 09:18:04.214 INFO EDCORE: Minidump created. TEST - SC LANDING CRASH.miz Logs for flight dll crash.zip

Just a quick note guys - I've finished the beta supercarrier version and this should be in a future patch. Watch out for that (hopefully soon)! Supercarrier is in early days - so if you encounter any bugs please do let me know here! In the interest of keeping patch sizes down and the number of campaign files included with the F-14 sensible, I have cut this down to two 'official' versions: - Hot start, no supercarrier - Cold start, supercarrier These are the versions I will support going forward. In case you are after the cold start, no supercarrier version, I have included this on the DCS userfiles site: https://www.digitalcombatsimulator.com/en/files/3305079/ Please note that I won't be maintaining this legacy file going forward. Hope you all enjoy!

Glad you worked it out!

I don't see anything here that makes me think it should be resetting your campaign. Is the .CMP file in that exact location (the filepath in your logbook) and the exact same name? DCS seems to treat any changes as a new campaign. And not to assume anything - are you definitely trying to play the right .cmp file?

It sounds like something has been overwritten - I've only ever seen that where changing the .cmp file. You could manually change the progress of a campaign to skip to Cargo: https://forums.eagle.ru/showpost.php?p=2180489&postcount=740 Thanks for sticking with it, sounds like you've run into a fair number of technical issues!

When you say inactive - have you lost your progress? Or do you get an error?

Yoda - any info on what odd things happened when just changing the Stennis unit? The one thing I did notice when doing so is that statics linked to the old Stennis behaved strangely - resetting to the centre of the new carrier, and losing their rotations. I did not notice anything else.

Yeah something wrong with the first files I uploaded. Have updated this now - please redownload and give it a try.

UPDATED: Now includes Supercarrier version of the campaign. Download the update HERE Select the Supercarrier version of this campaign from your campaign menu to restart fresh on the new carrier - OR - Replace your existing missions with those included in the SUPERCARRIER folder to resume your campaign using the updated missions. Please let me know of any comments, bugs or suggestions!