Brach

Ok, I'm stunned, it is working. :D This also solved my problem where the LAlt key wasn't simulated properly. No clue what the cause of that one was, but now it is. Ok, I'm off programming my profile. At least this way is a bit more user friendly. Once I'm done and have a bit of spare time on my hands I might compile a howto for other users with the same difficulties that I had. Thanks a ton for the tips guys, this really helped me out a lot. Soon I'll be flying so much more smoothly. :P :pilotfly: Edit: Well, it seems I'm running into some problems still. Not all key combinations are working and neither are all buttons doing what they are supposed to. I'll need to try out some more things still, but will report my findings once I feel that I covered all options.

Hyperfighter, mate! I'm for sure going to try that. Obviously using the SST software would be best since it gives us access to so many more options. I'll get on it tonight and let you guys know how things went. Thanks again mate, great tip. :thumbup:

Ah, thanks mate, that was just the info I needed. :thumbup: I'll put myself today to turning those 'till I go nuts and see if I can manage to get them detected also. :smilewink: Now I need to figure out if I can get the modes switch to work in some way also. :book:

@ nemises: Well, these things I already knew so far, but thanks for the tips anyway. :smilewink: See, the thing is, that certain buttons or rotaries cannot be assigned inside the DCS software. Or at least not that I have been able to discover. I'd love to be able to use the "mode" switch on the joystick, through which we could theoretically have 3 times as many functions on the controls (I'd imagine a seperate take-off/landing mode for which specific functions could be assigned to buttons in that mode). I think due to the tips from glottis I can actually use all the 'clickable' buttons. This leaves the rotary switches. In the SST one can define them as buttons instead of 'sliders'. I was wondering if the DCS mapping software allows one to do the same thing. And why are there so many buttons in the drop down list? Is that because in reality they created input for all buttons in all mode combinations (1, 2 and 3)? And if so, which code stands for which mode? To give you guys an idea: I find in the axis commands list: joy_aslider1, and joy_aslider2 but also joy_fslider1 joy_fslider2 joy_slider1 joy_slider2 joy_vslider1 joy_vslider2 However, there is only one slider I can actually select: joy_slider1. So, which ones are the others? The rotaries don't trigger their selection when I turn them, however they are there in the X52 profile. Are these 'bogus' definitions? Should they work but they are just not automatically recognized when you use them? Many questions and little answers. :D Anyway, you guys get my point. The list with the buttons is even longer and less clear. I cannot imagine that the guys at DCS made lists like these that don't make sense. It is a bit hard to figure out what is supposed to be what and what we can or cannot do with them. I come from an IT and programmer background myself, and we always used to reason: if it is not to be used, don't put it in there. Hence I expect all these functions to actually be 'usable', I just need a guide on what they represent, and why lots of them obviously are not recognized automatically when you select a button or a rotary button on the controls. But keep them coming those suggestions. The more the marrier. :thumbup:

Nice one Glottis, :thumbup: That freed up a couple of buttons. ;) Now if only I would be able to get rotary buttons to work as switches instead of slider types.... :huh: So for I'm still not getting those recognized by the game. At least not automatically. Any suggestions?

Hi all, Well, to start; I have tried the SST software from Saitek, both the latest version and the beta. Both have some serious errors in there which don't allow to create a proper profile for DCS since the software doesn't properly support the modifier keys. The Left-Alt key is not simulated at all even (simulates a Menu key instead of the alt key in my case), and the profile for some reason also creates some stutter in the game itself. For these reasons I want to map all my buttons in the DCS software itself. There is one problem though: it doesn't automatically recognize all my buttons. :cry: When I go through the drop down list of all buttons I would think they are all in there (the list is huge), but I have no clue which button stands for which on my joystick or throttle. Does any one know of a mapping chart for the X52? What I mean with this is a table in which it makes a clear reference to which code stands for which button on my controls. To give you an idea: now it has 4 hats defined, while in reality the X52 has only 3 and a virual mouse. I recon the 4th might be the mouse, but I'm not sure. Also, there are two mouse buttons, a wheel, rotaries, etc. The rotaries are for sure not recognized, not even in the axis configuration section. I'm hoping that they are potentially identified as buttons though. The question is which? Now I have a list with button1 through button120 or so. :music_whistling: Anyone know which button is button86? :P Indeed, not very practical. Anyway, any info would be most helpful. Maybe we could turn this into a X52 mapping thread for all those users out there who also use a X52. Those must be quite a few. The controls are great, never had a problem with them. Now it is just a matter of getting them configured properly. :joystick: So don't be shy, please share any info you guys got. Hopefully it will make my mapping life a bit easier. :smilewink:

What I would like to add to the wishlist is: In game mission editor. As it is now, we have a map-editor. Here we cannot see (enlighten me if I missed something) in game what we are putting where. Last night I tried to set up a simple mission with some fixed objects and such, and it is really hard to figure out what ends up where. A FARP's dimensions are not shown in the map, just the icon. So if you want to put it close to a road and align it with the road, one has to go back into the game numerous times, just to align the FARP and see where it ends up exactly. There has to be an easier way to do this. The way it seems to me now it is so time consuming to know where objects are placed and with which orientation (openings are not always oriented towards the direction in which they point), that to me it is silly to start designing missions yourself. So, an in game mission editor, or at least object placement tool, would be a must I would say.

Just out of curiosity: are there any good free online courses russian? I just cannot stand that I don't know how to pronounce the words to start with, let alone know the russian alphabet. Any good resource would be very helpful.

Hmm, let me check that one next time I try it. I'm still trying to get everything under control, so I might have missed that detail. :P :joystick:

Ah, that would explain a lot. :) I'll try the mobile command post for sure, now I'm curious. :joystick: :D

Well, what I noticed is that once I am hovering more or less stable (not drifting too much) the tower tells me that I'm cleared for take-off, even though I did not request it. Odd maybe, but very practical because it makes sense to do so after an established hover. I have no idea how this is handled in reality in the russian military, but I imagine that officially one would have to ask for permission first. After all, I could just do the hover check, land and then wait for another 30 mins before I really want to take off. Also, direct take off clearance has never been given to me when I'm on a landing pad. When I'm on an apron on an airport it does work though. I figured that on an airport I'm "supposed" to do it that way, so maybe that is why it works like that. But I'd be the first to admit that it doesn't really work the way I would expect.

I am having the exact same oddities. However I did notice that when you go into hover really low to the ground (like 1-2 meters height) the tower will automatically grant you take off clearance once you are in a fairly stable hover. It would be nice though if we could get a response from the tower when requesting take off while in hover. Even a "negative" would just do. Not getting a reply whatsoever seems a bit unrealistic. :huh: Also when you are on a pad, I noticed that take-off clearance is never given upon request, not so far as I tried the game (only have it for about a week now). I don't understand the auto hover problem at low altitude, since after having flown a bit you can engage the auto hover without a problem. So I'm not really sure what is up there. When you hover a bit higher, it has no problem maintaining hover. So I am not sure if the INU has anything to do with it. So the safest thing I have found to solve this is: 1) Request controlled hover. 2) Perform hover at really low alt. (max. 2 mtrs.) 3) Expect auto clearance for take-off from tower once you hover. If not, just land it on the pad again and try again, either control hover or direct take-off.

I'm with Sobek on this one: learn to trim for a hover. With the trim button that is pretty easy (map it to a joystick button for easy access). And don't feel embarressed to trim a few times before you have a decent hover. Small inputs and once you have something aligned properly (one of the axis) just hit that trim button and go for the next axis, until you are in a proper hover. Don't worry if you drift a tad at the beginning. Once you get the hang of that, it will be very easy to enter a hover from 200km/h and a 10 m/s side wind, just having trimmed your helicopter. Being lazy, once I have it trimmed I always turn on the auto-hover. Benefit is though, that when you disengage the auto-hover, you will hardly have any surprizes. :joystick: :D Good luck!

Good point, I was wondering the same thing. :helpsmilie: Can't imagine that there is no quick key one can press to achieve the same thing instead of pausing and un-pausing the game in order to get this to work.

I'm also using 8.12 and never had any problems. Unless there is a pretty urgent reason to upgrade drivers, I'll stick with these. Vista 64 Ultimate here.

After only having played the game for some days now, there are some things that I feel that are missing: 1) Pilot Log: should contain a distinction between dying and POW or MIA and such. Now when I eject, I'm always reported as dead. To me this doesn't make sense. When I successfully eject, I did not die. :cry: How about a number of crashes (instead of deaths) with added to that the result for my pilot (dead, missing in action, POW, etc.)? 2) Option to use a second monitor (any resolution) to project a screen of choice onto (shkval or abris), where it retains the aspect ratio of the original screen. The way it is now one can only use multiple monitors when the desktop can be stretched over multiple monitors and then the abris looks awefully scewed. Best would be to make them both undockable screens that can be dragged to another monitor. :D 3) Make the usage of new skins easier. Right now it is too much of a hassle to add a new skin. Wouldn't it be possible to make a simple tool that just adds a new skin and allows one to select it for missions, campaigns, etc? Also one that would allow us to keep using them with new patches and such. 4) Instant Action: give us a simple config screen in which we can select the number of wingmans, number and type of threats and weather. That would give us some flexibility as to how we would like to try out things instead of forcing us to design a whole mission for this purpose. Those would be the things that I would like to see in a future upgrade/patch. Still having a blast with the game though, great job you guys did there. :thumbup:

Does anyone know if MS actually did roll out a patch to solve this memory issue? Just being curious. :smilewink: