Jump to content

Brach

Members
  • Posts

    43
  • Joined

  • Last visited

Everything posted by Brach

  1. I'm with Viper and Sobek on this one. I normally don't hit the auto hover until I establish a stable hover myself. The auto hover just serves for me to not have to worry about flying while I zoom into the shkval screen to pick off targets. Turning to a target that way becomes very easy also. I just momentarily disengage auto hover, jaw towards the area I want to engage and re-engage auto hover. The "auto turn to target" option for me doesn't always seem to work properly (must be a bug) since it doesn't center the nose of the copter on the target, basically forcing you to jaw the helicopter a bit anyway before you can get a clear shot. Really, just keep trimming whenever you see fit, the button is there to be pressed, so press it all the times you feel the need to. Heck, it's even for free. :P Seriously though, trim until you are satisfied and when you get to slower airspeeds make small adjustments. I messed up a few missions before I got the hang of it, but I can assure you, under the pressure of battle, one does get the hang of it really fast. At least I did. :lol: And don't worry, we all crashed this bird a ton of times at the beginning before we actually managed to fly it a bit smoothly. And still, I have to admit, I sometimes manage to loose track of something and crash over the most stupid things ever. One just keeps learning with this game. Gotta love that one. :D Just keep practicing mate, I'm sure you'll get there also. :smilewink:
  2. Hi all, Now I know this is going to be a daring question... :music_whistling: But is it known yet around what time the patch should be out? :D I don't mean to push or anything, I'm just being curious. I searched the forums but couldn't find anything specific. And since there are quite a few interesting fixes/changes I was wondering if anyone from DCS had made an official statement of when they were projecting to release the patch. I imagine that an exact date won't be possible, but a nice (gu-)estimate would be great also. Cheers.
  3. Shame, I already bought the download version a while ago. Maybe once the misses allows me I can also buy the boxed version. I'm not holding my breath on that one though. :music_whistling:
  4. ROFL muell :megalol: Most priceless remark ever! Seriously though, it would have been fun if we would have had an option to radio for a rescue mission and sit and wait for the rescue chopper to pick you up. Maybe a nice thought for a future small add-on to the game: "DCS rescue pack" :D
  5. I voted Apache since I've seen too many fixed wing sims already. :P Not that I would mind to see a good combat plane in development, it's just that it is such a nice and refreshing change to have a good combat helo sim. I just can't get enough of it. :thumbup:
  6. Great work mate, thanks for your efforts! Maybe you could include some other common resolutions (if you have the time). There are lots of us out there who also use lower resolutions like 1280x1024 and others. Nice tests though, I for sure was curious to see how much of a potential difference there would be between vista and windows 7.
  7. Mitch, Are you out there still mate? You'd really do us a favour with a ModMan compatible package, since your skins really look very good. Any chance you will be able to do that?
  8. Same here on Firefox on Vista, so it is not you. :megalol:
  9. And we are having fun at the expense of someone who obviously has no clue what he was reviewing. :P
  10. Well, it looks like I solved my problem with the help of Saitek support on their forums. The solution was so simple that it was rather embarassing. It turned out that while programming the SST software I had not been consistant in pressing key combinations at the same time. At times I pressed one key, released it, and then pressed the other, not knowing that it simulated exactly that sequence. So it has been merely a matter of remapping the buttons with key combinations and making sure that I pressed all buttons at the same time. Can you believe that? :doh: Anyway, what I did in the end is make a full X52 profile, take all joystick assignments out of the DCS profile except for the axis assignments, and that was it. It seems to be working fine now. Back to flying. :pilotfly:
  11. Erm, now you guys have got me worried. I did reinstall Windows completely due to a new DVD player I installed (I always do this with a hardware change). I however did not deactive DCS and just reinstalled it on the new Windows with the key that was provided through mail with the download version of the game. Does this mean that I used up one of my activations? I never got any confirmation of this while installing or through mail after activation though. :cry: I'm really confused now. :noexpression:
  12. I bound the zoom function to the scroll wheel on the throttle. It does not work as well as the mouse scroll wheel, but at least there is no stutter. Might be worth the try. ;)
  13. Well, I did some more in depth tests, but it seems that even the beta 6.2.2. SST software is not working for me. The two errors that make it impossible for me to use are: 1) Left Shift is not always transmitted well, resulting in just sending the key without the Left Shift. (example: dial lights with LShift K at times are transmitted as just K and switches on the cockpit lights instead of the dial lights). 2) Left Alt key is not transmitted as such but as the List key. I've been waiting for a couple of days now to be able to post in the Saitek forums. However, so far no go yet. :cry: It seems admins have to authorize people by hand, so this might take a while. :mad: It's pretty frustrating since part of the X52 controls can be defined as buttons even though they are technically sliders (rotating dial sliders), which in DCS we cannot do with their mapper. Worse even, the small mouse joystick is not recognized at all by the DCS mapper, while it is really convenient for stuff like the shkval slew function. Anyway, I recon I might just be unfortunate in that my keyboard is obviously not used by Saitek in their QA department, otherwise this probably wouldn't be an issue. I'll update when I know more. Oh, and I did try combining profiles, partly SST partly DCS, but that doesn't work and results in conflicts, even if you make sure you don't double assign keys. So that one I can forget about.
  14. Now correct me if I'm wrong, but there is a distinct difference between night vision and infrared vision. 1) Night vision just amplifies the little light that there is when it is night. 2) Infrared vision allows you to see the infrared light spectrum translated into light we can percieve with our own eyes on a screen. With the latter one would see humans and vehicles, no matter how they are disguised or where they are hiding, after all their heat signature would show up with infrared. With Night vision, it would be the same as during the day, since it is only amplified light, nothing more. I haven't delved enough into the manual yet to be able to tell you what the KA-50 carries. But if it is night vision only, then it makes sense you don't see hidden units. If it is supposed to be infrared however, one would expect to see units in the woods very clearly. Again, I'm for sure no expert on this matter, but from my experience with several sims and reading up here and there, this is what I would make out of it. But I leave the technical details to the ones who know more about this matter. :P
  15. Hey Mitch, For those who are a bit less shavvy at all this modding stuff, would you be able to make a ModMan package of your skins? This would avoid all the manual editing of files and risks of things going wrong and stuff. Might be worth the time investment instead of having to explain to everyone how to edit files. Just a thought. ;) Great skins btw. :thumbup:
  16. Ok, if you use a clear profile in the SST software and load that, you can use the second stage trigger without a problem. Also with the SST software if you make a full profile, you can use the second stage trigger without any problems (think you have to use the version 6.2.2 beta to be able to do this though, but not sure). So there are ways to use it, you just need to try the various options and see which one works best for you.
  17. Thanks for the heads up mate. But strange all this, since I have an us-intl keyboard, which should be pretty common I would think. It is a bit old though (3 years or so) and officially not even listed by Logitech anymore (even though they still support the drivers for it, one just has to look around a bit to find them). I should have a look and see if I have a different keyboard laying around somewhere still. That would make a good test to see if it is maybe the layout of this particular keyboard that might be the problem. Thanks again though Adrian, much appreciated. :thumbup: Edit: I registered at the Logitek forum and am waiting for approval of my registration. Then I'll start asking them if they might know what I can do about it. At some point we'll nail this one down for sure. :P
  18. Check the post above about Mapping the X52 in DCS. We are trying to work out some oddities in the profiling of the X52 either through the SST software or through DCS. ;)
  19. Ok, did a quick try of that software, but that one has a bug in there as well. The left Alt button is not being simulated as such but instead as Menu. So that one doesn't work either. It's a bit frustrating that over there at Saitek they are obviously having problems getting this SST software right. Which seems a bit odd to me, because all they have to do is follow the windows keyboard definition and they are set. Weirdest part of all is that my keyboard (correct drivers updated and installed) doesn't even have a "List" button on the left side. It does on the right though. So in my case, that beta doesn't work either. Thanks for the tip though, it was worth the try. ;)
  20. Just click one of the mappings, in the upper bar on the right you can select "load profile" (or something like that) and just select the blackshark one. This is the default mapping. Unless you overwrote it, then I don't know how to restore default mappings other than going through those you changed, like you already did. Good luck!
  21. Oki, thanks Slayer, gonna try that one right away and see if that works better. :)
  22. Oh, Golden Tip about the clutch there mate! Thanks a lot. :thumbup: The mutliple keystrokes I had already figured out, like what you are saying. That's not my issue really. The problem is that when I take the cockpit light switch LShift T (if I remember correctly) and program one of my buttons to send that to the computer, it in reality sends something different. I don't know what, but it doesn't fuction the way it is supposed to. At least not though the SST software. My right shift key is not recognized at all by the SST software, which also provides some problems. Obviously there is no distinction between left and right shift buttons in my case. And yes, it's the most recent driver and accompanying SST software. Maybe it is related to Vista 64, which in the past had some problems with these kind of things. For that reason I'm now trying to configure things solely through the DCS keymapper and see how far I can get with that. At least I know for sure that the buttons will do exactly as I assign them. Programming through the SST software would be ideal, but so far it seems to me that there are still several bugs in there that don't permit you to program it completely to your heart's content. I'm still trying out though. I don't want to give up that easily. :P
  23. Yep, like they ^ said. Too difficult for your taste: go arcade! :joystick: Really, it's there for those who just want to hop in there and shoot stuff and not bother with the realism. Have fun! :D
  24. The thing is, when you delete all shift states in the SST editor, and use that profile (with no definitions whatsoever), you free up the following buttons for usage inside DCS: Pinky button Mode button Mouse fire Scroll button (or second mouse button) Without an empty SST profile these cannot be used through DCS because they for some reason are not freed up by the SST software. Also, not having a profile loaded will not allow one to assign these buttons in DCS. I don't know exactly why, but it seems this is the way it works, and I can confirm that with an empty profile active the above mentioned buttons can be assigned in DCS without problems.
  25. Thanks a ton mate, I'll give it a try for sure. It turns out to be a bit tricky, since some mappings don't seem to work, and it is not clear to me why. I really want to go through this a bit more thorougly to see what might be going on before I decide it is not working. For practice I did try to map everything in the DCS software, and I have to admit that I can manage to map all needed fuctionality (mapped after how the real cyclic and collective controls are configured in the KA-50). However, the rotary sliders and the one slider cannot be used. This is where I miss the ability to define them as 'virtual' switches like one can with the SST software. At this point I'm leaning towards trying to make a combination of both. But I'm not sure that will work properly. Just to give you an idea, on the stick I mapped the A fire button to toggle the gauges lighting (like in the real KA-50). For some reason though, that key combination doesn't work when I have a profile active. Not even when I punch in those keys on the keyboard. I'm really baffled as to why this would happen. I'm thinking a software or driver conflict might be the culprit. But since I have quite a bit of stuff like that on my computer it will take me some time to figure that one out. The other thing is that the 'clutch' button on the throttle of the X52 can be mapped through the SST software, but once you run DCS, that button is disabled and doesn't do anything but make a few leds on the joystick flicker. Also a pretty strange one if you ask me. So anyway, this will probably take me some days to figure out (don't have that much spare time on my hands) but I will definately check what I can and report on my progress. Especially since there must be others trying to battle similar problems as well. Maybe in the end we can find a workable solution, also for others. I'll be back. :pilotfly:
×
×
  • Create New...