Revert to 2.5.4.30386 solved map initialization crash

and **another** crashes (most sent via automated crash reporter, most well before 32533 promoted to stable), 2.5.5 series is really a curse to me.

2.5.5.32533 and 2.5.5.32299 reached a state: only Nevada map was initializeable in freshly repaired an cleaned state with empty saved games and temp folder (so without mods),

Caucasus and Persia crashed every time even straight after start with Mission Editor/New Mission

((1.5.8 also running fine))

Attachment created with config/autoexec.cfg line "log.set_output("dcs", "", log.ALL, log.FULL)"

Goodbye to fly with buddies in OpenBeta servers.

Why I said: it is a curse?

I have 78 succesfully (many lost due OS modal window, system32\WerFault.exe) created crash files from 2.5.5 series since 22 of june:

dcs.log-20190622-121632.zip

dcs.log-20190622-121808.zip

dcs.log-20190622-122917.zip

dcs.log-20190622-123256.zip

dcs.log-20190622-123750.zip

dcs.log-20190622-124650.zip

dcs.log-20190622-125751.zip

dcs.log-20190622-131019.zip

dcs.log-20190622-133629.zip

dcs.log-20190622-135136.zip

dcs.log-20190622-140911.zip

dcs.log-20190622-141209.zip

dcs.log-20190622-141538.zip

dcs.log-20190622-141855.zip

dcs.log-20190622-142522.zip

dcs.log-20190622-143228.zip

dcs.log-20190622-143855.zip

dcs.log-20190622-151103.zip

dcs.log-20190622-160931.zip

dcs.log-20190622-165956.zip

dcs.log-20190622-171346.zip

dcs.log-20190622-172006windowsInterceptAfterNoToDxdiag-zoom.zip

dcs.log-20190622-173338wp1p60.zip

dcs.log-20190622-173815pleasewait.zip

dcs.log-20190622-174211notriggers.zip

dcs.log-20190622-182456.zip

dcs.log-20190622-184128.zip

dcs.log-20190622-185516.zip

dcs.log-20190622-202512.zip

dcs.log-20190622-223511.zip

dcs.log-20190624-175501.zip

dcs.log-20190624-180846_f4_secondTime_mp.zip

dcs.log-20190624-181230.zip

dcs.log-20190624-182122newlyCreatedMission.zip

dcs.log-20190624-183015prepareMission.zip

dcs.log-20190624-185813.zip

dcs.log-20190624-190256.zip

dcs.log-20190624-190604.zip

dcs.log-20190624-194027.zip

dcs.log-20190624-194957.zip

dcs.log-20190624-200755.zip

dcs.log-20190624-201431.zip

dcs.log-20190624-201609.zip

dcs.log-20190624-201942.zip

dcs.log-20190624-203245.zip

dcs.log-20190624-205441.zip

dcs.log-20190624-212715.zip

dcs.log-20190626-143343.zip

dcs.log-20190626-144952.zip

dcs.log-20190626-145009.zip

dcs.log-20190626-151336.zip

dcs.log-20190626-151746.zip

dcs.log-20190626-153911.zip

dcs.log-20190626-153913.zip

dcs.log-20190626-154852.zip

dcs.log-20190626-161745.zip

dcs.log-20190626-164518.zip

dcs.log-20190626-184953.zip

dcs.log-20190626-193238.zip

dcs.log-20190626-193514.zip

dcs.log-20190627-170817.zip

dcs.log-20190627-193157.zip

dcs.log-20190627-203641.zip

dcs.log-20190628-154935.zip

dcs.log-20190628-163053.zip

dcs.log-20190628-164032.zip

dcs.log-20190628-195121.zip

dcs.log-20190629-094353.zip

dcs.log-20190629-094629.zip

dcs.log-20190629-094921.zip

dcs.log-20190629-095319.zip

dcs.log-20190629-100317.zip

dcs.log-20190629-101151.zip

dcs.log-20190629-103027.zip

dcs.log-20190629-103955.zip

dcs.log-20190629-120040forumCaucasusInit.zip

dcs.log-20190629-121016.zip

dcs.log-20190629-121615,32299CaucInit.zip

The DCS SSD going for warranty replacement.........

When a freshly repaired DCS install crash often try to make a copy of the full installation to make sure all files are readable. Make sure not happening I/O error on [game crash/test copy] time on Windows System log. (source: disk; level: warning)