Kazius

Thanks for the info. And I did do searches but only 3 posts came up related to Bear Trap that I could find and none of them were regarding my issue. If people posted under some other campaign name that I don't know of then I apologize for not knowing what campaign name they posted under. Also, searches for FC3 F-15C Mission 2 came up with pages upon pages of search results and I wasn't going to read through thousands of results.

Today I decided to try the F-15C Bear Trap campaign. On mission 2 I am tasked with TARCAP. AWACs never reports anything closer than bulls 40-50 even when I tell the SEAD to push. After repeated attempts, the SEAD is always shot down by SAMs, AA and other guns from land vehicles. Any tips to help the SEAD not get shot down by ground to air attacks every time?

SSAA is another form of Anti-Aliasing. Likely added since MSAA is not compatible with Differed Shading. SSAA does have a higher performance hit than MSAA but its likely they didn't have a choice.

Found a bit of an annoying bug on Push 12-1 for Georgian Hammer campaign. The two objective groups are code named Ram and Giant. Ram makes it to his final objective waypoint. However, Giant seems to run into a pathing issue and units just start to circle a building over and over and over again. Tried the mission 2x. First time I think I waited an hour (Went for supper while waiting). Second time I increased the time scale and turned on F10 viewing so I could see what was taking so long and recorded a short video of the pathing issue. https://youtu.be/qhZFKySPvpM This bug prevents mission completion. Tried to fix it myself by moving the waypoints so Giant doesn't try to drive through buildings, however the game won't let me save the mission.

Just ignore this. I just found a post where someone explained that the campaign can't be edited but can be bypassed by editting the logbook which is actually better because I really don't want to fly this for a 3rd time when I was already successful twice. Found a bit of an annoying bug on Push 12-1 for Georgian Hammer campaign. The two objective groups are code named Ram and Giant. Ram makes it to his final objective waypoint. However, Giant seems to run into a pathing issue and units just start to circle a building over and over and over again. Tried the mission 2x. First time I think I waited an hour (Went for supper while waiting). Second time I increased the time scale and turned on F10 viewing so I could see what was taking so long and recorded a short video of the pathing issue. https://youtu.be/qhZFKySPvpM I tried to fix the mission by modifying the waypoints so the tanks don't end up pathing near buildings to much. However, it won't let me save the mission file. Are Georgian Hammer campaign .miz files locked? Is there a way to unlock them so I can fix it myself? Or do I have to bug report it to ED and wait for them to fix the campaign? I reported this on the bug report forum but wondering if anyone knows a way to fix this on my own as I don't want to wait months for a fix just to continue the campaign. Decided to add a screenshot to help explain what I mean by it won't let me save. Even tried to save as a different name which apparently won't display cause I put it on google drive. https://drive.google.com/file/d/1p_vP9rRU3284gkQcMg3c3gOgGq_p11oN/view?usp=sharing

I am not 100% sure but I think I fixed my JTAC issue. When I stopped using the 2.5 Open Beta version, I only copied the customized keybinds folders, my missions and my logbook file into the new DCS folder in saved games. The JTAC is now working, so I am assuming something bugged out and the clean files fixed it.

What mission are you running. Some of the big multiplayer missions with tons of npc aircraft / and ground targets do take way more memory. Pretty sure some optimization will help these but if your playing on a mission that was created for large groups of players, maybe wait on those until code optimization is done and do small missions. I have played on some multiplayer maps people made that take up 12GB of memory and on some custom missions I made that are small that barely use 5GB of memory. Hope this helps in the short run.

My new SSD arrived today so fresh install. I will try the campaign on the weekend and see what happens. Maybe my installation became bugged over time.

So I checked which mission I recorded that on, it was Georgian Hammer Push 5-3. I also noticed the airport and looks like I was a bit off the beaten path, but not by to much. Thing is, in most other missions I can even contact the JTAC right after taking off from the AFB and even if I am 30nm away he will give me correct coordinates. It only seems to be the Georgian Hammer missions that are messed up. I will try to record a better example in a few days. It happens every time no matter what my location is.

I was circling in between the fence waypoint and ip waypoint on that one. On Push 8-1 which I was just doing yesterday I was basically over top of the target waypoint beyond the fence and very close to the predator JTAC on that campaign and that JTAC was still giving coordinates 870 nautical miles away. I am also playing this in beta 2.5... Perhaps I should try in 1.5.8 and see if the same thing happens?

I am currently on Push 8-1 and in this mission as well as 2 or 3 previous missions the JTAC seem to be giving me coordinates 400-900 nautical miles away. See the video I recorded to help show what I'm trying to explain. https://youtu.be/_pZgBLHmkIE So question is, does anyone know if I can fix the JTAC for the Georgian Hammer campaign missions so they give correct coordinates? I backed up the missions folder for campaigns and tried to edit the mission file and moved each unit a couple feet each in case it was because of the mission being super old and maybe elevation changes happened in updates, but that didn't fix it. So I'm hoping someone else might have some ideas. Any help people can give is greatly appreciated.