I install CDK under File G:\STEAM\steamapps\common\War Thunder. But when I started it up, it reported the following bug to me.
failed to load texStreamingFile=settings.blk
Call stack (16 frames, imgbase: 7FF6A6F10000, reloc delta +0):
7FFEA49F9074 daKernel-dev! stackhlp_fill_stack +132/169
prog\engine\osApiWrappers\stackhlpFill.cpp(432) +0
7FFEA482AFDA daKernel-dev! _core_set_fatal_ctx +122/213
prog\engine\kernel\fatalerr.cpp(38) +0
7FFEA482A6D5 daKernel-dev! _core_fatal_fmt +21/47
prog\engine\kernel\fatalerr.cpp(419) +0
7FF6A71AB4D0 assetViewer2-dev! load_tex_streaming_settings
+992/1345
prog\tools\sharedInclude\libTools\util\setupTexStreaming.h(37) +0
7FF6A71A4E74 assetViewer2-dev! init3d +1076/2402
prog\tools\AssetViewer\av_appwnd.cpp(2043) +0
7FF6A71A6295 assetViewer2-dev! AssetViewerApp::loadProject
+1061/21115
prog\tools\AssetViewer\av_appwnd.cpp(2170) +0
The “failed to load texStreamingFile=settings.blk” error usually points to a CDK/game-version mismatch or an incomplete directory layout, not to the model project itself. Installing into the game folder is correct only if the CDK build matches the current client and its files are not placed inside an extra nested directory.
I would first update War Thunder completely, remove only the separate CDK installation, then install the current CDK directly into the same War Thunder root and verify that AssetViewer is using that root. Do not copy files from an older CDK over the new installation. This thread reports the same signature and may help consolidate the diagnosis: [CDK] Fatal Error: failed to load texStreamingFile=settings.blk after Heavy Cavalry update
If it still fails, post the CDK version, game version and the top-level folder layout; the first fatal-error block is sufficient.