Jump to content

ampentium2

Members
  • Posts

    21
  • Joined

  • Last visited

About ampentium2

  • Birthday November 29

Personal Information

  • Flight Simulators
    Hornet, FC3
  • Location
    Malaysia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The reason why it doesn't effect Hornet and Viper is simply because the way the input is being translated. In Hornet's FFB, center of actual stick is translated as no input in the virtual aircraft stick (in the indicator; ctrl+enter the diamond is at the cross between the 2 axis). So, it doesn't matter much if your stick is FFB or not. Center means no input. In Hog's FFB (and a few other aircraft that I know like Sukhois) the position of the stick is translated 1:1 (and factored with the curve afterwards) so center of actual stick is translated as center of virtual stick which also means the stick is being pulled back (you can check the indicator it will show you the stick is being pulled) resulting in the aircraft pitched up, since it is quite a substantial pull no amount of trim will level the aircraft back. Learned this the very hard way when I first fly the Hog coming from Hornet with Logitech G940 but flying these aircraft with FFB is a lot of fun.
  2. I do, but budget does not allow at the moment... So, I make do with toggle detent...
  3. That's the funny thing... I've always use the ctrl-enter overlay but I've never noticed it... Though I mostly use it to see if I'm in AB or not, didn't pay much attention to the stick position....
  4. Based on my learning when trying to troubleshoot and setup force feedback settings on different aircraft in DCS I find that each aircraft control input are modeled differently, at least based on few aircraft that I have tested. I think I can try to explain this. With ForceFeedback Eagles and Hornet are modeled with 0 stick input equals to neutral stick, however Flanker-D and A10-C Tank Killer does not, neutral stick position on aircraft is fedback to actual stick position so you have 1:1 stick control with ForceFeedback stick. Any attemp to center the stick (e.g by implementing centering spring) will cause the input translated as stick being pulled. But, without ForceFeedback I can imagine this becomes a small trouble as there's no way you can do 1:1 stick input so it comes down to how each developer modeled their aircraft. Obviously they will have to do 0 input as neutral stick. As forward movement is usually limited on actual aircraft they will have to decide whether to follow 0-100% forward range at the cost of being less responsive or 0-30% forward range and ignore the rest while having more realistic response. And it just so happens ED decides to model the later for the Hornet (having said that, I have never noticed this behavior before; not because it never happened but I have never paid attention to this. I only assumed they do 0-100%). Take it with a grain of salt, the only party who actually knows the actual reason is the developers.
  5. After I test it out a little bit more, I now know why it works with slider and not postive-negative curve. The stick was translated into the game 1-to-1, as in center of the actual stick translated as center of the curve instead of stick neutral. As such, the control in the game is translated as stick being pulled (center of the whole pitch range, stick neutral would be a little bit forward instead of center of range). In positive-negative curve, this center of range will not move and always translated as center of range. When I was playing around, I got the curve set to 15. In slider, this "center of range" is translated to be a little forward and it hits the stick neutral area. I have a feeling this has something to do with the driver and how the input is being translated into the game (center of range = stick neutral for Hornet vs center of range = center of range for Tank Killer). I don't know who can help me in that regard then... Maybe I should just hold off from purchasing this first... Thanks ED for the free to play sessions... Update: I finally nail it.... The issue was this aircraft comes with FF... That's why the stick position was translated 1:1... I have centering spring enabled in the profiler, causing the stick to be pulled to the center... Once I disable the centering spring option, the stick moved forward to the neutral position and follows what the trimmer does... Hornet doesn't behave this way because there's no FF I think... The Eagle also behaves similar to Hornet because there's no FF... What's left for me is to study the system and get used to the new flying.
  6. what I was saying is that G940 might not be the same as other stick (e.g Warthog, Extreme 3D Pro, Virpils) and depending on how the aircraft is modeled, it could need the change; Tank Killer needs the change, Hornet does not, Eagle does not... I use the same G940 for Hornet, Eagle and Tank Killer.
  7. It Is strange since Hornet doesn't need it to be set as slider... But hey, if it works, it works... It might be per device basis so not all stick behaves similarly... I have a feeling that the reason I can't fly in any Sukhois probably for the same reason...
  8. Apparently my stick pitch input behaves as slider in Tank Killer, the center in the input indicator is actual center... This isn't the case with Hornet... Once I tick the axis as slider, everything works well...
  9. in the screenshot, there's 2 diamond in the input indicator. small diamond and big diamond... per my understanding, small diamond is the indicator of trim. I have already trim nose down left wing heavy. And that's not the problem. I have trimmed nose down to the max, it still behave the same. The problem is the big diamond is not at the center of the cross even if I'm not giving any pull up input. Because of that, I won't be able to set auto pilot because stick is not neutral. Unless my understanding on the input indicator is wrong, I don't think trim is my problem.
  10. As shown in screenshot, with zero input from my actual stick the game says that I'm inputting a pull back. Why is that? Is it intended? I have a feeling it is not intended to work that way since the autopilot got cancelled. I'm using Logitech G940 (with FF) if that matters... Another note, I've double checked and remove all bindings to pitch and roll control from any devices... Also, this doesn't happen when I fly my Hornet...
  11. Try to use the mission that came with the module to familiarize yourself with the radar. Prisoner of Caucasus is so heavy with triggers that if you don't fly by the set course the mission will definitely not be able to complete itself. The way the mission is setup:- 1. Fly to WPT3, enemy spawn 2. You're asked to turn to intercept with ROE weapon hold 3. The enemy release a missile, you're told to engage (this trigger somehow I never got to trigger, thus mission never got to progress) 4. After the 2 tango splashed, another group spawn engaging you. 5. You're told to retreat and RTB. Sent from my SM-G950F using Tapatalk
  12. Try to turn your wheel (rudder) first before apply throttle. If you let it move and apply full rudder with HI the front wheel will slip and you will not turn. Sent from my SM-G950F using Tapatalk
  13. Attached is the track file. Every time I extend the probe a flickering light source appear from behind, not sure from where. This cause serious discomfort. Looks like AAR is off of my menu. flickr.trk
  14. [ALREADY REPORTED] Refuel probe cause some flickering light source appear Attached is the track file. Every time I extend the probe a flickering light source appear from behind, not sure from where. This cause serious discomfort. Looks like AAR is off of my menu. flickr.trk
  15. Just tested, the keybind that I use (LAlt + LShift + LCtrl + S) seems to be conflicting with something else. Is it some special key in DCS or Windows? At control settings it reacts just fine, just not in the cockpit. Changed the keybind to something else and everything works fine. Sent from my SM-G950F using Tapatalk
×
×
  • Create New...