Spectre_USA Posted March 14, 2011 Posted March 14, 2011 So, I somehow finished Devil's Cross with a win, so pressed on to Georgia Hammer. I'm digging it, got through the first 3 missions, then had to abort early, as my wingman got waxed before inflicting damage, and I could not get refueled/rearmed/repaired at Kobuleti, and my Rudders were damaged. It popped me onto mission 4-2, I assume from the brief, and as soon as I got in the `pit, lined up, nothing was working. Clicking anywhere produced a "ding!" noise from the OS. Great, we have an error. Alt+Tab to the desktop, fire up Task Manager, switch to DCS, and an error apperars; I do a retry or two, no help, and settle on ignore. Twice. After the 2nd time, the sim won't re-draw, so I hit escape, right arrow once, and get the debrief. Full shut-down, go back in, am presented the next mission. Use mission planner to get my "WA" paint scheme, and my usual Mavs and CBU loadout. Fly. Cockpit. DING! But this time it re-draws, set switches, and I'm off. Climbing to waypoint 2, no responses again. There is the same danged error message, hiding somewhere, but brought to the fore via Crtl+Alt+Del, switch to. This time it won't re-draw, so `ESC,' right arrow, enter. Debrief shows takeoff, campaign shows I've flown 6 missions, and my success rate is dwindling. Next mission gets me back to 4-1? Ouch. Is there a LUA I can alter to get past this error, and not get stuck in this loop? [sIGPIC][/sIGPIC] A tale of 2 hogs
Forza42 Posted March 14, 2011 Posted March 14, 2011 i had exactly the same issue on mission 4. but it s not a crash, just an assert. You can skip it each time it appears. finally, i ve finish the mission while i skip this assert ... around 30 times :D i m actually on mission 9 and i ve never had this assert again, only on mission 4.
Hack74 Posted March 15, 2011 Posted March 15, 2011 Check out this thread: http://forums.eagle.ru/showthread.php?t=68198
Spectre_USA Posted March 15, 2011 Author Posted March 15, 2011 Check out this thread: http://forums.eagle.ru/showthread.php?t=68198 If I may paraphrase; I can confirm that the this is the cause of the crash in 4-2-0 as well, to fix it: - Load the mission in the editor. - Open the All Units list and select the USA AWACS - Change the call sign to something else (I used Overlord) - Save and you are good to go. I am off to give it a go. Many thanks, Hack-man... :thumbup: [sIGPIC][/sIGPIC] A tale of 2 hogs
Recommended Posts