NSAdonis85

I said I did: I run on mostly minimum to medium graphics settings. Your issues wouldn't be the same anyway. This is something specific to the Mirage F1 since it's the only module doing it, I have at the peak worst 25fps otherwise save for MP situations, pick any module out of the list in my signature they all perform the same way. Since I tried reinstalling the module completely and it didn't help. And Aerges seem to not care to even reply here which I find...interesting. Here's the log, and lets see what becomes of this. dcs.log

I'm getting it too.

I have to add to this: in certain cases it also can half the fuel load. Say, put CBU-97's on wings first then GBU-10's on inner CFT stations. If I was to add the 4x GBU-12 per side, then the situation happens that Mobius described. Attached mission file as an example of the fuel set to 50% on load but saved in ME as 100% thing. DayNav_Syria.miz

I have this problem only on the Syria map, and only with the Mirage F1 (both CE and EE) out of all modules I own gives a low fps (8-10) with visible texture bluring around mostly on the trees, as soon as I hit Esc FPS goes back to normal, if I hit esc again to hide the menu continues with the low FPS. doesn't matter which mission I load in, it always happens, and only with this module/terrain combo. Tried deleteing shadercache. Let me know what is needed to troubleshoot this.

So, repeatable front seat crash, happens every time I do a TDC press with A2G radar. Couldn't do DXDiag report, DCS just closes itself before I can hit the button. I have CPU cores for radar use set to 2. dcs.log

Happened to me

On opening it gives error: Shader "/shaders/heightmapFrameBufferCleaner.fx" failed to compile. Reason: warning X4717: Effects deprecated for D3DCompiler_47 G:\shaders\heightmapFrameBufferCleaner.fx(26, 34-57): error X3004: unclassified identifier 'invalidSurfaceDetailHint'. Happens after folder deletes in SavedGames, AppData\Local and with or without admin mode. model_viewer2.log

I tried entering the Razbam Discord today, but each time I got an "Unable to Invite" message.

My addition to this would be to make it period and type specific too across the board instead of only forcing one all over.

...and why does this need a workaround to begin with instead of being fixed ages ago...

It would be beneficial in the long run to have the F10 map have a button which would change the bearings to show in 1 or 2 decimal places (so far Mi-8's DISS computer would instantly benefit from this as far as I am aware of the modules capabilities). Second thing is to have magnetic declinations, runway threshold and midpoint lat/longs shown as it is on real ones and true and mag headings shown in one decimal point.