JNelson

Did you turn the radio on?

Don't get slow, you will get hammered by they huge amount of induced drag that comes with a delta wing. Keep it on speed or faster. I also find using the airbrakes keeps the engine at a higher RPM which tends to have a slightly faster spool time for power changes. Also don't stop moving your throttle, if you keep it in any one position for too long you are likely going to overshoot what you were aiming for.

It is to prevent low effort clones where people just take the dll. The tools to update the protection for the files are all on the repo so if you are willing to rebuild the dll you can modify it easy enough. The empty tanks are on our radar and it's something that will be added before the official release.

You don't actually need to tune the radio with easy-comm's on, you just need the radio on. Currently easy-comms will set the frequency however the display will not update. I recommend flying without easy comms though because the radio is fully functional. TACAN is a workaround and doesn't hook into the CockpitBase code the same way the radio does. Unfortunately although completely possible to reverse engineer the TACAN, it is not possible to create an instance of the TACAN meaning the only way to create a TACAN device would be to write your own which would require the header files from the SDK. Which of course we do not have. ILS can be hooked similar to the radio, however one cannot tune the native ILS device to the carrier frequencies. So there is no point in replacing the existing workaround we have anyway.

Yup this is a known issue.

I think you just missed underneath.

Check the A-4E-C/bin folder for a A-4E-C.dll if it isn't there then that is why.

Let's not link directly to exe files please. https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0

This is actually the same with all modules at the moment. The LSO is calibrated for the hornet's speed/aoa.

Report any defects here: https://github.com/heclak/community-a4e-c/issues

Make sure you are on the develop branch. Then click code and click download zip.

You are right, somewhere my axis calibration got screwed up. For some reason in DCS it was mapping my pedals perfectly from 0% to 100% instead of -100% to 100%. I'll commit a change tonight if you wish to get the fix. If you don't want to get it from the repo then it will be in the next beta. Thank you for spotting this one.

Are you talking about where it overflows if you are too high or low? Because I have noticed that in the hornet too.

This must be something to do with your setup, as in the EFM code all that is ever received is 0-100% signal. Unless I fully come off my pedals then it jumps to -100%

Does the behaviour mimic mine in axis tune? Because I checked last night and although it looks strange it is smoothly increasing from zero to 100%.

IFLOLS comes up for me without using radio for both regular and super carrier.

Yea the 408 has almost 7 kN of thrust more than the one modeled. The engine modeled is a J52-P8 with 43 kN of thrust. The brakes are just really bad, so perhaps you are just not noticing that they are engaging before 50%. You can see if they are working by looking at axis tune. As soon as I touch my pedal it jumps to 0 and then increases slowly to 100%. When I let go it jumps to -100%.

AFCS Engage means you have the autopilot enabled. This will be default to AFCS Attitude mode, where it will hold the pitch and roll for when it was turned on. If you move the stick from centre (2lbs in the manual) more than 3% (15% by default for FFB sticks) it will go into CSS mode. In CSS mode the AFCS will trim for g. Once the stick is returned to centre it will drop back into attitude mode. If you force the AFCS to disengage while it is trying to roll it will disengage with that trim setting, this is a discontinuity because this is a flight sim, in reality the stick would be in your hand so this would not be an issue but in game this presents as suddenly rolling. I've mitigated some of this by making the AFCS reset the aileron trim if you disengage it by doing more than 50%, but it does not reset for +4 or -1.5 g disconnects.

I or non of the 15 something testers have experienced this. Can you record a track and submit a bug report. I suspect this is likely just your controls. https://github.com/heclak/community-a4e-c/issues The acceleration and speed are accurate as well as the instantaneous and sustained turn rate. This actually has physics unlike the SFM so stores will cause drag and add weight.

Stop holding the brakes All the comms for the carrier should work. For easy comms to switch frequency you must first call someone this is how it works in all modules. I recommend disabling easy comms and then using the radio as expected with the radio PTT. Ignore what the preview says, the brakes are indeed mapped to the full range. Check the beta-2 for a bunch of fixes including the fix to the hook bindings. You can disable the stick by clicking at it's base. As far as drag goes I can get it up to about 550 kts completely clean at 50% fuel at sea level. What is your source for 585?

That indeed would be the effect of deleting your controls. If you don't want to rebind everything the version 1.4 scooter is still downloadable.

https://github.com/heclak/community-a4e-c/issues

You are going to need to contact the viacom people to make it work specifically with the A-4.

You don't need x86 because only binaries which are compiled for the same platform can be loaded by a program. Since DCS is x64 you only need x64. We think this is required because we are using a newer version of the VC++ SDK than ED and in the newer version there is a new dll which is a dependency of some of the other redistributable dlls.

Little teaser.