heclak

Honestly, I don't think to install a free mod is as big a barrier as having to buy a map.

It would be great if some people could start some MP servers.

I've tried to code the weapon systems to follow all the procedures and quirks based on the NATOPS and information that I have (except for one tiny quirk, I'll be very surprised if someone finds it). To my knowledge, the AWRS should always be used. The AWRS should be kept on all the time as turning it off will wipe the internal memory. If you're confused by STEP vs RIPPLE as you've tried v1.2, you'll need to relearn v1.3 as v1.2 had the procedures incorrect. v1.3 is the correct operation of the AWRS and weapons (including CBU).

If you delete the entire A-4E folder then you would have gotten that. The keybindings though are in another folder. Delete the contents of the "saved games/dcs/config/input/A-4E-C" folder to clear all previous bindings.

Did you delete the older version before installing v1.3? There’s a number of files that were deleted so deleting the whole folder is the only way to update. It also solves headtracking issues. If you have done that then try deleting your keybindings as it might have been left over from the previous version.

I would love to have this. I’m also loading a mission multiple times to know what it looks like.

Not going to debate for or against. Just going to chime in from a development POV. Coding in an autopilot when an aircraft doesn’t have one is not a straightforward affair. There’s no on/off or fly straight command as the flight model calculates a large number of forces then updates the next frame. Coding an autopilot will require using something like a PID controller and you’ll probably need to tune it for each aircraft to avoid oscillations. Especially for aircraft that are less aerodynamically stable. In short, it does take some dev time.

It can be set to either. It’s as designed in the aircraft. The trigger in the A-4 is labelled as the GUNS/ROCKET TRIGGER. If you set it to ROCKETS then you’ll using the TRIGGER to fire. This is the normal procedure. The alternative is the set it to GM UNARM and press the BOMB RELEASE button. I’m not sure why there is the alternate procedure but my guess is the alternate procedure keeps the trigger available for guns.

There's definitely a problem at Google. It is now reported as a service disruption on the Google services status page. https://www.google.com/appsstatus#hl=en&v=status Edit: The Google Drive service disruption is now over. Downloading should be back to normal.

There seems to be some issues with Google Drive in general, there's performance issues in downloading other files for me too. I just tested with Chrome, if you let it hang out on the service unavailable page for awhile then it started downloading eventually. I'm not sure if this is caused by over-downloading of the file which I doubt so as I'm having issues on other parts of Google drive as well. Let me know if it doesn't work still and I'll look into it again.

Thanks for the compliment. I’m still updating it when I’m free so look out for more details.

That’s weird. Can you provide your dcs log file?

Can you provide your dcs log file?

My guess is you've set up your carrier incorrectly. Look at my guide for the carrier criteria again. You've probably not followed: The Stennis must be in its own group with no other ships The carrier may have only one waypoint and must drive with a constant speed and the speed must be greater than zero. (check the speed on both waypoints, they must be the same)

Detailed truth is you only need to rebind if 1) you manually bound your throttles in a previous version 2) you currently have problems with the throttle. The easiest solution is to just delete your keybinds and rebind them. Although if you can bind your throttle to the new "Throttle Axis" then you should be golden. When all else fails, just delete your keybinds folder and start again (i know it hurts for some people but its the easiest solution)

There's no friction/ funny wheel physics when on the carrier so wheel brakes and chocks are the solutions right now. After spawning, hold down the wheel brakes while getting the ground crew to places the chocks. We're constantly looking for ways to improve it though so we'll improve it if/when we can.

Sounds like your update isn't correct. Did you delete your A-4E folder then reinstall the entire module when updating?

Sideways or forward and backwards.

As long as you don’t perform that step you quoted, your keybinds will not be deleted.

I’ve updated my guide with some stuff for v1.3 especially the new carrier catapult procedures and weapon updates. Look for the 1.3 tag on the left side of the pages. I’ll be updating my guide in the days to come. https://docs.google.com/presentation/d/1cUH7jpAoGHm-IzUDnv_NDhiZlvX55Q9WvpgR1d9ksYY/edit?usp=sharing

I’m all for receiving and giving feedback too, as long as it’s given in a constructive manner. Suggestions and demands are not the same. Being a community module, I view feedback as the crowdsourcing the research. While I’m glad to get as much feedback as possible, I hope people can realise that as a non-full time dev, there’s only so much we can implement/change. Merker is the only dev handling all the 3d work so please be gracious with what and when it gets done. We coders also need Merker to make 3d work when we are implementing new features so his plate is rather full. That being said, I think the next update will be distracting enough....

The weapon system wasn’t functioning accurately. I’ve since recoded most of the weapon system and it’s changed significantly for the next update. AWRS functionality will be as accurate as the information I can get.

No worries. Its DCS, bizarre is just another normal day.

It’s a bug in DCS and not the A-4. ED fixed it in OpenBeta but have yet to fix it in the stable release. You’ll need to wait for ED to update the stable release.

ED announced that next openbeta patch is on Friday due to the Mig. Hopefully the fix is in there as mentioned.