KEULE

Just fly 1500m or below and it can detect. :smilewink:

Not sure if this is the ultimate solution. On Nevada map I have seetings at hight with absolutely smooth gameplay. 1.5.3 goes down to 26 fps at ground. Are you sure that there is no potential from ED in terms of map optimisation? Is 1.5.3 now more demanding than 2.0? Thanks in advance.

Dont get serial Hey folks. I bought Nevada map September 11, 2015. When I am correct this includes both Red Flag campaings at no extra charge. Unfortunately I didn't receive any serial code for the A-10C campaign nor can I install it ingame. I might need some help, please. edit: F15 campaign now works, A10 not

Well yes, if you already know they are bad guys. Think as of todays russian patrol engaging into european air space with transponders off.

It's quite obvious. To bring light into darkness. No seriously: To visually identify unknown targets at low light conditions. Other than in DCS normally you do not engage BVR, you must positively identify target as enemy before engaging.

This is not Nevada map :) Didn't happen to me so far.

After latest update many things have changed which weren't in change log. The most serious error that happened (maybe I'm wrong but I don't think so) is that some keyboard assignment are no longer working. The most serious is TDC down which is standard the "K"-key. However in DCS configs it's marked red like it's double used. Which is it was until I deleted the second "K"-assignment to kneeboard (also a standard). Unfortunately it's still marked red and simply not working. Also "Magic II Select": standard key "M" as well as "Special Modes Deselect": standard "D" are red without being assignmend twice. So neither can the TDC slew down, nor the Magic II can be selected or the Special Modes can be deselected. With this it's simple impossible to fight. In addition there has been made changes to the autopilot modes. Hold modes are no longer working. And to several switches and flips left and right mouse click has been switched. Am I the only one experiencing this? :helpsmilie:

They are looking very good. Have you modified your Throttle so far? It is very generous to share some of your spares. How much do you want for one?

yeah... No. It's not that im too stupid to place it somewhere or that buttons are hidden by the mouse cursor. It's that I'm too stingy to pay 160+ for a track IR headset. And until the Oculus comes out I'm using FaceTrackNoIR with an PS3 eye toy camera for 8 bugs. As this works pretty well during day time as light conditions are good the darker it gets the worse to headtracking. In the evening or at night head movement is detected where no movement has been and due to that it's very very very hard to hit buttons as mouse cursor moves along with head. So is there any file I may edit so mouse cursor stays where it was placed by mouse?

Is there a way to not move the mouse when head is turned? Meaning mouse stays where it has been left.

Dont touch the radar. Neither turn it on standby nor on! Then it'll work.

Lol, was checking updater and tested before writing my post. However, after I read your reply I started updater again and...I got an update which is now running. Hopefully you are right. Fingers crossed!

Really? You fly Mig-21 in 2.0? What did you thats it's working? You must tell cause you're the only one able to fly it over Nevada.

If this would be the only problem...

You're right.

BVR is not more than Beyond Visual Range. And it is able to fight in that range. Maybe the first comfirmed BVR kill might from the Gulf War (I don't know) because there were no war with use of BVR Air-to-Air missiles until than? I often read people writing that they are surprised that Mig-21 lacks a good radar and getting shot down. But the underlying assumption in that has errors: 1. Russian air fighting doctrine back than was to rely on ground guidance. Especially for intercepters who aren't supposed to dive deep into enemy territory. Russian interceptors back then were made to stay at the very front line of war and to intercept especially incoming bombers. According to that there were no need for a better radar in these jets which would have been bigger, heavier and more expensive. You have to keep in mind that a mig-21 costs roughly half of a F-4. 2. Even though Mig-21 is delta wing jet which are basically very maneuverable Mig-21 isn't that espcially maneuverable. It's, according to it's role to intercept primarily bombers, made to fly high and fast. And for this task delta wing is best practice. Mig-21 is not a dog fighter. 3. Even though you are behind an enemy in a shooting position. Rockets of Mig-21 are by far less reliable compared to F-15 or Su-27. 4. Don't fight in a Mig-21 against a F-15 and Su-27. You'll win only 1 in 100 times. Better try F86 or F-4.

You aren't seriously comparing a jet developed in the early 50's with a 4 gen fighter, don't you? It's like trying to win a race in a bettle against a ferrari testarosa. Of course Mig-21 has barely a chance against these jets. However it can BVR.

Ehm, what about the Mig-21?!

Where may I get this?

Really noone replying?

Since last update of DCS Beta (1.5.1.) new information are shown on F2 view. However thrust data are incorrect. While flying with full afterburner F2 data shows 50% RPM. When flying with almost 100% RPM F2 shows 79% RPM.

Kneeboard map of Mig21 isnt working in current DCS Beta version. Is there anything i can do? Maybe copying kneeboard files from Non-Beta to Beta folder? Thanks for your help!

Since last update of DCS Beta (1.5.1. updated yesterday) rearming window showing black boxes.

Trees look artificial Since last update (1.5.1, made yesterday) trees are looking somewhat artificialy set on the ground and showing up and disappearing with zoom level. I am unsure if this is supposed to be due to my settings or a bug? In addition loading times seems to be longer than before. Thanks for a short reply in advance.

L39C