VAF [136] Striker

I just wanted to thank you guys for the beautiful work on the A-10C cockpit. As someone that spends most of my time in it, I'm very happy to have this free update. I would like to add that it does look a little newish but as you posted 9line, there will be a weathered version in the future. The only thing I would say is that I was used to the overly bright panel lights and now they're pretty dim in comparison. I'm sure I'll get used to it but it would be nice if they were a little brighter, just my opinion anyhow. Thanks again!

Thanks for the comments. We've discussed using a mission saving script but it really makes stuff glitch out and crashes a lot when you try to save MP scenarios. At least that's been my experience. Best thing is to start it early on a Saturday and have it pause without clients and then just let people jump in over the weekend. That's what we do anyhow. We use the dedicated version of the server and leaving the mission paused for long periods causes absolutely no problems. We've even had them paused for weeks at a time.

Campaign has been updated to 2.0. Includes a bunch of trigger fixes along with some enhancements. Please read the notes on the downloads page.

I just wanted to say thanks for the work on the TGP, especially in the A-10C. I know you guys are working on all of them but I've seen a huge improvement in the last month or so. It's actually starting to look like I can see things again.

Yeah, Bignewy please move it. I didn't see a bugs section and the back and forth discussion isn't helping.

Really? Not very likely since I was descending at about 5 degrees at about half throttle and the probe heat was on since taking off. I'm not the only one that has experienced this problem. So you might want to leave it for someone from ED to analyze instead of putting forth your own speculation.

So we did this little fingertip training hop and as we were coming back and descended below 12k, the airspeed started reading wrong. It went down to 150 on the HUD and then the aircraft started porpoising up and down uncontrollably. I went into the burner for a few seconds and thought I had control back but it came back so bad that I tried rolling and pulling to get it to stop. It finally stopped after I blacked out for a few seconds. The whole problem starts at 36:10 into the mission and you can clearly see it in Tacview. We've been experiencing this problem mostly at low altitudes and high speeds over the water but nothing like this. VAF SUPT And Refueling Caucasus-20191207-141001.trk Tacview-20191207-141026-DCS-VAF SUPT And Refueling Caucasus.zip

The AI pathfinding is incredibly bad right now. We did a mission on Wednesday evening and I had four groups of armor columns going along the roads for the majority of their routes and the warping was so bad it made the scenario pretty much unplayable. I'm voicing my concern on this because when you are building missions that you want to have interesting and believable events happening, it pretty much requires having units moving on the ground. But this is almost impossible currently. I'm running it on a fairly fast system with 32GB of ram and the 3d disabled and it still turns into a mess. Please do something to fix this problem because having objects just sitting still is boring and we would like to be able to build missions like in past years with tanks and other vehicles moving around.

Thanks! Appreciate the follow up and confirmation.

What's happening is at anything at high elevation, like 6000 feet, they miss where you are targeting by at least 100 feet or more. I'll do a video today and try another track file.

Seems like I keep having problems with the JDAMs on the A-10C and the F/A-18C at high terrain elevations. Not having the same problem at low elevations. But in these track files they miss by 100 feet or more. Not in all cases though. I was able to hit the tunnel but not the road. VAF SUPT And Refueling Caucasus-20191112-125024.trk VAF SUPT And Refueling Caucasus-20191112-140259.trk

Yeah, only the Super Hornet can do that.

We've found that before you run this mission make sure that your windows installation is up to date first. There's nothing wrong with the mission itself but if Windows, particularly Windows 10, starts to run updates in the background, it will freeze the missions in progress and clients will appear to be stuck in space. This is not an issue with Windows 7 because the automatic updates can be disabled, at least on pro on our auxillary. To avoid any problems makes sure you are completely updated before you run this.

This problem seems to have been corrected mostly in the last couple patches. Haven't done anything different to my controls. But it definitely feels better.

No, nothing to do with Autopilot but thanks for that video. Again, not Autopilot related. I'll try to get a quick video of the problem I'm having and post it today.

I appreciate all the work you've done BD and not meant as a criticism. I would recommend putting something in the briefing panels or the main text that "please refer to the kneeboard for additional info" when it comes to frequencies. This confused me as well. I was used to seeing it in the panels and I started digging through the forums for an explanation. Just a suggestion. If I overlooked it then apologies.

RGR, I figured that was the case but thank you for the confirmation. I'll keep investigating it.

Definitely not the flaps but I did find out one thing that helps. When I use the "Y" key for the deflection override, the problem goes away. Apparently this is tied to the SAS system in some way, or at least that's how I'm finding it to work. I did a search of the manual and there's no mention of this control. I would like to assume that it's something similar to the g-limit override in the F-18? I found another thread that mentions that this is the function. But why would it affect the stability augmentation?

I've been adjusting the curves and dead zone and have toned it down some but it's still there. So you are confirming that this is how it is supposed to be? I would at least like to know if that's the case.

Nothing mapped to anything else except for the standard keyboard bindings. And the only one I'm having trouble with is the Mig29. I have all the other FC3 birds and this is the only one causing me trouble. It happened at the same time the flight model was updated to the PFM or whatever that update was back awhile ago.

OK, nothing flashing like that so it must be ready. The only thing I see in the list is "Stick Deflection Limiter Override". Is that it?

That would explain it if that's the cause. Didn't realize it need to be enabled now. Even on a hot start?

I keep having trouble controlling this bird. When I take off and try to get into stable flight and trimmed out the plane constantly rocks left and right slightly. I'm getting some nose rocking as well but not as bad. I've tried tuning the curvature but it's constant and annoying. I'm not having this happen in any other module. Anyone else experiencing this problem and what to do to correct it or is that just how the thing performs? I do have a Thrustmaster HOTAS.

That is really odd. We've run it on two different servers to test it and it's always run perfectly fine. In fact we tested it for the full duration of the campaign and it completed without any problems. I ran it on the old client shell (3d disabled) server in my office and the dedicated version on our main. Can you send me a log file in a PM? I'll give you my email address so you can send it there. Also, please provide your server system specs (processor, ram, render, no render). Are you running any server side mods? Are you running on a client machine trying to run the scenario at the same time? The mission itself is really light on objects. Almost everything is done on A2A with MOOSE and scenery destruction with MIST and Troop deployment with CTLD. The reason the file is larger than normal is because of the sound files, about 10MB (very compressed OGG files) but they are only accessed one at a time over a long period of time. You need a good amount of RAM though. If you are not running on a dedicated server with 32GB then that could be the problem. Please let me know.

I don't understand. I thought that this was a confirmed problem going way back according to several other posts.