Jump to content

WipeUout

Members
 View Profile  See their activity

  • Posts

    633

  • Joined

  • Last visited

 Content Type 

Everything posted by WipeUout

  1. WipeUout
    Found the culprit: Options.lua The file was corrupted by starting my steam version which was not the same as my non-steam version of DCS. When I replaced this file from my previous Savegame/DCS/config folder, the GUI did not start. Reverting back corrected the issue but I had to re-set most of my options. At least I did not lose my flight stick/throttle/pedal config.
  2. WipeUout
    Worked! Thanks @Flappie. Now, what can I copy back in the newly created DCS folder in order to get my settings back? The "config" folder? Obviously, the mission folder should be straight forward but would like to avoid file by file trial and error...
  3. WipeUout
    The GUI, either in 2D or VR, is failing to start. I tried to do a repair with no change. I tried to revert to 2.7.18 with no change. In VR I see the hangar with the MIG-29 but no GUI. In 2D, just a black screen. Tried also both SteamVR and OpenXR and no change. There is an error message in the log stating the GIU failed to load, but no idea what is causing it. Help! dcs.20230204-200407.crash dcs.20230204-200407.dmp dcs.log DxDiag.txt
  4. WipeUout
    Since DCS native support for OpenXR was introduced, I reverted back to OB 2.8. Unfortunately, running the sim with PimaxXR 0.3.0 and OXRTK 1.2.4, I started to have "convergence" issues and stutters as soon as I would start moving my head. Reverting back to use Opencomposite and PXR 0.2.8 and OXRTK 1.2.1 made the issues go away. What I labeled as "convergence" issue was causing the image to be blurry, slightly out of focus. It could also be a slight de-synch between the right and left images. As for the stutters, they were appearing just at the start of a head movement, one or twice, and then go away. My frametimes both for CPU and GPU were well below 16.7ms, not even close. I have the 60hz / 75hz Pimax 8KX (older) model and run the HMD at 60hz. I do not use motion re-projection and my resolution is 4k native. Sorry, I did not have the reflex to save my dcs.log file. @mbucchia, could this be related only to the older 8KX?
  5. WipeUout
    Difficult to assess if your performance is where it should be. What map, airplane, mission are you using? What are your DCS, NVCP, SteamVR (or OpenXR) settings? A lot of variables can influence performance. Also, are you monitoring your CPU/GPU frame-times? This can help tremendously to guide you, fpsVR for SteamVR is a good tool for that and if you are using OpenXR, there is an option to display this info as well.
  6. WipeUout
    Happy you had a good experience with a used(not much) GPU. I was not so lucky before getting the 4080 when I tried to get a cheap ''refrubished'' 3090Ti from eBay. The card was completely dead, not even fans turning when powering on. They did reimbursed 100% plus shipping cost to get it back but after this episode, I went for a new GPU. Did you noticed any image quality improvement over the AMD card?
  7. WipeUout
    No but I don't have your horsepower with my 4080. One thing I tried is flying with 120hz HMD refresh rate with reprojection on. I find that running 60 FPS on reprojection creates far less ghosting than 45 FPS when HMD's at 90hz or 37 FPS when my HMD's at 72hz. Granted that the Pimax is a different beast.
  8. WipeUout
    Thinking alone fails again. What is being simulated in MSFS, X Planer etc.. is much less demanding than a FULL COMBAT SANDBOX like DCS. Adding yet another dimension like weather modeling, would for sure be cool and increase realism but at a cost that would result in even less performance. It already takes a top rig to run DCS in VR, last thing we need is more stuff being simulated. DCS needs to first solve performance and then look at cranking additional realism or whatever the customer wants next.
  9. WipeUout
    I believe that DCS does much more as far as simulation of other stuff such as weapon, enemy AI, troop movement, radars, etc... Very different sims!
  10. WipeUout
    Just make sure you set power management to "prefer max power". You may also use profile inspector to check that rbar in section 5 is "enabled", by default it is disabled. Other settings leave to default.
  11. WipeUout
    Never mind, I found the lines in the 2.7.18 file version, they are the same but elsewhere. Even in 2.7.18 there is a noticeable improvement, I gained 3 FPS in the F-18. This is very good and almost gets me to go back to 2.8.1... Almost.
  12. WipeUout
    Dear @Taz1004, Seems awesome but I can't get it to work with 2.7.18. Do you have a different version for pre-2.8.1?
  13. WipeUout
    Have you tried also going over the top of mountains? There is a bit of wind effect I noticed when flying close to mountain top. Nevertheless, I must agree with @speed-of-heat, this would require so much resources to simulate and I don't think we are there yet with the present code and even hardware capabilities.
  14. WipeUout
    Could be several things but in general, it takes more resources to render cockpit vs outside view. Have you checked your GPU/CPU frame time how they fluctuate when you look inside or outside? Also, what is the load on your VRAM? If it is reaching 8 GB, than it could be causing a re-load of textures and thus stutters.
  15. WipeUout
    For me I leave it on but there is no appreciable gain (or loss). You will have to try with and without and see if you have any gain.
  16. WipeUout
    Hardware Accelerated GPU Scheduling. Setting is in display/graphics/change default graphics setting/. Improvement is very dependant on your particular setup. No effect on mine.
  17. WipeUout
    SSAO = off In my case, it is a 1.4ms negative impact on my GPU frametime for very little difference in image quality. Even in pancake mode it does not make a significant difference in visual improvement for me.
  18. WipeUout
    DLSS in VR?
  19. WipeUout
    Yes but when will this be implemented in DCS. if ever? DLSS 3 is a great technology but needs to be implemented by software developers...
  20. WipeUout
    4080. I did the switch from a 6900XT. It was a good card but AMD's support for VR is not on par with Nvidia, particularly for Pimax HMDs. The 4080 is providing me better compatibility and also improved image quality for contrast and black levels. Joining the green team cost more but the 4080 is cheaper than a 3090Ti for 15% more performance! The FPS performance increase for DCS from the 6900xt to the 4080 is about 31% using SteamVR. I paid $1450 for my 4080 which is about the same price as a 7900XTX on amazon.
  21. WipeUout
    Here you go. Two tracks, one for F-14B and one for AV8B. The F-14b takes a little longer to have the mod effects come back but they do come back eventually. I also included the mission I used to create the tracks. Hope this helps. 3DMigoto fade with blackout (AV8B).trk 3DMigoto fade with blackout (F-14B).trk 3DMigoto Test.miz
  22. WipeUout
    I forgot to mention that I also tried at different PD (1.1 vs 1.2) with no noticeable difference other than the one caused by the 121% vs 144% super sampling. I even went to the extent of changing my HMD's refresh rate and switch my 8k+ with my 5K Super for no difference. I would rule out also Win11 vs Win10 as both OS were used by people reporting the drop. Men, this is not easy!
  23. WipeUout
    Feedback from ED staff stated that not everyone is experiencing a FPS drop with 2.8, which got me thinking at what could cause the issue in my setup and not in others. In this case, then it could be related to certain configurations. I took this as the main assumption for the test I ran. I did not find any culprit but it may provide some good lead to look into to find the issue. Also, looking at my dcs.log, I noticed several warning and errors which could have been related to mods installed/removed/installed over and over again. So my first step was to un-install DCS completely and re-install fresh. I also took the extra step of making sure all the sub-folders, other than skins, were emptied before re-install. After a fresh stable 2.8.1 re-install, which took quite some time, I started to run my test track file vanilla and for each of the mods I used in hope I would find the culprit. Unfortunately, no different results were observed, I still take a GPU Frate Time hit of 1.6ms from 2.7.18 to 2.8.1. My results are in the table below. Findings: 1. It seems that the drop is not related to a broken install or the mods I have been using. 2. The drop is significant also from med shadows to flat shadows. 3. I tried both SteamVR and OpenXR and there were no differences. 4. I use default settings for NCP, HAGS on/off with not difference. Other possible causes would be driver/hardware issue that would be common to all experiencing the drop, which would not be impossible but unlikely. It does point to the changes that were made between 2.7.18 and 2.8.0. The question remains, why would some experience no change or improvement in performance? Did ED received testing data to demonstrate this? After re-install dcs.log Before re-install dcs.log DxDiag.txt performance track Caucasus F-18.trk
  24. WipeUout
    Not sure if this is a bug but in F-14 and AV8B, whenever I start to go blackout, the mod stops working and re-start working after the blackout effect goes away. I haven't tried in other modules. P.S. the mod is still working fine in latest update.
  25. WipeUout
    Man, I was having a good time flying in 2.7.18 with lots of FPS and details and then boom, back to the problem! Anyone knows how to revert to 2.7.18 with a Steam install?
×
×
  • Create New...