Limaro

have nothing setted up to something special. Driver is Adrenalin 22.10.2

Yes, the same. thanks for linking

I've made some more tests and also compared some modules and many maps, but the results show all the same. Only Channel and Nevada are less affected. All Runs were about 80seconds long. Full data attached, here a overview of average data: Caucasus 2.7.18: 106.7 FPS Caucasus 2.8.00: 90.0 FPS -15.6% Marianas 2.7.18: 74.7 FPS Marianas 2.8.00: 64.6 FPS -13.5% Nevada: 2.7.18: 103.1 FPS Nevata: 2.8.00: 96.7 FPS -6,2% Persian Golf: 2.7.18: 108.8 FPS Persian Golf: 2.8.00: 91.5 FPS -16.2% Channel: 2.7.18: 91.4 FPS Channel: 2.8.00: 83.6 FPS -8,5% As a side-node: I believe this is the same thing as discussed in here: And It feels like the same flat-rate performance loss we had last year. I just hope, that we must not wait three patches again. @Flappie I count on you again to reproduce this and forwarding it to the dev-Team Benchmark.txt Performance_Fly_7_Caucasus.trk Performance_Fly_7_Channel.trk Performance_Fly_7_Marianas.trk Performance_Fly_7_Nevada.trk Performance_Fly_7_PersGolf.trk

Hello, I have this strange crashes again since 2.8. Before I see the desktop, it looks like all elements of the map start flickering once. and after two runs, crash to Desktop. attached the logfile. dcs.log

Hi, I want to report a general decrease of framerate by about 13%. This might be to the new cloud and lighting effects, however I think It might be useful to let you know this. Since the 2.7.6 to 2.7.7 - Performance-Loss Bug I have a small replay I regularly check before updates. These are now the differences: 2.7.18 27-10-2022, 16:05:09 DCS.exe benchmark completed, 8549 frames rendered in 101.203 s Average framerate : 84.4 FPS Minimum framerate : 56.9 FPS Maximum framerate : 109.9 FPS 1% low framerate : 58.7 FPS 0.1% low framerate : 33.7 FPS 2.8.0 30-10-2022, 20:50:31 DCS.exe benchmark completed, 7452 frames rendered in 101.015 s Average framerate : 73.7 FPS Minimum framerate : 51.4 FPS Maximum framerate : 92.6 FPS 1% low framerate : 52.8 FPS 0.1% low framerate : 47.7 FPS My PC in short: Ryzen 7 3700X, AMD 6900XT (Adrenalin 22.10.2), 64GB RAM, Windows 10 21H2 Unfortunately, I can only share a actual 2.8 log file (attached). Currently I try to make space on my drive, to update the stable and -counterverify the original numbers. I will post the log for this later. What I've done so far: - Delete fxo - Delete metashader2 - Removed Scripts-Folder As soon as the stable is ready I'll try diffent settings to compare the impacts. But meanwhile, if someone has valuable suggestions, I am open for tipps. EDIT: I finally could find some place for the stable and installed it. I've created two more flight, one in very bad weather, the other without. Also changed the modules. But the results are very compareable. 30-10-2022, 22:11:55 DCS.exe benchmark completed, 5598 frames rendered in 74.672 s 2.7.18 Beirut_4_2 Average framerate : 74.9 FPS Minimum framerate : 56.6 FPS Maximum framerate : 99.8 FPS 1% low framerate : 56.6 FPS 0.1% low framerate : 55.1 FPS 30-10-2022, 22:15:30 DCS.exe benchmark completed, 6445 frames rendered in 63.859 s 2.7.18 Beirut_4_3 Average framerate : 100.9 FPS Minimum framerate : 72.7 FPS Maximum framerate : 137.7 FPS 1% low framerate : 72.4 FPS 0.1% low framerate : 70.8 FPS 30-10-2022, 22:19:27 DCS.exe benchmark completed, 4906 frames rendered in 74.469 s 2.8.0 Beirut_4_2 Average framerate : 65.8 FPS Minimum framerate : 52.2 FPS Maximum framerate : 87.3 FPS 1% low framerate : 51.6 FPS 0.1% low framerate : 47.5 FPS 30-10-2022, 22:21:04 DCS.exe benchmark completed, 5590 frames rendered in 63.438 s 2.8.0 Beirut_4_3 Average framerate : 88.1 FPS Minimum framerate : 60.8 FPS Maximum framerate : 115.7 FPS 1% low framerate : 60.1 FPS 0.1% low framerate : 58.6 FPS EDIT2: Updated Title EDIT3: Corrected GPU Number dcs.log Performance_Fly_4_1_Beirut.trk Performance_Fly_4_2_Beirut.trk Performance_Fly_4_3_Beirut.trk dcs_2.7.18.log

Yes many different without success

Not in use either.

With Nvidia, it did not matter. There, I had them in both bound. Also i checkt, and the use hotkey were NOT bound to anything (active) in dcs. I checkt my module, Gui layer und some other rando Elements.

My point is, that the combox work everywhere, but in DCS.

All not working. Alt + T, Ctrl + Alt + W, Alt + Z (this worked with my nVidia previously) I also tried some other simpler once.

Hi, does anyone has the same issue? Any hotkey of the AMD Adrenalin driver is not working, as soon as DCS is focused. When switching to another application (alt+Tab) then I can perform them. Latest driver installed, 22.10.1, but it was always like this. and it's indemendet of the fact of the combination exists or not. Anyone an idea? Regards

I am not an VR expert, but AFAIK from guys of my squadron, they now run VR using OpenXR instead of Steam (since 2.7)

Hi, as the title sais. After using GBU-38, the gun starts aiming high. see attached track file, its a 2 minute file. F18_Gun_Too_High.trk

Hello, Currently it's very hard to distinguish the terrain. There has to be a better shading, like the terrain in google maps (screenshot compare). I'D hope /think that from the 3d data of the map, this should not be too hard to generate. The "map" mode currently looks very nice though, but only usable in a small scale.

Hello ED, My whish for the Mission editor came up with the problem, that it's hard to predict, whether units can "see" earch other or not. This is one one side for Air units seeing the ground, but also the ground units, seeing each other. This makes a lot of planning a bit painful, as predictions if units will fire or not are hard to be made. This problem is enforced by the fact, that the available maps don't visualize the shading for the terrain very good (this will be a point for my next wish!) So, how do I think this visualization could look like in the attached screen<profanity> (sorry for my Paint-"Skills"). What you see there is a artillery unit, and all the areas that are "reachable". Espacially, when trees or buildings are in their way, this could be very easily identified. nullnullThe same thing can be very interesting for air units, for placing SAMs, AAA or just targets. Regards Limaro

When you have less than 27" display and 4k this might be correct. But not in general. This thread reminds me of the wish to get a general benchmarking tool for DCS... this is just missing. And it would be such a great thing to fine tune settings for everyone. And with a light upload of system data and results, ED could quickly figure out bottlenecks and also performance bugs.

Have you deleted content of C:\Users\<user>\Saved Games\DCS.openbeta\metashaders2 and C:\Users\<user>\Saved Games\DCS.openbeta\fxo? Also try to run without scripts (rename C:\Users\<user>\Saved Games\DCS.openbeta\Scripts, and name it back later)

Interesting to see this discrepancy between usage. But my question to you now is: What is your actual point. - Is it that the values shown in DCS are "not well" calculated" - or that ED shall reduce the over all cpu usage? Personally, I could imagine, that DCS calculates only the net usage of CPU, not the gross including the actual cpu consumption of e.g. third party libraries and scripts. I'd consider scripts as the most propable cause of your experiance. I often struggeled of CPU performance drops, resolved by fixing/updating or removing scripts (C:\Users\<user>\Saved Games\DCS.openbeta\Scripts)

Hello Whishlist , I'd wish the colors to be having less color cast in general (I hope it's correctly been translated from google, in german: "Farbstich"). Meaning, that there is way to much over all blue, independet from distance, colored over the whole screen. Of course, for distant objects on ground, it makes perfectly sense, but espacially for near clouds, where you have less dust or humidity, it looks to intense. Also, it reduces the contrast too much for the clouds. To make the thing more clear, of what I mean, I just edited two screenshots in Photoshop. Flying in real life is not my every day business (sadly) - maybe I am wrong and it looks more often like the original image. So feel free to correct me if this is the case.

Oh, I am sorry, I missed the part with the menu being also slow. In that case, it makes it much harder to find. Still, did you have this wil older versions? Can you verify, that your CPU is running at full performance in this situation? (Can it be overheated)? Does this drop also affect other applications (You meant, you have to restart, so what happens if you dont restart and start another game)?

I would guess the CPU as bottleneck. And such large servers also leads on drops on my PC, even though not so hard as you have. What are you system Specs? (CPU, GPU, Memory) Since when does that happen? Was there a special version? Also maybe 4YA changed somethin in their missions. Somehing like wake turbulence. Can you run logs of CPU/GPU usage - once in SP once in MP. This may show what component might be responsible. As first approach, you can open the Performance monitor from windows, and while being in the game show what they show (the graphs). Do you use Steam for VR? Maybe try alternative OpenXR

Sounds fir me like a delay of Hardware to get back to work. Make sure that CPU energy management is set to full power in Windows. Also it could help to have a cpu and gpu workliad graph during this action and fps loss.

TOO1 and TOO2 are possibilities to store coordinates for the station. However, the one which is selected will be applied for both bombs. when you want to have differnt, after dropping first, switch to other TOO before dropping other. Yeas this thread could be closed. I can't marke anything as solution. However last Hint: TOO now behaves again like very long time ago. You have again to depress to apply the coordinates on station. It does not automatically slave to new positions of FLIR. This is actuall much better and I guess also realistic. Thanks again ED.

Coming with 2.7.11 I've heared a lot of issues in VR , combined with Steam. I was told that OpenXR would not cause that problem (Guide:

When having a lot to setup, and multiple controllers, it's a painful scrolling, checking, testing (when they ar enot well named). In order to make the controller configuration more comfortable, it would be great to have one column with which you can work to manage setting up new inputs. Just by automatic recognition of what controller made the input. Anyhow, this is actually the way most games I knew do it. Having one column, in which then the button assignments are listed with corresponding controllers. But for the current purpose it would already be great to have that auto column. Or, secondary Idea: When chosing the wrong controller, pressing a button, DCS could see that and offer a "Ok, then assign this button from the other controll".