Winston 60

This bug is back in 5 Aug 2016 Update 1.5.4.55584

We are experiencing these difficulties when Clients are shooting at AI airplanes..... not just Player vs. Player. Are you investigating this as well?

That would be great! Please upload.

Mission two: "Beslan's Bombers" has been posted. See the first post.

Wanted: One additional playtester for the Steel Winter single player missions in the A-10C. Qualifications: 1. Must know the "C" model well and how to effectively manage two AI Wingmen. 2. A native English speaking pilot is preferred as these missions are HEAVILY voice acted. (OK though if you understood the voice acting in mission one) 3. Must be able to play the mission and return to me any comments and/or bug reports in 2 to 3 days max. Interested pilots please send me a PM with the following info: 1. Your native language. 2. How well do you understand spoken and written English? 3. How proficient are you in the A-10C? How long have you been flying it? 4. Can you test a lengthy mission in 2 to 3 days from when I send it to you and return results to me?

Highlight the TrackIR Z axis box and select "default". Then restart DCS. :pilotfly:

Mission two uploaded. See the first post for the briefing and links. Enjoy!

Is there a way to mod the runway and taxiway lighting in ver 1.5.4 to be brighter/more intense and visible from farther away? I just can't see them until I'm nearly right on top of the airbase! Perhaps some .lua file adjustment?

Many thanks!

Sorry..... this belongs in the FC3/A-10A section. Would a moderator kindly move it please?

ED... Could you please get the cockpit gauge lights to work in the A-10A for the mechanical compass and "G" meter? (the ones on the front cockpit frame) Can't see 'em at night!

Low or high, doesn't matter. One missile will never hit, but two will always get it! I prefer to launch one missile at a nearby SAM and then another after a few seconds at the Tor. He gets busy with the first one and the second one gets him every time! :smilewink:

I'd love to do that! Exactly which .lua file would I edit?

Thanks guys! It's nice to know some are still flying the A. Mission 2 for multiplayer is now in testing. After it's released I'll begin the modifications to a single player version and get it out for testing. Looks like it will be another few weeks for the next single player version of the series.

After suffering this from day 1 after the initial 1.5.4 patch, I'm leaning towards believing that it's a netcode issue with the "changes" ED recently made starting with the 1.5.4 beta and then the release 1.5.4 1. Multiplayer. New extrapolation algorithm 2. Multiplayer. Reworked aircraft motion algorithms to improve resistance to lags. After missing so many gun attacks from offset angles where I can see the bullets pass directly through the target at very close range, I'd say the above two items need a lot of work!

If you get overlapping SAM indicator diamonds, try to approach from another angle, or turn away somewhat. This may separate the targets if they are overlapping. I have a lot of trouble with the SA-15 Tor SAM vehicle. It shoots at and hits my anti-radiation missiles with great accuracy. Try to shoot two missiles at it, or one at a nearby SAM followed by another shortly thereafter at the Tor. It can't hit two incoming missiles that are fired so close together.

+1 Yes, this needs improvement along with the current dim runway lighting. You can't see the airports until you are nearly over them.

I had this axis in "red" in all my modules since the initial 1.5.4 release patch. I solved it by highlighting the TrackIR Z axis box and selecting "default". That was the only way I could get the Z axis to work. The "red" highlight was gone after a DCS restart. I had to do this on all modules.

I have this "flipping" as well. I didn't notice it until I tried dog fighting in an F-15C tonight.

We sure wish ED would comment on this. Their deafening silence leads us to believe that multiplayer is not high on the "To Do" list? :hmm:

Thanks for the info. Has someone from ED commented on this yet? It would be nice to know that they acknowledge this problem.

Here's a tip if you're having trouble with the SAM's in mission one. Read at the risk of spoiling some of your fun.

TrackIR is much more stable for me now since today's patch, but still if I look well away from the screen for too long I still get the "Head tracking disabled" message and TrackIR stops working completely and won't recover. I have to restart TrackIR and restart DCS. Don't know if that's the way it is should be but the best thing I've found to do is "pause" TrackIR when looking away and then unpause when returning your eyes to the screen. No problems then.

Thanks ED for fixing TrackIR in this latest release patch. All my TrackIR problems are gone and I'm no longer getting the "Head tracking disabled" message unless I look away from the screen for too long then I have to restart TrackIR and restart DCS. Is this the way it's supposed to work?

Multiplayer missiles, Client against AI airplanes, there seems to be an accuracy problem. Is this a product of the new netcode changes? Tonight our Squadron as a whole got less than 10% hits in F-15C's with AIM-120C's and AIM-9M's as client players against a variety of AI aircraft (MiG-23's, MiG-29A's and MiG-25's). We flew the same mission in our rotation that we previously always got 50% or higher hits. Single player seems OK so is this now a netcode issue? All was OK in release 1.5.3, then the problem started in the first release of 1.5.4 and then now this one. There seems to be something terribly wrong in multiplayer now? What has changed here since 1.5.3?