geogob

I think it's a 8-pin mini din connector. I'll check on my X52 cable when I get home. Or it could be a 6-pin. I'll check tonight (or check yourself using the guide below). here the cable I think you need (to be confirmed) http://www.cablestogo.com/product.asp?cat_id=928&sku=02316 Here's a guide that might help you: http://www.cablestogo.com/resources/din.asp Any good electronic store should have 8-pin mini din male-male cables in stock. Many online store have them. EDIT : now that I think about it, I have the X52 PRO. Might be different than the X52. Better check yourself the connector type. Should be easy with the guide I linked to. Or just count the number of pins :P

Maybe you didn't close the door hard enough :P

Ah, yes, macros. What I didn't know is that what they call standard keypress behave like macros (with registered time). I tried to use macros with the hat switch, to make the Shkval pan up and left or down and left, etc. It didn't work out well. All macros I created caused heavy lag for a few seconds when ever used. I'll try again with something more simple, to see how it works out. Thank for the suggestions. I'll also check out some profiles I can find for BS so I can compare how its done. Hopefully it will work.

So I understand, the step reproduce are now know. This happens all too frequently. Very annoying. Laser fires in the off position, but weapons won't register it if it's not on the STBY position. Hence nothing works as intended. Until this gets fixed, are there any action to avoid mixing the rangefinder up? In the same line of thoughts, is there a know work around to re-invert the rangefinder stdby switch?. It tried everything I could think of.

Very interesting. I didn't know that and I see how this could be a problem. Not too sure what you mean by a "release" keystroke, though. Could you explain this a bit more please?

Go to the options page of the user interface. Where you can setup all the keys, in the drop down list, chose the section to edit all the joystick axis. There should be one axis for the collective. Try to clear it and then assign it again. Open the dialogue box to assign a new axis to it and then move the X52 throttle axis on it's full range. It should be registered as JOYZ or something like that. Hope this helps. More info can be found in the user interface manual.

The design and tech is fairly old in the KA-50. Pretty impressive still today, even at its age. Military aircraft have many upgrades as they grow older. New version come out of production chains with newer, modern equipment and older are retrofitted with new systems (and the same could be said about civilian aircraft). As I understand it, the KA-50 never entered full production and no major contract was signed. Because of this, no major revision of the systems where made (it's not really interesting to make a major overhaul process of only a few models built and for some prototypes). If the KA-50 or 52 ever enters full production, I think one can expect a full overhaul of the systems. Possibly include better night capabilities, etc. But for such a small number of built units, it's a process that's too expensive. edit: I see the KA-52 seems to have more advanced systems and avionics. Understandable... it's more recent. If new KA-50s are built, these systems will probably migrate to as well.

1) Just old the designate target button to unlock the shkval and slew it off target. 2) C just means that the weapon is ready to fire and the target is in range. If you didn't turn the laser range finder on standby before targeting, the gun might say it's ready to fire even if the target is out of range. Also, there will be no range correction (obviously). If you want to unlock a target, you can either: - recenter the shkval (button on the cyclic) - press designate target (collective) and slew the shkval away from it - reset the targeting systems (not what you are looking for I guess). - You may also press the uncage skval (cyclic) button. If the HMS is activate, it should slew the skval to that point of sight. If not, the shkval starts scanning. 3) Rockets. The key, again, is the range finder laser. Without proper ranging, the predicted impact point is locked at 1100m or something (can't remember exactly). Laser range finder can be used both in bore sight mode or auto tracking mode. mm.. and lots of practice with the rockets ;) One good idea and suggestion I can give you is to read the pilot manual, then watch the video tutorials, then read the manual again. Practice. Read the manual again. Go back practicing ;)

Yeah. A mysterious aura of burning metal and super hot plasma slowly vaporizing the left wing. If it wasn't so sad, I'd probably laugh. :noexpression: Just hope this incident helps to move space programs forward worldwide. I feel like space exploration and exploitation hasn't moved forward at all in the last 20 years. At least, now, with the X contest, there's some movement on the commercial side. To the OP. are you sure you have the right link? I remember reading the CAIB volume 1 in 2003. That nothing new.

Well. I finally reverted to use a default profile and setup all the keys in the DCS interface. The drawback is that I cannot use the multi-mode and shift features of SST and the X52. Because the sticks forks very well without using SST and using direct in-game configuration, I'm setting hardware issues aside. Maybe I'm having something in my system interfering with the saitek drivers and magic keyboard :( Fact that no one else seems to have this issue is not a good sign :s (or maybe it is...)

Very nice! Thanks for the PDF, Aser.

Clearing out all assigned keys does not help nor does disabling the SAI Direct Output service. While doing some practicing today, I noticed that key that got stuck on down was also displayed on the MFD (the keypress name from SST was displayed). It kept repeating exactly like if I kept the key pressed. Eventually the key started working normally again, but the MFD still acted up, showing the command name (that, until I restated the Direct Output service). Either something is really buggy or I'm having hardware issues. I'll try connecting into another USB port for starters.

OP = Original Poster :music_whistling: I hope you feel the insult :megalol:

I agree with the OP. All these posts about multi monitor setup are very nice. They even helped me setup my own monitor rig. But everything I did was empirical and experimental. It's really not a clean setup... among the problems I still have I can note: - Fullscreen mod crashes the game - Requires a "ghost" monitor to the left because the viewscreen is always centered on the primary - Loss of most usable feature of the F10 map (out of view on the ghost monitor) - Loss of view of the control display [RCtrl-Enter] - Radio text captions displayed on center and right monitor. - etc. For most setup problems, I would be compelled to blame the general lack of understanding of the multi monitor configuration. All we have are examples on how to do a setup, which we can tweak, but we have no actual information on how the parameters are used and, even more, what are the limitations. That would definitely deserve a chapter in the configuration/GUI manual. Something written by someone with more than trial-and-error understanding of the video engine.

aw! It's that simple. Thanks for the explanation. Makes sens.

GGTharos, do you have any good reading reference on the subject? I'd like to know more and understand the physics correctly. The way I saw it was that the counter-rotating rotors would create counter-rotating vortex (vortexes?) that would eventually interfere and get disrupted below the lower rotor. So only the top rotor would ever enter a "stable" vortex. Heck, I barely understand VRS with a single rotor... with two rotors, it's way over my head. Reading time :P

I wonder if anyone ever seen alternative drivers for the Saitek flight controllers? I have the X52 pro and I have the feeling other drivers, perhaps better than those made by Saitek, might exist. Just to give an example, I have a creative sound card, but I stopped using the creative drivers years ago. Instead, I'm using the Kx audio drivers. These are more stable, take less overhead and much more configurable. They really give you low level access to card systems. Something similar for the flight controllers would be nice to try out.

That's how I would tend to do it in the context of this engagement. You have a special meeting with important people you want of the map. Step 1) disable their transportation. Step 2) Bring the building down. Step 3) finish off anyone running away with the 30 mm HE. It's easier to track fleeing people that are on foot ;) Speaking of which... I've never seen any infantry move in DCS (but I'm not far into the first campaign). Do they eventually move around or is there no AI for ground troops?

Those tend to be rather hard to find :music_whistling: Reticuli, interesting setup. I use the pinky for auto hover, trigger level one for gun fire and big fire button for weapon release. I use another key (the mouse button on the HOTAS) to action the cannon/weapon selector flip. I tried to have all the commands that are on the cyclic and the collective on the controllers, but with some limitations. Would be nice to be able to map the flip switch from the cyclic to the fire button cover :D Right now, it only changes the led color and it doesn't seem like the driver is aware of it (not visible in the control panel). I wonder if it could be made aware of this flip switch (hardware wise).

I guess that the whole lake was used to make that good champagne ;)

Strangely, I would have thought that co-axial rotors would be less likely to enter VRS situations because the wake of one rotor influences the other. At worse, only one of the two rotors would enter VRS, causing a slight loss of lift and loss of yaw stabilization. But that just a guess following my (limited) understanding of VRS. I should take the time to read more on rotary aircraft flying.

Kurtz, that works because the function you assign 2 different keys. trigger level 1 -> [key 1 press down] -> trigger level 2 -> [key 2 press down] -> trigger release -> [key 2 release then key 1 release] In the case of cannon/fire or brake/parking, it's only one key, with a modifier. So instead of having [key 1] and [key 2], you have [key 1] and [modifier]+[key 1]. How would the magic keyboard send this to the system? trigger level 1 -> [key 1 press down] -> trigger level 2 -> [modifier and key 1 press down] -> trigger release -> [release all] I'm not sure of this is mad dog is trying to do. He only said he wanted to put weapon release on trigger level 2. But if fire canon is on trigger level 1, I can see how the input system gets confused. When the level 2 is pressed, it's like if the key is already pressed and the modifier is subsequently added. May remapping the keys for a different keyboard layout where two distinct set of keys are used or no modifier (good luck with that :P)

On the Targeting Display Control Panel (below the IT-23 monitor), you have 3 knobs. Form left to right, Helmet Mounted System brightness, IT-23 monitor brightness, IT-23 monitor contrast. It would be the first one. Page 2-54, figure 2-40, point 1.

Yep, don't fly with the instrument lighting on. Turn it of. You can always quickly turn the instrument lights back on with the cyclic push-button if you need. You may also want to turn on the night vision lighting and dim it as much as possible. You should have enough light to read the instruments below the NVG in the light blue light. I would also dim the HUD and put it in night mode. Dim the Abris AMMS as well. Anything that raises ambient light and washes out the NVG should be avoided. As for the Shkval and laser designator/rangefinder, I'm still trying to figure out how to use them under low light conditions. I manage to use the system with some limited success at dusk or dawn, but with very poor rate of success or efficiency under night skys. I tend to turn the contrast way up on the IT-23 to be able to track targets visually, but I can't get the Shkval nor the weapon systems to lock on targets - that even if I can clearly see them. I think good briefing/video note on night operation and night weapon usage would be very useful. ;) Finally, regarding night flying and loss of spatial awareness, this is a problem true to life. It's the reality of night time visual flying. I'm not a pilot myself, but I have a few friends who are pilots and I packed hundred of hours of flying with them on the right seat... most of these hours during night time. Losing most of your visual landmarks make VFR flying very difficult. Most of the area here is fairly flat, but we have some low mountains not far. The only time I got a real scare flying was during a touch and go on a runway fully cross wind and surrounded by mountains. It was a dark cloudy night with isolated rain showers. That time we really when out of my comfort zone (and it was the last time I flew with that guy... never again). I had my eyes on the VFR charts and the altimeter and I somewhat felt like a GPWS beeping and saying "pull up". All that to say that the feeling I have during night flight in BS around mountains (without NVG) is similar. The loss of orientation is very close to the one in real life. Instrument wise, the ADI and altimeter are your friends. You should scan the instruments continuously, always panning back to the ADI between them (assuming you are not using the HUD). Be weary of autopilot when flying around high ground. Outside, city lights and mountains silhouettes with dusk sky behind are very good horizon indicators. Keep an eye open for references like these. I would practice night flight without NVGs a lot before going into night operations. Try flying patterns first, then try to fly some routes over flat surface. Finally fly some routes and do some maneuvering around high grounds. It would be nice to have a good VFR map of the region depicted in BS. Would help navigating a bit. The Abris moving map is nice, but it's not quite like having hands on a map.

I had a similar problem with the 2nd trigger level. In one of my X52 modes, I wanted the first trigger level to be the brakes [w] and the second level to be the parking brakes [LShift + w]. It didn't work out because when the 2nd level is pressed, the first level stays pressed down. I believe that was the cause of a conflict that prevented my setup to work as expected. I believe something similar might be happening with your setup.