Bucic

Is this in line with your experience?

Please post a bug report with a mod less track if you can. I won't be able to update for another week. The sooner it gets reported, the better. Also please take a look at

Call Heatblur...

Cockpit shaking, LERX, wing tip vibrations... Continued 'aliving' of the F-5E experience. Merry Christmas, ED Team!

"The fans are thirsty. Either we go or you go!"

Just a word of advice. Even if the problems like those have been acknowledged but change somewhat with time it's worth noting that in the respective issue forum topics, with a fresh modless track and maybe even a fresh dxdiag report.

I don't think it's more serious than this https://forum.dcs.world/topic/366205-performance-trees-huge-performance-hit-especially-up-close/

Got the culprit yellow background but I still don't know where is the content (laser codes etc.) programmed with that huge red/blue font.

I've got a confirmation the bug has been confirmed for the current build/Remaster so I guess we just sit and wait now. I highly recommend the new Caucasus Free Flight instant action mission which lets you fly at 2 in the night, pitch dark with some stars. On that note, I'm going to check how such conditions look with and without my bloom mod.

So that would confirm the bug. I managed myself to trigger it even with LOD 0.3. Like I said before, as soon as "non-minimal" LOD is in view, the performance dives dramatically, with sawtooth frametimes. It's worth realising that as soon as you hit sawtooth frametime on a graph, FPS don't matter anymore. That characteristic is indicative of a serious performance problem where a game engine will not and cannot deliver any satisfactory end user experience as it turns itself into a heat virus, akin to Prime95 "benchmark".

Yeah, I cranked gamma up in my recent night flight video and I can see that as well. They just turn of the bulbs. BTW, what are those two blinding lights behind each pilot's ear? They seem to turn on and off by nav light knob as well.

Just checked it on my end. I was wrong. This IS how F-5E SAS works, at least in the sim The main purpose of simple implementations of such systems is to quickly dampen yaw oscillations. Apparently does that plus has an anticipateur implemented. BTW, here's how it looks when it's trully needed but turned off (both channels)

I got a little bit lost here. Could you guys tell me what's wrong with the current logic? In my yesterday flight putting either the Landing Light "T" switch to OFF (OR) turning the Nav Lights knob to OFF caused the lights to retract. Or was it so dark they simply went off...?

Good point. Weird behaviour then. Is there another arcade setting? Simulation/game?

Featuring getting lost at night and night time double engine flameout landing. No F10, no preparation either

Looks like the Rudder Assist cheat got enabled somehow. This is not how Yaw SAS works.

Could you please set LOD ~0.7 or whatever and look at the frametime metric graph while getting very close to the trees?

Edit: I already tried placing a renamed model (coming from the mod by fercho) into: SavedGames\DCS.openbeta\Mods\c-17a.edm SavedGames\DCS.openbeta\Mods\Shapes\c-17a.edm SavedGames\DCS.openbeta\Mods\Aircraft\c-17a.edm No luck.

Hi! Could anyone plese help me out with gathering and installing a pack of AI mods so that I never see the ugly external models while playing Free Flight and training missions? C-130 seems to be the number one candidate So far I have only found C17-Globemaster III by fercho 1-1 v.2.8 — https://www.digitalcombatsimulator.com/en/files/3335664/ but even with that I don't know how to install it. By installing it I mean simply replacing the external model AI uses. Nothing more, not even the damage assets etc.

I had them set to Normal since I bought the RTX 2070 with no such problems. For now I'm going to just use the LOD set to minimum or even force some lower value in the graphics settings lua file.

I know. Hardly a game-breaking bug VVV Middle mouse button (scroll) click to open full-resolution versions.

The frame times turn into sawtooth even with LOD set to 0.1 and Tree Visibility Slider turned down almost to minimum. It seems that the bug is triggered MAINLY by the close proximity to trees. The only required factor is: the trees are out of the lowest LOD. That's it.

OK, I've just confirmed 100% similarity of my current vs pre-December updates configuration. That includes both in-DCS and in-nVcpl settings. To better illustrate the problem, compare the DCS performance metrics (notice the frame time sawtooth pattern!) between the scene where barely a 1 km radius is visible in the scene vs the other shots. The last screenshot I took deliberately at the exact moment the distance to the trees corresponds to start of the performance dip. https://1drv.ms/f/c/66cf2646234394fc/EkB24ygz9mBLqN6BJlpqAMoBauptRXW6rOmTCLgQXMurkg?e=CEWV8j