Martillo1

:joystick:

One minute of arc at equator equivales to one nautical mile (about 1.86 Km), so one tenth of minute of arc is about 186 m. Maybe it is not enough for guiding a JDAM, or for precise navigation in autopilot between canyons, but for general purpose navigation is quite good.

It is due to the fact that some systems need more current than the supplied by the inverter (which has limitations), so they require the generators being turned on and the rotor spinning at nominal values. UV-26 an LWS are two of these. I think datalink is another.

NBQ :megalol:

I think that if a DCS SU-25/SU-25T module were released with interoperability with KA-50, it would give more flexibility when playing missions, provided you could switch between cockpits. Thus Ka-50 would not be forgotten. Anyway, A-10 is in development, so no chances there, but it would be nice.

Yeah, clickable cockpits are the perfect solution (plus HOTAS).

¿Really? :huh: Well, let us try :joystick: Edit: No changes at all. You can try it.

I also have encountered the "just one Vhikr launched problem" when the long-medium-short burst switch is on the "long" or "medium" positions. It is a nuisance when engaging MBTs.

Well, after you press [P] for the second time, you leave gun sight mode and go into automatic tracking mode. Then you can lock (TA) and lase to find range (ИД), so it should show TA-ИД for a while, or just lase to find range (ИД) without lock. You can also find range in gun sight mode, but with no lock (ИД for some seconds) because in gun sight mode ther is no lock by definition.

If you can learn to use a PC keyboard, you can learn to use anything.

It also happens to me. Standard procedure: After loading Windows (Vista64), move the X52 mouse to left<->right & up<->down until the drift disappears.

The [P] key (Automatic tracking/gun sight) is your friend here. That way the Shkval skreen shows where you are aiming at.

Well, you can also turn and change angles without pressing trim, but when you want to trim the new attitude, depress the button and wait a bit instead of just clicking on-off. In the wait do not be idle, but correct the parasite trends that always happen thanks to the Yaw AP channel. This method allows me to turn without pressing Trim all the way, something very useful to keep the right thumb free for other HOTAS buttons :joystick:

Track Here it is mine. In this track you can see I send Wingman 4 on reconnaissance for 3 klics and when finished, I ordered him to hold. But he does not hold, he goes to the right and then traces a circle around my position. Note: part of the track is recorded with accelerated time. wingmandonthold.trk

I confirm that hotkeys do not work in DCS:BS under Vista 64.

Try mines if you want to ;) Martillo1's X52 profiles. I recommend you the 1.2.

I do not know you, but for me 23 fps against 15 fps is the difference between a slideshow and a quite playable game. You state that dual-core is better than single-core, of course. And quad-core is better, and octo-core is better... if software is programmed with multi-threading in mind. For that is the tendency these days in hardware, so software has to go the same way. The difference between our points of view is that you prioritize polishing some aspects of the game before using programming resources to improve its performance, and I think the performance leap will permit solving those issues more easily through the new computing power available.

So you get "only" 30-40% increased performance by going multithread. Not bad, at least IMHO. But it is true, technological progress is no sense, let's go back to Intel 8080 :doh:

Are you serious? :huh:

I would like to see a multithreaded engine first ;)

Have you tried just to lock a target and say him to engage your target?

Well, I went out (on holidays) since the middle of July to the middle of August, and I am way off schedule, but I have made some work. Here it is: My X52 profiles I hope they are useful for you, but the work is still in progress.

Attatched, several versions of X52. To see them more clearly, print to XPS format. Maybe You will have to change some keys in the profile and in game, like "ç". Work in progress... Version 1.0 and version 1.1. They are different: the first engages cannon with 1st trigger and fires with second, and the layout of the latter resembles more the Hokum's handles than the former. versions 1.2, 1.3, 1.4 and 1.5 are built from 1.1. Watch: key assigments of 1st & 2nd trigger (letter "ç" instead of space in one of them). the V1.1 consumes more CPU cycles. I do not know why . Edit2: Added Version 1.2 that fixes the CPU usage. Edit 23-12-2009: Added versions 1.3 and 1.4 (N.f.A.: skip 1.3 and use 1.4) Edit 28-12-2009: Added version 1.5. It is a simplified vesion of 1.4 and uses "pinkie" for trigger. I find much easier to fly with this version. DCS Black Shark for X52 + Track IR by Martillo1 V1.x.zip

:huh: I have an Asus P6T Deluxe V2, i7 920, 6 Gb RAM, 1x Asus GTX260. I play around the same framerate than you, and the guns' explosions do not bother me. Maybe the initial load of textures. However I do suffer from occasional hickups, but not when firing.

Thanks, I have read the manual, but I do not understand why flipping off NAV switch turns off the navidaton system as long as K-041 switch is in the on position. The process design seems weird to me.