Aernov

My DCS_AJS37 folder contains nothing at all, no .ini, no hidden files too. It was like that after all reinstall and repair attempts. Edit: and I never went in multiplayer with the Viggen, I have attempted quickstart missions and self-created training one. No special characters in my name, and my DCS is in English.

It won't let me create folder named "Saved games" in my user folder, it says that there already is a folder with the same name and offers to merge newly created one with already existent (so, system does not care for folder name language, which was already confirmed by "%USERPROFILE%\Saved Games\DCS_AJS37" search path working). I will continue messing with folders and reinstalling/repairing. Was something changed in module loading algorithms lately? Viggen worked fine on this exact machine this spring/early summer.

It works, taking me to the folder I have created. But there is no folder named "Saved Games", mine is in Cyrillic. Can this be an issue? Earlier Viggen worked fine with the same folder names.

I have created DCS_AJS37 folder in Saved games (which is named "Сохранённые игры", since I use Cyrillic as system language), no effect, CTD occurred as before (it was crashing before I deleted this folder, which was empty anyway). About two-three months ago I have used Viggen without an issue. dcs.log-20201022-185617.zip

I am getting the same CTD now, tried reinstalling the module, clearing cartridge data folder (deleted entire folder, even though it was empty), repairing DCS, no effect. I have even deleted custom liveries, which didn't help. dcs.log-20201022-130027.zip

When disembarking (from Mi-8 for example), soldiers are placed close to each other, and, when receiving order to move somewhere, they can not assume selected formation and spin around in one place. Same occurs with tanks too, but you can move tanks apart manually. With sufficient distance between individual units move orders are executed normally, units have enough maneuvering room to form column/line/whatever formation is selected.

DECM pod operation mode indication lights (P JAM and CW JAM) on caution/advisory panel stay on when turning the pod back from RCV to STBY and OFF. Here is my test procedure (in sequence, with numbered illustrations): 1) Initial setup - AV-8B with DECM pod and SA-11 battery, Harrier is flying towards the battery, SAM radar is detected by RWR. Same behaviour can be observed with any number of radars, regardless of their type, in single- and multiplayer. 2) DECM is in RCV mode, P JAM status light is ON; 3) DECM in STBY, P JAM light stays ON (I don't know if actual jamming continues or not); 4) DECM is OFF, P JAM light still ON; 5) RWR in LIM mode (no radars on it's display, but Snowdrift search radar is still operating), DECM pod stops jamming in RCV mode (correct?); 6) SA-11 is locking Harrier, DECM in RCV mode is jamming in pulse and continuous wave modes (P JAM and CW JAM lights are ON); 7) DECM turned in STBY, both lights are ON still; 8) DECM is OFF, lights are ON; 9) DECM is OFF, RWR is OFF too, both lights are ON anyway. If DECM is then turned to RCV with RWR off, no jamming will occur (both lights will extinguish) regardless of remaining radar lock from SA-11 (correct?). If DECM is turned to RPT, both modes of jamming will be active and indicated, but, on the way to STBY, control knob is placed in RCV mode anyway, thus "resetting" jamming modes and indication. In conclusion: it seems that indicator lights are displaying same status that they were showing before turning DECM pod to STBY and subsequently OFF (or to BIT, since pod control knob is going through BIT position on the way to STBY). Also, if ECM control knob is moved to STBY or any other mode without DECM pod equipped, NO GO lights will remain ON even if knob is returned to OFF, until pod is equipped.

Glad to help, Harrier is one of my favorites in DCS and I want to see it made complete one day. And it's really good to see it being actively worked on, so thank You.

I've been learning use of JDAM with DMT TV designation (never knew this was possible, always used TPod and laser ranging. Latest open beta, no mods or scripts, just liveries, but this test was conducted with default one), and noticed the following: 1) First TOO designation (designate waypoint from EHSD to slave DMT on it, slew camera around, find target, WP increment hold) went without trouble for GBU-38, LAR appeared on EHSD, but accuracy readout on the HUD seemed to be "reversed" (it gradually went to 100 at the outer edge of LAR, then dropped to 0 at the middle distance between max and minimal range rings and increased back to 100 close to minimal range). I've tried dropping bombs at both outer 100 accuracy zone and the inner one, in the first case bomb was trying to fly almost horizontally and was actually holding nose up at the end of trajectory (and landed with good accuracy), and when dropped at 100 accuracy close to min range the bomb was falling almost vertically, fighting it's forward momentum to stay on target (and scored a direct hit too). When dropped in the middle of LAR (with 10-0 accuracy readout), bomb flies perfect trajectory and has best accuracy. 2) After the first drop (or sometimes at first designation attempt), DMT TV screen went black and target point was shown on EHSD and HUD as located at 000 course and had no distance readout. I tried to turn on it, but DMT did not turn on and there were no marker on HUD. Pressing NWS/Undesignate/FoV toggle button did not reset DMT camera, and EHSD desg OSB was returning me to the same "phantom" target. To "reset" this I've held WP increment button again thus designating this "phantom" point the TOO for the next JDAM (range ring appeared on HUD, no visible LAR on EHSD) and then pressing Undesignate button. Then I was able to do the normal procedure (find target with DMT, WP increment hold, drop in LAR). 3) For the newly added GBU 32 no LAR is displayed on EHSD, everything else seems to work as with GBU 38 (with accuracy numbers reversed). AV-8B JDAM.trk

Oh, right, I'm just dumb ) All is correct, sorry.

I own A-10C and just bought an upgrade which shown announced $9.90 and like 800 miles price on store page, but I was charged for and paid 9980 miles instead, which is full price of A-10C II. There were no warning about lack of discount if it is being bought with miles (at least I haven't noticed one). Is this intended?

Deleted all the bugs from this post, sorry. Missing features are: - EHSD overlays are not complete: OVL2 (planned route display) and NSEQ route display are operational (although sometimes I get a crash when fiddling with NSEQ), but OVL1 (the one that supposed to display SAM ranges and other SA information) only displays AAR zones that has been set in mission editor. - Snakeeyes and Mk.92 Air are always deploying their braking devices, even if you select low drag release mode (I think it worked as intended some time ago, so, probably, bug).

I haven't flown I-16 for almost a month, got in it in Syria for some sightseeing and encountered this. Plane still works, cold start and all, but instruments aren't working regardless of start type (cold/hot/air). Also, cockpit doors textures are visible as if the doors are closed even if they are not.

If you press airbrake in/out switch while on ground, airbrake won't retract automatically with the landing gear after takeoff. Which may be realistic since you have "moved" the switch controlling it, I don't know. But the same occurs if you use airbrake in-flight, land and then take off again (without touching the switch on the ground). It won't really interfere with takeoff itself, so once I have flown almost an entire sortie with my airbrake half deployed, wondering why I can't accelerate to the usual speeds :doh:. So, PSA: after takeoff check your caution lights panel.

Strange, I was able to update INS via OBL (radar slant range), and the waypoint cross moved closer to the actual WPT location (not exactly on the landmark, which, I assumed, was because of coordinates "scale" (degrees/minutes/two digits of seconds do not define a precise point)). Before update this cross was really far away (like 2-4 nm away after 2.5 hours of flight), and after - not farther than 200 meters.

Most wanted "feature" for me and many, many others is an introduction of REDFOR aircraft, russian in particular. Be it Yak-1B, MiG-3, Il-2, Su-15, Su-17, Tu-28, not even dreaming about Su-24/25 or early MiG-29/Su-27. I think we had enough "blue" winged computers for our lifetime.

As shown on the screenshot, 1B and 8B pylons with AIM-9 missiles on are lacking any texture, all official (and unofficial) liveries have this problem. Also, AIM-54s seem to have the same 54C texture regardless of their model. And, I don't know if it is correct or not, but official VF-74 Adversary livery has pylons and external tanks (and maybe TCS pod) in different color, which is minor yet kinda triggering thing.

And it is not an issue still. What's the difference between all of us getting, for example, Supercarrier at like 31st of May and us getting it at 31st plus some select few content creators getting it a few weeks earlier in a pre-release state? I assume that majority of us do not want to be unpaid beta testers (even though open beta is becoming the new stable) and get unfinished thing slightly earlier. At least that is what feedback/poopstorm generated by the last big patch suggested strongly. I don't mind this policy of press releases at all, it is a little more of module testing before the update breaks all of multiplayer, and a teaser to build up interest.

Choosing between another Bluefor flying computer with slightly different looks, loadout and functionality, and the first full fidelity Russian/Soviet more-or-less modern plane? For me it is Su-27 without any doubt.

Yeah, holding OFF for a couple of seconds worked, thank you. Edit: and holding INS button turned it off too! I won't be triggered anymore by a single green light remaining on otherwise dark AAP! Thank you for lightning-quick response. Awesome module by the way. JF-17 somehow became one of, if not my favorite, even though I don't like glass cockpits in general, and JF has the most glass of them all.

I have encountered a problem during shutdown. I could not turn off INS on AAP, tried both OFF button (which did nothing at all) and separate INS button, which didn't work (green light stayed on), while other systems turned off via corresponding buttons just fine. At that point in the process INS Mode knob was on STBY, engine stopped. Mission began by cold start, startup process went without any problems, I turned navigation system on by pressing INS AAP button and pushed CMBT after aligning it and activating NAV via separate AAP button press as well. After that I have tried a mission that begins with systems on and ready by default, and was also unable to turn off AAP via OFF button, and separate INS burron was doing nothing too. Otherwise everything worked fine in both scenarios (cold and "hot" start) as far as I can tell. Am I doing something wrong?

Red pilots can paint some stars on it and call it MiG 1.44 :pilotfly:

I just wish I could do this in something that has red stars on it, and letters like "Su" or MiG", or even "Tu" in its name. Or in something that requires more attention to stick and rudder operations than "just pull it" for a manoeuvre like that.

So, modern western winged computer with less capabilities than the ones we already have? Even less yay then.

We are getting a modern western fly-by-wire multirole aircraft. Yay...