Jump to content

Recommended Posts

Posted

Guys,

 

Sorry I have to ask, I have read every line about trimming but now I am stucked :helpsmilie:

 

As a n00b I start with the mission "shooting range". I do the start up according to DaWu´s Startup procedures v.1.1 and get everything running.

Then I try to do a vertical take-off and raise the collective. After a couple of meters from the ground I press the trim button and push the msffb2 stick forward and release the trimbutton (button 3 on the stick)

Here it is going wrong :joystick: The shark isn´t stable and I can´t get it stable whatever I do with the trimbutton. The pitch of the shark is rapidly going up and down and it is impossible to fly a decent course.

 

I tried several autopilot modes without any success :huh:

 

What am I doing wrong?

 

My specs:

Windows 7 64 bit

Black Shark version 1.0.1.c

MSFFB2 (I tried both of my MSFFB2, I have two of them (silver and red)

 

According to several posts on this forum I did the swap axis thing.

I checked the producer.cfg and forcefeedback is "true"

I checked the stick itself in windows 7 but there are no issue´s. The stick is just working fine there.

 

The strange thing is that the stick in the chopper itself is very nervous/jumpy.

 

Thanks for any help:worthy:

Posted (edited)

A track file posted can save everyone tens of text lines. But before you record a track check your Options - Controls - Axis tune for suspected axis and check if it doesn't go haywire. Do so for every suspected axis.

 

Then record a track with controls indicator turned on [RCtrl+ENTER]

 

By using an outdated version (1.0.1) you'll be facing a shortage of people that will be able to help you due to 1.0.2 tack files incompatibility. Recording a track as short as possible may decrease the risk of incompatibility, I think.

 

Without anyone's help you can do your startup using the cheat key command to eliminate the possibility that you do the startup wrong.

Edited by Bucic
Posted

Recalibrate the stick might help, the FFB will not hold correctly if the stick is not calibrated to the full range of motion.

 

Also, hold the trim button when manuvering, this will desactivate the AP hold but not the dampening AP. When the button is released, the stick should stay still and the helicopter AP will hold the trajectory even with slight wind.

Posted
Recalibrate the stick might help, the FFB will not hold correctly if the stick is not calibrated to the full range of motion.

 

I did. Thanks anyway.

 

I did both trimming techniques. :book:

Posted

you mean after the bird is in flight that is when you trim. it should start from the moment you r hands hit the stick, or hell maybe I am doing something wrong,lol

 

 

Bullet

I7 4790K running at 4390 with a gigabyte board with 16 gigs of ram with an Asus gtx 660-ti and 2 tb of hard drive space on 2 wd hard drives. A X-65F Hotas with trackir4 and pro combat peddles. A kick butt home built machine unfortunately running a windows 7 OS.

Posted

Maybe pilot induced oscilations? When I get my msffb2 I found it extremely sensible. Due to the lack of null zone the slightless pressure on the stick translates into control input.

Be sure you dont have any curve in those axis neither any null zone. That creates a mismatch between the "in-game joystick" position and the trimmed position.

Have you tried with FD on to see if there is any difference? Does it happen at any speed?

Posted
Maybe pilot induced oscilations? When I get my msffb2 I found it extremely sensible. Due to the lack of null zone the slightless pressure on the stick translates into control input.

Be sure you dont have any curve in those axis neither any null zone. That creates a mismatch between the "in-game joystick" position and the trimmed position.

Have you tried with FD on to see if there is any difference? Does it happen at any speed?

 

Put in a dead zone in the axis tune.

 

 

 

OP, You are waiting for the ship to stabilize before you release the trim, right?

[sIGPIC][/sIGPIC]

Aaron

i7 2600k@4.4ghz, GTX1060-6gb, 16gb DDR3, T16000m, Track IR5

 

BS2-A10C-UH1-FC3-M2000-F18C-A4E-F14B-BF109

Posted

PIO perhaps? If you chafe the shark stick it'll take you down for sure.

Need TRK

[sIGPIC][/sIGPIC]

OS:WIN7 HP X64|MOBO:ASRock Z68|CPU:I52500k@4Ghz|RAM:12Gb 3x4Gb GSkill Ripjaws 9-9-9-24 @1600Mhz|GPU:ASUS GTX580|HDD:2x128Gb Crucial sataIII SSD raid0|PSU:Antek 1000watt|Case:Antek 1200|Peripherals: TMWH|Saitek ProFlight rudder pedals|TrackIr4

Posted

 

Did not mean to imply a huge dead zone. But, if any touch of the joystick causes attitude change, a small dead zone would help. Then I agree, set a curve like you mention.

[sIGPIC][/sIGPIC]

Aaron

i7 2600k@4.4ghz, GTX1060-6gb, 16gb DDR3, T16000m, Track IR5

 

BS2-A10C-UH1-FC3-M2000-F18C-A4E-F14B-BF109

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...