ZaltysZ

I don't remember any reports about keyboard so far. Well, hook other mouse and try playing; if there are no more errors with DINPUT8, then you will know that keyboard is ok ;)

Aha, Sidewinder. There is some sort of incompatibility between DCS and this mouse. You can do a search on this forum with keyword "sidewinder" and you will see that you are not alone. Sadly, currently there is no solution to this problem except that which involves using other mouse instead of Sidewinder.

Any fancy mouse? List all your controllers (including keyboard and mouse).

HUD isn't simple transparent display, it is collimated (focused at infinity) display, which uses reflection or refraction to present data to the pilot. You won't notice the change in size of symbols in the HUD by changing position of your head (or seat), because they are focused at infinity (you can test this in real life by looking at car 500m away and moving your head back and forth 30cm - it won't look smaller or bigger to you because of this). If you want bigger HUD symbology, then zoom in (narrow field of view) and if you want crisp symbology at wide field of view, then increase the resolution your game runs at.

Works well on Windows Server 2003 x64 without any compatibility mode, so it should work on XP x64 too. Check drivers.

I have watched your track 5 times already. Its wrong measured range or reticle outside cannon gate. Please tell precise T, when reticle is inside cannon gate, measured range is under 4km and cannon does not work. T (elapsed flight time) value can be read in the ABRIS, left column.

What time exactly the "bug" manifests itself? Judging from screenshot and your actions in the track, I suppose you have experienced the "bug" around T=5min (flight time shown in ABRIS). If so, then watch your track yourself again and look what HUD or Shkval displays shortly before and after T=5. The shortest range it shows is around 6km, and average range is about 12km. You won't be allowed by computer to fire the cannon if shown range is over 4km. Real range isn't important, shown one is, because the shown range is the same range which is used by computer to calculate cannon solution and to make decission if target is in range. Watch your track again, near the T=5 press ESC and take control. Try to fire the cannon, it won't work. Move Shkval Camera to look at point which is in range for cannon (less than 4km), try to fire the cannon, it won't work, because Shkval (or HUD) still shows invalid range. Press autolock button and observe how the range shown in HUD and Shkval changes. Fire the cannon, it will work. This is not a bug, this is just wrong range information, which must be corrected by reamesuring range with auto lock button.

Laser overheat becomes problem only on intense missions when you quickly expend all your Vikhrs at long range and rearm multiple times. If this is too abstract for you, then look here: http://forums.eagle.ru/showpost.php?p=614775&postcount=50. :)

Lasing happens only then you press auto lock button. Skewing Shkval camera does not use laser, that is why you need to press auto lock every time you move move Shkval camera onto new target - if you don't, then range information might be wrong (especially if new target is in different elevation than a last one). Keep in mind that the first press of auto lock button will make Shkval gates to become "sticky", if their size is correct (i.e. according to target size) and Shkval will automaticaly stick to any target onto which you move the gates, however you will still need to press auto lock once again after that to get correct range. This isn't necessary for Vikhr launch if you already have "C" and know that target is in range, because laser will automatically become active anyway when missile is launched. However, for cannon usage it must be done before firing, because accuracy depends on correct range information and this information must be obtained before rounds leave the barrel. Laser in stabdy position will not burn itself. How long it will work depends on how long you lase the stuff . Everytime you measure the range, laser will work for about 3s, so quantity of such measurements is limited. Also, laser will work all the time while Vihr is in flight, and depending on range, it might be pretty long.

Yes, you were 1km away, but your fire control computer thought differently. Always look at HUD or Shkval display and check the distance to target. It should be no more than 4km to be allowed to fire cannon in auto mode. You simply did not remeasure the distance to target by pressing auto lock button, so fire computer used last (already invalid) measurement and denied the use of cannon. We noticed it, however it does not matter, because it never shows ammo type when cannon is selected.

Partial reason for slow loading times is how game searches files. If you check with Process Explorer, you will see that game searches most files not in precise locations, but instead it traverses predefined directory tree until it finds required file or until the whole tree has been traversed without finding that file. There are about 6800 NO SUCH FILES events and all of them adds delay. This delay of single such event is very small (in good system), but still the sum of them all can be viewed as significant (in order of tens of seconds). This can be avoided by letting the game to know precise location (relative path is ok too) of every required file and not telling it to look for files which don't exist.

Try setting more standard resolution in game. Something like 1024x768.

Yes, D-Link needs line of sight to operate. Shape of threat depends on terrain and your altitude (for example, if mountain is between you and center of threat zone, then ABRIS will cut out some part from that zone). However, threat zones remain even if you destroy the threats, because there is no automatic way for ABRIS to know that the threat has been removed.

What joystick do you have? X52 Pro?

http://forums.eagle.ru/showthread.php?p=632574&highlight=launcher#post632574

I have written some text in bold on purpose. :smilewink: If FD is off and direction channel of autopilot is on, helicopter will always try to turn to designated direction. What direction? The one to which the helicopter has been facing when trim button was released.

Waypoints do not matter if your helicopter is not in route mode. Probably you are not using trim right. You have to make attitude and direction corrections only when trim button is pressed.

If you manage to find good spot for "dance", SAMs my run out of missiles and you will get a few minutes window to engage them without their retaliation while they are reloading. Not very realistic approach, but it works.

http://forums.eagle.ru/showthread.php?t=38885

I will define more precisely. Situation: default instant action mission Start speed: default speed after unpause Start altitude: default altitude after unpause End speed: 0 km/h in all directions, a.k.a. hovering End altitude: the same as start altitude Aim: measure time of deceleration without changing altitude or direction during it. This is not a competition. Adequate deviation is allowed. It means that few meters or degrees here and there is allowed, but if you jump up by 50-100m, then this exercise won't be completed correctly.

The point is to keep altitude constant while decelerating. For sake of simplicity, everyone test this in instant action mission: unpause and decelerate.

Instant action mission, 25s, 1 trimming at the end.

In Options screen there is nothing fancy which could cause such slowdowns. Well, maybe Controls section can cause it if it does some detection when you enter options screen. What control devices do you have: mouse, keyboard, joysticks, pedals?

Maybe this is the reason.

Check options screen. Tooltips are setting of difficulty. Some missions can have them turned off, but you may override this in options screen by turning tooltips on and ticking "Apply these settings to all missions". In case of multiplayer, server will dictate settings, so you won't be able to use tooltips if server forbids them.