Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by PiedDroit

  1. I depends on your flying style and how your stick is configured. I modded mine so I get almost no resistance in the center and resistance increase when going outside of the center (for choppers and also to have more natural feeling of controls, I don't want F-16 style stick resistance), so having extra precision in the center is pretty good for me (I'm still testing without the HW deadzone enabled but I didn't have much time to fly recently). If you have the stock joystick, going out of the center area always require some force, so I guess in that cas it's better to have the HW deadzone and use it "F-16 style". So what's works for will probably not work for you :D Hence my very first answer to this thread. P.S.: To keep things flexible, maybe you can have the HW deadzone disabled, then calibrate your stick, and setup a 1% deadzone in DCS depending on the aircraft? I can't help you on TARGET GUI, never used it sorry...
  2. Nice ! I solved the mass balance issue by tilting the base a bit, works for any extension.
  3. One could say it is already there but right now it's not very flexible (see 3-positions and 2-positions abstraction in the M-2000C). Having a "on release" modifier in the controller settings (assign button) would make it universal, without the need for tweaking the control luas :thumbup:
  4. I got one of those, love it :thumbup: The design is really good. I also bought one of the simpler design (i.e. metal tube with thread) from another seller but I ended up keeping the one with the nut as is was much easier to use.
  5. Another problem bites the dust! :thumbup:
  6. Not sure to understand... First, which aircraft are you trying to tune the detent for? Second, what do you mean by: When throttle is idle, you get military power in game? Or vice versa? Do you mean that you move the throttle and in game, nothing happens between idle position to the detent? There is something seriously wrong with your throttle if that's the case :wassat: Normally to adjust the point where the detent is, you only need to set the axis to "slider" mode and adjust the curve. Also when doing the calibration, make sure to go past the the detent to the full range of the throttle. If it's obvious to you, perfect :)
  7. You'll find the setting you like best ;) I never had it disabled before so I disabled it, did the calibration (as without it the stick is a bit off center) and I will test it for a while to see if it makes a difference at all. It seems it is a bit more sensitive in the center.
  8. Yes. I start TARGET script editor, choose my profile, then run, it takes 10 seconds.
  9. Where exactly do you set it? It seems I don't have the control panel installed, the only place I could see this setting is in the TARGET GUI, and it was enabled. Since I never bothered with this setting I can't really tell you about it - ff you really need an answer I'd suggest leaving it enabled ;) P.S.: Maybe you'll fix your centering issue by doing the stick calibration in windows (with hardware deadzone disabled)? I tried a bit this setting a bit since you asked the question, for me it doesn't seem I need to have a profile to be running for the deadzone setting to take effect.
  10. If you're comfortable with contacts then you're golden. There won't be any distortion unlike glasses. Also using contact or glasses is really a personal thing. You may or may not be OK with them - try and see.
  11. Maybe the reason is that the VR lens is not on your eye directly, and not perfectly centered centered. With prescription glasses the lense is cut so it is centered when the glasses are on your nose. Also even with prescription glasses, the vision on the edges will have a bit of distortion, only the center will be in perfect focus, so having the VR lenses a little off center or a little too far from the eye will make this distortion more noticeable.
  12. It's not too long to get into a module like the M-2000C or the Viggen, learning where the switches are is quick, you just need to make sure to write down some the procedures and practice them. This will depend how familiar you are with basics of aircraft handling and systems. Usually I the traning missions one to several times each depending on my succcess, I study the manual and I build practice missions to test certain aspect of the aircraft that are more complicated (for the M-2000C, it was mostily the INS and the use of the radar), then I'm good to go. During that time I also build my controller profile in a incremental way. Since those new aircraft have clickable cockpits, it's usually fast, a couple of axis to tune, HOTAS buttons plus maybe one or two switches hard to reach in the cockpit, and it's done. FC3 aircraft take much longer to configure, controller-wise as they don't have clickable cockpits. In terms of timeframe, this usually takes a week (maybe two if I don't spend much time on it) or even just a week-end if I dedicate my time to it. Of course mastering the aircraft will take longer ;) If you're new to aircraft systems and (radio-)navigation, it might take a while longer for you grasp everything, but learning the basics will be helpful in the long run - in my case this even helped me to land a job . As the recommendation for a strike aircraft, well the Viggen seems the ideal candidate hehe (but beware, no moving map nor fancy avionics). Otherwise the A-10C is slow and cosy (modern avionics, moving map, targetting pod), great for target plinking. M-2000C is not really a strike aircraft, sure it can drop bombs and rockets but if you're planning to use it for this sole purpose it will be frustrating.
  13. I suspected so about the .fcf. I don't have much experience with it as I only made my profiles through the TARGET script editor, so, this is good to know.
  14. The deadzone setting depends on the physical stick and your own feelings, so it will vary greatly. If you like the stick without it, don't add it ;)
  15. Mine are not really fancy, they barely fit in width, they were stuck a bit. The other issue is that I couldn't put the CV1 on while wearing the glasses, I had to fit the glasses inside the rift first, then put CV1+glasses on at the same time. And while wearing everyting, I had very little room to wiggle without having the glasses touching the CV1's lenses. To solve that issue I would need glasses that filt really close the the face (with eyelashes brushing on the lenses haha)...
  16. Well I would need to bring my friend's CV1 to shop to make sure it fits :music_whistling: It's a maybe, for now I'll wait and see :p
  17. This is not the only reason as far as I'm concerned. I wear glasses and using the CV1 was really a pain with them :( I think if the CV1 was comfortable in that regard I might have bought one but to me the discomfort with glasses makes it a no-go. I'm waiting for more adapted designs to hit the market, such as hinge mounted displays, like the Playstation VR for example (or ).
  18. It will probably reset, if you modify your .fcf (I guess), I can't tell you as didn't experiment with .fcf. Just try it ;) For the leds, I told you it was a bit flaky, some users had more chance than others. I'm not using them at all now since for me it was making my profiles unstable (sometime it would stop responding and I need to stop and restart). Also depending on which intensity value it was more or less stable. I don't know the exact reason but some user once hinted it would be power issue, changing it would affect the board's other components. The slider has a little bump in the middle, it's normal. In that middle area values don't update. P.S.: Attention: Important thing with the WH: avoid plugging it into a powered USB hub or on an USB 3.0 port without doing a bit of reading first. Some users had bricked throttles (read: dead board) because of that kind of thing. I also had this kind of issues too with USB 3.0 ports, I didn't brick it but the throttle would stop working from time to time and I needed to unplug/replug (even with the port set to not go to sleep mode in windows). It only got well as soon as I used the PC USB 2.0 ports or an unpowered USB 2.0 HUB with buttons to switch off the ports. I also make sure not to boot the PC with the ports connected, just in case. If you take care of this you shouldn't have any nasty issue. Again, it's variable, some user use it on USB 3.0 without issues, some other not. If you treat it right it will give you long years of service ;)
  19. Glad you like it, especially considering your eyes. Cheers :pilotfly:
  20. Yup, but bear in mind that when doing this your "Thrustmaster Combined" can only generate keyboard key strokes and mouse output, so, no axis (which is the thread's question). I personally use MODE_FILTERED, with this mode you can have all three devices active at the same time (stick, throttle and combined) with all DX outputs and axis available. We can dump all tips we have, it could be useful but it will be soon overwhelming :D. Here's one for free: when assigning a key, you can use DX outputs (ex: DX1) instead of keyboard keys (ex: 'm').
  21. I'm not 100% sure for the color, I need to double check. It should be mentioned in the scripting manual.
  22. Most of the time you'd need to actually program something only for some buttons, so leaving the other buttons as regular stick buttons make thing easier. At the very beginning (with LO/FC2/FC3) I was tinkering a lot and trying to put something on every single button with different states and all, so I had big profiles, but now with clickable cockpits you only need several functions on the stick as the rest is reachable with the mouse, so it's not really necessary. It is very rare now that I rely on programming for some functions, I keep my profile very short and put everything in DCS as normal button presses. I never use shift state, sometimes I use TEMPO or SEQ but it's rare, as I have enough buttons to do everything most of the time.
  23. Lol that really seems creepy when you put it that way :D I also try to refer to the manual except when I'm writing from my phone where every character counts :music_whistling:
  24. Shift state mentioned here will also work for axis (in the axis assign page), the Throttle axis will always be the same, except DCS will use it for different simulator function depending on the state of the shift button. But as I said before, the way you want to use your axis will require your axis to behave differently if in brake mode or zoom mode, somethign DCS can't do, that's why the shift state is not the solution in that particular case (I told you what you want to do calls for headaches :p). Benefit with doing everything in DCS with shift states is that you can use your HOTAS without even firing up TARGET, so, no scripting required. P.S.: Leds can be tuned in brightness. However I would recommend not trying to fiddle with them, even if the scripting manual tells you how to do it. I don't know why it is like this, but playing with the leds (ON/OFF intensity) made the profile unstable for me. Some other users had the issue too, but few of them, so *maybe* it will work for you, but it is a possible cause of instability.
  • Create New...