Jump to content

RealDCSpilot

Members
  • Posts

    1364
  • Joined

  • Last visited

Everything posted by RealDCSpilot

  1. Yeah, i really like that i have to think more about tactics, be more creative and strategic as a pilot. Every engagement contains more risk and more reward at the same time. It's definitely more thrilling than attacking from a much more safer distance. I'm absolutely enjoying it since release.
  2. Just for info, DCS uses two different systems for haptics. FFB and telemetry output, independent from each other. FFB is meant for Directinput compatible joysticks, telemetry output is for motion seats, simpits, haptic mats (Jetseat, Buttkickers etc. via Simshaker for Aviators) - in general everything that is able to process that data. As far as i know, CLS2Sim only uses telemetry output. Telemetry output needs to be defined with via Export.lua in your Savegame/Scripts folder.
  3. Have you guys set curves on X and Y axis? Try again with linear setting and report back.
  4. @Dunravin Yep, "Default" is for FFB on all ED helicopter modules. Only the Hind seems to need the inverse setting for FF tune on X and Y axis.
  5. Atm, their products are not targeted for the consumer market anyway. Custom built simulators, for the military or aviation industry are their market, where the Brunner I/O gets deeply integrated. In Germany you'll find them in Eurofighter training simulators for instance.
  6. I would also call it Hover Assist instead of Auto Hover. Route mode did work on my end, just dial in a heading during a trimmed forward flight, engage route mode and it turns itself in the right direction.
  7. Thanks for the new SSA beta 2.2.3, i hope the 30mm gun problem will be solved later.
  8. If Brunner would step up and make it a native FFB stick for Directinput i would buy it right away, it's hardware part is surely worth the price. But as long as the software part lacks certain functionality for DCS i'm happy with the modding route i chose for my G940.
  9. There is nothing wrong with FFB in DCS, it's the problem with no native support for Directinput from Brunner like i already told you in the other thread. It's really sad that Brunner doesn't implement it, people are asking them for years. Your only solution will be the Arduino "FFB translator". The overcorrecting issue may come from using curves, if stick input isn't linear - FFB comes out of sync. Always use linear input settings without curves and with default saturation.
  10. @Cthulhus Try to get rid of everything WMR related (drivers and WMR for SteamVR) on your system and retest the other two HMDs.
  11. Oh yes, it's so ready! Perfect match with the FFB stick.
  12. @zerO_crash The Arduino mod gives full control for DCS over the stick. All you get with Brunner's solution is only stuff from DCS's telemetry output ("just" effects) and Brunners trimming solution is only glued on top of it. With true Directinput FFB, DCS can also control the stick position and move it around. Which is one of the best features i see in FFB in DCS.
  13. Look at his sig... It's VR performance not pancake 2D.
  14. I see a performance hit in frametimes, ~40% more than in other modules.
  15. Yeah, it doesn't have ground stabilisation. Those gyros are already working as much as they can. The rest is pilot's and operator's work for precision ATGM strikes.
  16. @DmitriKozlowskyDeactivate Control Helper in special options to fully control it on your own.
  17. It's a fast double tap, like a double klick.
  18. Okay, maybe this feature is real for the Mi-24? Normally, trimmer reset is a DCS function for the other helicopter modules to clean up an occasional trimming mess. IRL it doesn't exist, but maybe for the Mi-24...(???) Control helper activated? It makes an AI assisting you, based on your inputs. If not, than it's strange...
  19. @SparxOne preparation: forget about how you operate a plane, this is something different. Imagine being a race driver, who constantly has to play with pedals, shifter and steering wheel to run the race car in optimal conditions for maximum speed. 1. Check if you need to inverse the FFB axis options for X and Y. 2. Never use axis input saturation curves or dead zones for helicopter cyclic or the FFB will get out of sync with your input. Always use default linear input. 3. Never just tap the trimmer button, always push and hold it while moving the cyclic. 4. I recommend disabling the rudder trimmer option, because it get's confusing very quickly (since we don't have FFB trimmable rudder pedals). Just hold the rudder pedals where they need to be. 5. Think of it this way, every change of attitude needs readjusting of cyclic, trimmer, collective and pedals. During combat maneuvering, starting and landing - you are playing with inputs constantly.
  20. Not here with "default" option and FFB stick. All works as usual, like with the other ED helicopters.
  21. @Viking 1-1 Avoid long hover-like slow descending approaches. This beast isn't designed to stay at a fixed point in air for long. Try to loose speed with long flat nose-up approaches or fly curves (slight down spiral) around the landing zone to get safely near the ground. Also be aware of your weight, always start with as much fuel as is truly needed.
  22. @Picure Just to make sure, which trimming mode did you set? If you have a normal spring centering joystick and "default" trimming option set, it would be logical because you send the trim command on a centered stick. But "default" is for FFB sticks, usually you have to go for the 2nd option "spring centered joystick" and use the appropriate method.
  23. @Doc3908 Keep your nose down (under the horizon) in these situations and the tail rotor will have enough power to counter.
  24. @Fri13 Isn't it available for two weeks via the new free-to-play system? How about letting me buy it as a gift for you? Just PM me.
  25. The good thing with the new free-to-play system, it'll prevent buyers remorse. We can test Polychop releases before buying, what a relief.
×
×
  • Create New...