nomdeplume

A0/A1/A2 is the radar operation mode (off, PPI, B-scope). The T0/TV/T1 is the trigger on the front of the stick. I don't know why you can't assign it in the controls menu, but that's what you need to use for operating the Maverick, as well as doing own-position and radar fixes. Basically you hold it at the first detent (D1) to enable slew-control (using the radar stick), and then pull it the second detent (DV) to command it to lock. Releasing the trigger will cause it to go back to boresight.

I consistently get freezes for a few seconds when switching to BER, but haven't had it crash. Normally I do this on the ramp, but I think I've done it while still on the runway with the same result.

Yes, look in the Radar stick category. They're listed as T0, T1 and TV, I think. It's a two-stage trigger; T0 represents the 'unpressed' position, T1 is the first detent, and TV is the fully-pressed position. If you want to actually use it with a two-stage trigger, you'll need to modify the command configuration (or find one of the posts in this forum with the updated mapping). The existing mapping is for a 3-stage switch (i.e. a button each for T0 and TV, and releasing puts it back to T1, which isn't super useful for most people). Edit: this thread has the modification needed for using an actual 2-stage trigger for the radar trigger. Second page has a modified file if you just want to replace it rather than modify it yourself.

I believe it's because the canopy is not drawn when the pilot is not in the aircraft. Related to this bug: AI Viggen losing canopy. So it's also a problem for static aircraft and AI aircraft set to 'uncontrolled'.

Just some leftovers from the development/testing process, as I understand it. https://forums.eagle.ru/showpost.php?p=3019310&postcount=11

So I bork bork borked up a take-off and came down pretty hard just after starting the landing gear retraction. Got back in the air and everything was fine (no landing gear light on the panel, no aerodynamic effects) so I figured it hadn't caused any problems and the gear are just really robust. Later I happened to check the external view and saw my left main gear was still extended. Deployed and retracted the gear again and everything worked fine - so it was only the graphical model which considered it extended, I guess. Didn't try landing on the single gear to see if the sim actually recognised it as down. But my landing was normal with no ill-effects. Attached is a cockpit view showing stick position (normal) and lack of indicator lights, and an external view of the same scene.

The manual also says radar ranging begins when the calculated range is less than 7 KM. So if the target elevation is wildly wrong then it might not think you're close enough to switch to it. It also requires you to have a certain minimum dive-angle, which might be steeper than you think. But: the AJS-37 just isn't designed for engaging 'targets of opportunity'. It doesn't have the fuel capacity to loiter waiting for a target to show up, and even if it encountered something on the way to its target it's unlikely it would just change its mission right there and then. If you've sent strikers to an area you probably want them to hit the planned target... So, it probably just wasn't much of an issue in the real world or a design goal. I would guess if it came up, it would be handled either by switching to the backup (fixed) sight and conducting a "standard" attack (see e.g. the F-5E rocket delivery) using gut feel more or less; or they'd* use a map to work out the terrain elevation and derive the QFE from that. * - they might get the QFE setting from someone else, e.g. ground units in the area, or someone back at base could do the calculation or reference weather charts for them, etc.

The read-only flag only applies to files, not folders/directories. Not sure about Windows 10 but Windows 7 actually tells you that - "(Only applies to files in folder)". If you look at the properties of a folder it'll show read-only in an 'indeterminate' state; clicking it to set or clear the checkmark and hitting apply will let you recursively apply it to the files in the folder (and subfolders).

Not TV fix (radar/flyover fix), there's a separate button in the "Navigation" category called "Reference button" in the controls list. When on the ground prior to take-off it will set your heading. You're supposed to press it once you're lined up (accurately) on the runway so the navigation system can have a solid idea of your heading. It also picks the heading up automatically on take-off, but if there's crosswind or you're just a bit slippery during your run it won't get a good reference. While you're in the air, the "Reference button" will update the altitude reference (shown by the 3 pairs of bars) to your current altitude.

Press the Bx button on the waypoint selector panel, then press the waypoint number on the data input panel (numeric keypad). So Bx8 = Bx button, then 8.

You can add the Bx waypoints from the aircraft properties. It's the tab with a square box on it, and only appears for player or client aircraft (not AI). If you specify the time on target for the waypoint in the editor it will be loaded as a target waypoint. I don't think you can input popup point data in the editor. Attached is a screenshot of the waypoint ETA and nav targets tabs, probably easier to show than try to describe.

Just a note for the rotaries, this applies to using the mouse scroll wheel to change the values. If you use the 'click & hold and drag up/down' method then it enforces the limits properly.

Worked perfectly fine for me. Did you verify in external view that the re-arm was actually done? Did you get the 'rearming complete' notification? If so, what specific weapon mix did you switch between? I just did a little test sortie with 2x RB-15F and then landed and re-armed with 4x Maverick and was able to fire them without issues.

First flight using a custom mission, following an AI AJS37 on a little trip across Georgia. Noticed that the RWR gives indications from that Viggen regardless of my position relative to it. Flying behind it right now and I'm getting indications from the front left or right as appropriate. For completeness: there are two SAM sites in this mission but they're both far away and masked by terrain, and to my southwest + southeast (so to the right in this screenshot). I expect this can be reproduced with just the AI aircraft, though.

I think this is the relevant error: 00041.813 ALERT LUACOMMON: Error: GUI Error: [string "./Scripts/Input\Data.lua"]:1612: attempt to index local 'defaultCommand' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./Scripts/Input\Data.lua"]:1612: in function 'getCommandAddedCombos_' [string "./Scripts/Input\Data.lua"]:1668: in function 'getKeyCommandDiff_' [string "./Scripts/Input\Data.lua"]:1687: in function 'getKeyDiffs_' [string "./Scripts/Input\Data.lua"]:1750: in function 'saveDeviceProfile' [string "./Scripts/Input\Data.lua"]:1872: in function 'saveChanges' [string "./MissionEditor/modules/Options\TabViewControls.lua"]:82: in function 'save' [string "./MissionEditor/modules/Options\TabsView.lua"]:211: in function 'onOptionsSaved' [string "./MissionEditor/modules/Options\Controller.lua"]:65: in function 'optionsSaved' [string "./MissionEditor/modules/Options\Data.lua"]:151: in function 'saveChanges' [string "./MissionEditor/modules/me_options.lua"]:98: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:318: in function <[string "./dxgui/bind/Widget.lua"]:313> Full log file attached. I deleted all logs before starting the game, so this is the result of simply: Launch -> Options -> Controls -> AJS37 -> Clear category -> OK.

Did you make the unit actually transmit anything?

And to add to renhanxue's comment, when he kicks in the afterburner (1:15 of the ARAK pop-up attack video) you can see the afterburner stage indicator lights on the right side of the dash - he overshoots and lights stage 3 for a moment so you can see all 3 lights until he throttles down a bit to leave it in stage 2.

The AJS can carry countermeasures in an external pod; there's also an external pod with a jammer. They use the wing hardpoints so you can't carry the famous anti-ship missile with them - which is presumably why only one would carry the countermeasures, and lay a 'chaff corridor' to distract the enemy radars while the other aircraft carried out the attack. As far as I know in DCS you can't spoof missiles that are locked on to another aircraft, so unless there's changes made to the system or some special provision is somehow made for the Viggen, then I don't think this tactic would work. I think what basically happens is every time an aircraft emits a flare or chaff, the game checks if any missiles (and maybe aircraft radars?) currently have a radar or IR lock on that aircraft, and then randomly decides (based on the missile's sensitivity to countermeasures) whether it has broken the lock or not. There's probably also a cooldown period before the missile can start trying to lock a new/same target again. Edit: this thread has a bunch of info about the ECM pod and RWR.

The manual does mention that the rear fuel tank was installed on some aircraft with clipped wings, and that using the full-length wings was prohibited on those aircraft. So maybe when the clipped wing variant is available the rear tank could be available on those?

Looks like this was probably just a bug, which should be fixed now: Might be worth giving it another go after you update.

Did you add a trigger to check if the cargo is in the unhook zone?

I wouldn't get too excited, the DCS EW environment is very simplified and while Leatherneck can simulate the Viggen being jammed by other sources in novel ways, I don't think they're going to be able to impose any new jamming methods on the rest of the game environment.

And the stable 1.5 release as well (same version as open beta).

No, 2.0 has not received an update this week.

Maybe check wind conditions and such? I have a theory that maybe the rope breaks when it intersects the helicopter fuselage, but haven't actually tested that's the case. I've normally tried to keep it around 150 kph but have pushed it just over 200 by accident without issues in some situations. I don't think I've ever seen it break it only 100 kph though. I've used a variety of the new cargo types up to maybe 9,000 pounds and always felt pretty comfortable at 150 kph. But maybe lighter loads are actually more prone to swinging?