scotth6

I assume there is some sort of inhouse checks to ensure that no malicious files are included in install files? Otherwise why are people so quick to turn off their antivirus. If my anti virus labels something as "severe" and quarantines it, and labels it as a trojan, I'd at least want to look into this file before just ignoring it. nullnull

It's possible. There were remains of what looked like a truck and generator. I never saw the radar before they were destroyed either though. I'll see what happens on the second playthough. I played the first mission about 8 times before I was happy to move on . I use campaigns as learning tools so I like to repeat missions until I have mastered them.

First of all, I'm loving the campaign so far. I'm up to mission 4, and just had my first play through. I couldn't find the EW radar despite looking for ages, but I did find the generator. As lead told me to take out the radar I obviously had to keep searching, but even after they gave me the coordinates I had no radar visible with the TGP right on the mark. Also, when I dropped the JDAM on the coordinates they gave me the voiceover for a successful hit came about 5 seconds after bomb release when the bomb was till in the air. I then watched on my TGP as the JDAM just hit dirt and exploded.

On the TGP screen, press CZ if it is visible (one of the buttons on the right). I guess it shows up once you have slewed the targeting pod off the default steerpoint location. I cannot tell you it's purpose, but pressing the CZ button will correct the error it produces when you slew the TGP off a steerpoint. Apparently TMS down short will also activate cursor zero, although I have not tested this.

One question. WHY? Why would they design the sensors like this. Slewing the TGP moves all of your steerpoints? I'm failing to see any way this could be helpful or necessary.

Playing the F-16 Arctic Thunder mission 2. I am aligning my jet correctly. The steerpoints are correct when I start the mission, but at some point they become corrupted. I'm not sure if it's when I input a manual steerpoint, or when I use the TGP. Last time I flew it, I entered the manual waypoint from JTAC into an empty slot (SP19), and it all seemed correct. The TGP slewed to the correct area when I entered the waypoint. Then I am orbiting, and find the targets, but at some stage my TGP loses focus on the targets, and then it never aligns itself back on that point. After flying around a bit trying to get my TGP to slew back to the steerpoint, I realise all the steerpoints coordinates and altitudes are moving as I fly. EVERY steerpoint, not just the manually entered one. They stay in place on the HSD, but a steerpoint that should be 15NM from me according to the HSD now reads 32NM away from me. Basically everything is corrupted. It's happened twice now, but didn't happen the first two times I flew this mission. I read somewhere that the TGP can mess up the steerpoints in the F-16. Is that still an issue?

Thanks a lot. I just learned that, and I never knew it was a thing. Appreciate your response!

I have not. I guess that would be it. I feel like I've flown hundreds of missions with the F-16 and AGMs, but I'm probably thinking of air start missions, and AGM missions in the Hornet and A-10C. You don't need to boresight in the Hornet or A-10C right? I can't say I even knew you had to do that. Along with all the hours I've flown with AGM-65s, I've also watched a dozen hours of AGM tutorials and never once heard of boresighting the AGM for alignment . You learn something new every day. Thanks.

I can't figure out what I'm doing wrong. I have flown the training mission for AGM-65 on the Viper 100 times, and every time I can do every variation of firing the AGM-65, but when it comes to the Arctic Thunder mission 2, I cannot for the life of me get the Mavericks to lock onto the tanks. I am locked on with the TGP, within range, but the Maverick seeker is just stuck in a spot 300m away from where the TGP is locked. I have tried Auto and manual handoff, and have also tried Pre and Visual for the AGM-65. I cannot get the Maverick seeker to slew anywhere near the tanks, let alone lock on. What am I doing wrong? Is it a contrast problem due to the snow? If I'm locked on with the TGP, shouldn't the Maverick slew to where the TGP is locked on, despite a contrast issue? The Maverick seeker never moves when I lock on with the TGP.

I can't figure out what I'm doing wrong. I have flown the training mission for AGM-65 on the Viper 100 times, and every time I can do every variation of firing the AGM-65, but when it comes to the Arctic Thunder mission 2, I cannot for the life of me get the Mavericks to lock onto the tanks. I am locked on with the TGP, within range, but the Maverick seeker is just stuck in a spot 300m away from where the TGP is locked. I have tried Auto and manual handoff, and have also tried Pre and Visual for the AGM-65. I cannot get the Maverick seeker to slew anywhere near the tanks, let alone lock on. What am I doing wrong? Is it a contrast problem due to the snow? If I'm locked on with the TGP, shouldn't the Maverick slew to where the TGP is locked on, despite a contrast issue? The Maverick seeker never moves when I lock on with the TGP.

cef_log.log dcs.log

First time playing the mission. DCS crashed while on short final to EFRO. Faulting application name: DCS.exe, version: 2.9.11.4686, time stamp: 0x67696102 Faulting module name: edCore.dll, version: 2.9.11.4686, time stamp: 0x67651f77 Exception code: 0xc00000fd Fault offset: 0x0000000000182e37 Faulting process id: 0x305C Faulting application start time: 0x1DB628635B14B45 Faulting application path: D:\Eagle Dynamics\DCS World\bin-mt\DCS.exe Faulting module path: D:\Eagle Dynamics\DCS World\bin-mt\edCore.dll Report Id: 106a048d-4fd3-42c0-89ed-6855c2454935 Faulting package full name: Faulting package-relative application ID: dcs.log-20250109-114408.zip

First time playing the mission. DCS crashed while on short final to EFRO. Faulting application name: DCS.exe, version: 2.9.11.4686, time stamp: 0x67696102 Faulting module name: edCore.dll, version: 2.9.11.4686, time stamp: 0x67651f77 Exception code: 0xc00000fd Fault offset: 0x0000000000182e37 Faulting process id: 0x305C Faulting application start time: 0x1DB628635B14B45 Faulting application path: D:\Eagle Dynamics\DCS World\bin-mt\DCS.exe Faulting module path: D:\Eagle Dynamics\DCS World\bin-mt\edCore.dll Report Id: 106a048d-4fd3-42c0-89ed-6855c2454935 Faulting package full name: Faulting package-relative application ID: dcs.log-20250109-114408.zip

Thankyou for your answers. My next comments are directed towards DCS and ORBX. So why do 1/ DCS tell me to update my DCS to see the three new campaigns, with no mention of a purchase. Also, what is the third mentioned campaign if two of the three are for Arctic Thunder? and 2/ ORBX tell me that they are working in collaboration with Baltic Dragon and Reflected Simulations UNDER THE "FUTURE UPDATES" SECTION OF THEIR KOLA MAP SALES PAGE?! This is misleading at best and fraud in the worst case. It is one of the reasons I thought the map was good value while in early access, and why I bought it. This is not about paying people for their work. This is about misleading communication. I assumed that ORBX had made some arrangement with Baltic and Reflected for their work. Other modules have come with campaigns, especially aircraft modules, so it was not that much of a leap to imagine a terrain would come with one or two, when the developer said they were collaborating with two campaign developers to bring campaigns for the Kola map, ON THE KOLA PRODUCT PAGE!!!

Hi, Just saw a message on the DCS Launcher that there are two new campaigns for the F-16 and one for the F/A-18. I have updated, but see no new campaigns. I assume that two of these would be the ones that were to be included with the Kola Map but I may be mistaken about that. I have Kola Map installed, and I have the Viper and Hornet installed. Why do I not see these mentioned campaigns? Thanks

Just wow. After waiting several days, Microsoft got back to me about the 2 files that I submitted as being false positives, after Windows Defender flagged and quarantined them. Their response: "The submitted files do not meet our criteria for malware or potentially unwanted applications. No detection will be added for these files."

OK, I have submitted the files to MS and labelled them as False positive PUAs. They didn't get flagged when doing an individual scan on each file, so I'll go ahead and allow them. Thanks.

Have these files been deemed safe though? I'm yet to see confirmation anywhere, despite a number of posts on the matter. It's a bit disturbing that Razbam files are the only ones that have ever been flagged considering the ongoing rift between ED and Razbam.

Installing the new 2.9.6 update, and Windows Defender popped up with the following warning:

Excellent mission. Thanks!

Hey Sedlo, Just ran the updated mission a few times to test out the wingman departing. It seems to me that he just departs at a set time, rather than being triggered when I move. I can be in any location and he always leaves about the same time. Taxi roll begins around 04:18:20 and takeoff roll begins around 04:19:40. Doesn't matter if I'm 50 miles away, circling the airport or sitting at the hold short point. I always use stored heading to align my INS, would that maybe be causing me to leave too soon?

Sure! Thanks for the mission, and thanks for the info. I did try and just spot the vehicles outside, but no worry I'll keep trying. It's a fun mission to replay, and good practice for inputting steerpoints etc. As for the wingman, it's definitely not a dealbreaker, I just fly slow to the tanker and he catches up eventually. Thanks for replying.