ChillNG

Hi sorry to hear that, a lot of time was spent on testing and balancing the performance but frustratingly DCS can be really peculiar when it comes to performance. Your system sounds like it should be able to handle things acceptably, its fairly close to what I built and tested the campaign on (Ryzen 2600, 32GB RAM and a 2080, Quest 2 as well). I only fly VR and I always had good performance (apart from in the hangars, but it was always playable). For me I always ran Syria with low terrain textures, turned down the general textures, lowered visibility, pixel density etc. Obviously I don't know what your settings are but perhaps there's more performance to be gained from there, personally I run a different set of graphics settings on Syria than on other maps, knowing that it's going to be quite taxing. As for not starting in the hangars, it's a possibility, although there would be a few trigger issues to fix as well. I'd say if you've not already done so, see what performance you can squeeze out the settings first, if after that you still think there's an issue I'd be happy to send you a test version, starting outside the hangar to see if it helps, and we can take it from there.

Thanks for the feedback, yeah the FLIR issue is a new problem, the campaign was built back when vehicles lit up like they were on fire on the TGP. As you play through the campaign let me know if you think any targets are too hard to spot, I might be able to make small adjustments to their positions. I'll have a look at the other task you mentioned, I thought you could recall the nine line but possible I'm wrong on that (you can review messages from the pause menu though don't forget).

Ok thanks, not sure I ever tested that high so it'll be the bomb fall time...I'll adjust accordingly, thanks!

Thanks for the heads up, this can happen as there's a backup timer that fires a certain amount of time after the cleared hot call, just in case the player fails to trigger the off target call when egressing. I try and set that backup timer to take account of calling in further out or high altitude release with a longer bomb fall time. Where you really far out when you called in? Or particularly high? If I can clarify exactly what you did I can look at making the correct adjustment.

I wouldn't worry about a track, the missions are too long and the track will go off course well before the end. I'll jump into the mission near the end and test it and go from there.

Just looked through that thread, very strange. Honestly I'm totally stumped, I've never seen this myself in testing but there's several reports of it so there's obviously something to it although doesn't sound like its unique to just PersianFreedom. There's nothing unusual in the weather settings in the campaign and nothing scripted in the behaviour of the jets systems. I'd have to guess at it being an A-10 bug, but maybe there's a specific condition that can trigger it. Let me know which exact missions you see it in and I'll take a deeper look, if I can reproduce it I might be able to isolate the issue and make a detailed bug report.

Thanks for the review, much appreciated!

Just retested, scored 100. I checked the trigger, there are a number of conditions that must be met to get the 15 points for departure, if you miss any of them you won't get any of the points. Sure you already know all this but the only advice I can offer is to make sure all the following apply: Request Startup - get cleared before starting engines. Request Taxi - get cleared before leaving the hangar. Request takeoff - get cleared before entering the runway. Contact departure - be on heading 230 and below 1500 feet AGL. On your path out (heading 234, FL250) there will be a check-in by ATC as you reach the halfway point (departure will contact you and either say "maintain course" or "you're off course" (or words to that effect). You need the on course message to score. As you reach the hand off point, approx 30 miles out you need to be on 234 and at FL250. Once handed off make sure you don't stray into the restricted zone over the water (gunnery range). Unfortunately no way from the scoring of working out exactly which one you missed without watching you do it.

No that's intended, as per the SPINS until 5 miles out you must stay below 1500 feet to deconflict with the overhead pattern. The discrepancy with the distance is dependent on where you take take the measurement from, IIRC 5 miles is set from the end of the runway, so the distance to the beacon can be a lot more than that given the size of the base.

I'll have a check and see, I haven't changed anything since release and it was all OK so most likely you've missed something but I'll check through and see to make sure.

Thank you!

Thanks very much for the feedback, great to hear how much you've enjoyed the campaign and glad it's helped you learn new things. Feedback like this always makes the effort worth it. Steam is....well the reviews are always an interesting part of the steam experience. Some of the feedback on there is fair enough and people's opinions, so that's cool if the campaign isn't your cup of tea, but some of them are clearly down to user error or non campaign issues, pretty frustrating but goes with the territory so we learn to live with it. Thankfully there's been far, far more people like yourself with great feedback!

Hi thanks for the purchase! I'm not sure if you can create an offset from bulls, but the SA page will reference the bulls bearing/position as you slew the tdc, which is what I've always used to figure out where to go.

Hey, I've not put one together yet for Persian Freedom, but it's a good idea and Ill endeavor to do so soon.

Thanks for the feedback Brett, always appreciate the input and great to hear how much you've enjoyed the campaigns!

HI thanks for trying the campaign! There isn't anything from the mission/campaign that should stop the DL working, there aren't any failures programmed or any AI settings changed at this point so I'm afraid I can't really offer anything here to help. So long as your DL is set up correctly to start with (you should see Poodle, AWACS etc on DL throughout the whole mission) then it should keep working. I just did a really quick test at WP4 and didn't see any issues myself. I'm a bit rusty in the Hornet but IIRC slaving the TGP to radar is automatic as long as you are in A2A master mode and everything is turned on (I think).

Yeah I think it was the Maple Flag A-10 qualification missions that did it. Hopefully I'll get to it one day!

Thanks for the kind words! Great to hear you enjoyed the first few mission and I can promise you plenty more to follow! This query has been raised previously, for now I've put together a scoring guide covering the points for each mission. You'll find this here: A debrief at the end would be pretty cool, it's something I've thought about, the main thing stopping me at the moment is the time it would take to implement and more importantly test it. Them triggers are pretty simple, but the process of calling the debrief and timing it correctly and testing the combinations would be quite an undertaking.

DCS is a strange beast at times, possibly could be the number of triggers then. Good shout on TACVIEW it can be a real drag on performance, although for me definitely worth it

I'll recheck and ammend if I think it needs it. I've so far been reluctant to change thr clouds post 2.7 cloud update (coverage was less patchy after the new clouds) as I've had just as many players welcoming the challenge as I have saying they found it too challenging. You've raised a good point however, and are the first to do so, so I think it warrants another look. I'll keep you all posted.

Ok thanks, I'll double check the TOT, been a while since I flew this one so things might have changed over the updates. You're right, there was a large de-spawn event later in the mission, just made me think...do you have wake turbulance turned on? With lots of aircraft it can be a good idea to turn it off and it puts a fair bit of extra work on your CPU. But like I said, DCS performance is a lottery, I kept balancing the performance on this mission so that it worked well on my system and my testers...if only we could rely on that. Here's hoping for a multi-core solution in the near future.

No worries, glad you got it sorted .

It is to a certain extent I think, the performance lottery of DCS at the minute. The system I built and tested the campaign on was pretty similar to yours (Ryzen 2600, RTX 2080 and 32GB RAM) and I never saw issues...but I also know of people with better systems that have struggles, and those with worse that haven't. There are quite a lot of units in the campaign, especially in later missions, but not an excessive amount. If anyone more technical minded can offer more insight it would be great to hear it, to me your settings look fine, fairly similar to what I used. When you fly mission 11, if you experience any performance issues please let me know. I am trying out a version with less aircraft in the air so I can give you the file to swap into your campaign folder and see how it works for you if you need.

I would watch your altitude and position, keep high if you can and drop your JDAM first if you have one left. If you have to get low and use guns then try to maximize your distance by putting the building with the MANPAD off your nose and firing at max range. Use your wingman as well if needed. If you fail this task the mission will still complete so don't get too hung up on it either.

A bit of both, the clouds were always there as a challenge, but the mission was built pre clouds update, so it wasn't built with those exact clouds in mind. Last time I flew it though I was happy with the difficulty balance, as a late stage mission it was definitely designed to push you.