Jump to content

RedX

Members
  • Posts

    116
  • Joined

  • Last visited

About RedX

  • Birthday 06/08/1976

Personal Information

  • Flight Simulators
    DCS World
  • Location
    Finland
  1. Checking the reviews of Vive Pro 2, I get disappointed. Their pricing is much higher than that for Valve, but the only thing where there is improvement is colors and resolution. That FOV improvement over Index is marginal, basically the panels are rotated 90 degrees . For any serious FOV increase there is only Pimax and the expensive industry grade gear. Simultaneously, the audio side on Pro 2 appears to be very poor, sweet spot remains small, and lens glare is significant just like in Index. Very difficult to justify the price bump, I would say. Dburne, please may we have a comparison from you written here on Index vs Pro 2 when you get it?
  2. Replying to myself... I investigated a bit further and found the following. This applies to my case, not sure about others. YMMV. - the slowdown/jitter/cpu frametime increase depends on the mission file - 2.7 has made it worse - deleting saved games\dcs improved the situation a lot on certain missions; at first it was not clear why; it turns out that delete is not really necessary, but instead... - Ta-daa! TACVIEW file recording has some issue with the new version, it was not turned on immediately after deleting saved games folder and thus things looked better. It may have something to do with the number or type of AI units or their activity in the mission. --> if you have this issue, check out whether turning your Tacview completely off helps (options - special - tacview - completely off)
  3. Exactly the same on my AMD 5800x, the CPU frametimes are through the roof with 2.7 update. Maybe this is some kind of thing that is CPU or chipset related as that would explain why not so many are reporting the problem? Perhaps Intel/Nvidia is more tested and optimized? Maybe ED has no AMD hardware to test with due to cryptominers buying it all? In any case, the performance issue has to do with DCS core(?) engine overloading the CPU. Graphics is hardly related, because if I hit "pause" everything is super smooth and un-pausing makes things go slow and jittery again. Tried to remove the infamous windows KBs (500...something) and vortex calculation - no help. Ditto driver updates.
  4. The values are pulled from "somewhere" where they have been written at the factory when the headset was calibrated. The values vary from one individual unit to another, because the mechanical panel placement is not as accurate as needed in this application. Most likely the left-right values are calibrated ok at the factory and the values should need minimal adjustment if the headset is ok. The up-down values seem to have a bug regarding the sign convention somewhere. In some headsets the calibration values are symmetrical enough so that it does not matter.
  5. I'm not sure whether frametimes shown by DCS match those shown by fpsVR. Do they?
  6. CPU frametimes on MP is a difficult test to perform reliably as the workload on MP servers can vary a lot during the time it takes to swap the cards. To tackle this, a cycle of quite a few card swaps would be required in order to make the differences of 10-20% observed reliably. Maybe 3-6 times back-and-forth. I don't plan to perform such a laborous testing at this time. To avoid it, one could have a custom, non-changing MP server with no other clients on it, but it would probably not be any different from SP testing.
  7. @med0ra Tested with that mission 1 you suggested, both 6800XT and 2080Ti. And, well, would you guess, the result was the opposite: now 6800 XT produced slightly faster CPU frame times than 2080Ti. Key figures below. 6800XT: CPU 50% 13.6ms; CPU 99% 22.1ms; GPU 50% 10.6ms; GPU 99% 14.6ms 2080Ti: CPU 50% 14.5ms; CPU 99% 22.1ms; GPU 50% 11.5ms; GPU 99% 15.7ms Despite all the card swapping, driver reinstallation etc. the results for instant action missions (my first post) are still repeated and there, when standing on the ramp / ship, the Radeon card is more taxing on the CPU than Nvidia. I can only conclude that the changes in CPU load may vary greatly depending on the mission. Perhaps the computational workload of different graphics items is differently distributed among the CPU and GPU. Now I have no clue whether I should keep running 6800XT instead of 2080Ti despite the larger amount of VRAM
  8. exil, did you clean up nvidia drivers with utility like DDU when you switched the card? Or did you just insert the new card and leave all the old drivers around? Did you reinstall steamVR? I wonder whether it matters which output port is used for VR headset, too. The RTX 2080Ti is back in the computer and CPU frame times are the same as before as recorded by fpsVR. I think I'll try to install 6800 XT again and see if the result changes by tinkering with the installation procedure or settings.
  9. I benchmarked Nvidia RTX 2080Ti, RTX 3090 and Radeon 6800 XT using the same settings in DCS. While RTX 3090 is of course clearly the fastest of the bunch, I found a weird thing considering the CPU frametime values recorded using fpsVR. It appears as if both Nvidia cards have similar CPU frametime and performance despite the large difference in GPU performance. This is expected. The Radeon 6800 XT, however, shows much higher CPU frametime values. The difference is enough to be of practical importance. Actually, sometimes it seems that the 6800 XT is resulting in lower fps rates than my old 2080Ti due to higher CPU load. I very much prefer lower CPU load, because that is usually what is limiting my frame rate in VR (graphics load is tunable by various settings). I'm not sure if something went wrong when reinstalling SteamVR etc due to the entirely different set of graphics drivers. I attach an example of fpsVR graphs. In this specific case: -all possible settings the same for Nvidia and Radeon -mission is the F-18 instant action "ready on the ramp" in PG -30s fpsVR recording sim stopped, then 60s more fpsVR recording with sim running (plane just idling on platform) --> 2 peaks in graphs corresponding to pause on and pause off -steamVR set at 202% with Valve Index (2864x3184) -CPU is i7 9700K @4.9GHz, Z390 chipset, 32GB RAM @3200MHz -Nvidia CPU frametime is around 15.5-16.5ms paused, 17-18ms unpaused -Radeon CPU frametime is around 18.5-19.5ms paused, 20-21ms unpaused, around 15% worse than Nvidia! Can anyone else verify that Radeon drivers eat this much more CPU than Nvidia drivers in DCS and VR ? Or did I mess up something when switching drivers?
  10. Looking at the results and especially the very nice photographed results above (galinette, excellent simple but functional setup!), it appears that at least some headsets have an issue when the top and bottom values are reported. Whether that is due to DCS or drivers or headset or some other thing, I wouldn't know for sure. However, since I detect less misalignment in other games, I'm afraid that it is DCS that might have some numbers reversed somewhere, not steamVR. In order to not sound too harsh here, I want to say that I've encountered similar things numerous times in my work when there are just 2 options of how things may end up, front/back-up/down-left/right-mirrored/direct etc. It is very easy to confuse those and miss them in testing when dealing with optics and software. The great thing is that DCS allows the tools where such stuff can be corrected as long as the user knows what he/she is doing. More documentation would be appreciated BTW, regarding galinette and his/her images, the remaining misalignment may easily be due to the mechanics imperfection of the IPD adjustment system. (The left-right misalignment I would dismiss for now, because the HUD data display is not really projected at infinity and is modelled so in DCS so there should be small left/right misalignment with infinity-aligned imaging system such as the camera setup used.) Uxi: you can create that file in C:\Users\<your windows username here>\Saved Games\DCS\Config or equivalent on your system. It does not exist by default.
  11. Hi all, I'm having a trouble where I often accidentally click an additional direction of a 4-way hat simultaneously when keeping the intended, original click pressed for an extended period of time (>1s). The switch is mechanically such that this happens very easily when not intended. Especially since the orientation of the 4-way hat changes slightly along with different throttle position so that my muscle memory has a bit more trouble than usual keeping track of the orientation. How to programmatically prevent that from happening? So that when any of the 4-way hat directions are clicked, all three other directions (or the 2 nearest ones) turn inactive so that they do not work/give signal until the original 4-way hat click is released? That way simultaneous / diagonal clicks of the 4-way hat would be prevented. Currently the hat is configured as 4 buttons, not as a POV hat. EDIT: Found it but in such manner that the diagonal click turns off the original click i.e. there is no input when hat is in diagonal direction (Button page - ALPS decoding - mode pulldown list: 4W instead of 8W) . I would like to have the original direction/click to stay on when simultaneously clicking the additional direction/diagonal direction until the original direction click is released. Does this make sense? Is this possible? BR, RedX
  12. I've experienced this on Valve Index both on carrier and elsewhere. MSAA is always off. However, I get a feeling that it most likely appears if I have high graphics settings (despite MSAA off) and especially if Nvidia GeForce Experience driver's video recording function is turned on.
  13. Exactly the same here. Autostart option is corrected but the crash is still there after PC restart. Is it possible that it has something to do with the installation option "Everyone" vs "Me only" ? I used the "Everyone" option.
  14. It seems that the crash is reproducible. The "USB reconnect required" was a different issue, I don't know why that was needed at some point and I can't reproduce it. About the crash: If I click "quit", the simshaker starter stops. If I click "continue", the simshaker starter keeps running, but: - start simshaker via right-click-menu or the UI button does not do anything at all - if I quit the starter and restart it, everything works normally Required to reproduce: - start simshaker starter - click "start when windows starts" in settings - restart computer - starter is automatically started - start DCS --> crash (simshaker crashes as explained above; DCS runs normally) Test case: no autostart with windows, just manually start simshaker starter - works normally Test case: autostart with windows, quit simshakers starter, start simshaker starter - works normally Test case: any start of simshaker starter - open settings menu, the tick at "start when windows starts" is always missing - no touching of the tick: if simshaker started automatically at last PC restart, it starts automatically again when PC is restarted, and crashes again - no touching of the tick: if simshaker was not started automatically, it will not start automatically when PC is restarted; manual start of simshaker and DCS results in normal operation - touch the tick: turn it on and simshaker starts with windows when PC is restarted; regardless whether it started automaticall at last PC restart - touch the tick: turn it on and then off, and simshaker does not start when PC is restarted; manual start of simshaker and DCS results in normal operation - whenever simshaker starter is quit and started again, the "start when windows starts" tick *appears* always to be unticked in settings Hope this helps. Regards, RedX
  15. Hi, I encountered now 3 times (randomly) the following. It might have something to do with recent windows restart or newly started simshaker but I cant confirm that yet. -simshaker is started automatically with windows -DCS is started up and when main loading screen shows up, i.e., when the "simshaker starter" is supposed to launch "simshaker for aviators" (SSA), an error occurs -SSA does not start but .NET error message is displayed -software version 2.1.3 beta -"simshaker starter" halts when error message is displayed and exits if I click "quit" -latest DCS version, Windows 10 Home FP 2004 I wonder what's wrong ("cannot find the file specified"). EDIT: The JetPad is not found by any software until USB cable is disconnected and re-connected after the error above. After that, it seems to work normally. Yours, RedX The full error message is below.
×
×
  • Create New...