PeaceSells

http://store.steampowered.com/hwsurvey/ Current results of the Steam survey... Win10 is actually more popular than Win7

That poll is from 2010...

You are spot on.

+1 Thanks for this info, SithSpawn!

The way I found to accomplish the kill AWACS mission in the F-15 campaign was to fly very very high (above 50,000 feet) and very very fast. This allowed me to fire from a very long distance, specially because the AIM-120 will hit an AWACS at a longer distance than it will hit the escort fighters. I waited for pitbull and ran away, flying stupidly high and fast. The escort fighters couldn't touch me and the AWACS was killed. But I guess that was only possible because, in that mission, the AWACS don't turn away form you, it just keeps flying in almost a head on path, which probably doesn't make a lot of sense.

Yes but that's not a viable solution, it's extremely harmful for your eyes. Point is things should be visible at visible range, and not visible out of visible range. Not really that compliacated...

Yes, it's there. Exactly as Boris and others have described it. Even I described it many pages ago, still in 1.5.5. You can see clearly the dot against the sky and even against terrain, because it's pitch black, so it contrasts. The dot is even visible behind clouds. If the enemy is far but not enough to be a dot, zooming out turns him into the dot and makes him visible. The sad part is that when the enemy gets closer, or when you zoom in, he becomes invisible again due to the plane model not contrasting enough against the sky or terrain. Everything is now backwards, you see them when they are outside visible range and you don't see them when they are within visible range. Not to mention the black dot happens to missles too, I now see my missles hit or miss the enemy 20+ km far and also see enemy missles incoming from that far. The missles are exactly equal to the planes at distance (black dot). The fact that expert people don't see this really worries me. You guys are not playing with labels on, are you?

Can you guys tell me if it happens in 2.0 too?

With so many planes that never had had a study sim released, why would you want so much a second study sim of the F-16? If you asked me, it'd be more interesting to see a study sim of a Mig-29 (or another "virgin" plane). But of course I wouldn't mind the F-16...

I agree 100%. Plus, a gaming mouse with high polling rate is more expensive and much better for looking around in every game, except DCS. And I don't like having to my lower polling rates manually every time I play DCS. However, in the mean time while ED don't fix it (if they will ever fix it), if your mouse doesn't have software to change the polling rate, maybe you could try having a cheap second mouse that you plug in only for DCS. Not the ideal solution, I know, but anyway... I'm obviously assuming that the cause of your problem is the same as mine... I don't even know if everyone having this issue have a high polling rate mouse... ...By the way, what mice do you guys use?

exray nailed it on the other thread: https://forums.eagle.ru/showthread.php?t=178817 Lowering my mouse's polling rate solved it for me!

exray nailed it on the other thread: https://forums.eagle.ru/showthread.php?t=178817 Lowering my mouse's polling rate solved it for me!

You are right!! And yes, I could fix it from the user end! Lowering my mouse's polling rate from 1000Hz to 500Hz solved it for me. I did it inside the manufacturer's program (Logitech). Most common mouses use much lower polling rates than 1000Hz, but gaming mouses for 1st person shooters, like mine, usually have high polling rates. I guess that's why most people seem to don't experience this problem. Thanks a lot exray!! And how did you know it was related to polling rates?

Guys, I've read in another thread that having the system specs in your signature really helps ED to hunt down the issue. I now have it in my signature.

Is it me or that P-51 is dogfighting with its rudder? I don't own any WWII modules, only have experience with FC3 aircraft, but I feel AI there is also pretty bad. In my opinion, you don't have an actual simulation if you don't simulate real pilots too...

@Sweep and @Bushmanni: What you are both saying makes sense, see if I understand this right: if you ignore the computer launch cues and fire according to your own DLZ in your head to maximize PK, you will fire the ER at a greater range then the AIM-120, despite the computer cue for the ER are at shorter range than the one for the AIM-120? I don't know if I'm hijacking this thread, but I guess this issue is very relevant to the OP's question...

If you don't pay attentio to launch authorization, how do you know when to fire the ER, since the range varies greatly with your altitude, target's altitude, your bearing, target's bearing, your speed, and target's speed?

So I understand that the ER could reach the target faster, but still the AIM-120 will be launched first, right? On the other hand, the AIM-120 won't give a launch warning until pitbull, so the ER might put the enemy in defensive sooner due to giving the launch warning first, would that be the real advantage of the ER?

Are you sure that the ER's have more range? I was doing some testing a few weeks ago and, for the same altitude and speed, I could fire an ER at almost 40 km (head on) and an AIM-120 at about 50 km (head on). Both were fired as soon as launch authorization was achieved. Am I doing something wrong with the ER's?

I'm having a similar problem in the release version, after the 1.5.5 release: https://forums.eagle.ru/showthread.php?t=178817

Hey, I experience this too in the release version, but only after the 1.5.5 release. I started a thread about this in the release version section (https://forums.eagle.ru/showthread.php?t=178817), before I found this thread.

Hey, I don't know how many people besides me still use mouse-looking instead of TrackIR... But I'm experiencing trouble in looking around since the first release of 1.5.5. The mouse speed seems to be varying with FPS. In heavily urbanized areas, it takes a very long time (and several times the length of my desk) to turn my head a small amount, while in fast areas I turn a lot with small mouse movement, as if mouse sensitivity (saturation Y from the axis tune setting) was varying wildly. Dogfighting in some areas is now very difficult. Another issue is that zooming and panning simultaneously seem to not be possible anymore. When I use the mouse wheel to zoom in heavily urbanized areas while moving the mouse, it stops panning or stops zooming, never does both at the same time. I wonder if I'm the only one experiencing these stuff, because I see no other threads on this, despite it being very noticeable to me. I use the mouse with my left hand continuously to look around during dogfights, since I have padlocking disabled. EDIT: Found a similar thread, but it's in the Open Beta section (I'm not running the beta version) and it's from way before 1.5.5: https://forums.eagle.ru/showthread.php?t=153411. Two more threads from the beta section and from way before 1.5.5: https://forums.eagle.ru/showthread.php?t=157579 and https://forums.eagle.ru/showthread.php?t=152300 My hardware isn't ideal, but probably not too slow either: Core i7 4770 3.40GHz GeForce GTX 770 2GB 8GB RAM Intel motherboard DB85FL Windows 10 64bit EDIT: Mouse Logitech G300 1000DPI 1000Hz EDIT: I'm using no mods and I fly FC3 aircraft at the moment. Anyway, it's not about being slow, because, before, 1.5.5, I also had FPS dropping a lot in some areas, but mouse-looking speed was constant and independent of FPS. It was according to the setting in 'saturation Y' from the 'axis tune' setting. I can attach a track or a video link if needed, but I don't think that would add anything... Thanks for reading this!

Yeah, the dots don't really worry me... I'm more interested in visibility well inside WVR... I know that an important skill of a RL fighter pilot (despite I'm not a pilot myself) is the ability to find other aircraft WVR with naked eyes. And I know that our generation of gamers sometimes thinks that everything can be handled in an MFD screen, but that to me is boring. If I wanted to look at MFD graphics, I would be playing ATARI still... The thing is I think planes visibility well inside WVR could undergo some fine tuning to make them slightly more visible. This would stimulate looking at the world instead of just keep rocking the plane around in vertical radar scan while looking straight forward. Or, in case of flanker pilots, relying too much on the datalink...

Please see if this attached pic helps... this is from video 1, at the mark of 00:03s. You'll have to maximize the pic. Also make sure you watch the videos at 1080p fullscreen. I have an ASUS gaming monitor, size 24", not sure if this makes a difference...

Nice to see that I'm not the only one that noticed this... I recorded a couple of videos to help illustrate: https://www.youtube.com/watch?v=aJrmOP0DdKc You can see the two planes on my 7 o'clock just below the cloud and above the horizon. They appear as dark dots when zoomed out and disapear when zoomed in. https://www.youtube.com/watch?v=nPDWMUYkFtk I added a white caret at 00:29s, 00:48s and 00:55s to show the plane's position in my HUD (it's not the F-16 close in front of me). You can see it as a dark dot when zoomed out and, when zoomed in, it disapears. (Those videos are not listed, you only see them if you have the link) EDIT: I should mention that Youtube compression exaggerates the effect. In game you sometimes can see the aircraft after zoomed in, but it's still much harder to see. My humble guess about what's happening: the dark dot is visible because dark contrasts with the light blue sky and white clouds. When you zoom in, the aircraft is drawn with its true colors instead, which are usually light blue/grey, which blends well with the sky and clouds. Plus, afterburner is drawn as white. So that's why you have more trouble seeing them up close than far away. I like this system of drawing dots at distance, I just think that aircraft at close range need a little more contrast, I often see the target's shadow on the ground but can't see the target itself. Maybe this is a work in progress and ED is fine tuning it. I look forward to see the end result, I'm fairly new to DCS and it's already my main game now!