Maggot

Ok! So, back to my original question: Is the graph behavour shown in the picture normal? Shouldn´t they be more stable? This is with basically every graphic option turned down as much as possible, or off if possible, and me sitting in a cold F18 on the supercarrier deck. No difference if looking at the sky or towards the carrier Island exept for a few more FPS at the sky... But: I also just realized that the graphs actually behave the exact same in non MT-mode (but no CPU/GPU-text so I know in on the right version). And that my CPU:s don´t seem to work very hard, see newly added picture. Maybe something´s really wrong here? null

Aha, ok, so I should not expect any gain from the MT-update? Too bad I guess. But at least then I don’t need to spend any more time trying to figure out why I don’t see any improvement…

Hi, and thanks! Please tell me if anything missing. Intel i7, 9700K Nvidia Geforce RTX 2080 Super 32 Gb Ram Win 11 VR, using Reverb G1 SSD dcs.log

Hm, my text seems to have disappeared... But, is this graph-behavour normal? The graphs fluctuating very fast and never being steady? The text abouve, showing CPU-or GPU-bound, is actually fluctuating really fast between red and yellow, it is never steady nomatter what I do. And as stated in the title, no improvement what so ever in performance.

Hello! Could you (or someone else) please give a short explanation on how this is done? Or maybe point to an explanation elsewhere?

Hello! Had the same experience the first time, with heavy nausea after a short flight of about 10 min. I could still feel it the day after. Still went on to buy my own VR-set after a couple of months. Difficult in the beginning, a lot of really calm flying, and paused as soon as I started to feel anything. It passed in a couple of weeks. Now I have no issues at all!

So, I lowered the refresh rate fr 90 to 60 on my reverb G1. I find it introduces some discrete periferal flickering, which is irritating at first but I find you get used to it. And I definitely prefer that flickering instead of stuttering. And there’s suddenly a lot of head room to turn things up:) Raised SS in Steam VR from 100-140, turned on shadows (low settings though). I can even fly a furball instant action mission over the cities in on the channels map with almost zero stutters. Looks great! On this map the details level slider has a huge impact, and its possible to tune while in a mission to se exactly what happens. So - this will be my solution until 2.7 runs better.

So, Definitely worse performance for me in 2.7. FPs-wise maybe 10-15 less. But there’s a whole lot of stutter that doesn’t seem to be reflected in FPS-loss. With reprojection it mostly stays above 45 (jitters alot between 43-55-ish) but still lots of stutters... when looking up it locks att 45 as expected. But in 2.6 it locks at 90. So a clear difference. Sorry for my ignorance, but is it possible to have acceptable FPS but lots of stutters? Reverb G1 I7 9700 5,0 32 gb ram Rtx 2080 Super SSD Don’t think my settings are ’too high’...

I dont think it works properly. I had the same issue, only difference I AAR:ed first and then quit... Plan to play mission 3 as single mission instead from the campaign folder, where you can choose the one that starts after the first AAR, and then continue with the actual campaign at mission 4.

As already mentioned it’s perfect for safe/unsafe or master arm on/off.

Ok, will try as soon as possible, thanks for the advice!

I have removed the extention from the base when I opened up the gimbal to look for loose wires (found none) if that’s what you mean? But I haven’t removed the grip from the extention.

Hello! I have a Gunfighter mk2 (rev B) with MCG pro, and extension. About 3 years old now. Last year I had issues with the axes going out of calibration with movement of the stick. This was fixed by replacing a cable in the base, where the wire kept coming loose from the connector when the stick was moved... Lately another issue has appeard, which is that movement of the stick causes presses of different buttons, mostly 9, 18 and 23. My guess would be that this also is caused by the cables moving inside the base with stick movement. I did find an older forum post with the same issue (actually the exact same buttons) where the issue seemed to be cable related. So my question would be - do you think this is the case, and would an electronics upgrade to mk3 solve the problem? If not... suggestions?

Isn’t there an option if you contact ground crew? Like ”ask for launch” or something...? Not at the computer at the moment, and don’t remember exactly...

If you have space to keep the base game, it’s easy just to move the maps to another disk, using the windows command ”mklink /j”. The maps are what takes up most of the space. That’s how I do it at least.