Jump to content

ilikepie

Members
  • Posts

    771
  • Joined

  • Last visited

Everything posted by ilikepie

  1. viewporthandling lua. -- in red square has been added
  2. let us know what you use, the rwr is a smudgy mess
  3. https://www.digitalcombatsimulator.com/en/files/3306442/ for take off speeds. handy.
  4. this might seem a bit strange , but are both programs run as admin? could it have something to do with privilege level. I know my TIR and DCS required to be run as admin so they could communicate. Also, the Modifier key (RALT) or the function key could be a "trapped" key/s by the occulus software?
  5. is full screen unchecked in dcs options?
  6. there is no aspect set in the lua? I've had a look at mine for comparison and thats the primary difference, might be effecting it ?
  7. no, u want 105's for mbt's
  8. i went 34" uwhd. has a touch screen underneath. went from a 27 and i like the extra fov and still get good frames with some candy settings. it is a ASUS ROG SWIFT CURVED PG348Q 34" ULTRA-WIDE QHD 5MS IPS G-SYNC 100HZ GAMING MONITOR
  9. perhaps HOF was too low?
  10. if it does work, please supply a track of the rain dance. we already have lambs.
  11. https://discord.gg/QjPd5pM
  12. i think you can bind the tracking gate to button/hat switch. it'll be in the control options of dcs. in DGFT mode you have the level5 eegs sight, which is very easy to use
  13. D/L is a wip. known bug, its a little sporadic currently
  14. are you running the open beta on steam or stable release? iirc you have to opt into the OB on the steam version I have stand alone OB and this issue is not present. I've always been on the OB standalone branch so cant really compare apples with apples. I cannot recall what level functionality the viper is at on stable, do you know someone that you can compare it with, or perhaps another steam user could jump in and verify?
  15. tried running a repair on dcs?
  16. I've experienced the same thing. rendering problem.
  17. looks like the TGP is masked? was it flashing before it went dark? I see that the indication is present in the other shots too. Could be the wing blocking it looking at the angle of bank and where the target area is located.
  18. send it back. it sounds like a fault
  19. or set it to AUTO
  20. this. it might be unbound by default
  21. There is a sub section in the input output forum that cover has some hardware listed. A lot of people seem to like the Virpl gear but from what I've read production is slow and not readily available. Vkb is another. hope you get it sorted, sim time should be enjoyable. Not a chore
  22. when you say replicate the issue on the laptop, you plug the stick in and it behaves exactly the same way, with completely out of sync movements? If that is whats happening it could be that a wire has become pinched internally and there has been a disconnect in the circuit causing incorrect data to be sent. If it is still under warranty, I'd return it to the place of purchase for testing and replacement. I've had the TMS switch on my stick be faulty out of the box, and view hat on the throttle fail through bad soldering work. For the former, the unit was returned and replaced, the latter was a case of taking it apart and fixing it myself as the unit was 9 years out of warranty. It sounds pretty unusual, especially if it was fine....and then it wasn't. Could have been coincidence that it occurred after playing with calibration
  23. so when you look in the windows joystick properties its all screwed up or is it only in dcs? maybe delete the folder in your User/savedgames and let it recreate it?
×
×
  • Create New...