Jump to content

Raven (Elysian Angel)

Members
  • Posts

    3662
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Raven (Elysian Angel)

  1. Oh yes: they both have that “feck around and find out” attitude!
  2. May this put a smile on your face then:
  3. Other than myself I have met 2 that I have been in squadrons with, but that's a very small sample size. I know of a RL F-16 pilot who used to be very active here, but I haven't seen her post anything recently. ED probably has more accurate numbers.
  4. It seems all major manufacturers are planning to jump on board the FFB train now that the patent headaches are gone. It will likely take a few more years at least to get manufacturing going and getting the software just right. Eventually, competition should pull the prices down. The Rhino is extremely impressive, and well worth the investment for anyone serious about flight-simming.
  5. This is my current bike: a 2021 R1250GSA
  6. The USB 2 hub is connected directly to a PCI-E slot on my motherboard, and the USB C hub is connected to a USB C slot on the back of my motherboard. You mentioned 100% spring force is excessive, though it is the default setting. Any recommendations?
  7. You're correct: it didn't. No idea why it worked just fine yesterday though. This test today was after a fresh boot and the F-4 being the only aircraft I flew in that session. Oddly enough I had to rebind my buttons just now. Yes I read that earlier, but I wanted to try 100/100 first, and I also gave 150/150 a try. Reply to all of the above: I disconnected the Rhino from the USB slot (a USB 2 hub) - which worked fine yesterday I might add - and connected it to my usual USB-C hub (all of my other Virpil controls are also in there). It is fixed for now, but I find it quite odd that I only had that problem in the F-4, while the other aircraft worked just fine... I'll keep following it up. Thanks for the replies!
  8. I hope someone can help me out here: My Rhino arrived yesterday and after faffing around a bit in the software I settled on pretty much the default settings. The exception being compensation that's needed for my particular setup: the Rhino pivot point is too far forward so I added a Virpil Z-extension (which is remarkably heavy - far heavier than the CM2 grip). This way the position of my grip is pretty much perfect for me. The F-14, Mirage F1 and F-15E all work beautifully but the F-4 is next to uncontrollable: I crashed several times trying to keep it under control even doing a simply take-off instant action mission. What seems to happen is that there is a massive delay (a full second at least) between my physical inputs and the in-game stick movement, and therefore control surface movement. I obviously have FFB enabled in the DCS misc. settings, stick limiter and blending disabled in the F-4 special options, and FFB forces at the default 100%/100%. I'm not using TelemFFB, and these are my VPForce configurator settings: nullnull Can anyone point me towards a solution? Much obliged!
  9. Look at the screenshot.
  10. I did not, in fact. I tried a few other aircraft as well but the FFB effects seem to bug out if you swap from one aircraft to the next within the same DCS session. Tomorrow I’ll see if turning off the unit and then back on perhaps helps (if you have any practical tips and hints feel fee to send me a pm, so we don’t derail this thread). I faffed around a bit with the software today but then I reverted to the default settings so I can get used to that first…
  11. The black TCS is because of a bug introduced in April last year (when MT launched).
  12. Few things beat the feeling of lining up behind a carrier for the first time in ages in an F-14, with a brand new and improved setup and finishing with an (OK)_SLOX_3 (silly LSO)
  13. My Rhino arrived earlier today, and I have been playing around with it all afternoon. O H M Y W O R D !!!! I'm in love!
  14. Yes the base already has a “built-in” extension, and combined with say a CM2 grip it may not be needed. I ordered a 11 degree throw limiter nonetheless so I can test including my extension and see what works best.
  15. TAA has been there for as long as DLAA/DLSS/FSR have been.
  16. Are you using an extension?
  17. Yes: 8GB RAM is far below the recommended specifications for DCS.
  18. Great to hear! Mine just shipped, and I can't wait to install it into my pit!
  19. We will likely all have different techniques for refuelling, but I find Jester to be a huge help and I also do use the PDL lights. As always though, the key is being smooth, making small/tiny corrections and above all - patience. Just yesterday I made a mess of a dogfight with a MiG-21 so it took me ages to finally kill him, and almost all of my fuel. By the time I reached the tanker and hooked up I had less than 300 lbs of fuel remaining (yes that's not a typo). I connected and stayed connected until I had full fuel (12.000 lbs or whatever it is - I forgot the exact number), even through turns. I also noticed the change in engine spool times but I found them having no effects at all in how I do my aerial refuelling. The Phantom still is - I find - the easiest aircraft to refuel in DCS, with the F-14 as close second.
  20. Are you using a headset for cockpit sounds? I’m using speakers for aircraft sound and the small headset speakers of my G2 for communication and cockpit warnings etc, such as RWR sounds. It works very well and I have zero problems understanding Jester - if anything, I find him a bit too loud compared to the other cockpit sounds
  21. That’s why settings such as “loud afterburner” are available
  22. I know perfectly well when my throttle is moved past its physical detent: no need for audible reheat in the cockpit I have asked myself earlier for the audio to be linked to the DCS sliders, so people who do want those sounds can have them. Everybody wins!
  23. This update completely transforms the map: it is a massive improvement. Thank you!
×
×
  • Create New...