Jump to content

stiinc

Members
  • Posts

    31
  • Joined

  • Last visited

  1. For just DCS? No. But I will say going from a 7700k to a 5800x was a nice bump in performance overall for my system, it did reduce the CPU frame times, to allow going from 1.0 to 1.3 PD, but the 1080 ti was still the limiting factor. If you were going to upgrade one or the other, IMO I would go with the GPU in your case.
  2. So I ran a quick start........Every single DCS setting on absolute lowest or none, PD 1.0, Steam SS 150% I was able to get pretty solid 90FPS on the Index with a 0.8% reprojection rate and 20 dropped frames over 15 minutes flying in the Huey Harbor Tour quick start on a 3080 clocked to 1935MHZ, Vcard Ram usage was 5.5 Gigs and a 5800x with 32 gigs ram @ 3200MHZ. I however prefer to fly with all the eye candy on, so with the settings a posted earlier I'm at about 45FPS with 50% reprojection......
  3. I think your right, nothing other than a full engine rewrite is going to solve all the issues. I'm waiting to see what MS FS looks like on the 23rd maybe that will be a look into the future for DCS. For now I'll accept what is is currently, as my experience went from IMO, unplayable on a 1080ti to at least enjoyable on a 3080....And I doubt you would get a full 90FPS w/o reprojection on the index, I'll try tonight with everything on low........
  4. Index here as well, I had pretty much given up with DCS VR, just wasn't the experience I was hoping for. Running a 1080ti as well with a 7700k, so very close to what you have. I just didn't want to run everything on low and off just to get 40 fps. I was running 2 monitors, full Helios touch screen setup, track ir and still getting over 60 frames with high settings and full shadows before. Everything else ran great at 90 or 120 in VR, so when my MB released the magic smoke, I bit the bullet and upgraded to a 3080 and a 5800x. I'm quite happy with my set up now, 1.3 PD mostly high settings, flat shadows on and still getting 45-to 50 fps in the standard scenarios, also knowing I can still tweak /oc to get a few more fps. out of it. I'm also running the alternate shaders /canopy settings as well. Hope you can get your set up sorted......
  5. Hmmmm still no joy with the uncapitalized letters. Could you perhaps send back a verified working profile on your machine to test using keyboard sends? Just a couple random switches in the panel. This way i can determine if its my helios install or Dcs install thats not workimg correctly. Im using the latest version of Helios and latest open Beta Appreciate all the help!
  6. I added an example of a test switch I made on the front panel underneath the Indicated airspeed gauge to toggle the Flex site for the copilot, with keyboard press of "m" when toggled. Worked on the old versions and old export to do this way but for some reason it will not accept. All other settings are stock on the profile other than a monitor reconfig. UH-1H_v2.0b.hpf.zip
  7. For some reason Dcs will not accept any newly created Helios key presses. I have configured the switches the same way as before using keyboard interface but nothing works..
  8. Thanks for your hard work in this community. I have an issue you may be able to help with: I am having difficulty adding new switches and buttons on the new V2 profile. It seems the keyboard interface does not work anymore for assigning new key presses like the old versions of export and profile. For example I added a few helpful switches in the old huey v1 profile for flex site, pilot site, site brightness ect to the pedestal 2 panel and autopilot switches to the overhead panel, but these can no longer be cut and pasted from one profile to another, nor will adding them through the keyboard interface work in game either. I'm stumped......
  9. That processor still has a lot of life in it, swap out your graphics card and add more memory. I also agree with Konovalov get a ssd for DCS and OS, it makes the load times super quick. Check out even some of the smaller 240g or 120g ones if your on a budget. What about a 2560X1440 monitor?
  10. Same issue here on a X-52 non pro. I gave up and now use the 4 way hat on the throttle for zoom in and out. Works better for my hands anyway.
  11. Great work as usual Capt Zeen! This is my new favorite module and I've been scraping by with a few switches and viewports I cobbled together, can't wait!
  12. Great mod, export works perfectly on second or third monitor or computer. Problem I'm having is merging the export I use for Helios and your export, I cannot get either to work when adding your code as specified on 2nd page, it breaks both functions no matter how many different iterations I try. Any chance you could help a fellow out?
  13. Managed to get if fixed, wiped all monitor drivers, helios, several reboots and reinstalled everything again and this time issue is solved. Very frustrating...
  14. Just wondering if anyone out there has has any issues with Helios and Windows 10. I recently upgraded to w 10 and now it seems that my Helios panel and buttons are "too sensitive" ie it seems like the touch screen is registering too many touches at one and buttons either get stuck or panels open and then immediately close. Tried to update drivers for panel, it a 21 inch Viewsonic TD2220 and reinstall Helios but nothing seem to work. Issues happen with DCS running or not. Yes I also tried cleaning the monitor... No settings I can find in W10 for sensitivity, there are less options in Pen and touch settings than in W7. As it stands all my fly out panels work only with a mouse click but open and close immediately with a finger touch. In the a10 my mfcds register stuck buttons. Any help with this issue would be appreciated. Thanks.
×
×
  • Create New...