docehrenhoefer

Well, multi-monitor works with Vista. I´ve got Vista 32Bit and it works on 2 monitors with the cockpit on the left and shkval/abris on the right monitor. What you need to know: the cockpit will always be on the middle monitor. So you´ve got to change default.cfg, for example, I´ve got 2 1280x1024, then you have to change the display size to 3840x1024 ("virtual" first monitor). Like depicted in some other threads, change the monitorsetup luas to the values that cockpit will be shown in the middle and shkval ans abris to the right. Important: Has to be run in windowed mode.

Thanks guys!

Hello, just a question... Which kind of vehicles do I need if I want to place a FARP where I can rearm and refuel and where I can connect to a ground power source? What has the status to be, Rank or Cone? Thanks for your help, Greetings docehrenhoefer :smoke:

1. Accidentally pushed CapsLock? 2. Sometimes Windows changes Keyboard Setup, still in your correct language? (Mine tends to switch between English, German (Germany), actually correct, and German (Switzerland), formerly correct)

Hi BaD CrC, I´m in Europe (very far south of Germany), so thanks a lot for the link! In the moment I have a Region 2-DVD but i plan to buy a DVD with hard disc recorder, so I´ll have to look for a regionfree device... So sad John Belushi died so young of age... Greetings!!

Thank to the gods I´m not the only one starting with dilettantism and with a slow but steady learning curve. BaD CrC, you have definitely chosen the right avatar photo. :clap_2: I love this film and would be glad if I would find it some day on DVD... Greetings

Well, it was a lot of training for me either. Until I found that out, I´was able to start the KA-50 without using a checklist any more. And no cheating. So, I´ll have to work on my startup speed, but the order and the procedures are clear.

Well, as far as I´ve been able to find that out, the ground speed measurement is somehow linked to the shkval. If you fly with low throttle, ground speed is not measureable and the shkval blacks out.... So, if you lose sight contact to the ground (of e.g. to the topside of a cloud layer) you don´t get your ground speed measured.

ok, ok, stupid me :doh: It was a clear piloting error. I didn´t realize until today, that the main switch for the de-icing is the same as the dust protectors, only another switch position. Test flight successful: with external tanks I was able to climb to 3400, then I jettisoned them and up I went, reaching 5400m with an IAS of 150. "Yessir, I did it! Yessir I learned something! Nosir, I´m not to stupid to learn! Nosir, I won´t forget that again!" :argue:

Yeah, i think DCS affinity tool is an solution. I don´t have 4 monitors, but I have 2 Monitors ans therefore using one ghost monitor on the left hand side, totalling 3840*1024 Pixels. I have an E8650 with an 1Gbyte Radeon 4870. Before using Affinity, I got about 20 FPS over densely populated area, afterwards more than 45 FPS... :pilotfly:

I´ll try this evening and report it! Still 7 hours work to go:crazy:

...of course it must be a piloting error of me... only if I knew what I did wrong. If I only knew what (except for flying too fast). All inverters were on, all anti-icing equipment was activated... batterys, inverters were on (AC/DC on auto), ground AC and ground power off, APU off, throttle on auto, dust protectors off, climbing speed 3m/s, then suddenly rh and lh eng limiter on, and just a few seconds later engines out...and gearbox temp failure. The throttle was something like 97%, 98%. The only thing I could think of, that I was moving too fast for outside conditions and that this made an engine overheat. Is there a table of the power characteristics / flight profile anywhere where I can look up at temp and weather which speed is allowed? Thanx

...seems as if I´ve been too fast... IAS about 180 km/h... I´ll try again this evening. Gotta work now.. .:cry:

ah, and I forgot: I received a message, like "gearbox overheat"...

Hi Nate ...absolutely sure...

I made myself a little free flight mission over the mountains. Rainy conditions at 10°C on sea level, of course flying with all anti-icing equipment on. When I climbed up to 3000m above SL the engine limiter went on. I jettisoned the external tanks I had loaded, slowed down a bit and was able to climb up some more, to about 3500m with snowy precipitations. :cold: Suddenly the engines suffered an akute power loss and stopped working, the only thing to do was to try an autorotation landing. :joystick: Can someone explain this to me? How can I check if the KA-50 is able to fly to what altitude under given conditions, and how can I decide how much IAS is allowed? Thanks fpr your help in advance, doc-e

...an employee of Saitek Germany gave me information today, that they plan to release a force feedback variant of the X52 some day... she couldn´t tell me when, but it seems to come. Yesssss.... :D

Position change? I am not used to programming lua files: Does anybody know how the position of the control indicators is defined? For example, I want to change the position from lower left to lower right... :huh: Thanks in advance

Well, Shrubbo, in a way you are right, in a way not. I own a Saitek X52 and the Saitek Rudder Pedals, and sometimes after continouus trimming the rudder is so much off-center it is almost impossible to re-trim (see all the posts about Saitek and re-trimming). So this little tool may come handy. ...and: American Helos have a cyclic position control inside the cockpit, at least the CH-53 Super Stallion and the Sea Hawk and derivatives afaik so it´s not so far off....

I really would like to try your GlovePIE script, Reticuli, but I own a Vista 32Bit Machine and PPJoy does not want to work on it... In the meantime I have fussed a little bit with my computer chair and modified it, so that a have an approx. Huey-Like HOTAS and Collective Config. (...ever seen that darn grinning face of your wife :D telling you she thinks you are just an over-sized child???? :gun_rifle:) Now flying the beast is just a dream...

So, after doing a lot of research in SimHQ and eagle.ru forums and trying a little bit: the best method to bypass the trimming problem is to engage flight director when you use a self-centering non-FFB-joystick. Esp. when flying NOE or in the attack phase. It´s not exactly fly-by-wire/autotrim, you still have to trim, but much less and you don´t have to fight the autopilot (I still can´t believe it´s just 20%... for me it seems like it is much more). You don´t have any problems with rudder trim far off-center and with wrong trimmings that made my helo rotate fast or crash tumbling into the ground (very embarrassing when that happens 3km off your targets - can you imagine those grinning mudrats??) So: fd off and route mode/dth on while in transit, when carefully closing in to the battle area fd on with a careful trimming (trimmed on a 40km/h pitch lets you gain and lose speed very fast), when establishing hover fd off and autohover on. That worked like a dream for me. You can even take the right hand of the joystick, doing slight heading changes using rudder and keeping altitude (collective brake and heading hold mapped on throttle, FD, auto-hover and trim mapped on joystick (X52)). Trimming while in full battle is much more difficult than keeping flight attitude.... Greetings.

Problem-solved. Easy. Guys, I think I solved the problem. the trick is, to enter hover with stabilzed heading and with an airspeed lower 8 km/h. Avoid fast changes of the altitude. Then the helo will find a stabile position rather fast. When the helo has stabilzed, press trim and the collective brake. My mistake was, to trim the helo when it still did corrections to stabilze itself, so the small rudder inputs from the autopilot were trimmed.... an this made the helo rotate. No need for .lua tweaks... @aphelion: I used the rudder by turning the joystick grip for a long time (in FSX). But think about it, having rudder pedals is much easier und more decent to use... fine tuning works much better. Greetings Uwe aka docehrenhoefer

That wouldn´t make sense, since helos always have a tendency to rotate, and the KA-50 has this tendency too though it has 2 rotors...this is because one of the rotors is slightly higher than the other one. And then there is that wind effect... So it makes sense to trim rudder, and I wouldn´t want not to have this feature. @bobcat: that was exactly what happened. I slowly stopped the fst movement by counter trims. @nemises: I´ll try this, thanks. docehrenhoefer

spasibo, guys... I´ll try that, Kula66, maybe I kicked rudder while trimming after initiating autohover... doce-hoefer

Hello! I just entered a hovering state that is rather scary and annoying (though I didn´t crash jet...) I initiated autohover, and just a few seconds later the helo started to turn around very fast and was becoming even faster though auto heading and auto-turn to target was activated. I was able to stop that process by applying a lot of counter rudder, but imagine hiding behind a ridge with some leopard waiting for their vikhrs, but the helo rotating furiously around its axis??? :megalol: It would be very nice if someone could explain me what I was doing wrong.... :huh: Thanx a lot, docehrenhoefer