Hogges

Thank you for following up! That was also something we thought about and we did try with and without sight repeater, radar and mirrors in both cockpits and unfortunately it was always the same result. It does seem like it might be linked to the video memory as this is also something we had noticed looking at the numbers. I was interested and did a quick test in the same scenario as my previous flight with a variety of modules to see what the video memory does immediately after launching the game. All on the Caucasus map with the same settings and just a few static planes placed at the airport. Here are the results: Mirage F1 BE with sight repeater and mirrors: 8.833Mb Mirage F1 BE without sight repeater and mirrors: 8.788Mb Mirage F1 CE: 7.296Mb Mig 15: 5.053Mb Mirage 2000: 6.471Mb MB339: 6.815Mb F14: 7.897Mb Viggen: 5.986Mb Hind: 8699Mb So the BE definitely has the highest usage. It makes sense to me that some older modules like the Mig 15 have way less usage but the BE does seem to use a lot of resources here and it seems logical that this might cause performance issues. I will try lowering the textures but this is certainly not something I like to do since it is not necessary for the other modules and the game generally runs perfectly fine with my settings.

Thank you for your help! Really interested to hear about other results. options.lua

Dear Aerges Team, I have been having issues with flying the F1BE specifically due to massive performance issues and after another failed attempt tonight feel compelled to try and create a bug report about it. I am on the latest open beta and play in 3440 x 1440 resolution with Vsync enabled via Nvidia to cap the frames at 60fps in line with my TrackIR. Ever since the F1BE was released I have been experiencing frame drops. Sometimes after a while, sometimes pretty much instantly but it usually gets so bad at some point that the plane sadly becomes unplayable for me. This is strange because it is the only module that I have this issue with. Everything else is running completely fine and smooth including the EE and CE. Tonight we tried to do a multiplayer flight on the Caucasus map on a private server hosted by me with one person joining. I was in the BE and my friend in the EE. At first everything was smooth but as soon as we entered the runway together my frames started dropping again. Shortly after take off I was only seeing frames between 10 and 25 frames with huge lags. This time it happened righter after changing back from the F2 outside view into the F1 cockpit view. There was a slight delay getting back into the cockpit and I could immediately notice the frames not being fine any more. Previously it has often started while looking outside to one side and would then initially only get bad on that one side. We then reloaded the mission with my friend now flying the BE and he could also notice a large decrease in frames compared to the EE, although not quite as bad as for me. We also noticed that the BE seems to use more video memory than any of our other modules. I was able to take some screenshots. You can see the difference between the BE and EE. The same is true for all other modules. I am also attaching a track hoping it might help as well. I really hope there is something that can be fixed because I would love to fly the BE and especially utilize the Multicrew aspect of it but this is sadly not possible for me at the moment. I also looked for other reports on the forum and did find a few references to resource usage but am not sure if these have been addressed yet. See these two examples: Thank you for looking into this and I am happy to provide more information if needed. server-20240116-195422.trk

@Flappie I am happy to report that all of the desync issues are completely gone in the latest open beta release. We just had a long flight testing all the functions and had no issue whatsoever. Start-up was also completely smooth. Thank you very much for reporting this and looking into it!

I can confirm this behaviour from my recent multicrew session on a server hosted on my machine. Co-pilot could not see the start-up happen at all. Going back to the briefing and slot selection and then spawning back in worked. I will try and create a track but it should be easy to replicate.

It would be absolutely fantastic to have both, 38+13 and 37+15 in their final liveries of the WTD 61 test unit as those were the last two Phantoms to ever fly in the German Airforce, bringing an end to decades of service and thus very important to fans of the German Phantoms. They were allowed to fly on a little bit longer after the official retirement due to belonging to the special test unit and the unit put on two very memorable farewell flights with 38+13 being the final German Phantom to ever fly. I was personally very lucky to be there in person for both farewell flights so having these two in DCS would be truly special for me.

Having played a few missions with a friend where I was hosting the server from my machine, we have noticed that labels seem to no longer work while playing on such a hosted server. It does not matter what setting is used for labels within the options menu and the key-bind toggles (Shift-F2 and Shift-F10) also have no effect whatsoever. Trying the exact same mission in single player works perfectly. We are on the latest open beta. Since we have been using grey dot labels previously, this is now sorely missed. I am also attaching a short track. It would be fantastic if we could get the labels back for our multiplayer sessions. I strongly assume that this is a bug as we have never had this issue previously but I might have missed a new way to set this up properly. Thank you in advance for any feedback and for taking it into account. server-20210506-215055.trk

I just spent an hour aimlessly flying around and found myself continuously laughing out loud at how good this looks. Not just the clouds but also the, to my eyes, vast difference in lighting creates a simply fantastic experience! What a time to be in this hobby. Thank you very much to the whole team for making this a reality!

I absolutely love it! Looks like a completely new game. No performance hit at all so far with clouds on "Ultra" on my end.

Just saw this now, thanks for getting back to me! Happy to hear that initial testing seems positive. Flying the UN missions in multicrew really was a much enhanced experience and I really hope that we will see co-op and multicrew enabled and supported in campaigns in the future. I am very much looking forward to seeing what you come up with!

Hey there, I have noticed recently that the right wing texture on the VVS Demonstrator livery seems to be mixed up with the normal grey wing texture. I have attached a short track showing the issue. Thanks for taking it into account! Mig21_Wing Texture.trk

Hey guys, Thanks for your input. Happy to provide my settings but I completely agree with Flappie. This seems to be a general issue with the way rendering and anti-aliasing is currently working in DCS. This is also why I picked official DCS videos to showcase this. After all, if ED themselves presently have no solution for this, we at least know that it is not our system or set up. At best, we can play around with the settings to mitigate the effects. Thus, I have arrived at the following: In the Nvidia settings I enable MFAA, Maximum Performance, LOD-Bias on "Clamp" and also V-Sync plus setting my monitor to 60HZ. The last two are more to sync everything up with TrackIR as that also runs at 60HZ or increments of 60 and I feel that this gives me the smoothest experience and am not too concerned with reaching the maximum frame rate. My system is: i9-9900K RTX 2080 Ti 32GB RAM DCS installed on an NVMe SSD For me, the above is currently my best workaround to limit the shimmering and get the best possible visuals whilst maintaining rock-steady frames. I'd like to get "Default" terrain shadows to work but find them incredibly performance hungry in the large wooden areas of the Caucasus map, which I use exclusively. Perhaps this might be a starting point for other users looking to find the best setup for reducing the shimmering effects.

Hey there, I have been flying and enjoying the Huey in Multicrew a lot recently and a friend and I have just completed the UN Campaign with it, which was good fun. I was wondering if this campaign would also work the same way? All I did for the UN missions was to set the aircraft to Client and host them in the server, which generally worked great. Would love to hear if this is possible for Argo as well. It is obviously understood that we would both have to buy the campaign. Thanks in advance!

Hi, I hope this is the right section of the forum to post this in. Playing DCS I can't help but notice the generally large amount of shimmering going on in the scenery. Mostly visible in the shadows but also quite noticeably with trees, river banks and shore areas. I find that this is especially prevalent at low level and low sun settings. I have been flying the Huey a lot recently where, naturally, you spend a lot of time down low so that might be the reason why I have noticed it even more in the past few days. I thus wanted to post this here as I would generally be interested in others' opinions on this topic but mostly because I feel that this is absolutely something that would have a great visual impact if this issue could be eliminated or at the very least mitigated by the developers. I am absolutely no expert and am more than happy to be proven wrong by someone more knowledgeable on the topic but I do feel that the current anti-aliasing methods used in DCS have something to do with this. After reading into this topic it seems that the two solutions we have are rather old technology now and have been somewhat replaced by more contemporary and also somewhat less performance hungry methods. I have seen in other games the great effect that temporal AA has on shimmering like this so perhaps with the current work going on with the DCS core this is something that could be introduced in the future? In case you don't know what I mean, I went ahead and picked examples out of official DCS videos to show it: Visible at 0:17 Visible at 4:03 Visible at 1:21 Thank you in advance for taking this into account and I am always happy to provide more information.

No problems here either.