Jump to content

tmz

Members
  • Posts

    16
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS - BMS
  • Location
    France

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I confirm that performance is a lot better for me as well, have only done two short flights but without encountering drops like in 2.9.6/2.9.7.
  2. I don't use this launcher for the updates, I find the terminal less confusing. I believe you should select "Release" in the scroll-down list, leave "Custom Branch" empty and 2.9.5.55918 as the version.
  3. Hmmm... just tried it, worked for me... Were you on OpenBeta originally? Could you try the same but appending @release? .\DCS_updater.exe update 2.9.5.55918@release
  4. How can it not? On the same machine, sequentially, same mission, same settings, same SSD, 2.9.6+ doesn't work, 2.9.5 does. That is, again, the whole point of this thread.
  5. That IS the whole point of this thread! And we are many to experience it. Everyone understood that you are not impacted, please try not to derail the thread for those of us who are. If ED needs hard data, we will definitely provide it, I imagine most of us will be happy to spend time troubleshooting this. With ED. Using the terminal it is pretty easy : open a terminal, and go to the bin folder of your DCS Home followed by 'Enter', see below for my system. cd 'D:\DCS World\bin\' From there, input the following : .\DCS_updater.exe update 2.9.5.55918 DCS should now downgrade.
  6. See that’s what I’m having trouble with… with 2.9.5 all is fine, with 2.9.6/2.9.7 everything turns to crap. Hence this thread. If something is broken on my end, fine, and I’m happy to send ED any track log or spend time to debug this. But something is broken on a lot of users systems. And this is definitely systematic for us Retribution users. What’s your config for my information?
  7. It's the one I've been using since 2.9.6 came out, after completely reimaging my machine fixed nothing. We do have density options in Retribution, and culling... but it's not just Retribution that is impacted, is it? It's a lot of paid campaigns as well. FIWOS for instance. Haven't tried Reflected's campaigns but heard some were impacted as well. Currently it's 50 up to 100 flying units and 10 ground units per frontline that are recommended on the Retribution Discord. A war with 50 flying units up and 20 ground units fighting each other? Come on. The whole point of this thread is that in 2.9.5 it worked (and still works) appropriately, in 2.9.6 and 2.9.7 we had enhancements that were so drastic that even a 4090 and a last-gen x3d processor cannot run missions that used to work anymore. So while only "Stable" (sic) remains, a little bit more testing on the dev side and a little less testing on the end-user side would be appreciated, on the "Stable" (sic) branch and longer dev cycle that we were sold as a way to get a more "Stable" (sic) product.
  8. Same here. As it stands, paid campaigns or dynamic campaigns like Retribution are out of the question at the moment, which are my primary interest in DCS. It's been what, four updates since the regression?
  9. Could you try to run the mission at the top of the thread? Runs at my headset refresh rate 72FPS in 2.9.5 (more than 100 pancake), runs with 10-40 FPS Pancake or VR with 2.9.6+. On a 4090 + 7800X3D. I get the same perfs in VR and pancake, this is not a graphics problem. Same mission has planes litterally going backwards running on a server with 2.9.6+, no FPS issues then on the client but unplayable as well.
  10. The problem is the performance degradation between 2.9.5 and 2.9.6/2.9.7. What used to work does not anymore, and that is a big problem for those of use that run missions with large unit counts. How can you simulate a war with 20 planes and 50 ground units?
  11. Tried again yesterday with DCS 2.9.7.59074, still a stuttery mess. Log attached. dcs.log
  12. Thanks for the testing! This is a vanilla version of a DCS Retribution campaign I use (with all scripts removed), as there is no active frontline there should not be many moving units. What strikes me is the performance difference between 2.9.5, where I am running routinely campaigns of this scale, and 2.9.6/2.9.7 where it is not possible at all.
  13. I’ll try, but 2.9.7 is just the second release installed in that path since I reinstalled Windows (also run 2.9.5 as the others are unplayable for me). As I had a performance problem with 2.9.6 hotfix before reinstalling, and as we are many to have this issue I don’t think this is related to my DCS install (and I don’t want to screw up my 2.9.5 install).
  14. Thanks for the reply. I'm not editing shaders manually, I tried another run and deleted fxo/metashader2 folders, same error and same results. dcs.log
  15. Hello, I noticed a huge performance degradation with 2.9.7.58923 and 2.9.6.58056 compared to DCS 2.9.5.55918 on most busy SP missions. A mission (attached) that is playing perfectly on 2.9.5 shows a huge CPU usage with 2.9.7. As an example, I get 20-30 FPS in VR, 20-50 FPS in pancake with 2.9.7 compared to 72 FPS (max rate set on the headset) in VR or 75 (max FPS set in DCS) pancake with 2.9.5. Specs : Happens on VR with VD and Pancake 4090 / 7800x3d / 64GB DDR5 2-week fresh install of Windows (reimaged after 2.9.6.58056). Sorry about the quality of VR screenshots, but the graph shows it all. Attached : Benchmark miz file (no scripts) DCS log from 2.9.7 run VR and pancake screenshots from 2.9.7 and 2.9.5. dcs.log Scenic-Bench.miz
×
×
  • Create New...