Tasmanian

Turn the laser on.

For Logitech Force 3D and Extreme 3D (they are the same but one has FFB, the other just a spring) the spring is much smoother and allows precise control when using guns, bombing etc. I believe more expensive sticks should have smoother FFB but have not tried any.

Using Force 3D Pro. Works well, no issues. Deadzone 20, curvature 30 for pitch/roll, deadzone 30, curvature 30 for yaw. It's a cheap stick so feedback is not smooth at all which makes it hard to perform accurate maneuvers. Tried Extreme 3D (with no feedback) - it's much smoother.

SU-25 ILS indication axes seem to be swapped. Track included. Demonstrated horizontal axes responding to aircraft vertical movement. However SU-25T and Su-27 look working fine. 25_ILS.trk

Creating a CAS mission for 25T, setting waypoint action to attack two groups. The problem is that in cockpit only targets of one group are marked with diamonds and can be cycled with ctrl+`. The other group is not marked =( 25T_diamonds.miz

-01n BUKs at blue side do not have CC in group - so they will NEVER fire.

"Search than engage" seems to override your "Weapon hold".

Missing FC1 Ukranian region....

same with Su25T on Kuznetsov. Just spawns inside carrier.

Su33. Setting CAS - attack group or attack unit or Groung attack - Attack map object does not provide a target diamond on HUD in AtG mode. However it does ok for Su27 and Mig29. For Su33 it only marks a triangle on cockpit display but it is impossible to select it as target marked on HUD. P.S. By the way it puts a diamond for Vulkan. Tested also on Stinger, Avenger, Abrams, Static objects, ships, ground point - no diamond for them.... Su33AtG.miz

Great. This makes sense. Reasons why "fake launch" is not implemented in reality can be this "missile launch normally doesn't trigger the enemy RWR" or this "every time you lock somebody with an STT lock, you have your "fake" launch".

Whenever someone wishes an option there IS always a point. Why not put a real missle - it will have 90+% miss chance. In DCS it can be very useful to "fake a launch" in many situations: 1.Head to head combat. Faking long before getting the target into launch envelope so he does not really know when the actual missle is launched (until visual). Can make him perform unnecessary maneuvers, use chaff or turn around. 2.Chasing. Faking a launch makes him maneuver - makes it easier to catch up. In game often wished this to be simulated, but had to waste a missle instead. Of course it missed, but the target behaviour due to this wasting launch gave me profit. I have no idea about real aircraft but suspect that there is such a mode that simulates radar emissions as when missle launched at least for testing\training purposses. But since you are keeping the target locked anyway and this option can be used in combat to mask actual launch why not implement it? I am afraid only real fighters and designers know.

I had similar issue on GTX260 896Mb and 32bit XP. They say this is due to lack of video memory. It is true. Monitoring video memory usage under high details it really reaches full 896Mb in 5-20 minutes of gameplay and one can see missing textures. So reducing texture quality to medium/low helps. Or if you run in true fullscreen mode alt+tab forces to reload trextures. It is a pity that ED do not solve this. Because card performance is enough even at high details, memory is enough to display the scene (the overfill occurs after changing several different aerodrome views). The only thing needed is to free the memory from unused stuff. I have games that also go up to limit but none of them causes texture or objects missing.

Aiming mavericks in A-10A is really tricky - the crosshair does not always move the direction you want it to move. Do not know about A-10C.

Transforming from polar coordinates to cartesian you do not have to solve any equations. x=r*sin(a) y=r*cos(a)

Don't know about FC3 but in FC2 managed to fly, land and repair SU-25T and SU-27 with both wings half-cut XD

Today in 1.2.2 multiplayer landed a damaged 25T got engine, body, wheel repairs but hydraulics was not fixed. After engines started the pressure was still zero.

Would like to see "Unfiltered" mission option which could make all aircraft and actions for them available.

Entered mission (multiplayer), started engines, switched to map, clicked to remove grid and got a crash. DCS-20121117-191117.zip

Same problem with logitech force 3D. Force feedback is working wrong with all aircraft. Feedbach axis seem to be messed up (I trim up - it rolls right).

Just got another crash (multiplayer this case). The screen goes black, then the error pops up. Similar thing also happened in single player and even in mission editor screen. DCS-20121114-063833.rar

It may crash for me in multiplayer when my SEAD missles hit the radar. I shoot, turn around and get the crash. (do not remember which of the reports is for that case) DxDiag.txt Logs.rar

Wish the "Task" filter in mission editor was not so strict. Sometimes one would like to set both ground groups and ships as targets or ground groups and ground ccordinate. But it is impossible within a single task. Also wish it is no so strict for aircraft choice - can't assign su33 for anti-ship or B52 for CAS. Without it I can't set groups as targets. Maybe introduce some unfiltered mode with all available actions and aircrafts? (NoTask is good - gives all crafts but no actions - can't assign targets at all) Also it could be useful in some scenarios to be able to target friendly units/groups. And by the way Israel and Russia have A10C but do not have A10A? Mb add or remove something.

Confirm that Tor does not shoot kh-25 missles (even if launched from 15-20km and turned away). Tunguska shoots kh-25 but does not see mavericks.

Tunguska shoots down small fast kh-25 perfectly but does not shoot large and slow mavericks. Mb this should be fixed? P.S. Targeting mavericks in A-10A is pain. The crosshair often moves in random direction, especially when flying at low altitudes. Mb a fix for this as well?