Jump to content

PawlaczGMD

Members
  • Posts

    808
  • Joined

  • Last visited

Everything posted by PawlaczGMD

  1. So you bind both left and right throttle over gate to the same command "Throttle - Start Engine" ? I was not aware this would work, I thought the second detent is activated with "Throttle Up", which the game won't let me bind to HOTAS.
  2. I am using a HOTAS mini joystick and some buttons to implement the mouse cursor, as I don't want to switch to it in VR. Currently, I think you need Joystick gremlin or similar software to do this. It would be nice to have in DCS, so that I don't have to run and activate other software each time I play. Add bindings for mouse slew and buttons in controls.
  3. I've assigned the TDC slew to a mini joystick on my HOTAS. This bugs the target designator: diagonal inputs with one component too strong will not move the TDC, it just locks up. To reproduce: In A2G mode, move the mini joystick in full circles, the TDC will behave erratically. This is in Su-25 T only : in Ka-50, which also has the Shkval, this works perfectly fine.
  4. I've managed to create a situation that bugs out the whole comms system. When initially communicating with Ground and ATC to get power, startup clearance, etc, anything from the comms menu just stopped responding. This seems to be a different bug from what you've mentioned. Here's a short track. I observe this sometimes, it might be an unfortunate input sequence and timing. radio.trk
  5. I've tested more, and it seems to be a bug. This happens even without saturation, and only for the Su-25 T. Ka-50 target works just fine! Both in the sense that it's not bugged, and it's nicer to use.
  6. I will play around with it today too. In the Shark, I don't need to saturate the axes, as the cursor seems to move slower. So I don't think they share the exact same code.
  7. To be clear, I'm fine with the tuning I've found, but the game (or my HOTAS hardware?) ignores diagonal inputs when one axis is saturated. So is this a bug? It looks to be on DCS side, as the HOTAS control works perfectly fine.
  8. Manual bombing is very hard. Yes, you need to follow a profile almost perfectly, and have the intuition on how to correct mistakes. Try doing it in an F-5 with just manual sight depression. The F-86 is easy in comparison.
  9. The F-86 seems to have a weird/artificial engine startup procedure. My throttle has buttons for cutoff<=>idle. I would want to start the engine using this function. So this works for moving the throttle to the first position up, but then to fully start the engine, you need to additionally move the throttle into a second position using the "throttle up" command. This cannot be bound to my HOTAS, as the menu won't let me, only to the keyboard. So I have to awkwardly reach for the keyboard to press this button... Also, it seems like this command just corresponds to moving the throttle up as normal in flight, so it seems artificial to only be able to do it with the button bind. Is there a better way to do it? Why won't the game let me bind HOTAS buttons to this command? Is this some special second idle detent in the real aircraft?
  10. It's fair that FC3 does not have the full fidelity functionality, but it also seems like all it would take is to copy the JTAC code that already exists. The functionality is already developed, it just needs to be inserted into FC3.
  11. I've tried playing with the deadzone, but I'm not sure I understand. Because the full cursor speed is too fast, I need a very small deadzone, so that I can make precise adjustments when fully zoomed in. So I have reduced the deadzone as much as the hardware allows and doesn't get stuck. This is Winwing Orion 2 throttle ministick. My problem is that the cursor is too fast without saturating the input.
  12. I understand that, but it's a semantic disagreement. The JTAC system is in the game, and they are maintaining and updating all modules. So why not add that bit of JTAC code to FC3 planes as well? Whether you call it a bug or an update, it doesn't makes sense that these specific planes can't talk to JTAC.
  13. Ministick, wrong terminology. It has 2 axes.
  14. Why is it not a bug? Pilots lose the ability to speak to this one guy when they're in an FC3 aircraft?
  15. There's no special tab for it with FC3 either. The price for having R-77 is that you need to fly with the moon runes.
  16. They will need a track file for issues like this.
  17. I want to use a joystick hat on my HOTAS as the target designator in the Su-25 T. The problem is with tuning the axis. Even with large curve, like 40, the designator is very hard to control, as it moves too fast. It works well when I set the saturation to 40-50. However, a new problem appears - when I give a diagonal command that goes into oversaturated region, the target designator doesn't move. So I have to be careful to not saturate the axis if I want to move diagonally. Is this intended behavior? Seems to me like the game should accept the diagonal input, and figure out a way to cap each axis separately... If this is not a bug, does anyone know of a good way to tune the hat for this purpose?
  18. When you select the Vikhrs, the weapon name on the HUD is "1". Watching some older videos, it was "9A4172". This would seem correct... Is this a bug? I suspect so, as "1" is not a useful designation of the selected weapon.
  19. In VR, when peeking over the nose, there is an area, highlighted in red, where textures are missing, and you can see into the nose of the aircraft.
  20. I saw that. My question is, is it in your opinion worth paying $70 to get them if you're probably not going to run a dead stick for helos?
  21. It's probably a preference thing, and maybe I wouldn't actually like having to use lifts to engage AB. But if someone sells such a part for a few bucks, I'd buy it to try out a different feel. I don't have the capability to design or print this myself, and don't know people who do. I really like the STECS detent system from what I've seen, although overall I wanted the WW set.
  22. Would you recommend getting the damper kit mostly for jets? Does it improve the feel of the stick? I also fly helos, but I'm not sure I can be bothered to disassemble the cams every time, and I don't want to buy another stick just for that.
  23. I'm looking for options to modify the physical AB detent on the throttle, as I don't really like the stock feel. It's too easy to push through, and doesn't even need the finger lifts. Unless I'm careful, it's easy to push a bit into the AB range. I'd like it to work more similar to the idle cutoff detent, or at least something in between. The 3rd optional detent that comes with the throttle looks better, as it has a groove that would hold the throttle just before AB. However, it doesn't fit in the AB slot, as it has a special shape. Did anyone try to modify or 3d print alternative AB detents? I also thought about filing down the extra detent to somehow fit in that slot, but don't want to destroy it just yet. Otherwise, what are your thought on the stock AB detent feel? Maybe I'm just too fussy about it.
  24. I don't own the mirage, but you could use the in-game axis tune to set saturation to cut out the part where it shuts off your engine. PS the game only has symmetric saturation, so actually use Joystick Gremlin to implement the response curve that you need. Physically, I think you can move the cutoff detent up a bit as well.
  25. Doing the Su-25 T Mercury pod training mission, the screen looks bugged after turning the pod on. Screenshots of the view with just the Shkval, and with Mercury on. The Mercury has the top right flooded with something very bright, while the rest is dark. This stays constant as you maneuver the aircraft, or slew the pod. This is both in VR and normal.
×
×
  • Create New...