Heroman30

It does seem that the only fix for this is to completely stop using the F10 map in VR or upgrade to a GPU with at least 24GB VRAM.

I’m still having this issue as well. It appears that the whole map and its assists are being loaded in the F10 view, which floods your GPU’s VRAM. I would appreciate it if anyone has a workaround or if someone from ED could comment on this issue as it really is a game breaking bug for those of us In VR.

Since the latest updated (2.9.6), this issue still persists. One user has suggested using Alt Tab to restore the video memory, but this does not fix the issue for me. Is it possible to get an official update on this game breaking bug yet?

I'm having a similar issue. My FPS is fine when during the flight but as soon as I check the f10 map (which is essential on a MP server), my FPS becomes really unstable, and my quest 3 headset becomes laggy in my right eye. Its like as if my headset or graphics card cant sustain going in and out of the F10 map view. Could it be a VRAM issue as I only have a 10GB card? I have set my textures to medium to help reduce VRAM load.

I have the same issue, and it happens when I press the F10 map on a busy server. I think it may be VRAM related as my graphics card is only 10GB, and the F10 map loads all assets in. Have you found a solution other than restarting DCS?

Hi Guys, Bit of a strange one however, I have set up my CM3 throttle and I have created a deadzone (21) so that I am getting true idle when the throttle is all the way back to the first detent (I am using the classic detents). I have noticed though that when taxying, small CM3 throttle inputs from idle match the the movement of the thrust levers in the sim which is great. The issue occurs when I get airborne and the throttle movement out of idle does not match the actual CM3 throttle movement. It's almost as if the deadzone is causing a slight delay when out of idle, and more travel is needed for it to move the thrust levers in DCS. It's only a small band of travel but it is noticeable. Does anyone have any ideas? Thanks.

Hi Guys, Bit of a strange one however, I have set up my CM3 throttle and I have created a deadzone (21) so that I am getting true idle when the throttle is all the way back to the first detent (I am using the classic detents). I have noticed though that when taxying, small CM3 throttle inputs from idle match the the movement of the thrust levers in the sim which is great. The issue occurs when I get airborne and the throttle movement out of idle does not match the actual CM3 throttle movement. It's almost as if the deadzone is causing a slight delay when out of idle, and more travel is needed for it to move the thrust levers in DCS. It's only a small band of travel but it is noticeable. Does anyone have any ideas? Cheers.

Hello, I have received my CM3 throttle and I am in the process of configuring and setting it all up. I have researched and found that the Z axis on the right hand throttle grip is the best for the zoom feature. I am however, running into issues when assigning the Z axis with the zoom function in DCS. The main concern is that the Z axis has a centre detent, and when the slider is placed in the centre detent within DCS it is really zoomed in. Is there any way to set a default zoom with the correct FOV without having to move it out of this detent as it can be really sensitive and fiddly? Can someone help and show how they have assigned this axis with zoom correctly? Thanks.

So if I check this box, would it cause any potential performance issues?

It must be something significant like MT or DLSS.

@BIGNEWYwould it be possible to get an update on this? Thanks.

@BIGNEWY Would it please be possible for you to look further into this bug and look at the track file? Many thanks.

Hello, So I’m thinking about purchasing a Dell Optiplex 7040 to use as a dedicated server to play liberation missions. The server box I’m looking at will have 16GB of ram. Is this enough in order to play heavy liberation missions (just me as a client) on Syria? For context my main gaming rig is a 5800X3D, 64GB ram, RTX 3080. I think I’m experiencing rubber banding as I’m currently using a dedi on my own rig, hence the reason why I’m looking at getting another machine. Thanks!

So the workaround would be to only play this mission in single player? I would rather play this in multiplayer due to performance issues. Is there a way to play this in the multiplayer server tracks as stated above?

Hello, Please find attached the track replay file. As you can see the flight deck crew are just walking in the same position. It may be worth noting that I'm running liberation off a dedicated server on the same machine - could this be the culprit? Although I have seen this to some extent on an normal multiplayer server. Thanks. liberation_nextturn-20230208-092832.trk