-
Posts
333 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Nereid
-
I think I have found it: It's not an issue with the Mig-21 but with DCS. If you are flying in a aircraft of western nationality (e.g. a german Mig-21) than you can't communicate with EWR at all - just AWACS works. With a red (sowjet, ukrainian,...) F-86 or Mig-21 communications with an EWR unit works. If you jump in the same plane as an american or german it won't work. Seems that the english language is just missing the right words to make EWR work. :lol: So, it's a DCS bug in my oppinion. If we are playing the Mig-21 on the western side, we will have to use AWACS.
-
I have tried the "Custom Ground Controlled Interception unit creation process" as described in the manual (page 153ff). The goal is to make units available to other countries that don't have them in their arsenal (EWR units in this case). But I don't get this to work. After creating the template and adding it on the map, it will get assigned to the original country. Changing the country just before adding the template to the map, will remove the template from the list of available templates. Somehow I have manged it to assign an EWR 55G6 site to USA but I can't reproduce it. Does anybody know the trick how to accomplish this task? :helpsmilie:
-
Ah! The instruction is wrong? Never tried it. But the numbering is weird - even for the the instructor perhaps. ;) You have to drink a lot of wodka to get it right... :D
-
Here is my mission. The Mig for the player is in flight (this makes testing easier), channel 0 is set to 141 MHz AM. The EWR I want to communicate with is Mantis1, frequency set to 141Mhz AM. The other EWR is not used. The AWACS (frequency 142Mhz AM) is there for testing purposes. Communication with the AWACS works. Are the radios of the EWR not suited for the frequency I have used? EDIT: This may be a general DCS issue as well. But because of the importance of EWR to the Mig, a working example would be great. Maybe we will get one to work. Mig-21 Intercept.miz
-
There are no frequencies assigned to any of the EWRs. This would not work for me, too. But there is a difference. Asking for a bogey dope the sound of my transmission is played at least. But no answer of course (which frequency?). EDIT: After assigning frequencies to the EWR it works. Strange observation: the callsigns are missing (just numbers, if you assign them). EDIT2: Numbers are the callsigns for non-western units. So all is fine.
-
Still editing. I will do so tomorrow. Its way to late now.
-
That what I meant. I would not blame LN for not implementing this.
-
Yes, but it's not LN fault. The numbering of the pylons in the mission loudout is unrelated to the pylon numbering in flight. Numbering is: (left) 3 1 2 4 (right) A simple graphic that illustrate the numbering in the manual would be nice. But I see no bug here.
-
I have no problems communicating with ATC, except that sometimes (very rare!) they will not answer.
-
I have tried to use an EWR radar in a mission but without success so far. In my current mission I'm using an EWR 1L13 and on the first waypoint (the startpoint) he has a "perform command - set frequency - 124Mhz AM". Selecting channel 0 in the Mig should give you the option to communicate with the EWR. The good news: There is an option "AWACS" in the radio menu. Selecting this shows the EWR. Choosing the EWR and any of the entrys showing up will do .... nothing. No answer from the EWR. Channel 0 is selected in the Mig (124MHz AM). The EWR is not displayed in the RWR (the emissions from a friendly AWACS aircraft are shown there). This may caused by the constraints of the RWR (45°) but I'm not sure about it. Any ideas how to get the EWR to work?
-
Take the XK-80. Its more expensive but more bang for the money. I have one myself and they are great. But... even with CH-Fighterstick (20 keys), CH-Throttle Pro (20 keys), CH MFP (50 keys), CH Quadrant (another 12 keys) and a XK-80 (80 keys) I still feel the need for more... another XK-80 one day perhaps. ;)
-
Me too. before the update: 25 fps on ground. Now 30 to 35 fps on ground. Landing is completely smooth now. The improvement is quite noticeable, but hard to measure. Maybe 20% more fps for sure. Great tip, TY.
-
Please! Don't reduce the details of this bird. The Mig is just beautiful at the moment. :) Well, in real and for my personal taste the Mig-21 is one of the ugliest aircrafts out there. ;) But LN has done a real great job with the Mig-21 in DCS. It would be a shame if we lose something...
-
I got this red circle (padlock mark) in singleplayer. But its centered on the screen and because my DCS screens spans two TFTs (for usage of Helios) the center is somewhere on the outer right of the cockpit. Not a big deal but definitely some kind of bug.
-
The problem is, that this switch takes immersion away, because it produces a gun cam out of thin air. If a checkbox in the mission editor is to complicated/impossible, whats about an additional loadout option? Just like the ASO-2. If somebody wants the gun cam for aesthetical reasons, he could add it as a seperate loadout. And a real gun cam footage would be very cool, too. ;)
-
Ah, yes. Forgot the missing decimal.
-
Does anybody know how to convert the QFE given by ATC to the values used in the altimeter of the Mig? I have the strange feeling that the Mig is using different units than ATC... A-10 inches, Mig centimeters?
-
This was my first mistake, too. I still have the question in mind, that the ASP mode (regardless if HUD/ASP is on or not) prevents the pilot from dropping bombs is there in the real bird, too. Maybe some way to prevent missing targets caused by wrong ASP mode... AFAIR weapon mode neutral isn't necessary. But ASP has to be in bomb mode.
-
I have observed a strange mismatch between the pylon loadout in the mission editor and the chosen pylon in flight: 1. Weapon Selector is set to AA Missiles, Launcher 1. 2. By pressing fire a missile launched from left INNER pylon. 3. Pressing fire again a second missile launched from left INNER pylon. 4. Left INNER pylon is empty now. I would assume that launcher 1 is pylon 1 from the loadout menu. But pylon 1 in the loadout menu is the left OUTER pylon? Pylons in the loadout menu (frontal view): (right) (center) (left) 5 4 6 3 6 2 1 Is this a bug or some strange concept I just do not understand right? EDIT: The loadout in the mission editor seems not to be corellated with the actual launcher in flight. Rightmost is numbered 5 and thee is no launcher 5 on this bird. So 1-2 must be the inner launcher and 3-4 the outer ones? Correct? EDIT2: The launchers are numbered as follows (left to right): 3 1 2 4
-
Same here. Brake pressure sound and brake release sound are the same when bound to an axis. But to play the right sound is a bit more complex if an axis is used instead of a key.
-
Running at 40fps on ground and upto 50 to 60fps in flight. Performance is ok for me. Better than the F-86. 2600k GTX 770 8GB DDR3
-
Personally I would prefer a checkbox in the mission editor or leaving out this useless gadget as a whole.
-
Maybe. Unfortunately it auto-corrects after mission start and not while creating the loadout. But this may caused by some constraints or missing functionality of DCS. EDIT:And if this is true, then the loadout is broken, because it allows us to load 8 missiles if they are just of different types. :smartass:
-
Well, you can. But you have to load a single missile on the outside ones.
-
Is the weapon loadout (in the mission editor) broken for the Mig? If I try to load 8 R-60 missiles (4 on each wing) and start the mission, all missiles are gone. After returning to the editor the loadout is empty. This happens for the R-60M, too. It happens independently for each wing. If you assign the same loadout for all stations on that wing, then the wing is empty on mission start. Is the Mig not capable to load 4 R-60 under a single wing? Mixing loadout (2 R-60A and 2 R-60M under each wing) works.