heclak

I’m waiting so much for ED’s bug fix first.

I don’t recommend using the alpha except for internal testers. It should only be used for testing as some changes that we make through the version may mess up key bindings, etc. Testers are expected to be willing to redo bindings, reinstall, etc. We are unable to provide support for alpha versions.

Delete both the headtracking and trackIR folders in the input folder of the mod.

Which mode select? If you provide a list of missing control bindings then I can add them for the next release. Sorry for the trouble but it’s too difficult to check for every binding so we’re relying on community feedback.

You can’t join any multiplayer server that doesn’t have the mod installed/enabled. This applies for any major mods. But you can leave it installed and go to the module manager to toggle the module on/off when you in Single player or Multiplayer. Disabling the module in module manager will let you join servers. There is no need to delete the files/uninstall.

I'm not sure if this is still a work-in-progress. But there is a UV texture glitch for the weapons selector where it says RB75. I also recall a mention of increasing the texture space assigned for the weapons selector label, is that still happening?

The default DCS intercom system with the ground crew has it own checks which demands that canopy be open. I’m not are which commands must have the engines off right now.

NOW AVAILABLE: Community A-4E-C Mod Here's the link to the issue tracker on Github. Anyone can view it but you'll need to create a free Github account if you want to file a bug or comment on something there. This is the most visible place to get the attention of the dev team. https://github.com/Merker6/community-a4e-c/issues And here is the link to the Discord channel that Merker posted in the last official update. Discord is a chatroom style community where we discuss all the development for the A-4E. It is the best place to stalk the development progress but also a great place for others to provide information and resources to help the development along. https://discord.gg/VEmJWVP To be honest, everything on your list are things that I would hope to see implemented as well. It's just a matter of time.

I was coding the Shrike lock tones last night and streaming it on Twitch. Here are some highlights of the very early work-in-progress of the Shrike tone. I might stream more coding sessions as the live feedback and discussion of how some systems should work was very entertaining. Do let me know what you think. PS. I don't think it is possible to directly embed the video links here. Or maybe I just don't know how to yet.

Hi Norbot, DISCO is pretty much correct about those features. Shrike tone is a working in progress but not sure if it will make it this patch yet. And it is best to request the other features (IFF, Seat, Ejection Seat, Oxygen) via Github. That way the team knows that it is something that the community wants and we can prioritise it. FYI those are things that I have been considering to work on but wasn't sure if it was wanted enough by the community to prioritise.

I think TACAN is already included in the next release. I didn't code it so I can't say how it works yet.

You can still use step mode and click it multiple times.

Those are the three systems that definitely cannot happen. Those need SDK access so I’m asking about other systems besides those three. The AWRS is kinda bugged in 1.02. I’ve rewritten most of the logic for it for the next release. In 1.02, quantity is ignored for ripple mode and you cannot limit the number of bombs dropped. You just have to listen for the number of bombs dropped then let go of the pickle button. This is no longer an issue in the current dev build for the next release.

Here’s a question for everyone. What would you like to see worked on/finished/added to the A-4E with the exception of the following systems: - Radios / ATC - Mid-air refuelling - TV/Laser guided weapons Edit: These three systems cannot happen without SDK access.

I know there are some keys that are missing key binds. One of the to dos is to do a pass on key binds. To everyone, it would be great if you could feedback on missing keybinds. I’ve already added axis binds for some of the knobs. This would help a lot to make the next release even better for everyone.

Well. If it is a standard feature in other modules then we should try and include it. I’ll take a look at what standard views are in the other modules and I’ll see how to include them.

Oh. Didn’t notice it myself. I’m sure someone on the team can add it for the next release. Since I’m not very familiar with snap views, would you be able to describe what you’re looking for in the issue tracker? Any specific views? https://github.com/Merker6/community-a4e-c/issues

Please check my reply to mud. Sorry I’m on mobile and not sure how to quote multiple people.

I don’t have VR so I didn’t know of that problem. I’ll need to see if any of the other coders have VR. Would someone with VR describe that in the issue tracker? https://github.com/Merker6/community-a4e-c/issues Posting on the issue tracker is best as the devs would be able to ask further questions if needed. And the ability to post screenshots. For me it’s rather hard to remember to work on stuff that isn’t already on the issue tracker. So posting any issues you have there is the best.

What is the VR issue? There wasn’t any mention of problems in VR in the bug reports.

Cockpit lights was a work in progress for 1.02 but should still be functional. I think the console knob controlled most of the lights. The toggle switch next to it is bugged but should still be able to turn on the lights. The light were revamped and is totally functional for the next release.

AN/ALE-29A Chaff Dispensing System Here's something that I just finished for the A-4E. Its the implementation of the AN/ALE-29A Chaff Dispensing System. This will be tied into the RWR to automatically release a chaff pattern when a missile launch is detected. This is the automatic mode on the countermeasures panel. Changing the settings on the programmer can only be done the mission editor or by the ground crew when on the ground and engines off (via the kneeboard). Here is a video of me testing the sequence with flares for visibility. In the final version, this will only work with chaff as there is no IR warning on the A-4E. Ejad62hrGmo

That's interesting. If that happens again do you mind sending your log file? I know some people who fly multiplayer with the A-4 but have never reported such an issue. So your log file will be important to take a look at what happened.

Can’t think of any reason until it’s an error with Mission creation. The only issue I know with airfield is a crash when loading the A-4 on Nellis AFB.

Those having TrackIR issues just need to delete the headtracker and trackir folders. There is no need for those files.