Jump to content

Windsortheater

Members
  • Content Count

    217
  • Joined

  • Last visited

About Windsortheater

  • Rank
    Member

Recent Profile Visitors

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

  1. YES PLEASE! These FC3 aircraft are light on systems, but are perfect for teaching fundamentals. This would be perfect training for anyone new getting to DCS - the F15 for basic A-A, and the A10a for basic A-G. Nice job!
  2. What about with FC3 aircraft that don't have tunable radios? Maybe no way to select specific airfields with these aircraft without using F menus? Sent from my SM-T387W using Tapatalk
  3. I do this precisely (native 4K 3840x2160).... and was the primary reason to go to 2070super from 1070. From what I recall, a 1070 -> 2070super is like going from a 1070 to a 1080ti, or a 1070 to a 2080 (non super). I think on paper it was like a 30% jump (if that means anything to you). In game is most important to me.. I use a 40" 4K TV about 18 inches from my nose and a track IR so I wanted smooth >50FPS, ideally 60FPS. Less than 50FPS for me gives me a headache with TrackIR. I also wanted, ideally, to turn on MSAA 2x and run High view distance. The flickering in DCS of te
  4. To each his own, like you suggest I like to try things then decide. I really like using a common input to control things across planes.... with the top rotary on the X55 throttle using axis tuning I can use the same input on F15, F16, F18.... so far that's all I have tried... but it seems to work well. The only trade-off so far is F18 TGP interaction.. which I consider very minor.
  5. Here's what I do for the F18: X55 throttle with Joy_Z (top rotary) assigned to RADAR ELEVATION CONTROL (note - this also controls TGP Zoom!) Deadzone: 2 (my rotary has noise around its center detent so I needed a deadzone, your hardware may not. Note - set deadzone as small as possible - too high of a deadzone means that the initial input to the game will be high...OK for Radar slewing since it has very low sensitivity to axis inputs, bad for TGP zoom control since it is very sensitive to axis inputs) Saturation X: 100 Saturation Y: 50 Curvature: 40 Invert: checked For m
  6. Rolling back drivers fixed for me as well. I was losing 20 to 40 fps with SA + Dispenser switch on. Must be something to do with how the dispenser info is merged into the SA display maybe? I posted issue in NVIDIA forums in case they can address in next update.
  7. Thanks. Has worked perfectly on stable.
  8. Sure.. just offering a suggestion.... I tweak what I need to in order to be able to play. to each his own! Note - from what you are describing.. the HUD is responding with a higher sensitivity than the radar to the same analog input... with the method I describe you could tune so they are both responding (horizontal and vertical speed) essentially the same... just that they won't be "variable"...and one rate will be with partial input, and the other with full. not ideal.. but may work while they decide to fix or not.
  9. desaturate the axis so it clips the output and then smooth it..... or.... set a user curve so the initial rotary input has VERY low output. Play with the axis tuning settings (start with desaturation, then move to user curves) - they are really powerful. Note - the added complexity with tuning for the F18 is that the radar elevation also controls TGP zoom steps.... so don't forget to check your tuning using both!
  10. I haven't tried auto bombing...will check that out for slew rates. Note - what about setting x/y axis into two zones. full pressure goes to high speed (tuned to work on the radar), anything lighter than that is tuned to work on the HUD. Basically turn the axis into two different rates instead of continuous. I don't have a warthog but I do this for my ministick on the X55 for the F15 radar slew - which is SUPER sensitive... basically I have 90% of the axis desaturated and flatlined to a very low output, then at the very end of travel I ramp up to 50% of saturation to get a faster sl
  11. I use an axis (rotary)… I use it on F15, F16, F18.... tuning sensitivity is critical for each plane.
  12. My issue was it was too sensitive and it would raise / lower elevation too quickly before i could return to center. I tuned the axis within DCS and reduced sensitivity. Now I can increment the radar angels a very small amount, very slowly if I turn the axis a bit, or more quickly if I am more aggressive with the rotary. Works great now.
  13. THIS!! I hope DCS integrates into F18 and F16 next update (I'm on Stable... maybe already on Beta).
  14. Just found this thread relating the issue to drivers https://forums.eagle.ru/showthread.php?t=267685&highlight=SA+FPS I am having issue with driver 445.87. I will try rolling back. Sorry for duplicate post.
  15. Found the SA FPS fix was implemented on stable branch in December DCS 2.5.5.41371. I am still seeing bug with latest stable release on the below multiplayer mission. Track-file attached is a take-off and simple flying while cycling SA on and off a few times. No other clients on the server at the time, and server was recently restarted. FPS with SA off = 50-60 FPS with SA on = ~30 (or lower) Toggling SA provides immediate impact to FPS. Track file Mission: Through the Inferno Server: PRG Map: Caucasus DCS Branch: Stable DCS Version: 2.5.5.41371.1 Settings: 3840x21
×
×
  • Create New...