therion_prime

Edited for untrue content

This happened to me three times in three different missions: Everything works fine when suddenly - after at least 20 minutes mission time - the laser rangefinder displayes erratic numbers and I cannot fire Vikhrs anymore (I don't get a launch authorisation). From visual judgement, the target is at least 5km away, yet the lased distance shows something below 2km. I made an INU fix (but what does INU have to do with a laser rangefinder? but who knows?) but that didn't solve the problem - as I expected. Also I was not hit, nor did the laser overheat or something like that. Switching the laser standby on/off or caging/uncaging Skhval didn't help either. Did anybody experience something similar?

Did you turn on the targeting and navigation system switch (left hand panel near the collective) ?

IIRC some systems were not implemented in the Beta that Wags used for this production note.

Thanks for the very insightful explanation, ryuzu. Especially this part: "...that the ideal straight and level in trim flight is not necessarily something we should expect (or even try to achieve) - it isn't in real helicopters and while the KA 50 is co-ax in design I don't see why it should be any different." I always tried to achieve a perfect "straight" flight like I was used to. It seems that I'm not flying as bad as I had thought! :doh:

Were "Dynamic campaign" and "Dynamic weather" already mentioned? :P

Hmm. I have many years of flight simming experience - mostly props. I'm perfectly familiar with torque / sideslipping / rudder(trim). Its' just akward that the BS is behaving so different / akward. I always thought this is a bug or a "feature" of the AP dampeners that try to maintain a heading different to the longitudinal axis of the copter. But on the other hand: I'm pretty new to helo sims, so what do I know? :D

Not entirely true, there is another method. Change attitude -> push trim button quickly -> immediately let go of the controls -> tested and works perfectly.

But why am I not flying straight at high speeds, even when the slip-ball is centered (no side wind)? Example: acceleration to 250kph -> slipball wanders to the right -> i counter with right rudder -> ball is centered -> trim -> chopper is not flying straight :huh: Or from a different perspective: When I'm SEEING that I'm flying straight by observing the ground or watching with external views, then the slipball is almost always off to one side, sometimes all the way to the right.

You can copy the keybindings and controller settings, too (Input folder. Don't forget to make a backup first).:joystick:

Me too (Radeon 4780), but I have this in LockOn too.

I believe there's a confusion of the terms "collective" and "trottle". The collective-axis is what you probably want to map to your stick. The throttle is set to "auto" during startup and (under normal circumstances) never touched during flight.

I think you refer to the "gearbox oil pressure" message. That's normal. No malfunction here. Just turn off the EKRAN and the message will go away! :D

@ mvsgas: I thought the laser-designator mode switch is only for type 29 missiles and not for 25? I think it's in the manual. And that you have to hold down the button is new to me. I always hit buildings dead on with the normal way of employment. But maybe I missed something :dunno:

Well, they're in the loadout screen and I actually find them quite useful for destroying buildings where they actually tend to hit the target :D. @ sobek: Grüße aus Innsbruck ! :cheer3nc::beer::cheer3nc:

Should be no problem. Alternatively you could map the rudder axis to a rotary on your throttle.

Unrealistic shutdown procedure: 1) Trottle to Idle 2) Fuel cutoff levers off 3) When Rotor RPM is low -> rotor brake on 4) The rest doesn't really matter, you can just switch off the batteries and the chopper is shut down. If you want to start again, just switch the batteries on and everything's working again. The order in which you turn off the switches doesn't have any negative effects as I experienced so far :D.

Try to convert the music into WAV format, 22.5KHz 16bit mono. Never had a crash with these settings. There also seems to be a restriction on filesize. I tried to put the radio channels from GTA:Vice City into BS, but BS crashed as soon as I tuned into a channel. Each file was ~ 300MB big, so I splitted them into 6 parts each and now it works flawlessly. BTW, the music from GTA:VC rocks in BS!

Loopings and barrel rolls with high collective = bad :music_whistling:

Note: You do not have to set the monitors to "span horizontally". Just put them in "extend desktop" mode and run BS in windowed mode like described in another thread.

Yeah I thing that was the problem. Using Notepad++ now. Thx.

Thanks a lot! :thumbup: Rep. inbound

Can somebody please attach an unmodified Beacons.lua (in ..\Ka50\Scripts\World\Radio\ ) ? I corrupted mine while trying to mess with the radio stations and I didn't make a backup :doh:

Hmm... I always switch off the heading dampener autopilot blue button thingy. Works for me ... :dunno:

I actually dont find it that difficult, but I've been flying the FSX choppers (the Bell mainly) as a training for BS before it was released. That DID actually help a LOT. The second biggest help with flying the BS is a homebuilt long centerstick I made out of an old Cougar with hall-sensors from a defunct X52. It has no self centering but is dampened using RC-car hydraulic dampeners, so there's almost no need for trimming. I can tell you that flying with this stick is SO much easier than with my X52Pro.