Redglyph

Hello, Uncontrolled AI F-5E-3 aircraft make an engine start-up sound at the start of any mission, in 1.5 or 2.0. The sound dies after a while, but it's confusing because you always think the aircraft is starting when it shouldn't. The uncontrolled mode is the only way to make the AI start later, so it's quite useful. I'm attaching a basic example mission for DCS 1.5 to demonstrate the bug. The pilot's aircraft is next to an uncontrolled AI aircraft that makes that noise at the beginning of the mission. 100% reproducible in the following versions (and release): DCS 1.5.5.60565.216 DCS 2.0.4.59428.142 F-5 noise.miz

Are you saying the directional needles are a fiction and only used in PRMG mode? If there's a thread discussing it, I'd be interested to know, just out of curiosity for the real aircraft itself. I've seen this discussion but no source for this piece of information, and from the "official" manual translated to English for some non-Russian-speaking countries (*), I understand the vertical localizer pointer works in both modes. Was it false advertising? ;) (*) If that's what it is... Mig 21Bis Pilot`s Flight Operating Instructions, available for instance on Avialogs

My point of view is that if an issue is annoying for so many people, it's probably worth fixing / changing - I yet have to understand how it could be useful, the fact it's "made of (for?) different resolutions" make no sense to me, though I'm sure there IS an actual reason behind this ;)

It's not just you ;) This is easily confusing, doing some "live" tests really help understand how it works, which you did.

That's also how I see it, if you intercept a radial alpha FROM a station (I suppose that's what you call "the radial on your side of the beacon"), the 3K course needle points to alpha-180°, so that it actually points to the station and not from it. Otherwise it seems to confuse the director, though you could still intercept it manually on the NPP. If you intercept a radial alpha TO a station, the course needle must be set to alpha. It's what the manual describes pp. 114-116, or at least how I understand it. :) I noticed that if your current bearing is too far off from the radial, the director may point the wrong way, "thinking" you want to intercept to the station and not from it, which makes sense. Once your bearing gets in the general angle of the desired to/from radial, it'll adapt.

A few 3-way switches are incorrect in the TF-51D (I really have no idea where else to report it), both in 1.5.5 and 2.0.4, the left/right mouse clicks are inverted which makes it confusing: - Wing Position Lights Bright/Off/Dim - Tail Position Lights Bright/Off/Dim - Red/Green/Amber Recognition Light Key/Off/Steady - [Gun control] - [Left/Right bomb arm/chemical] - IFF TIME/OFF/ON Here are the original (clickabledata.orig.lua) and fixed (clickabledata.lua) files. The bomb switches are not fully fixed (must be switched up before able to be switched down), but they're not used anyway, so it's not a big deal. It's probably a bad/missing initialization. Would be nice to integrate this fix, since it's often the first contact people have with DCS :) DCS 1.5.5.60565.216 DCS 2.0.4.59428.142 clickabledata.lua clickabledata.orig.lua

FSLabs released the P3D version of its A320-X product. Make sure to read the reports on VAS issues, as well as those on performance issues, before deciding to buy it.

NOTE: now OBSOLETE, since included in version 2.0.5.3889 (update 4) and later, so no need to install this mod anymore. Hello! When trying to perform some basic navigation with the Mig-21bis in Nevada, I first saw that the Tonopah Test Range was not in the RSBN channel list. That was so shocking ;) Then when I did a little navigation mission I saw that another VORTAC had the wrong latitude (Beatty). And then of course, most of the beacons were missing... As a remedy, here is a complete replacement for the Nevada beacons, and a simple kneeboard (I'm no artist). Hope it's useful to someone :) No excuses to get lost anymore :D Instructions Download the files from the user file server. The file to replace is here, under the DCS installation directory (as usual, keep a copy, at least to see what may have changed on each DCS update): Mods\aircraft\MIG-21bis\Cockpit\Systems\R_NAV_data_Nevada.lua You can put the kneeboard pages in missions, or in your user files: %USERPROFILE%\Saved Games\DCS.openalpha\Kneeboard\MIG-21bis\*.png This version has been done with DCS 2.0.4.59428.142, I'll try to keep it up-to-date with future changes, though I don't expect many incompatibilities there, maybe just new beacons now and then. Details I kept the original RSBN stations and added the missing VORTAC/ILS/VOR DME beacons at the end, so there is no particular order unfortunately, but I didn't want to change the file too much for the sake of the existing missions. I saw some of the locations of PRMG/RSBN were slightly off when compared to the ILS localizers in the Nevada beacon file, I haven't checked or fixed them in the Mig-21bis yet, perhaps it's a must for Groom Lake. The few airfield homers are not in RSBN, since they give no distance information (Mercury, Meggi, Colorado City). For the ARC stations, I moved the only existing channel (Mercury) and tried to keep some consistency. Sector 1 is North of Las Vegas, Sector 2 is South. Sub-sectors 1 are West, 2 are East. I've tested only a few, please let me know if you find any error and I'll fix it. In each sub-sector, the stations are enumerated left to right, with some exceptions to try and keep them grouped. Most ARC stations have an RSBN equivalent, which allows to switch between two stations if convenient. That's why the 2nd kneeboard page shows the RSBN channels. To be honest, I haven't verified the compatibility of frequency ranges with the original Fishbed equipment (not detailed in the manual), but I don't think the 4477th TES would have hesitated to upgrade theirs, so I wouldn't see it as a problem anyway. I've noticed that the morse code was ... well, as bad as in the 1.5 version ;) Personally I can't recognize them most of the time, in this aircraft or any other, but I suppose it's WIP (or my hearing is particularly bad). In any case, the codes in the file should be correct. Update RSBN stations were sorted from N to S by slices of 1° latitude, then W to E within each slice. This should be much more practical than the default order, since the MiG is supposed to land mainly at TTR and Groom Lake. The only ARK stations kept were Mercury, Meggi, Colorado City, since others provide more information than just non-directional beacon (LNS/Magnitude 3 LLC policy). The previous ARK stations that were actually RSBN were removed. I left them on the kneeboard for their coordinates and to have a single sheet with all stations. The R_NAV_data_Nevada.lua file should be part of the next MiG-21bis patch, so you shouldn't have to replace that file in the future. Updates - v02: added North Las Vegas, fixed position of TTR RSBN, fixed ARC of Mc Carran - v03: fixed Nellis L/R which were swapped in the original file, many thanks to Accipiter for pointing that out! - v04: removed ARK stations that were not NDBs, sorted all RSBN geographically.

I know :) I just think many are curious to know how those issues are faring. Thanks for the info, Bignewy!

You're correct :) I saw that part, still it's not clear. In the AA_missiles mission, which equips the Fishbed with two R-3R SARH (semi-active / fox 1 if I'm not mistaken) and two R-3S (IR / fox 2), the following explanation is given for the IR missiles: "You will know the sensor has locked on when the LOCK SOUND is audible and when one of the green lights near the bottom right base of the ASP is ON. Those lights are named 55 and 62 and they should be around the highlighted area." But so the R-3S should not be related to those lights. While the RS-2US, according to the info I've found, is apparently a semi-active missile and not IR-guided, yet the manual states that "Finally, three signal lights (CU40-41-42) which are not placed on the ASP itself but are a part of the aiming interface, indicate if the IR missile seeker head has locked a target. The green light “1” will light up if RS-2US missiles on the left wing have locked the target; while light “2” is for the RS-2US missiles on the right wing. “62” light is for selected R-60 missiles, regardless of pylon position. Therefore, to recognize that the IR missile seeker has locked the target, you need to hear the lock-on sound and see the lock-on light. If any of the two is missing, the missile could have locked the target only temporarily or locked on to some IR noise." So in conclusion I find all that confusing. I'm mostly relying on the sound, but I think this great aircraft deserves a proper explanation in the manual ;)

Talking about the current state... have I missed something or the armament is not mentioned at all in the manual? There is a separate explanation for the different switches and avionics, but the characteristics of the R-3R, R-3S, R-13, ... are not given? For instance, which one is IR, which one is SAR? What are their ranges, the maximum acceleration? Or the ASP lock lights, how should we use them? Sure, there is a training mission, but all it says is that we should look at those lights to know when to release the IR-guided missiles. Only, I never saw them light up when closing in. Is completing the manual with this information planned in the near future? That would be a great help.

I certainly am! Already had quite some fun with it :)

Thanks :) Don't worry for the delay, no rush there, anyway all campaigns are mostly broken until the other problems are fixed (though I've not experienced these in The Enemy Within so far, fingers crossed). I do hope they finally release a fix next week.

I see no reply, has this been addressed? It certainly rolls and is almost uncontrolable when there is an asymmetric load (for ex. one or two fewer R-3 missiles on either side). The effect doesn't seem to change when it's pre-loaded or re-loaded though. So it's probably correct in its current state (tested with DCS 2.0.4.59428.142).

Reported on the bug tracker (if it's still used). Any idea when we can hope an update of the Mig-21 in 2.0, by the way? It would be nice, for instance there are no flood lights.

It can be tricky sometimes, when DCS changes ;) I've bought it early January so I can't tell when the missions files were last updated. In the mission .miz, files are timestamped 27 December. Not sure it means anything though.

Any news regarding this bug? It's been breaking most (if not all) campaigns for weeks...

I have the same problem with DCS 1.5.5.60565.216, I tried the mission two times. I tune the ARC-186 radio (top one) manually (MAN) to 128.00 MHz, I've also tried the emergency AM settings. Either way, there is no conversation from Uzi. The radio is on, I used it to communicate with ATC earlier. No problem to enter the offset coordinates, I see fire exchange when I arrive on the site so I'm pretty sure I'm at the correct location. I tried the F10 commands (only available once) to ask Uzi for their coordinates, to repeat, to mark the location with smoke, never got any reply from them. The only conversation is from Overlord. If I do something wrong, I have no idea what. Would it still be the same issue, has a fix been integrated in a DCS update since then, or should I look for it somewhere else? When I look at the debrief, I see this: [67] = { type = "pilot dead", t = 29989.001, initiatorMissionID = "34", initiator = "Uzi Pilot", }, -- end of [67] Note: even though I quit the mission at this point, the result is 60 which makes it pass to the next one, so I had to edit the logbook to put it back.

Well, I'm not using it but it seems the custom part is well isolated, if this old mod is the source of the problem, it should be pretty easy to just insert this part in the current version of the Mods\aircraft\MIG-21bis\Input\MiG-21\joystick\default.lua file. Indeed it seems to miss quite a few modifications that were made since then. Have you tried? Look for the line "--************** Custom" and the section just after.

This thread was intended for the specific "default controls" issue (hence the title...), trying to squeeze other problems and wishes in will just bring confusion and have it discarded.

What DCS version are you using?

I don't have this, but the red highlight is usually a hint that an update has made the configuration file incompatible. Simply delete your configuration files, it's in %USERPROFILE%\Saved Games\DCS.openbeta\Config\Input\MiG-21Bis\* (or \DCS\ or \DCS.openalpha\, you didn't mention your DCS version so I assumed openbeta). You can try to make a backup first, then merge the files if you're at ease with such operations. Otherwise you'll just have to re-configure the module. You may also try to only delete the Config\Input\MiG-21Bis\joystick\Throttle - HOTAS Warthog*.lua file first, perhaps it's the only offending one.

Here I'm just trying to make sure the behaviour above is not intended and reported (perhaps it's intended though it wouldn't make sense to me). My guess would be that you may want to use some specific device for a given aircraft which is generally used for a common control. Also, common controls are not always implemented in all aircraft, so you'd lose the general mappings that are not used in such an aircraft. Being able to override them, but still keeping them for individual modules seems a better, more flexible solution. That's an entirely different issue so it should probably be in another thread. There is a standard, and this has been reported for the Mig-21bis. I'm not sure when it will be addressed, but you can use this mod in the mean time (I fixed them, it's quite easy). You'll find all the details in this thread. The same is true for the A-10C (there's also a fix for this one), most other modules seem consistent enough. Can't comment on this one, I have no idea what this is (I don't own C.A.) :) Strange, but again, it seems to be a completely different problem.

bump

bump