Jump to content

Aries144

Members
 View Profile  See their activity

  • Posts

    325

  • Joined

  • Last visited

 Content Type 

Everything posted by Aries144

  1. Aries144
    Thank you for sparing some time for me, I know you must be busy. No I haven't ever removed the 22pin header, yes the adapter is well seated on the 16 pin header.
  2. Aries144
    I'm unable to upload pictures to my picture host for some reason, unfortunately. What is it you need to see?
  3. Aries144
    Underside of the throttle's board or underside of rel4y's board?
  4. Aries144
    Yes. I bought the Cougar throttle used, and also recently bought rel4y's USB board for it. First time install.
  5. Aries144
    I don't know. The throttle was an ebay purchase from a couple of years ago. I don't have a cougar joystick.
  6. Aries144
    rel4y, I'm having an issue with my Cougar Throttle using your USB conversion board. All axis work great, but only button 1 (uncage) and 3 of the 4-way radio switch buttons work (down, left, and right. Up does nothing.) The speedbrake switch, dogfight/mrm mode switch, and the mini joystick press button are completely unresponsive. I've taken a multimeter and checked all legs of all the switches and I have perfect signal from all the switches to the original throttle board. I even had a friend who's a professor of electrical engineering talk me through some tests over discord. We're down to questioning either the diodes or something on your board. I'm stumped. Do you have any suggestions? Is it possible the board could have an issue?
  7. Aries144
    Thanks ED!
  8. Aries144
    Turning hyperthreading back on in BIOS had no effect. Still experienced input lag. Also, no improvement with MSFFB2 plugged into powered USB addon card.
  9. Aries144
    Gyro, Fat, thank you both for giving this some attention. This looks like one of those glitches that's going to be a PITA to pin down. I have a powered USB3 card (that has it's own direct connection to the PC power supply) plugged into my motherboard that I can try. SgtNathan, I also just realized that I'm running an Intel 7700k processor with hyperthreading disabled in the BIOS. You aren't running with hyperthreading disabled as well, by any chance? I'm going to try turning hyperthreading back on in BIOS and see if that changes anything.
  10. Aries144
    I can confirm this removed the input lag! I still need to try and measure differences in FPS/frame time to confirm what you report there. Thank you SgtNathan! I consider this to be an improvement. I wonder what is going on that's giving us these issues, yet Fat Creeson can't duplicate them?
  11. Aries144
    Well, looks like access to these files has been removed. At least, they aren't in the Scripts\Database\Weapons folder anymore.
  12. Aries144
    I am champing at the bit to buy this either premade or even just for access to the plans and code to make it work!
  13. Aries144
    It's annoying since, if you change loadout during a mission, you can't rearm with MK-20s. Even if you select the same preset again.
  14. Aries144
    Does anyone know why it was removed?
  15. Aries144
    I just discovered this issue as well. Any updates on possible solutions? The FFB guy at Heatblur doesn't seem to be able to detect the problem on his system.
  16. Aries144
    I have amended the original post to include pressing the esc key repeatedly in the "How to Reproduce" section. This makes the issue obvious, whereas it might otherwise briefly escape notice. Note that the delay here can be as much as two seconds. I can confirm this does not occur with any other module, including others that make use of FFB, including the F-5E and Spitfire. It can also be reproduced in the Free Flight instant action mission, though it seems to take some maneuvering for it to show up. Again, repeatedly pressing esc key makes this apparent. As soon as lag is seen pressing esc key, it can also be witnessed in the response of the aircraft, firing of the gun, and delayed movement of the virtual joystick in the game relative to the user's real flight controller.
  17. Aries144
    This happens only with the F-14. I have most of the modules and this doesn't happen with anything but the F-14. This is a recent issue for me. New GPU (6900XT), new VR headset (Reverb G2) is all that's changed on my system. Never had this problem before with the F-14 and my force feedback stick. Could someone with a MS Force Feedback 2 joystick run the F-14 Dogfight Instant Action mission briefly and confirm that I'm the only one experiencing this issue? It'll take about 5 minutes.
  18. Aries144
    Updated: It's caused by Force Feedback. Turning off force feedback completely eliminates the issue. Also, if something happens to interrupt force feedback, i.e. the stick stops receiving force data and goes limp, the input lag goes away. This is new, as I've been using force feedback since the F-14 launch and never had this problem. Either this was introduced in one of the recent patches, or it's some weird interaction with the AMD 6900XT.
  19. Aries144
    EDIT: I determined conclusively that this is caused by activating force feedback. Turning off force feedback eliminates the issue completely. It seems likely that this is caused either by something introduced in the last couple of patches or it's related to my new AMD 6900XT. EDIT 2: I have an update that I think completely solves the issue without using the "input = { threaded_ffb = false }" line in the autoexec.cfg file! This new solution is better because it comes without the negative performance aspect of using that autoexec entry. I stumbled onto this by happenstance while researching a completely unrelated problem. All credit goes to user l3VGV from the Russian language IL2 forums. The solution is simply adding the linked dinput8.dll file to the DCS World\bin folder. https://github.com/l3VGV/FixFFBStutterH/releases/tag/v1.02 No lag, no measurable negative impact to performance. Force feedback forces appear to all work correctly. Problem solved. Bug: 0.5 second control input lag when force feedback is on and Microsoft Force Feedback 2 stick is in use. All controls including keyboard affected. Also affects opening menus ex. Esc to open menu. Can I reproduce it 100%: Yes. 100%. Just turn on force feedback and play any mission with the F-14A or B with Microsoft Force Feedback 2 joystick in use. How to reproduce/ description: Turn on Force Feedback in DCS Settings Menu. Easiest way to observe is to launch F-14 Dogfight from Instant Action. Input lag may not be immediately noticed by moving joystick. Repeatedly pressing the escape key to open and close the game menu makes this obvious, as it will lag anywhere from a half second to a full two seconds. This lag is also present in all other inputs, most importantly, flight and weapon controls. Turning off force feedback completely eliminates the issue. DCS Version: OpenBeta 2.5.6.60966 System Specs: Intel 7700k AMD 6900XT 48GB RAM SSD OS: Win10 Peripherals: Joystick: MS Force Feedback 2 + CH Fighterstick for buttons + Leo Bodner board for axis inputs Throttle: Thrustmaster Warthog Pedals: Saitek rudder pedals Headtracker: HP Reverb G2
  20. Aries144
    jojo, thank you sir.
  21. Aries144
    After this latest update, I found that my joystick's trigger was unmapped. I discovered this early in my test and remapped it. No ordnance other than the gun will release/launch. Procedures checked: 1. Weapons on board 2. Master Arm on 3. Bomb/Rocket selected on weapon panel (light under button lit) 4. Fuse and ripple settings set 5. Radar on, TAS selected 6. Weapon Systemcmd Forward pressed 7. Put HUD aiming symbol on target 8. Pull trigger Also checked select jettison: weapons no longer release after selecting a weapon, activating select jettison, and squeezing the trigger. I verified that the gun will fire in A2A and A2G modes, just no other ordnance. I also verified that all weapons function normally when flying other aircraft in DCS. Has something changed with firing procedure in the last patch? Can anyone else duplicate this?
  22. Aries144
    What you're describing is the reprojection kicking in. Basically, your frame rate is getting too low, so the drivers for your reverb G2 are using predictive algorithms to insert "fake" frames to help keep the video from getting choppy. The blurriness is because the predictive algorithm isn't perfect and can't perfectly predict exactly how everything should look. You'll need to try reducing graphics settings and consider reducing your VR resolution by going to the VR tab in DCS settings and changing the "PD" setting to something less than 1. Try 0.8 to start and reduce from there until things aren't blurry anymore. I also recommend setting water to medium, turning off terrain shadows, and setting cockpit shadows to either "flat" or just off as well. Further, check out speed-of-heat's " My variant of Kegetys mod with clear water and also IC PASS for current beta" mod in his signiture. If you don't see it, here's the link: https://forums.eagle.ru/applications/core/interface/file/attachment.php?id=177807
  23. Aries144
    Great! I eagerly await purchase options.
  24. Aries144
    Good work Razbam. Thank you for your effort on getting things rounded up, it is much appreciated.
  25. Aries144
    Any updates?
×
×
  • Create New...