Wali763

Hello. Quick forum-search did not give me anything, so I thought, Id make a new thread. Ever since 2.5.6 game loading times are TERRIBLE. Before 2.5.6 I soley used OB and load times were around 25s to the main menu. Since then I oc'ed my CPU to 4,8Ghz allcore and along OB use stable 2.5.5. Just tested this again. Loadtime of stable (2.5.5) is about 20s now to main menu. Loadtime of OB (2.5.6) to main menu is 01:20s at the first try!!!! Four times as long as loading stable. Second try was 01:05s (see log); thrid try was 40s... strange..... Ive already done numerous repairs, deleted of savedgame-folder etc........... and already kind of got used to this. Still this is all very strange to me stable dcs.txt OB dcs.txt

I did this test and the difference between stable (2.5.5) and OB is huge! In OB the mission I had 274 units and fps went down as low as 16fps, even mostly being around 20-25. In stable I had 251 units and the lowest fps I saw was around 48!

Shimmering will be there for a long time. Best to accept it. Had briefly a Reverb and also with that high resolution, shimmering is still painful, especially on the carrier looking around. But also on monitor you do have that, but to a lesser degree. I guess, only once we have real high resolution headsets like 8K per eye, this will go away.

Im am successful reconverter from VR to monitor/TrackIR and not regretting it. VR is nice but I never really had that WOW-effect in the first place. There are just too many shortcomings to make it great. At least up to now. At first I tried to accept them (eg the poor resolution) but eventually (one might call this "wear off") I could not. Tested also the Index and Reverb, but both - though being great so some areas - for me are still beging far from really enjoyable. One thing, that also might attribute to my lacking joy with VR is, that I actually dont consider myself as a real pilot like many here do, but more like a gamer. IMO from the distance from monitor to reallife flying VR does only shorten this distance by maybe 10%. Just think of the consequences of not doging an incoming missile in DCS: NONE. In real life that potentially would end your life. Still: also Monitor/TrackIR does have its problems and im pretty sure with the proper hardware Ill "go back" to VR eventually.

Also have both installs on the same ssd. First one (OB) was about ~120GB to download with my modules after a recent Windows-reinstall. Stable (with the same modules) then only required for some 30 additional GB to download since it copied most of the files over from OB. Only mistake I made was when copying over the SavedGames-folder from C: I did not create a new folder, so I have now 4 DCS folders on my D:-drive.... Both OB and Stable with the Savedgames-folders have 350GB in total

Thx for the help. Ive been flying the misson "Dawn Raiders", where I had my problems. I now found out, after I designate the target-WP and the Walleye gets slaved to the target after uncaging, I have to wait long enough to get a lock. Using AWW-13 though seems not useful, since the transmitted image is not always looking the way, the bomb is gliding and because of that corrections are pretty hard to make... About the use of the TGP to find a target and designate it, this hint was very useful. Overall Im not too interested in the Walleye, since it really seems outdated and I very much prefer the Maverick/TGP-combo, still I wanted to be able to use it correctly, if a mission required for it. Now I think, I can do it. So thx for the help.

I know, that Walleye is pretty old and has quite a few limitations. But watching Wags video for the Walleye it seems just so easy. He from far away gets a lock on a small unit. I have even trouble getting a lock on bigger buildings. Neven was able to get a lock on a mechnical unit. Its very hard for me to acquire a lock on a target. Since its a TV-guided I look for contrasts to lock on. Often very hard. I tried higher up (25000ft) or from medium hights (15000ft) and even quite low in straight flight or a shallow to steep dive. Up to now, Ive found nothing to increase my chances of a lock. Using the aww-13 pod for me mostly dont work, since Im aquiring the lock (if so) so late, that I dont have the time to push the right buttons..... Anyone got suggestions, what I could do to improve my results?? Thx.

I checked the fps in that mission again and found some situations, where I have also drops into the twenties. I dont think upgrading to a I7-9700K would change too much for you. I also thought about this (when I read a GamersNexus report about the poor 0,1 percentile of the I5-9600K), but I think it makes no sense, since the 9700K would change very little to nothing in DCS. What little Ryzens have less in singlecore-perf will be perceivable only in rare cases and if one is able to distinguish say 27 to 30fps. Id say, this is just DCS (rupposedly only really using 2 cores) and and this mission especially. Its like a MP-mission with lots of units. I think, until ED impement real multicore-support this stituation will not change. But once this is implemented Ryzens will rule, if Intel does not bring a really new platform (not the powerhungry 14nm 10xxx-series). Or at least be like most other games really GPU-limited. Overall this testing helped me quite a bit, since I really was planning to upgrade my GPU to the best of the upcoming Navi2/RTX 3xxx series, when finally a VR headset comes along, that reaches my requirements, like maybe the Reverb G2. But as I see it now, a new RTX3080Ti would give me only good fps in missions with low CPU-requirements and in normal or MP-missions Id be stuck in the same low fps as with my current card because of the current CPU-limitation. In such a case the RTX3080TI would run at 40% usage while my current card would run at 80%. Its like a friend owning a RTX2080Ti on MP-missions often complains having very low fps and only 60-80% usage of this GPU... So to me right now upgrading to such a new GPU only would make sense if CPU-multicore-support is finally implemented. The only scenario where such an upgrade would make sense now is, if your primarily are playing SP in moderatly demanding missions. But again thinking of the upcoming Supercarrier, I dont see less strain on the CPU coming along. But coming back to the situation at hand, I think this specific mission is an extreme example and most other missions are much less demanding on the CPU.

Hi. Did some testing now. That mission seems to be very CPU-bottlenecked with lots of units in it. When I did some testing with the Reverb (that I sold two days ago), I had in that mission quite a few heavy stutters and CPU-frametimes where very high around 20ms with spikes up to 60ms. Eg in the Caucasus-Hornet-freeflight-AI-mission I had about 10ms CPU-frametimes. On monitor I dont have stutters but fps get below 60fps, like 55-60 with rare dips down to 47. I have set 60 as max-framerate in the Nividia-controlpanel to reduce TrackIR-stutters. My monitor has 1440p. I did then a short test: Right after starting the metioned mission und hooking up to the catapult, I turn to the island, let the system settle for a few seconds and then look at the fps/frametimes. I did this with default CPU-clock (which is 4,3/4,4/4,5/4,6 for 6/4/2/1 cores active and with an OC of 5 Ghz on all cores. Looking at the default clockspeed, it seems DCS is taking usually 4 cores, sometimes only 2 (when I have 4,5Ghz). See the pics. Comparing those two settings for the default setting I get 47-54fps and for the OC 50-57fps. So doing simpel math, the OC offer 6% more fps. Anyway, my conclusion is, that this scenario (which could resemble a MP-misson) is CPU-bottlenecked and a RTX2080Ti in my case would do NOTHING. So my earlier opinion, that DCS is GPU-bottlenecked is wrong. This is only valid for simple missions I guess. I have also played the mission now and had also dips down to 35fps. Usually I dont have such low fps (had even 100+ higher up without the 60fps-limit) and I guess this is due to the misson. In mission with lesser units I guess, youll be fine.

You forgot to write naked "airfilled Minecraft"-Supermodel, that in 2.5.6 is brakedancing all the time! With an 1060 Id stay away from VR; even my 2070Super did not give me satifying results. Just sold my Reverb today since VR dont seem to reach my visual expectations. But of course, if you have both, try both and find out, what you like.

No sure about this (since I didnt do extensive testing) but I have a feeling about this. In some (heavy missions) I have a lot of red spikes in fpsVR (frametime>22ms) in the CPU-frametines, sometines even blanks (no rendered frames) for a moment. In such missions I have also judders, some even very bad. In other missions like Hornet-Caucasus-Freeflight-mission I habe CPU-frametimes constantly around 10ms and no judders. I think (at least my) judders are CPU-related. Overclocking did not help. Right now Im using Steam-motionreprojection. Maybe Motionreprojection takes up quite a bit of CPU-perf and therefore causes the judders. But as I said. This is just a feeling and I need to do more tests.

I dont get it. Seems, I have to change my opinion about the hardware-limits of DCS. Up to now I always said, DCS is GPU bound. Did a lot of tests with the Rift S and GPU-times were with my settings always 20-25ms, while CPU-times were about 15ms. Same for monitor/TrackIR. So clearly a GPU-bottleneck. With the Reverb it seems, it needs more CPU-power, since now CPU frametimes seem to be generally a bit higher than with the Rift S. On some mission (eg single-player misson: Hornet-1989-CAS) CPU-times usually are higher like 20-30ms and often, but very briefly jumps to very high values like 60ms. With the latest stable I had also many red spikes, but considerably less then in OB. And on the monitor/TrackIR I had constant 80-90fps (have no frametimes here), with some rare dips down to 50. Generally regarding the Reverb after some 10 hrs on it Im actually rather pleased. Almost no SDE and great resolution in the middle of the image. But as with most VR-sets it a PITA to set them up and lots of time go into tweaking instead of doing proper flying, but generally the Reverb is better, than I expected it. There are some things, that could be better, like the small sweet spot or soft image everywhere except in the middle, the very slight, but noticable mura and the slight distrotion in the middle of the image. And off course the stiff cable and the pronounced cromatic abberation are still annoying. Those were also the reasons last year, that I sent the Reverb back within two days, but I now found a quite ok solution for the cable and to the cromatic abberation one gets used to quite fast. Still right now Im not certain, but I will more likely sell it (after Im done with Half-Life) again than keep it. I kind of re-converted to monitor/trackIR on moth ago and only bought the Reverb since if was a good offer and I had the feeling, that my initial testing last year did not do it justice, which actually is true. But if the next gen of headsets gets a mixture of the best parts of the current generation (like cable and sweetspot, uniformity of picture and single programm of the Rift S, resolution and unnoticable SDE of the Reverb and build quality and FOV of the Index, all with decent peformance) Im for sure, sold for VR. But until then, Im as happy with my TrackIR-monitor setup. Regarding my posts from above: the jerky loading-screens are annoying, but that would be just a minor discomfort, since I usually close my eyes during loading. Also the strain on my eyes - yet still noticable - has got less. I for sure had the Reverb for 5+hrs on today and my eyes dont feel too tired.

Sold

Anyone got a solution for this? Is this standard? With the Rift S I did not have this. And with a Index the loadingscreen only sometimes merged with the SteamVR-horizon. But no flickering and wildly jumpy screen.

Today I unplugged my hub (where my T-rudders and the TM Wh and also TrackIR are connected to) and after that had to change the controlsettings of the T-rudders again. Already had this once before (after I installed the profile for toebrakes, that I actually never got to work) When I opend the controller-settings in DCS there were again 4 entries for the T-rudders and I had to delete them all again and set the rudders right again. Anyone know, how I can set this in the DevConfig, that I only get offered one axis (the rudder axis)???

I now got my second Reverb; just got a good chance and thought, 2hrs of testing the first time, did not do the headset justice. What I found now is, that cromatic abberation is still as bad as it was last October. But overall it was better than expected. The aliasing isnt as pronounced as on the Rift S or the Index and almost ok for me. What I dont like about the small sweetspot is, that one usually looks at the lower part of the image (to check the instruments etc), which is not bad, but still a bit more blurry as the middle part. Moving down the head everytime for me is tirering... Loading screens usually jump all over the place and do flicker very bad, so I usually have to close my eyes. Is there someting I can do to make this better?? The head set overall feels quite comfortable and since I fixed the cable to the halo on the backside of the headstrap, its stiffness isnt a big problem any more. Performance seems quite acceptable; I even dare say, that its better than with the Index. With settings for acceptable fps on my system the image qualitiy of the Index was worse, than the settings on the Reverb I found today. But this clealy needs some more testing. After using it for a few hours today my eyes felt rather tired/strained. I need to look at this closer, since the Index and the Rift S did not do this. Overall, I need to do more flying to be able to find a conclusion for me. Right now, its kind of 60% sell again and 40% for keeping it.

Thx for the info. Since this effect on my 1440p-monitor is greatly reduced compared to the mentioned headsets, I assumed it should be also better on the Reverb. I guess, it actually is slightly reduced, but only just so slightly..... The shimmering was one (of a few) things, that I could not get over in VR, which made me go back to the monitor. Still I think I need to give the Reverb a try; just to know.

Brief question: I had the Rift S and an Index, but on both the shimmering in some parts was really terrible. For example on the carrier, looking at the island all those cables around the antennas etc caused lots of shimmer. Is the shimmer also a big problem on the Reverb or is it slighly or even much better because of the higher resolution? Thx

Not sure. I bought the A-10A way before FC3 and right after installing FC3 the A-10A-Icon was gone in the menu. But once youre used to them clicky modules its hard to go 'back' to unclicky ones. Even most jets in FC3 actually would be quite interesting.....

Hi. Im having problems, setting up my virtual toebrakes. Up to now, I didnt need them, but now Id like to use them to making taxiing with the WW2-planes at bit more "straight".... I managed to get to see Windows two more axis, when I press the set joystickbutton, but then both axis go to 100%. When I then press one pedal, this one stays at 100% and the other goes to 0%. See pic. Is this correct? But how do I set this up in DCS? I tried on the axis-page to use it with left and right toebrake, but that did not work. When setup correctly, will I only have a either 100% or 0% brake (which would be quite the same as with pressing the two buttons for toebrake) or can I make smaller adjustments too? Maybe someone can help?

Ok, thx, for that post, Was quite helpful and I think now I get it. In the Nvidia-Controlpanel, I can choose at the G (Free) -sync-compatibility settings if I want it only for full-screen or also for windowed mode. I just have checked the first one. So when I hit Alt+Enter I go from fullscreen (with Freesync) to windowed mode, which does not Support Freesync because of my settings. So after starting 2.5.6 Im in fullscreen-mode even the checkbox in the graphicssettings is unchecked. Go figure.

Ive read many times about Alt+Enter to make the game fullscreen. When I tried it, it never seemed to make a difference for me though. Now with 2.5.6 I had to disable the fullscreen-checkbox in the settings since this would often freeze the start of DCS. Now Ive tested a bit with Alt+Enter again and found something strange. I do use a 1440p-monitor with 144 Hz, that supports Freesync and Ive set my Nvidia videocard to G-sync-compatible (=> Freesync). I dont see a big difference (which may be up to TrackIR) but it seems better, than without Freesync because there is not tearing, that otherwise is only just visible in fast up-and-down head-movements in the Cockpit. Only drawback of Freesync being, that I get some slight flickering on the loading-screens and the main-menu, but not in the cockpit. Anyway, my monitor also has a frame-counter and when I enable it, one can easily see, that the fps on the monitor are the same as the ingame-fps-counter or in MSI Afterburner. So eg 87 in the ingame-counter and 87 on the monitor-Counter, constantly going up and down. But when I hit Alt+Enter, the flickering in the main-menu is gone, but the frame-counter of the montior then shows fixed 144fps and also later in the mission. Also some minor screen-tearing is perceiveable again. Hitting Alt+Enter again and Im back to the variable fps as before. Strange. Is Alt+Enter also used by the Nvidia controlpanel to turn on/off the Freesync/G-sync-compatibility?? Is Alt+Enter still needed in DCS?? It never seemed to have worked for me anyway, so I used it only for testing.

Hi. Ive got a 9600K and not a 9700K, so two cores less. I do use a Noctua NH-D15S. Yesterday I did some OCing, since I wanted to know, what the max power-draw of my system is. So I had Prime95 run with and without AVX. Additionally for some time also Furmark to stress the GPU. Since I have a AVX-Offset of 3, I did 4,7Ghz allcore with AVX and 5,0Ghz without AVX. Temps went up to a max of 86deg, but usually were aroud 80deg. With 5Ghz I ran into some problems though since one instance in Prime95 (worker) stopped working. That was with the System already warm and after 2hrs of running Prime95 with AVX. But I dont think, this would a problem with DCS, since loads are not that high by far. Also dont think, this was due to not enough cooling. My system powerdraw was with my videocard also at max powerlimit (111% => ~240W) was 430W. Normally during DCS its around 300W. After the test, reset my CPU to default-values since right now, OCing does not help in DCS, since ist GPU-limited; at least according to my tests. https://forums.eagle.ru/showpost.php?p=4193266&postcount=56

Hi. Right now Im cautiously optimistic. Disabling Fullscreen should have done it for me. Also disabling SSLR afterwards, did not cause problems during loading of DCS. Do I have to press Alt-Enter now everytime I load the game? Never have done this before and am not sure, if this is just "relict" not needed anymore.

Just wanted to add to my above post, that I now sold the Index. But in the end it was a close call since I liked it quite much. If I werent only playing DCS, I would have kept it. But the poor implementation or high hardware-demand of VR in DCS kept me from that. I cant see any situation, where I could reach the fps Mr Biggs claimes to have. But of course, my GPU is maybe 30% less performant. But a guy from our squadron also said, that he cant reach that fps with his 2080Ti. And from his statements during our MP-sessions it does seem, he quite often has low frames. Anyway, Im pretty sure, that the Index will still be good in 6 months. Maybe by then, we have a new grafics-engine and better hardware. But then of course there is always the Pimax 8K-X.......