-
Posts
17395 -
Joined
-
Last visited
-
Days Won
11
Community Answers
-
Flappie's post in Dcs multiplayer crashing during long sessions was marked as the answer
Hi. It looks like a memory issue:
2023-03-13 00:13:57.638 ALERT EDCORE (8572): Out of memory in ed_malloc for 22369828 bytes. 2023-03-13 00:13:57.638 ERROR EDCORE (9644): More out of memory in ed_malloc for 22369828 bytes. 2023-03-13 00:13:57.638 ERROR EDCORE (9644): More out of memory in SharedBuffer for 22369796 bytes. 2023-03-13 00:13:57.638 ERROR EDCORE (9644): Not enough memory to decompress: HB_F14_EXT_02.dds 2023-03-13 00:13:57.638 ERROR DX11BACKEND (9644): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_02.dds'. Reason: The parameter is incorrect. 2023-03-13 00:13:57.638 ERROR EDCORE (9644): More out of memory in ed_malloc for 22369828 bytes. 2023-03-13 00:13:57.638 ERROR EDCORE (9644): More out of memory in SharedBuffer for 22369796 bytes. 2023-03-13 00:13:57.638 ERROR EDCORE (9644): Not enough memory to decompress: HB_F14_EXT_02_Nrm.dds 2023-03-13 00:13:57.675 ERROR DX11BACKEND (9644): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_02_Nrm.dds'. Reason: The parameter is incorrect. 2023-03-13 00:13:57.675 INFO EDCORE (8572): try to write dump information 2023-03-13 00:13:57.676 ERROR EDCORE (9644): More out of memory in ed_malloc for 22369828 bytes. 2023-03-13 00:13:57.676 ERROR EDCORE (9644): More out of memory in SharedBuffer for 22369796 bytes. 2023-03-13 00:13:57.676 ERROR EDCORE (9644): Not enough memory to decompress: HB_F14_EXT_02_RoughMet.dds 2023-03-13 00:13:57.676 ERROR DX11BACKEND (9644): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_02_RoughMet.dds'. Reason: The parameter is incorrect. 2023-03-13 00:13:57.677 ERROR EDCORE (9644): More out of memory in ed_malloc for 22369828 bytes. 2023-03-13 00:13:57.677 ERROR EDCORE (9644): More out of memory in SharedBuffer for 22369796 bytes. 2023-03-13 00:13:57.677 ERROR EDCORE (9644): Not enough memory to decompress: HB_F14_EXT_03.dds 2023-03-13 00:13:57.677 ERROR DX11BACKEND (9644): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_03.dds'. Reason: The parameter is incorrect. 2023-03-13 00:13:57.677 ERROR EDCORE (9644): More out of memory in ed_malloc for 22369828 bytes. 2023-03-13 00:13:57.677 ERROR EDCORE (9644): More out of memory in SharedBuffer for 22369796 bytes. 2023-03-13 00:13:57.677 ERROR EDCORE (9644): Not enough memory to decompress: HB_F14_EXT_03_RoughMet.dds 2023-03-13 00:13:57.677 ERROR DX11BACKEND (9644): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_03_RoughMet.dds'. Reason: The parameter is incorrect. 2023-03-13 00:13:57.690 ERROR EDCORE (9644): More out of memory in ed_malloc for 22369828 bytes. 2023-03-13 00:13:57.690 ERROR EDCORE (9644): More out of memory in SharedBuffer for 22369796 bytes. 2023-03-13 00:13:57.690 ERROR EDCORE (9644): Not enough memory to decompress: HB_F14_EXT_04.dds 2023-03-13 00:13:57.690 ERROR DX11BACKEND (9644): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_04.dds'. Reason: The parameter is incorrect. 2023-03-13 00:13:57.722 INFO EDCORE (8572): # -------------- 20230313-001357 -------------- 2023-03-13 00:13:57.725 INFO EDCORE (8572): DCS/2.8.3.37556 (x86_64; MT; Windows NT 10.0.19045) 2023-03-13 00:13:57.728 INFO EDCORE (8572): D:\Eagle Dynamics\DCS World OpenBeta\bin-mt\edCore.dll 2023-03-13 00:13:57.731 INFO EDCORE (8572): # 80000003 BREAKPOINT at 00007ffbf5cb701b 00:00000000 2023-03-13 00:13:57.734 INFO EDCORE (8572): SymInit: Symbol-SearchPath: 'D:\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'Marvin' 2023-03-13 00:13:57.737 INFO EDCORE (8572): OS-Version: 10.0.19045 () 0x300-0x1 2023-03-13 00:13:57.744 INFO EDCORE (8572): 0x000000000002701b (edCore): ed::fatal_out_of_memory + 0x3B 2023-03-13 00:13:57.747 INFO EDCORE (8572): 0x0000000000022a27 (edCore): ed::SharedBuffer::create + 0x37 2023-03-13 00:13:57.750 INFO EDCORE (8572): 0x000000000004bbc8 (edCore): edvfs::FSMappedFile::tell + 0x10A8 2023-03-13 00:13:57.750 INFO EDCORE (8572): 0x000000000004b99c (edCore): edvfs::FSMappedFile::tell + 0xE7C 2023-03-13 00:13:57.750 INFO EDCORE (8572): 0x0000000000042aa3 (edCore): CoreUtils::TempFilesManager::TempFilesManager + 0x3BA3 2023-03-13 00:13:57.751 INFO EDCORE (8572): 0x00000000000074ea (renderer): render::openFirstOccurrence + 0x8A 2023-03-13 00:13:57.751 INFO EDCORE (8572): 0x0000000000062b67 (dx11backend): createRenderer + 0x4ACD7 2023-03-13 00:13:57.751 INFO EDCORE (8572): 0x000000000006604b (dx11backend): createRenderer + 0x4E1BB 2023-03-13 00:13:57.752 INFO EDCORE (8572): 0x0000000000036485 (dx11backend): createRenderer + 0x1E5F5 2023-03-13 00:13:57.752 INFO EDCORE (8572): 0x0000000000035b3b (edCore): ed::this_thread::yield + 0x31DB 2023-03-13 00:13:57.752 INFO EDCORE (8572): 0x0000000000034cc2 (edCore): ed::this_thread::yield + 0x2362 2023-03-13 00:13:57.752 INFO EDCORE (8572): 0x0000000000036603 (edCore): ed::this_thread::yield + 0x3CA3 2023-03-13 00:13:57.752 INFO EDCORE (8572): 0x0000000000031fa0 (edCore): ed::thread::_get_current_thread_id + 0xA0 2023-03-13 00:13:57.754 INFO EDCORE (8572): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92 2023-03-13 00:13:57.755 INFO EDCORE (8572): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14 2023-03-13 00:13:57.761 ERROR DX11BACKEND (18144): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_01.dds'. Reason: The request is not supported.
Try lowering your Preload Radius in DCS graphcis options.
Also ensure no other program is eating up memory while you fly.
Last but not least: ensure the drive hosting your pagegile has enough free space for it.
-
Flappie's post in datalink et target point useless was marked as the answer
Thanks for your feedback. 👍
-
Flappie's post in Any Ideas? was marked as the answer
As it is now, DCS sometimes use more than 50GB of memory, depending on graphcis settings, terrain, flown aircraft and whether it's a SP or MP session.
The pagefile size is displayed at the beginning of your log file. Add your pagefile size to your RAM: if it's lower than 50 GB, you have three choices:
Buy more RAM (better choice, but it costs money). 64GB of RAM is enough for now. Boost your pagefile size (instant gain as long as your pagefile is stored on a fast drive with enough free space). Since you have 32GB of RAM, try a 32GB pagefile. Lower your graphcis settings (preload radius, shadows quality, water quality...). -
Flappie's post in SA19 100% miss target was marked as the answer
Thank you for the video. I think the issue is within the Skynet script, because I cannot reproduce the problem when creating the same scenario without using this script (SA-19 spawns after 10 seconds).
(I setup an immortal Apache to check whether results were constant: they are, missiles don't miss)
SA-19 vs AH64.trk
-
Flappie's post in Control settings not recognizing input after mission restart was marked as the answer
Thanks for the heads up! 👍
Issue reproduced and reported.
-
Flappie's post in TF-51D flyies too long with the generator turned off. was marked as the answer
Thanks. It took one hour and a half to empty the battery.
Bug reproduced and reported. 👍
-
Flappie's post in FPS limited to 30 total was marked as the answer
Thanks for your precious feedback. 👍
Sum up here:
Bad for FPS:
--1. WinWing stuff local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') -- 2. load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[C:\Users\jmgri\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[BIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[BIOS.lua]]) end --[[DCS-BIOS Automatic Setup]] --3. TacView local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') --4. SRS pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);
Much better for FPS:
--1. load the DCS ExportScript for DAC and Ikarus (moved up) dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[C:\Users\jmgri\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[BIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[BIOS.lua]]) end --[[DCS-BIOS Automatic Setup]] --2. TacView local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') --3. WinWing stuff (moved down) local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') --4. SRS pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);
I'm pretty sure the order of TacView and SRS calls don't change anything.
-
Flappie's post in DCS MT won't launch; Authorization fails for all modules, and DX11Renderer-Error was marked as the answer
@XCNuse Try a DCS repair in slow mode.
-
Flappie's post in Can't Open Old Mission on latest OpenBeta was marked as the answer
Is the Normandy terrain installed and enabled?
-
Flappie's post in Unable To Start DCS OpenBeta After Small Update was marked as the answer
Hi. Your log says this:
2023-03-17 21:44:25.581 INFO APP (Main): Loading cached auth data... 2023-03-17 21:44:25.881 ERROR ASYNCNET (Main): Auth data is for a different DCS version. 2023-03-17 21:44:25.884 WARNING APP (Main): Login failed, offline auth is not available. 2023-03-17 21:45:27.930 INFO Dispatcher (Main): Loading installed modules... Try this:
Go to "Saved Games/DCS.../Config". Delete "authdata.bin" file. Start DCS and log in with your username and password. -
Flappie's post in Varjo Aero Crashing when entering Mission MT (sometimes main screen also) was marked as the answer
Hi. Try this:
and this:
-
Flappie's post in F-14 Adjust Controls Bug was marked as the answer
Hi, this is an Apache bug, not a Tomcat bug. It was reported in late 2022.
-
Flappie's post in Crash on startup - C0000005 ACCESS_VIOLATION - on clean install/system was marked as the answer
Hi, your issue seems to be caused by a Force Feedback device. Workaround: try unplugging your FFB device then start DCS.
2023-03-15 16:52:39.508 INFO INPUT (Main): Device [Keyboard] created. 2023-03-15 16:52:39.516 INFO INPUT (Main): Device [Flight Control Rudder {C8AEB4F0-C26D-11ed-8007-444553540000}] created. 2023-03-15 16:52:39.516 INFO INPUT (Main): Joystick created[Flight Control Rudder {C8AEB4F0-C26D-11ed-8007-444553540000}], ForceFeedBack: no 2023-03-15 16:52:39.549 INFO INPUT (Main): Device [ VKB-Sim Gunfighter Modern Combat Pro {E9024510-C26C-11ed-8001-444553540000}] created. 2023-03-15 16:52:39.549 INFO INPUT (Main): Joystick created[ VKB-Sim Gunfighter Modern Combat Pro {E9024510-C26C-11ed-8001-444553540000}], ForceFeedBack: no 2023-03-15 16:52:39.610 INFO INPUT (Main): Device [Throttle - HOTAS Warthog {FF32DA60-C26D-11ed-8008-444553540000}] created. 2023-03-15 16:52:39.610 INFO INPUT (Main): Joystick created[Throttle - HOTAS Warthog {FF32DA60-C26D-11ed-8008-444553540000}], ForceFeedBack: no 2023-03-15 16:52:39.616 INFO INPUT (Main): Device [vJoy Device {244E7400-C127-11ed-8002-444553540000}] created. 2023-03-15 16:52:39.623 INFO EDCORE (Main): try to write dump information 2023-03-15 16:52:39.675 INFO EDCORE (Main): # -------------- 20230315-165240 -------------- 2023-03-15 16:52:39.675 INFO EDCORE (Main): DCS/2.8.3.37556 (x86_64; Windows NT 10.0.22621) 2023-03-15 16:52:39.676 INFO EDCORE (Main): C:\Windows\System32\pid.dll 2023-03-15 16:52:39.676 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffae4ac3612 00:00000000 2023-03-15 16:52:39.677 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'nicol' 2023-03-15 16:52:39.677 INFO EDCORE (Main): OS-Version: 10.0.22621 () 0x100-0x1 2023-03-15 16:52:39.678 INFO EDCORE (Main): 0x0000000000003612 (pid): DllGetClassObject + 0xE22 2023-03-15 16:52:39.679 INFO EDCORE (Main): 0x00000000000049a2 (pid): DllGetClassObject + 0x21B2 2023-03-15 16:52:39.679 INFO EDCORE (Main): 0x0000000000005230 (pid): DllGetClassObject + 0x2A40 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x00000000000155de (DINPUT8): GetdfDIJoystick + 0xA52E 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x000000000001a6dc (DINPUT8): DllGetClassObject + 0x401C 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x0000000000019f59 (DINPUT8): DllGetClassObject + 0x3899 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x0000000000011468 (DINPUT8): GetdfDIJoystick + 0x63B8 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x000000000005fbfc (Input): luaopen_Input + 0x90AC 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x0000000000014316 (Input): ForceFeedback::initPeriodicEffect + 0x56 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x0000000000004b0f (Input): ForceFeedback::`default constructor closure' + 0x5EF 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x000000000001d055 (Input): Input::unlockMouseEvents + 0x1F35 2023-03-15 16:52:39.680 INFO EDCORE (Main): 0x000000000001d629 (Input): Input::unlockMouseEvents + 0x2509 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x0000000000002527 (DINPUT8): (function-name not available) + 0x0 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x000000000001d29c (Input): Input::unlockMouseEvents + 0x217C 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x000000000001bdc2 (Input): Input::unlockMouseEvents + 0xCA2 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x00000000000195f4 (Input): Input::initialize + 0x144 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x000000000087ca8f (DCS): SW + 0x3E6A3F 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x000000000087af86 (DCS): SW + 0x3E4F36 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x000000000235ee0d (DCS): AmdPowerXpressRequestHighPerformance + 0xFB9E09 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x0000000000c512c2 (DCS): SW + 0x7BB272 2023-03-15 16:52:39.681 INFO EDCORE (Main): 0x00000000000126bd (KERNEL32): BaseThreadInitThunk + 0x1D 2023-03-15 16:52:39.883 INFO EDCORE (Main): Minidump created.
Chances are it is the peripheral recognized as "vJoy Device".
-
Flappie's post in Mission Editor - Units created in reverse order was marked as the answer
Hi. You have two ways of adding units to a group:
The "+" button which acts as you say (intentional). The ">" button (to the right) which acts just like you want. -
Flappie's post in DCS MT crash at startup was marked as the answer
Ive just found something werid in your standard dcs.log:
2023-03-10 19:46:24.726 INFO APP (Main): Command line: "G:\Eagle Dynamics\DCS World\bin-mt\DCS.exe" Dynamics\DCS World OpenBeta\bin-mt\DCS.exe It should look like this:
2023-03-10 19:46:24.726 INFO APP (Main): Command line: "G:\Eagle Dynamics\DCS World\bin-mt\DCS.exe" Maybe it's an issue with your shortcut?
What happens if you launch MT DCS by clicking on the DCS.exe icon?
Browse to "G:\Eagle Dynamics\DCS World\bin-mt\". Double-click DCS.exe. -
Flappie's post in Sound File selection button don't work in mission editor was marked as the answer
Hi. Please try this:
Go to "C:\Users\...\AppData\Local\Temp". Delete all folder starting with "DCS" (they are temporary folders). Retry to add sound to your mission in the ME.
If that doesn't work, try this:
-
Flappie's post in Unable to update + error message image was marked as the answer
Hi. Are you using ESET antivirus?
If so, please read this:
-
Flappie's post in ED_SOUND PROBLEM was marked as the answer
Hi. This message is a common symptom for freezes in DCS. It does not mean that the sound is causing DCS to freeze, it's the other way around: DCS is freezing, and the sound component says "I'm unable to do a proper sound rendering because the PC is too busy".
-
Flappie's post in missing things since last patch was marked as the answer
Missing Raduga doors animation was reported some weeks ago. It's fixed internally.
-
Flappie's post in TACAN Station Bearing Triangle Inop was marked as the answer
It's not fixed in "stable" release version yet.
@Bob1943 The fix made it to Open Beta. You'll have to wait for the next "stable" release patch.
-
Flappie's post in There's a "target" pattern in the upper right corner , How to remove? was marked as the answer
@Art-J Nice find.
Source: https://www.reddit.com/r/csgo/comments/crm1hi/weird_sound_radar_thing_again/
-
Flappie's post in function trigger.action.circleToAll draw no outline was marked as the answer
Hi. I think that's because lineType=0.
Try this instead:
local ref = trigger.misc.getZone("targetArea") trigger.action.circleToAll(-1 , 1, ref.point , ref.radius , {1, 0, 0, 0} , {1, 0, 0, .1} , 1 , true) local ref_1 = trigger.misc.getZone("targetArea_1") trigger.action.circleToAll(-1 , 2, ref_1.point , ref_1.radius , {0, 1, 0, 1} , {1, 0, 0, .1} , 2, true)
https://wiki.hoggitworld.com/view/DCS_func_circleToAll
-
Flappie's post in HOTAS key bindings after reinstalling was marked as the answer
Hi. Windows has re-discovered your devices and it gave each of them a new codename, but your situation is not lost at all. Here you go:
0/ Backup your "C:\Users\...\Saved Games\DCS\Config\Input\" folder if you haven't already.
1/ Open your dcs.log file (from Saved Games/DCS.../Logs).
2/ Look for a section such as this one:
2023-02-28 20:21:34.435 INFO VISUALIZER (Main): SceneManager initialization 2023-02-28 20:21:34.879 INFO VISUALIZER (Main): cascade shadows init (preset:'default' quality:4 layers:4 size:4096) 2023-02-28 20:21:34.963 INFO INPUT (Main): Device [Keyboard] created. 2023-02-28 20:21:35.029 INFO INPUT (Main): Device [Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}] created. 2023-02-28 20:21:35.029 INFO INPUT (Main): Joystick created[Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}], ForceFeedBack: no 2023-02-28 20:21:35.036 INFO INPUT (Main): Device [Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}] created. 2023-02-28 20:21:35.036 INFO INPUT (Main): Joystick created[Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}], ForceFeedBack: no 2023-02-28 20:21:35.048 INFO INPUT (Main): Device [VKBsim Black Box {75D8AB30-73DD-11e7-8001-444553540000}] created. 2023-02-28 20:21:35.048 INFO INPUT (Main): Joystick created[VKBsim Black Box {75D8AB30-73DD-11e7-8001-444553540000}], ForceFeedBack: no 2023-02-28 20:21:35.049 INFO INPUT (Main): Device [Mouse] created. 3/ Copy the codenames between braces (not the ones from my example of course, the ones from your file).
4/ Browse an aircraft "joystick" folder (e.g. "C:\Users\...\Saved Games\DCS\Config\Input\su-25T\joystick"). You'll see find some .diff.lua file(s) such as these:
You'll have to do the same for each aircraft and each device.
5/ If I'm not mistaken, you will see that the codenames have changed. All you have to do now is to rename these files so their name mention the new codenames (the ones from dcs.log). Be warned: each device has its own codename.
Please let us know if it works for you.
-
Flappie's post in Crash and loss of graphics was marked as the answer
Hi. It looks like a memory issue. Time for manual pagefile setting: https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/
Init size: 32768 (32GB)
Max size: 32768 (32GB)
The drive hosting the pagefile must have enough free space, otherwise it won't work.