Amarok_73

I did actually copied this name from the other module where this directory is present. Could You put here for me package with the file(s) from this directory, so I'll be sure that they're up to date? The thread i've taken it from for my tests is quite old, so it could be the reason that these files did not worked out. And still, only the mods of Spitfire and Bf-109 (bought on current sale) shows the non-localized entries in controls.

Attach Your Export.lua file too.

I did not had this file, so according to the other thread from this subforum, I did described changes, but without any effect. It can be, that I've downloaded obsolete files from this thread. I can see, that some modules do not have the I10N subdirectory with LC_MESSAGES, so is it something special for selected modules only? For this module, the existence of these subdirs is obligatory, or it's just the way to assure, that the localisation mechanism works correctly?

@LeCuvierJust for the record, second WW2 module bought on current sale, the Spitfire, and there's the same issue. null

...two switches of locales and total repairs later... null I did also what is described in this thread, but in vain...

Yes, I am using most recent OB, but then, something came to my minds regarding the DCS Updater GUI. I remember, there's somewhere place, where locales have to be defined, that may have something to the issue. I'll check it when I'll return to home.

Hi @LeCuvier, I am not using MT as it's too buggy yet to me, so in OB ST I can see this.

Should I consider this as corrupted? If so, how to correct it? I've already tried to reinstall module...

This. Suggested is to use mod manager like OVGME or JSGME to install it, as after the update, this file will be overwritten with the default one.

Are there chances @BIGNEWYand @NineLine, that change in the dots mechanism if will be implemented, will work similarly to the labels, so they'll be dependent of the file embedded, in the mission file, so the server admin will be able to decide if these parameters have to be forced, and with what values?

I don't think it was confirmed as resolved yet.

Here's my registry that I am trying to use now with MT: null Tested with VSYNC enabled, and received CTD after few minutes of flight...

This started with the patch from March 17 (don't remember the version number).

Flappie may have such information, as he was actively supporting other thread about the black rectangles issue, which seems to hit mostly 5700XT owners...

I did it already, and still CTD happens. However, I've not enabled yet VSYNC and now thinking, that maybe forcing the slow down of graphics generation with this parameter may have some positive effect...

Everything is in my footer AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS

I keep all drivers and system updated, no overclocking at all, tried some underclocking as @Flappiesuggested, but CTDs still happens.

Can it be installed as server mod? If so, where should it be placed?

@Flappie I tried different approaches according to the suggested lecture, all the time having the CTD related to the "DX device removed. Reason: 0x887A0006", then finally got back to the "computeOptimalBarriers" What makes me wonder, regarding the DX device removed crash is, that this one is usually preceded with large number of these errors from the screenshot. Anyway, I sent all the errors immediately after crash, but attaching them here for the record. dcs.log-20230414-060542.zip dcs.log-20230414-062052.zip dcs.log-20230414-074518.zip dcs.log-20230414-063148.zip

I fly this machine a lot, like every day, few hours, and still I can't get used to it having in minds that there was already pretty good implementation of stabilisation. I remember that at that time, the only significant issue with the FM was, that in the stable straight flight, the helicopter could turn suddenly in strange directions, just as when hovering it could suddenly (with a stronger gust of wind) twist and lose stability.platform. And the patch that repaired above, the same moment destroyed the attitude and alitude stabilisation in hover and straight flight.

As I am flying with FFB joystick, for me, answer on both questions is positive.

Well, another CTD, not directly coming from computeOptimalBarriers, but looking into the crash log, seems to be related. I've sent it already with the crash dialog, but just for information, here's the crash log package: dcs.log-20230413-221712.zip

No, there's at least two of us with common feelings. There was a time, like somewhere around last Christmas (before rather than after), when it was totally possible to get into stable, hands free hover on stabilizers and fly stable forward with stabilization enabled on both, altitude and attitude. Then next patch ruined it. Now, whatever settings I'd try, I can't get into hover so stable, so I could try to leave the joystick to click anything with mouse. I've tried different approaches, the curves, different special options, to purge totally the module and install it from scratch, all in vain.

Here's today's report.dcs.log-20230413-193322.zip EDIT: I've noticed, that directory metashaders2 contains quite old files, so I've deleted this directory and fxo, then gave a try, and so far, there was no CTD.