lennycutler

Mini Guns -Fix for AI I just re-installed the lua file I used prior to this update....and now my AI is correctly using their rockets and guns. See the attached file. Goes in Config/Weapons folder aircraft_gun_mounts.lua

The current listing of Huey changes for this update, now only lists fixing the audio guns sounds.

Now with today's update notes...this is supposed to be fixed. I just tested it...it is worse...the AI do not fire any weapons...not rockets or guns.. Even the suggested change to the lua file which did fix it before...has no impact now for me.

I test the fix to the A I use of mini guns. I set up a simple mission...AI claims running in..and they do...but the do not fire their weapons. Not rockets, not guns. I had fixed the problem before with an edit to the config/weapons file to the respective lua file...but even that fix no longer works. So...some please confirm if they have indeed fixed this problem...because for me it is still broken.

Perhaps it has been suggested many times before, but at the risk of being redundant, a simple suggestion. For each module, beta or non beta, there should be an official list of bugs reported and the status of bug....i.e., bug validated, fix planned, fix pending, fixed, date fixed etc. A simple Excel sheet should be maintained and be updated by the developers and posted in the respective forum section, including the DCS world section for bugs common to the "world" environment. It is up to ED, as to how to administer this, -but having this simple kind of Bug Status Report would help all the dedicated users who are concerned about the improvement they reasonably expect to see over time.

Glad, that we now know we can see the rotary for Pilot Sight brightness, best from the Co-Pilots position.....ideally, we will have a keyboard.lua entry for this, that we can use...or map to a Joystick or Throttle button....and same for the Pilot Sight Lamp on/off switch.

So...seems like the developers need to: 1. Rename the keyboard control to Pilot Sight Armed/Safe - to lower or raise the Pilot sight..it now states Pilot Sight on. 2. We need a Keyboard entry for turning on the Pilot Sight Lamp...perhaps it should be labeled Pilot Sight on? 3. We need a Keyboard entry to adjust the brightness level of the Pilot Sight and we need a animated graphical light intensity dial rotary on the sight. Am I right?

My research of the forum forces me to conclude that for any update or revision that adds new Keyboard Commands, there is no easy way, currently, to update the related Joystick, or Throttle configuration, to accept the new Keyboard commands, without using the default settings for the Joystick and/or throttle and then re-configuring all previously set input settings. Just loading a saved config...does not do the trick. So, I am asking the developers to consider making a change that can make this painless for users. Re-doing a complete Joystick config...is a real pain in the rear for most users. Can code be written that examines the current (new, revised) default settings for controllers and compares it to the settings for controllers in the User/Saved Games/Config/Input directory. The code ideally, would recognize what needed to be added from the default lua to the Saved Games lua....and insert the appropriate lines or append them. Absent this...or as perhaps an optional work around, can the developers provide some clear instructions, with an update or revision that shows the user how to copy and paste the change from the new default lua to the saved games/config/input lua file using freely available text editors. This becomes even more important, when it is common to have users purchase beta versions.... Appreciate comments from DCS developers and the user community on this.

Just made the lua file changes you suggested....It worked.... Thanks, and I am sure others will thank you... Hopefully, the developers are reading this bug report too.

I have not tried your fix (Evil.Bonsai), hoping that the latest version had fixed the A I min-gun problem. But, no, the AI mini-guns still spin but don't fire. Seems to me that this would have been addressed by now, by the developers without us users having to look for a fix in the lua files. But I will try your fix.

agree, no sound for me, in the cockpit or outside when it comes to hearing the min guns fire.

PAC on A10A Rel notes say PAC is implemented.....but I don't see it in the options....and I del my keyboard.lua to get the sim to re-create the file.....

PILOT sight has no option allowance at the moment to assign function to the joystick or throttle....or did I do something wrong....I deleted the keyboard lua file...and let DCS create it...yet no ability to remap Pilot Sight On/Off to Joystick/throttle.

In my experience you need to have a wingman, set a target via the mission editor for you and your wingman...and the diamond should appear.

I checked again after today's update...still the mini-guns show they are rotating.....but no rounds are exiting from the barrels. So, whatever the code that enables the bullets to leave the barrel and strike a target...is broken...and still needs to be fixed. Again, I am surprised that no one from DCS or the developer has commented on such an obvious, significant bug.

As far as I can determine, none of the current FC3 aircraft models, have turbine spinning animation.

thanks for confirming that this is a bug....I am just surprised that no one else is mentioning it, since it was not an issue in the prior version.

I posted this in the Huey Module Bug area, but no one as answered it yet...so maybe it belongs here. I set up a simple mission of four Hueys attacking some light armor. prior to the current version, 1.5...my flight would first attack with rockets and then mini guns. Now....they attack with rockets, and then nothing...they don't engage with mini guns. I originally set a way point action to attack the armor group. When that didn't work to get the flight to use their mini guns...I just gave the command to attack targets of opportunity. Again, in the prior version...I had no problems with my AI Hueys using their guns. I have attached the mission file. Am I doing something wrong in mission design....or is this a new bug? ps....I downloaded the module again after the latest patch...and installed...and still my AI Hueys don't use their mini-guns. Can someone please review this and comment if this is a new bug? Attached Files File Type: miz Armor Mission BTR 80 M261 HP Rockets.miz (6.5 KB, 4 views) Armor Mission M261 HP Rockets.miz

I set up a simple mission of four Hueys attacking some light armor. prior to the current version, 1.5...my flight would first attack with rockets and then mini guns. Now....they attack with rockets, and then nothing...they don't engage with mini guns. I originally set a way point action to attack the armor group. When that didn't work to get the flight to use their mini guns...I just gave the command to attack targets of opportunity. Again, in the prior version...I had no problems with my AI Hueys using their guns. I have attached the mission file. Am I doing something wrong in mission design....or is this a new bug? ps....I downloaded the module again after the latest patch...and installed...and still my AI Hueys don't use their mini-guns. Can someone please review this and comment if this is a new bug? Armor Mission BTR 80 M261 HP Rockets.miz

I am a TrackIR user...and for me the best control over the Co-Pilot and gunner aiming is to use TrackIR with Precision On...in lieu of trying for finite control with the mouse. With Precision set...I use the F12 key....I have much better control for aiming....and I use the middle mouse button to assist in alignment of the front and rear sights as needed with the gunners. I use my trigger button on the Hotas Warthog or the left mouse button to fire the weapons.

OOPs After retrying this,,,,my Pilot died, but I could actually take over changes to the Armament configuration via the Hotas Warthog....guess I was a bit pre-mature on my post.

Seems that when I am the Pilot, and I am killed, my Co-Pilot automatically takes over, which is great, however, when the co-pilot tries to use the Armament Panel, using switches binded to the Hotas Warthog, I get no reaction from my inputs...but when I enable the mouse to activate the switches on the Armament Panel, it works. Is this a current feature of the Huey and is it a bug....meaning shouldn't any input binding that the Pilot has access to via the Joystick or the Throttle, be enabled when the Pilot is dead, and the Co-Pilot takes over?

This is a wise business decision, and great customer service. This action, should go a long way to attract and retain your loyal customers, and I count myself as one of them, and I too own all of your current modules including FC3

Agree..it happens with the 190s and also the other German fighter which was provided in Beta by Kato (BF 109E)

Until recently, when I started a mission with the P51D, the Gunsight was set at the lowest WingSpan setting and the shortest range on the K14. Either I changed something without knowing how, or it was changed by default in a recent update...now when I start a new mission, by default the K14 is still set at the lowest wingspan setting, but at the farthest range setting. How can I set the K14 up, so that it always defaults to the lowest Wingspan Setting and the Lowest Range Setting?...Is there a LUA file that can be edited?