Jump to content

Nobody96

Members
  • Posts

    211
  • Joined

  • Last visited

Everything posted by Nobody96

  1. Make sure that in the DCS options, under Axis Commands, using the button FF Tune, you have set the shaker value to 0. so long Mathias
  2. Nobody96

    Rain

    Really slow in a A-10 still means around 140knots, a speed at which the KA-50 starts to get into trouble. I really doubt that you will have a lot of raindrops on the canopy because they are hitting the canopy at a pretty low angle. My old 2cv has a very small but nearly upright windshield and at my top speed of 90km/h I cannot see anything if it is raining more than a bit. On a modern car, you have a windshield that is bigger because it is installed with a really flat angle. This way it is way bigger than the one in my old 2cv but provides only a slightly bigger field of view. Back to the A-10: the flat angle at which raindrops would hit the canopy would dispense them on a pretty big area. At a speed between 240-550km/h you would hit more raindrops per second but also blow them away pretty fast so I recon that as soon as you are fast enough to fly, you shouldn't see any drops on your windshield. so long Mathias
  3. Thanks guys, its working like a charm :) so long Mathias
  4. Either your CapsLock is broken or you are doing the equivalent of shouting at people, demanding that they help you. Why? so long Mathias
  5. Already? I have a massive hangover but in my timezone there is still a lot of Saturday left :-) so long Mathias
  6. Its starting to become "later this week"
  7. I really don't understand the problem. The BS2 patch is announced for this week, meaning today or tomorrow, since I believe/hope even ED doesn't work on Sundays. I recon the reason for this very little time difference is either, that a simultaneous release would have killed their servers or that the A-10 patch was indeed finished earlier and they didn't wanted us to wait for it needlessly. so long Mathias
  8. I just ordered some spare "F5" keys...
  9. Ok, thanks for the heads up :-) so long Mathias
  10. Hey ho. Any news? Have you tried it at 300m already or are you willing to share a track where the range calculation works? so long Mathias
  11. Ok, I did another test and well... I cannot confirm your results. Could you please send me a track where you measure the range and don't get the it mixed up after the laser stops? I tried several different heights and also checked if it might be related to the barometric altimeter but no joy. so long Mathias shooting-range shkval calculation different heights.trk
  12. Two switches left of the switch you used to turn on the shkval is on labelled AT/GS, which will fix your shkval on the inpact piper. Also you can simply put it to standby by pressing the reset button on the very same panel. This way you will also put your hud into nav mode. so long Mathias
  13. Uhm... I bought BS1 and BS2 two times, for me and a friend, but I used only one account. Is there a possibility to move one of each key to another account? If not, are there any problems that could arise? I mean could I still give him his keys to activate his install to play together online or are the keys also bound to the master-server login? so long Mathias
  14. Quite on the contrary, I like your results and already expected that there is more to it. I will check later if I am able to get your results when I am hovering at 50m. so long Mathias
  15. The current releases will not run as a VM because of starforce.
  16. I don't know, because I just played your missions since BS2 came out. I just wanted to say that HiJack isn't the only one having problems hosting them. I also, like him, have yet to find a reason for this. I will try to edit your missions, meaning that I will reduce the civ traffic. Maybe that helps. And no worries, I will not publish them. so long Mathias
  17. I also have massive problems hosting and playing the missions simultaneously. Don't know what the reason is. Graphics card seems happy, so does my processor. The only thing I noticed just now is that BS2 is only using 4gb ram even if there are another 4 available. My System specs are: Phenom x6 1075 AMD Radeon HD6800 8gb ram so long Mathias
  18. Ok, THAT might be the reason :-) Never used a twist-stick in black shark. so long Mathias
  19. What helped me most was getting a few hours in the shark without a single autopilot activated. This way I learned how it reacts to regular inputs and got a feeling for it. You cannot do a flat turn with a IAS of 100+ and the bird tries to roll when it picks up speed. Thats all explained in the manual quite nicely, but imho you have to get a feeling for it. That done, start using the APs with the FG swich on. This way you see where they are helping you and you get a feeling for them to. After that turn the switch off and try to use the AP to your advantage. BTW: The thing I currently miss most because of the ffb-bug and the inability to use the autopilots is that I cannot really trim my rudder anymore to slip left around a corner while locking things up with my shkval. Therefore I don't get it why anyone wants to unchain their pedals. Nevertheless, its a nice option, because everyone seems to have his one way to tame the shark. so long Mathias
  20. Well... what is a British pilot doing in a shark anyways? IMHO he should be court marshalled, not given a medal :-)
  21. sweet, thanks :-)
  22. Ok, I tested the whole thing a bit further and did a track. It uses the shooting range mission, so it should be easy to reproduce. In the track you see that the shkval range gets set to a wrong value as soon as you slew it. I also set up some NAV/TGTs to show that they get wrong values and also that these values kind of correlate with the wrong shkval range. Could someone please try to reproduce the range issue using the shooting range? Just fire the mission up, lase some place where you don't get a lock and slew the shkval afterwards. so long Mathias shooting-range shkval calculation.trk
  23. Tested it with 80, 60 and 40 as saturation, but it was even worse. It is simply to fast for minor corrections at heigh range. I am currently using: "0 5 6 6 6 9 15 21 28 45 100" for the horizontal and vertical slew axis'. I would prefer to use something like 0 2 4 6. I will keep hoping that someone takes a look at this someday or, if it is a needed game-mechanic, doesn't but tells us so :) so long Mathias
  24. I will do that. By the way: the issue is not that it is to fast overall, but that there is a minimal speed for the tgt-pod and the shkval which you don't seem to suffer from when you are using digital inputs to slew them. Sadly though I ran out of colie hats, because I use a cougar throttle in combination with a g940 stick and use the cougars comm switch as modifier. so long Mathias
  25. So curvature or custom curves below 6 don't work for the cougar ministick. Pretty disappointing... I will keep it at 6 and continue swearing than. so long Mathias
×
×
  • Create New...