Jump to content

toffy

Members
  • Content Count

    10
  • Joined

  • Last visited

About toffy

  • Rank
    Junior Member
  1. Never mind I think I got it now. Just got to stay low and avoid missiles. The a10 is still there to help
  2. I have flown mission 11 in the f86 at least 5 times now and the a10 that is supposed to be my wingman either crashes or just spontaneously explodes in the sky before reaching the enemy group in the river valley. I am flying pretty low following the mission briefing, but he always gets destroyed. I still hear him call out "missile, missile" and "don't get any closer" to the enemy position, but he is nowhere to be seen. I eventually get shot down by a missile because I no longer have his support. Does anyone have a clue what I could be doing wrong? I can't seem to progress beyond this mission.
  3. toffy

    Reverb G2

    Let us know if you are able to resolve your issues. I have nearly the identical system you have including SMT disabled, but with 32 gb of RAM and when I was running DCS in 20H2 my fpsVR looked exactly like your picture.
  4. toffy

    Reverb G2

    What windows release are you running? I have a very similar setup to yours(3900x with 2080ti) and my cpu frame times looked just like yours when I upgraded to windows 20H2 from 1909. Not sure what happened either some windows setting got reset or what, but when I upgraded to 20H2 my cpu frame times tanked. My solution was to go back to 1909 and my cpu frame times went back to being much better...nowhere near 27 ms. I'll have to research further what was actually going on, but for now downgrading windows helped me.
  5. Thanks for the link. I posted to that thread. However, I still have not resolved this problem.
  6. I'm having the same issue as the OP I'm using the p51 and F5 modules and I can't seem to select anything from the mission options menu items. None of the "take" commands work. I get the beep and acknowledgment. The debug window shows that the command was processed but nothing happens. I've tried cleaning up the lua files and also clearing my profile but that doesn't seem to work. The only way I've gotten things to work was to downgrade back to 2.5.21. Is this a bug in the latest vaicom pro?
  7. I've been using vaicom pro with the p-51(easy comms off). Every mission I play has this issue. I tried also with the F-5 and I get the same result. Do you have a link to that thread? I can't seem to find it.
  8. Ever since I updated to version 2.5.22.1, I cannot get vaicom pro to select any of the "mission" options menu items. i.e "Take 12" or "Take 4" do not do anything. I just hear the acknowledgement beep and vaicom pro debug logs show the command was executed, but nothing happens. I downgraded to 2.5.21 and the mission options menu selection works fine. I've done the troubleshooting steps, but I cannot get the latest version to work. I am using vaicom pro with the latest "stable" version of DCS. Is this a bug or did I do something wrong? Is this a known problem? I could not find anyone rep
  9. This is a vaicom pro issue https://forums.eagle.ru/showthread.php?t=198297&page=552
  10. This was very helpful and made a significant difference in performance. I can now have a good looking cockpit and decent frame times. Thanks to all.
×
×
  • Create New...