J3Langford

Greetings, I would like to document a bug found in the P-51D Beta. The bug has been found in the "Training Menu" as entered from the "Main Menu." Description Detail: - An attempt to enter the "Training Menu" from the "Main Menu" results in an indefinite loop. Retrace Steps: - All training missions completed until landing demo. - Landing Demo skipped. - Instructor led landing completed. - Solo landing skipped. - Air to Air training completed. - Exit to "Main Menu" - "Instant Action" selected followed by "P-51D vs. P-51D dogfight." - Played mission several times. Shot down repeatedly. - Attempted to eject too close to surface erroneously resulted in successful deployment of parachute. *** Last attempt to eject too close to surface with erroneous deployment resulted in crash to desktop. - Attempt to re-enter "Training Menu" resulted in continuous "loading" loop. - Ctrl-Alt-Del to close application. - Additional attempts produced identical results. - System Restart and additional attempt produced identical results. System Description: Intel Quad Core, 6GB ram, GTX 280, Win 7 x64, Track IR, TM Warthog, Saitek Pro FLight pedals, Application installed on separate HD not OS HD. Hope this can help, let me know if I can provide you with additional details etc. Thanks, -

I have tried the .Lua edit method and my frame rate was abysmal. Not exactly sure why but it was unusable at that rate. However everything looked proper except my center screen aspect ratio was slightly too narrow. Looked into Helios briefly, I created a profile just for the Shkval. However there was no game data displayed only the Shkval hood.

I run BS on a 52" screen. I still want the Shkval on an external monitor. I don't have anything very fancy for the job, just a little 14". I tried to use the in game monitor config but that just places everything on my 52". I know there are some 3rd party utilities out there. What are they? What is best? Links?

Thanks gents, Getting things done.

Yes, I have unfortunately discovered this. But is there a solution? Does anyone know why exactly? Surly there is some way to mitigate this...

I attempted adding my G13 to BS2 and as I try to assign input functions 'within BS' there is no cooresponding key/buttons showing other than modifier keys. What's up? I can program profiles with the G13 software. But I don't want that. I want it to act just like a keyboard.

Anyone know of a bolt-on / strap-on collective mod for the TM Warthog? Pictures please...

Fantastic information gentelmen, To further refine my original post let me add a few things: 1.) I am fully aware of the alarms the Ka-50 will sound with max IAS. They are hard to ignore. - thank you for the reminder never-the-less 2.) "Chasing the cyclic" implied that after trimming I had to very quickly move the cyclic to the neutral position after trimming or additional input would be registered. 3.) Usually after trimming with "central pos" I kick the anti-torque pedals to gain control over cyclic inputs (since the are frozen) I find the risk is less than slapping around the cyclic and then suddenly having tremendous inputs being made. I will certainly have to look more into the auto pilot and decent modes etc. Incidentally I had not due to the fact that I am currently a student helicopter pilot and the Robinson R22 I fly does not have ANYTHING remotely close. (sigh). So I was attempting to remain a purist so to speak to not "taint" my training in real life. Cheers.

*Please forgive if this has been posted* I have suffered countless rotor strikes with the various trim options. 1.) Chase the cyclic 'without' central position trim... (resultant instability + high IAS + over control = rotor strike) 2.) Cyclic does not always respond after trimming with central position option... (trying to gain control + high IAS + sudden regain of control = rotor strike) If I had to choose it would be the central trim method. I know there must be something I am missing from it's functionality. Tell me what I am doing wrong to loose cyclic and anti torque control... It can really be frustrating to fly for 30+ minutes and have the rotors mesh from this trim issue... :joystick: