Jump to content

Solbaru

Members
  • Posts

    22
  • Joined

  • Last visited

Posts posted by Solbaru

  1. Had an issue with Mission 8 last night. 

    Everything worked ok for a while, bombed the mortar then flew back to wapoint 4, at waypoint 4 poodle checked in again and they said continue. Poodle then turned 180 and flew back to around the same point as the mortar was and then just circled it. I stayed until bingo and then flew home but mission wouldn't complete.

    Will try again tonight to see if its a one off, but a bit strange.

    Thanks for the campaign tho, enjoying it so far.

  2. Yeah I did rename the input folder and tried and it was the same. The invert check box changes the direction of the X axis but the input from the toe brakes reversed with it. Is the same for every module I own.

    Not home atm but will post some photos tomorrow.

    As I said, I can use the rudder pedals in X-Plane and they work perfectly. It is only DCS.

  3. I Have been using these pedals for over a year just fine but this week the toe brakes are working inverted.

    I have checked the controls configuration and the invert check box is ticked, I have tried every setting to change this but they are always the opposite of what they should be.

    I have tried a repair, unplugged everything else, re-installed the drivers.

    I have x-plane 11 on my pc and that still works fine, its just DCS.

    dcs.log

  4. Im having this issue now as well, I have been using these pedals for a couple of years without issue. Just bought a virpil throttle and now my TFRP pedals have gone to shit.

    Toe brakes on bot have gone inverted. No matter what I do I can not remove this inversion.

    Go to the control settings and tick the invert box doesn't change anything.

    When I look at the output from the VPC tester I can see it inverted but I thought the invert checkbox would solve this. it doesn't.

    Thru the thristmaster calibration tool everything looks fine.

    as I said, very strange, this has been working fine for years.

    I have unplugged everything and uninstalled the thrustmaster software a couple of times. cannot solve this.

    Anyone have any ideas???

     

    Further investigation, I opened Xplane 11 on my PC and setup the pedals and the invert setting works correctly in the SIM.

    Looks to be an issue with DCS.

  5. Are there any plans to add the BOL chaff/flare dispenser to DCS?

    The BOL that is in use on a number of aircraft around the world and has been in use for nearly 20 years would fix the issue of the number of chaff and flares the hornet can carry.

    each adds 160 chaff/flares to a weapons pylon.

    Always found the hornet does not have enough.

    more info https://www.saab.com/newsroom/press-releases/2012/successful-first-flight-for-bol-countermeasures-dispensing-system-on-f-18-in-finland

    wouldn't have thought it would be that hard to implement in to DCS, not just on the hornet either.

  6. I made some changes last night and I think I have it working, only issue now is, whenever I use a button that uses a "ctrl" key in the combination it stops the whole thing from working.

    Its like the ctrl key is being held down, which screws everything up. Have to reboot to fix it.

    might need to email the guy that writes the software for that one..

  7. I have a Thrustmaster Cougar that I have upgraded the throttle with the mmjoy board, I am now trying to get this to work in joystick gremlin as I cant get it to work in TARGET anymore.

    I am having trouble with the speedbrake switch on the throttle as it needs to be a press and release setting to get it to work correctly.

    Has anyone done this with Gremlin??

    I imagine that the warthog has the same switch process so maybe someone has done it with a warthog on Gremlin...

    If anyone has this working and doesn't mind sharing the config it would be appreciated..

  8. i7 8700K

    Radeon sw 19.3.1

    Radeon Settings Version - 2019.0926.1648.30252

    2D Driver Version - 8.1.1.1634

    Direct3D® Version - 9.14.10.01410

    OpenGL® Version - 26.20.11000.13571

    AMD Audio Driver Version - 10.0.1.12

    Vulkan™ Driver Version - 2.0.106

    Vulkan™ API Version - 1.1.119

     

    There, I copied/pasted everything.

    Didn't mean to upset or contradict anybody, just stating that mine works fine. Vega 64 and a 5700XT are not the only AMD cards out there ;)

    Mind you, I have not updated since long, never fix what is not broken..

     

    Thanks for that.

    When I was troubleshooting with AMD they said go back to an earlier driver but 19.7 was as far back as I could find a driver for.

    Im going to try to find 19.3.1 like you are using and try that. if that works i will be stoked.

    Thanks for the info.

  9. Reverb + Radeon VII user here. My setup works perfectly, not sure which AMD cards you are referring to.

     

    As I said, that is with a Vega 64 and 5700XT.

    Put a Nvidia card in the system all works ok. Have spoken to HP and AMD and they have confirmed the issue.

    what CPU are you using and driver version??

    You are the first person I have seen that the reverb works with an AMD card.

    there are a number of people reporting this issue world wide as well.

  10. Is anyone using the Reverb with a AMD video card?

    I have been trying to get the reverb working on my pc but get constant blue screens.

    I have a 5700XT and have tried with a vega 64, getting the same error.

    It looks like an issue with the AMD driver.

    Have tried the headset on a mates system that has a Nvidia graphics card and it worked fine.

    System only crashes when I plug in to the display port.

  11. Finally received my reverb after waiting 4 weeks, went thru the setup I found on this site and plugged in my reverb, blue screen.

    Spent 2 days trying everything I could find.

    Rebuilt windows to a fresh build, still blue screens when I plug in the USB port.

    I even have tried a PCIE card with USB3 ports same thing.

    problem seems to be around the hololens sensors driver.

    As soon as that starts to load BSOD..

     

    frustrated as hell.

    Anyone have any ideas

  12. That is the beauty of the Reverb. Superior displays don't have a need for increasing clarity with SS/PD like it is with Rift-S or Cosmos so hardware requirements are the same with a slight advantage to picture clarity to Reverb.

    For DCS usage only this is a major advantage over the competition.

     

    My use will only ever be for DCS or Xplane 11 is the tracking ok on the reverb for DCS?

    Have read its not as good as the rift s.

  13. This is the exact decision i am trying to make atm.

    I was leaning to the cosmos but the price here in Australia at $1299 is just too expensive.

    I am going to go with the Rift S. Unless someone can convince me that the cosmos at twice the price of the Rift S is twice as good.

    Looked at the Reverb as well, price in the middle of the 2 but my PC has a Vega 64, not sure how that will go with the reverb, don't want to spend another Grand on a better GPU and tracking is not as good as rift s.

×
×
  • Create New...