Quirkitized Posted August 15, 2009 Posted August 15, 2009 (edited) EDIT: There is a fix for this now, it worked for me and others, credit goes to wombat One thing you guys might try is editing Config\Producer.cfg and changing ForceFeedbackEnabled to false. For some reason on my system BS thinks I have a force feedback stick even though I don't, and the trimmer would not work properly until I disabled force feedback in Producer.cfg. Just an idea. Hi guys, prepatch I never had a problem with trim. I could pitch down my helo lets say 10 degrees, hit my trim, keep my stick there (ingame)...could go afk flying for 3min while grabbin a drink for example. Now, since patch I cant see to even keep my helo stable, regardles if I use new trim or have it unchecked. How can I go about setting it up for prepatch trim? I have tried to hit my trim, release button, center stick. I've also tried hitting trim, center stick, release button, and others.....but nothing working atm. Biggest problem is my helo will continue to pitch upwards extremely fast, and I can no longer do a controlled hover aswell. I am not quite sure what happened, but before the patch I could fly this thing with my eyes closed, I could do the loops, cruise around 5m above ground, land on buildings....and now i cant even keep it level.... Is there anybody with a track or FRAPS of the new trim system and how to fully utilize it, because apparently I am failing at it. I just dont get it, I went from flying it without fighting it, and now since patch I am fighting the helo the entire time, instead of flying and doing a mission. I would greatly appreciate anyhelp. I've searched, but cant find an answer specifically. Edited August 17, 2009 by Quirkitized
Distiler Posted August 15, 2009 Posted August 15, 2009 Post a track. AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2
Quirkitized Posted August 15, 2009 Author Posted August 15, 2009 Here is a track. Hopefully you can see, right on take off I'll fly backwards, not big deal. But then I re-land, and hopefully you can see....when I try to set trim, it will not "set". I try a few times, different ways. I also fly into the air and attempt to hold pitch forward with momentum to continue flying forward, but it wont hold. I can still fly, and corner, and land fine, towards end you can see. But i cannot get my trim to stick and I am fighting my cylic 100% of the time. I must be missing something extremely obvious but i have no idea what, prepatch I could fly blind folded (shrug) This track was with the default new trim on introduced in 1.01trim_not_setting.trk
Panzertard Posted August 15, 2009 Posted August 15, 2009 (edited) Just a heads up before anyone with a modified trimmer watches the track - Remember what said in the readme: IMPORTANT! All of the above values (HelicopterTrimmerZoneNnnnn) are recorded for track playback. Any alterations of these values may result in incorrect track playback. (I have a sneaking suspicion that there are some pilots who will watch that one and find some odd flying) ;) --------------- EDIT: The above statement is no longer true - it was an error in the Readme.txt Edited November 12, 2009 by Panzertard The mind is like a parachute. It only works when it's open | The important thing is not to stop questioning
Quirkitized Posted August 15, 2009 Author Posted August 15, 2009 Yeah, all my settings for the FMOptionst file are at default settings. I just cant seem to get my trim to stick, and im pretty sure its a really simple mistake im doing, but cant pinpoint it.
hreich Posted August 15, 2009 Posted August 15, 2009 Ok- here is link to video of my flight - as you can see I also have problems flying after new patch. [sIGPIC][/sIGPIC] Pilot from Croatia
Quirkitized Posted August 15, 2009 Author Posted August 15, 2009 If it matters, I am using a Saitek X52. A fresh clean reinstall of BS then patch 1.01. Same system, video card drivers, hotas drivers, etc pre-patch.
spike2450 Posted August 15, 2009 Posted August 15, 2009 Hi I also have an X52 and i'm having the exact same problems, after a few trim adjustments i am also running out of any trim adjustment at all, i'm constantly having to trim reset to be able to fly her. Never had a problem until now, is it possible in the options to have the pre patch trim settings which worked really well, "if it aint broke"
spike2450 Posted August 15, 2009 Posted August 15, 2009 Hi all Can someone give me the basics of the new trim system? or point me to any instructions. Many thanks.
Kurtz Posted August 15, 2009 Posted August 15, 2009 I considered myself quite competant with the old trim system, im having a pretty wild ride now. The new trim system is turned off. Ive noticed that the trim click sound does not respond to input at times. I dont think the old trim system is still current. Perhaps theres some cpu lag or something? ps- X52pro user as well.
spike2450 Posted August 15, 2009 Posted August 15, 2009 Hi Is there an issue with the X52 pro and the new trim system, is there any other controllers with the same problem? Got sort it out before i can fly again. :helpsmilie:
Panzertard Posted August 15, 2009 Posted August 15, 2009 No, I'm using x52 pro (+ pedals) and haven't noticed any issues, however I do not use any Saitek profiler software. Instead I use the "other trick" keeping my Control Panel+GameDevices+Properties open while I fly. I must admit I reverted to the "old" trimming method though - I'm too old to learn a new method ;) The mind is like a parachute. It only works when it's open | The important thing is not to stop questioning
FOXFIRE TWOONE Posted August 16, 2009 Posted August 16, 2009 For those that are having a problem, did you reset all your AXIS in options, axis command after patching. :music_whistling: Intel core I9 10900K 3.7 ghz Asrock Z490 Extreme4 G-SKill Ripjaws V 32GB Cooler Master 120m GTX 980 Superclocked Corsair AX850w psu Samsung 1 T M.2 2 X 850 ssd's Sony 48 in HD TV Trackir 5 Hotas Warthog F/A-18C Hornet Grip Logitech Pro Peddles Windows 10 64
Martillo1 Posted August 16, 2009 Posted August 16, 2009 For those that are having a problem, did you reset all your AXIS in options, axis command after patching. :music_whistling: Is there any difference? I did not do it and I have no problems so far. Vista, Suerte y al Toro! [sIGPIC][/sIGPIC]
methods Posted August 16, 2009 Posted August 16, 2009 (edited) Hey, I have an identical problem. But what I have noticed about this... I use Lwin Home to start the chopper, and I do wait for all systems to be fully functional, I even tried walking away for a few minutes afterwards... And when I initially take off, and move around... Trim will not function, nor will autohover. After a couple minutes, it begins to work on its own. Im not sure if its because Ive moved away from the airfield, or the helo has 'warmed up' once in the air or if it is a bug. I also use the X52 joystick. Edited August 16, 2009 by methods
FOXFIRE TWOONE Posted August 16, 2009 Posted August 16, 2009 Is there any difference? I did not do it and I have no problems so far. For me there was after total reinstall. Some axis were set back to default from my assignments which was in conflict with my X52 profile. Intel core I9 10900K 3.7 ghz Asrock Z490 Extreme4 G-SKill Ripjaws V 32GB Cooler Master 120m GTX 980 Superclocked Corsair AX850w psu Samsung 1 T M.2 2 X 850 ssd's Sony 48 in HD TV Trackir 5 Hotas Warthog F/A-18C Hornet Grip Logitech Pro Peddles Windows 10 64
Guest Posted August 16, 2009 Posted August 16, 2009 One thing you guys might try is editing Config\Producer.cfg and changing ForceFeedbackEnabled to false. For some reason on my system BS thinks I have a force feedback stick even though I don't, and the trimmer would not work properly until I disabled force feedback in Producer.cfg. Just an idea.
methods Posted August 16, 2009 Posted August 16, 2009 (edited) One thing you guys might try is editing Config\Producer.cfg and changing ForceFeedbackEnabled to false. For some reason on my system BS thinks I have a force feedback stick even though I don't, and the trimmer would not work properly until I disabled force feedback in Producer.cfg. Just an idea. Already done, problem still replicates. When I turn on autohover, the hud cues come up, but the chopper still floats around as though there is no stabilisation, while trim still does not function regardless. It does trim a new position into the autohover(small square cue) but it doesn't stabilise. Seems like it is more of an autopilot problem than anything, the light cues are on for AP, but they do not actually stabilise. Im going to test it out right now, and figure out exactly when trim and autohover become functional. Edit: I tested it, and when pressing trim, it does trim the controller(verified on ctrl+enter), but there is no stabilisation. I turn on auto hover, still no stabilision. Once AP settings get overridden from me floating about like a retard with auto hover on, I can re-enable AP settings and trim and AH work fine. Not sure what to make of it. Edited August 16, 2009 by methods
methods Posted August 16, 2009 Posted August 16, 2009 I had a thought, could it be a problem with the autostart sequence? While the AP control buttons are lit, they are not actually active in function, there by leaving you with no stabilisation untill they are reset.
Boulund Posted August 16, 2009 Posted August 16, 2009 I've got a X52 Pro and it works very well with the new trim system for me so I guess it's not that. Core i5-760 @ 3.6Ghz, 4GB DDR3, Geforce GTX470, Samsung SATA HDD, Dell UH2311H 1920x1080, Saitek X52 Pro., FreeTrack homemade cap w/ LifeCam VX-1000, Windows 7 Professional x64 SP1. FreeTrack in DCS A10C (64bit): samttheeagle's headtracker.dll
bengo Posted August 16, 2009 Posted August 16, 2009 You guys do recenter your stick after releasing the trim-button, right. Controls are frozen in the new way of trimming until your joystick has been centered. Anyway, says so in the readme, and was the source of my problems. No other problems whatsoever. i7 6700k/GTX1070-8G/MSI-Z170A Gaming Pro Carbon/32GB DDR4 Kingston HyperX PREDATOR DDR4 3000MHZ Vengeance 1600/TM Warthog #6106/Samsung SB350_S27B350H/OCZ Agility3 SSD 128GB / Win10-64/TIR5
nemises Posted August 16, 2009 Posted August 16, 2009 Hi all Can someone give me the basics of the new trim system? or point me to any instructions. Many thanks. In essense, when you release the trim button, all control inputs (from cyclic and rudder) are disabled untill you return them to the nuetral posistion, and then they become active again. To use it is the same as in pre-patch, only now you no longer get that moment of double transformation that you used too. I'm using an X52 and have had no problems so far with new trimming method, though TBH, I never really had any issues with the old trimming method either....I have had a couple of instances when manually hovering or approaching a landing where I would normally constantly set trim without returning the controls to center which , of course, now means I get no control till I do return them to center, but otherwise, it's a very interesting solution to the problem of non FFB + centering force joysticks.
Quirkitized Posted August 16, 2009 Author Posted August 16, 2009 One thing you guys might try is editing Config\Producer.cfg and changing ForceFeedbackEnabled to false. For some reason on my system BS thinks I have a force feedback stick even though I don't, and the trimmer would not work properly until I disabled force feedback in Producer.cfg. Just an idea. THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! This fixed my problem 100% I can actually fly without fightning my stick 110% of the time! Woooo :) Here is a track with it working with FFdisabled in producer.cfg. Just to give you a comparsion, you can view track in first post of it not working. You can clearly see in old track Trim would not "Stick/set". With FFdisabled, it works perfectly, as it should. I knew it was something so small I overlooked.trimworking_ffdisabled.trk
Triangle99 Posted August 16, 2009 Posted August 16, 2009 One thing you guys might try is editing Config\Producer.cfg and changing ForceFeedbackEnabled to false. For some reason on my system BS thinks I have a force feedback stick even though I don't, and the trimmer would not work properly until I disabled force feedback in Producer.cfg. Just an idea. I should add my thanks, too - no working trim or auto hover until I tried this :) Cheers P45 Platinum, Q9550 @ 3.33Ghz, HD6970 w/2gb, X-Fi Titanium PCIE, 4gb RAM, ANTEC 1000watt PSU, Lian Li PC-A71 case, Win7 64bit, CH Throttle and Fighterstick, Saitek Pro Pedals, TrackIR 5 + TrackClip Pro, 3 x Samsung SyncMaster 2443
Snacko Posted August 16, 2009 Posted August 16, 2009 I was having problems of my stick and rudder becoming totally unresponsive using the new trim system after a while. I had that Ctrl-Enter thingy up and would move both all around but it showed no response. I was guessing that they were disabled until I recentered them, but for some reason they would just start working again after about 45 secs to 1 min. It may have just been me not centering them when I was out of control, fighting for flight before I crashed. It's hard to let go then. Also, I was not used to recentering my rudder. I assume I also have to recenter that? Anyhow, I just turned that ForceFeedbackEnabled to false also. I have an X52pro. It seems to have helped a lot. Time will tell.. Is there anyway to tell where your rudder is trimmed in the cockpit? Do I just have to look down at the floor pedals? Of is there some other gauge? Snack Snack Officer Intel I9-10850K (OC @ 5.0ghz) │ 64GB (4x16GB) DDR4 3200 │Gigabyte RTX 4090 Gaming OC 24gb - ҉ - Blackshark Cockpit Trainer - ҉ - ♣ Thread | ♥ Download
Recommended Posts