Runnan Posted August 27, 2020 Posted August 27, 2020 Hi! Since the last patch I really cant play the game. I have never had any problems before so this kind of ruins the whole game for me. Since the last patch I cant load missions or any MP servers. When I start a mission (any kind) Im able to fly something about 10 sec before it goes black. In MP servers I make it until the “select slot” page but it does not fully load. Tried it with and without VR and in high and low graphic settings but with the same results. I have tried repair the game, and even uninstalled it but with the problem remains. Specs: Processor: Intel® Core i5-9600K CPU @ 3.70GHz (6 CPUs), ~3.7GHz Memory: 16 GB RAM DDR4 2166mhz NVIDIA GeForce GTX 1070 anyone got any tips or pointers?dcs.20200827-203626.log
Flappie Posted August 27, 2020 Posted August 27, 2020 Hi Runnan. Here are the errors you're getting: 2020-08-27 20:36:15.693 INFO DCS: use_xRay: no 2020-08-27 20:36:19.046 INFO DCS: MissionSpawn:initScript 2020-08-27 20:36:19.280 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 0 squares 2020-08-27 20:36:19.282 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 207 squares 2020-08-27 20:36:19.282 INFO EDTERRAINGRAPHICS41: surface5 gc() 2.693700 ms 2020-08-27 20:36:19.428 INFO TACVIEW.EXPORT: Loading C++ flight data recorder from [C:\Users\Runnan\Saved Games\DCS\Mods\tech\Tacview\bin\] 2020-08-27 20:36:19.430 INFO TACVIEW.EXPORT: Tacview 1.8.3.200 C++ flight data recorder successfully loaded 2020-08-27 20:36:22.213 ERROR Lua::Config: Call error MarkPanel.show:[string "./dxgui/bind/Widget.lua"]:69: Invalid arguments!. 2020-08-27 20:36:23.100 INFO ANIMATOR: load_basic() started 2020-08-27 20:36:25.055 ERROR ANIMATOR: animation '' not found 2020-08-27 20:36:25.216 INFO EDCORE: try to write dump information 2020-08-27 20:36:25.218 INFO EDCORE: # -------------- 20200827-203626 -------------- 2020-08-27 20:36:25.219 INFO EDCORE: DCS/2.5.6.54046 (x86_64; Windows NT 10.0.18363) 2020-08-27 20:36:25.220 INFO EDCORE: D:\Steam\steamapps\common\DCSWorld\bin\animator.dll 2020-08-27 20:36:25.221 INFO EDCORE: # C0000005 ACCESS_VIOLATION at D666A433 00:00000000 2020-08-27 20:36:25.229 INFO EDCORE: SymInit: Symbol-SearchPath: '.', symOptions: 534, UserName: 'Runnan' 2020-08-27 20:36:25.230 INFO EDCORE: OS-Version: 10.0.18363 () 0x300-0x1 2020-08-27 20:36:25.523 INFO EDCORE: 0x000000000001A433 (animator): Animator::AnimationGraph::init + 0x4233 2020-08-27 20:36:25.530 INFO EDCORE: 0x000000000002A200 (animator): Animator::AnimationManager::create_gpu_animations + 0x10B0 2020-08-27 20:36:25.531 INFO EDCORE: 0x00000000000DF350 (edCore): ed::this_thread::yield + 0x2CC0 2020-08-27 20:36:25.533 INFO EDCORE: 0x00000000000DBCF8 (edCore): ed::thread::_get_current_thread_id + 0x58 2020-08-27 20:36:25.535 INFO EDCORE: 0x0000000000020E82 (ucrtbase): beginthreadex + 0x142 2020-08-27 20:36:25.537 INFO EDCORE: 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14 2020-08-27 20:36:25.538 INFO EDCORE: 0x000000000006CE51 (ntdll): RtlUserThreadStart + 0x21 2020-08-27 20:36:25.571 ERROR DX11BACKEND: failed to create vertex buffer. Reason: E_OUTOFMEMORY 2020-08-27 20:36:25.571 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:379 2020-08-27 20:36:26.159 INFO EDCORE: Minidump created.It seems an animation cannot be found. It might be caused by a missing or damaged file. You also have a quite low pagefile size (4 GB). You can try to set Windows virtual memory handling to auto, to start with (it may already be in auto mode, you tell me). ---
Runnan Posted August 29, 2020 Author Posted August 29, 2020 Update: Reinstalled the game one last time, and i changed my ram to 32 gb 2666 mhz instead of 16 gb 2133 mhz. The game did not crash and works fine now :)
Kula66 Posted September 1, 2020 Posted September 1, 2020 (edited) I'm getting a fairly regular crash on this screen too ... once DCS has crashed, it requires a reboot in order to load again. Annoyingly, I recently upgraded my RAM from 16 to 32 because I thought this may fix it ... may have made it worse. I'll do some more testing and get a crash log uploaded :( EDIT: Tried reproducing this morning (servers are less busy) and after a few tries got it to crash again, log attached. I then did a repair, so will see if that helped.dcs.log Edited September 1, 2020 by Kula66
ED Team BIGNEWY Posted September 1, 2020 ED Team Posted September 1, 2020 I'm getting a fairly regular crash on this screen too ... once DCS has crashed, it requires a reboot in order to load again. Annoyingly, I recently upgraded my RAM from 16 to 32 because I thought this may fix it ... may have made it worse. I'll do some more testing and get a crash log uploaded :( EDIT: Tried reproducing this morning (servers are less busy) and after a few tries got it to crash again, log attached. I then did a repair, so will see if that helped. It looks like a driver crash 2020-09-01 07:05:05.239 INFO EDCORE: try to write dump information 2020-09-01 07:05:05.245 INFO EDCORE: # -------------- 20200901-070505 -------------- 2020-09-01 07:05:05.246 INFO EDCORE: DCS/2.5.6.54046 (x86_64; Windows NT 10.0.18363) 2020-09-01 07:05:05.248 INFO EDCORE: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_55e7fb10ab85a7c2\nvwgf2umx.dll I would remove / disable all unofficial mods, run a cleanup and repair( or verify for steam ) and reinstall gpu driver. let us know if it helps thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Kula66 Posted September 1, 2020 Posted September 1, 2020 (edited) Many thanks bignewy, I think the only mods are Tacview, SRS & Simshaker. I'll try an NV driver update ... EDIT: Od, it does only happen on while the slots available screen is loading Edited September 1, 2020 by Kula66
Flappie Posted September 1, 2020 Posted September 1, 2020 Actually, you appear to have two more installed and active mods: 476 Range Targets Civil Aircraft Mod ---
Kula66 Posted September 1, 2020 Posted September 1, 2020 Indeed ... well spotted. I haven't used in a while, so can delete. Thanks.
Kula66 Posted September 1, 2020 Posted September 1, 2020 I switched back to using the Oculus beta software and so far, that seems have fixed the crashes ... very odd.
Flappie Posted September 1, 2020 Posted September 1, 2020 Good news. Please post back here if the crashes reappear. ---
Kula66 Posted September 4, 2020 Posted September 4, 2020 (edited) Happened again as the cockpit was rendering ... when reloading DCS, it just kept quiting, so had to reboot to fix it. Then fine for 2hrs of play. Very odd.dcs.log Edited September 4, 2020 by Kula66
Flappie Posted September 4, 2020 Posted September 4, 2020 (edited) Hi Kula. We need to know why DCS crashed. Can you please attach the latest dcs.log-2020####-######.zip files from your /Logs folder? EDIT: By the way, you can update your signature since you have installed more RAM in your PC. 2020-09-03 18:16:26.359 INFO DCS: CPU cores: 4, threads: 8, System RAM: 32684 MB, Pagefile: 24000 MB Edited September 4, 2020 by Flappie ---
Flappie Posted September 4, 2020 Posted September 4, 2020 I've listed all the errors you get that I don't. Some of them are very rare acording to the forum's search engine (I put those in red). Have you done what BIGNEWY asked you to? If not, please follow the cleanup and repair procedure, then post a fresh dcs.log. GLOBAL: ERROR_ONCE DX11BACKEND: texture 'bd3-usk-a_spec' not found. Asked from 'NGMODEL' ERROR SOUND: can't load wave: "speech\rus\common\awacs\numbers\4000-begin" ERROR SOUND: can't load wave: "speech\rus\common\awacs\numbers\3000-begin" ERROR SOUND: can't load wave: "speech\rus\common\awacs\numbers\2000-begin" F-14: ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/f-14/touchdown): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/f-14/groundroll): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/f-14/windrushing): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley/damage_impact): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley/damage_missileimpact): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:damage/structuralgroan): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley/damage_impact): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley/damage_missileimpact): gain ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/f-14/windrushing): pitch JF-17: ERROR_ONCE DX11BACKEND: texture 'jf-17_pf12r' not found. Asked from 'NGMODEL' ERROR_ONCE DX11BACKEND: texture 'jf-17_pf12r_roughmet' not found. Asked from 'NGMODEL' ERROR_ONCE DX11BACKEND: texture 'jf-17_pf9wr' not found. Asked from 'NGMODEL' ERROR_ONCE DX11BACKEND: texture 'jf-17_pf12l' not found. Asked from 'NGMODEL' ERROR_ONCE DX11BACKEND: texture 'jf-17_pf9wl' not found. Asked from 'NGMODEL' ERROR_ONCE DX11BACKEND: texture 'jf-17_pf12l_roughmet' not found. Asked from 'NGMODEL' F-16C: ERROR_ONCE DX11BACKEND: texture 'Fuel_Tank_370_diff' not found. Asked from 'GRAPHICSCORE' ERROR_ONCE DX11BACKEND: texture 'Fuel_Tank_370_NM' not found. Asked from 'GRAPHICSCORE' ERROR_ONCE DX11BACKEND: texture 'Fuel_Tank_370_diff_RoughMet' not found. Asked from 'GRAPHICSCORE' ERROR_ONCE DX11BACKEND: texture '/textures//liveries/f-16c_50/thk_191_filo/pilot_f16_helmet_roughmet' not found. Asked from 'GRAPHICSCORE' ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_L. ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_R. ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_L. ---
Kula66 Posted September 4, 2020 Posted September 4, 2020 Well, I ran a repair and told it to delete everything spurious. Not seen this issue in SP, only when joining a server and its happened on various MP servers. As I mentioned, once I rebooted and reloaded DCS, it ran fine for a couple of hours. I'll see if I can dig out the other logs and upload. Many thanks. PS> I don't seem to have an option to update my sig :(
Flappie Posted September 4, 2020 Posted September 4, 2020 PS> I don't seem to have an option to update my sig Up there "Quick Links" > "Edit signature". :thumbup: ---
Kula66 Posted September 4, 2020 Posted September 4, 2020 (edited) Cheers Flappie. There is no dcs.log.2020### dated 0903 ... I have a few from 0901.Next time it happens I'll upload the ZIP. Edited September 4, 2020 by Kula66
Kula66 Posted September 4, 2020 Posted September 4, 2020 Tried joining a couple of servers and eventualy one crashed (had a higher ping) while the slots screen was loading ... no sign of a dcs.log-2020###.zip I reloaded DCS to see if it would create a crash file, hence this is the previos log, ie. .old
Kula66 Posted September 4, 2020 Posted September 4, 2020 Also happens when I load with --force_disable_VR. Again no ZIP file ... crashed on connecting to a 130 ping server, ran another repair today, had already connected to a couple of other high user count servers without issue.dcs.log
Flappie Posted September 5, 2020 Posted September 5, 2020 OK. Below is a new batch of unusual errors from your latest log. It seems your game is still broken somehow. This blue error message happens the first two times without causing a crash. It follows an error message about the Tarawa ("CENTER_RADAR_10"). Line 1153: 2020-09-04 17:31:04.406 ERROR SOUND: invalid source_params(woLA-16858644:aircrafts/engines/f110afterburnerrearclose): gainOn your third go, we can see the game crashes righter after the "CENTER_RADAR_10" error message. I think it means the "f110afterburnerclose" error caused the crash. Line 945: 2020-09-04 17:30:54.419 ERROR_ONCE DX11BACKEND: render target 'fftw_foam' not found Line 1074: 2020-09-04 17:30:59.286 ERROR_ONCE DX11BACKEND: texture '/textures//liveries/yak-52/the yakovlevs/Yak52_Gear_RoughMet' not found. Asked from 'GRAPHICSCORE' Line 1076: 2020-09-04 17:31:01.857 ERROR ANIMATOR: animation '' not found Line 1078: 2020-09-04 17:31:02.055 ERROR ANIMATOR: animation '' not found Line 1118: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_R_01: there is no connector with such name. Line 1119: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_R_02: there is no connector with such name. Line 1120: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_R_01: there is no connector with such name. Line 1121: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_R_02: there is no connector with such name. Line 1122: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_BACK_R: there is no connector with such name. Line 1123: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_L_01: there is no connector with such name. Line 1124: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_L_02: there is no connector with such name. Line 1125: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_L_01: there is no connector with such name. Line 1126: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_L_02: there is no connector with such name. Line 1127: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_BACK_L: there is no connector with such name. Line 1128: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_NOSE: there is no connector with such name. Line 1129: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_MIDLE_01: there is no connector with such name. Line 1130: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_MIDLE_02: there is no connector with such name. Line 1131: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_BACK_01: there is no connector with such name. Line 1132: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_BACK_02: there is no connector with such name. Line 1133: 2020-09-04 17:31:03.118 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_RUBKA: there is no connector with such name. Line 1134: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (POINT_GUN_ZA_BL): unit type = LHA_Tarawa, ws id=2, ln id=1, br id=1 Line 1135: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_01): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=1 Line 1136: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_02): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=2 Line 1137: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_03): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=3 Line 1138: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_04): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=4 Line 1139: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_05): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=5 Line 1140: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_06): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=6 Line 1141: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_07): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=7 Line 1142: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_08): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=8 Line 1143: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_20): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=1 Line 1144: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_21): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=2 Line 1145: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_22): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=3 Line 1146: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_23): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=4 Line 1147: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_24): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=5 Line 1148: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_25): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=6 Line 1149: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_26): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=7 Line 1150: 2020-09-04 17:31:03.118 ERROR WEAPONS: Invalid connector name (Rocket_Point_27): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=8 Line 1151: 2020-09-04 17:31:03.119 ERROR wWeaponSystem: invalid connector CENTER_RADAR_9 for unit LHA_Tarawa Line 1152: 2020-09-04 17:31:03.119 ERROR wWeaponSystem: invalid connector CENTER_RADAR_10 for unit LHA_Tarawa Line 1153: 2020-09-04 17:31:04.406 ERROR SOUND: invalid source_params(woLA-16858644:aircrafts/engines/f110afterburnerrearclose): gain ------ Line 1188: 2020-09-04 17:31:14.025 ERROR SOUND: can't load wave: "effects\aircrafts\engines\f14_rear_distant_02" Line 1215: 2020-09-04 17:31:31.243 ERROR_ONCE DX11BACKEND: render target 'fftw_foam' not found Line 1305: 2020-09-04 17:31:33.742 ERROR Lua::Config: Call error MarkPanel.show:[string "./dxgui/bind/Widget.lua"]:69: Invalid arguments!. Line 1305: 2020-09-04 17:31:33.742 ERROR Lua::Config: Call error MarkPanel.show:[string "./dxgui/bind/Widget.lua"]:69: Invalid arguments!. Line 1335: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_R_01: there is no connector with such name. Line 1336: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_R_02: there is no connector with such name. Line 1337: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_R_01: there is no connector with such name. Line 1338: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_R_02: there is no connector with such name. Line 1339: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_BACK_R: there is no connector with such name. Line 1340: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_L_01: there is no connector with such name. Line 1341: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_L_02: there is no connector with such name. Line 1342: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_L_01: there is no connector with such name. Line 1343: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_L_02: there is no connector with such name. Line 1344: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_BACK_L: there is no connector with such name. Line 1345: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_NOSE: there is no connector with such name. Line 1346: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_MIDLE_01: there is no connector with such name. Line 1347: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_MIDLE_02: there is no connector with such name. Line 1348: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_BACK_01: there is no connector with such name. Line 1349: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_BACK_02: there is no connector with such name. Line 1350: 2020-09-04 17:31:34.224 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_RUBKA: there is no connector with such name. Line 1351: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (POINT_GUN_ZA_BL): unit type = LHA_Tarawa, ws id=2, ln id=1, br id=1 Line 1352: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_01): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=1 Line 1353: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_02): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=2 Line 1354: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_03): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=3 Line 1355: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_04): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=4 Line 1356: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_05): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=5 Line 1357: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_06): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=6 Line 1358: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_07): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=7 Line 1359: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_08): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=8 Line 1360: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_20): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=1 Line 1361: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_21): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=2 Line 1362: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_22): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=3 Line 1363: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_23): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=4 Line 1364: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_24): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=5 Line 1365: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_25): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=6 Line 1366: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_26): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=7 Line 1367: 2020-09-04 17:31:34.224 ERROR WEAPONS: Invalid connector name (Rocket_Point_27): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=8 Line 1368: 2020-09-04 17:31:34.224 ERROR wWeaponSystem: invalid connector CENTER_RADAR_9 for unit LHA_Tarawa Line 1369: 2020-09-04 17:31:34.224 ERROR wWeaponSystem: invalid connector CENTER_RADAR_10 for unit LHA_Tarawa Line 1377: 2020-09-04 17:31:36.583 ERROR SOUND: invalid source_params(woLA-16871963:aircrafts/engines/f110afterburnerrearclose): gain Line 1378: 2020-09-04 17:31:36.589 ERROR SOUND: invalid source_params(woLA-16778758:aircrafts/engines/f110afterburnerrearclose): gain Line 1379: 2020-09-04 17:31:36.591 ERROR SOUND: invalid source_params(woLA-16779297:aircrafts/engines/f110afterburnerrearclose): gain Line 1380: 2020-09-04 17:31:36.966 ERROR SOUND: invalid source_params(woLA-16871963:aircrafts/engines/f110afterburnerrearclose): gain Line 1381: 2020-09-04 17:31:36.966 ERROR SOUND: invalid source_params(woLA-16778758:aircrafts/engines/f110afterburnerrearclose): gain Line 1382: 2020-09-04 17:31:36.966 ERROR SOUND: invalid source_params(woLA-16779297:aircrafts/engines/f110afterburnerrearclose): gain ------ Line 1386: 2020-09-04 17:31:38.154 ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_L. Line 1387: 2020-09-04 17:31:38.155 ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_R. Line 1397: 2020-09-04 17:31:41.354 ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_R. Line 1448: 2020-09-04 17:32:13.382 ERROR_ONCE DX11BACKEND: render target 'fftw_foam' not found Line 1449: 2020-09-04 17:32:13.537 ERROR_ONCE DX11BACKEND: render target 'mainDepthBuffer_copy' not found Line 1450: 2020-09-04 17:32:13.537 ERROR_ONCE DX11BACKEND: render target 'DummyShadowMap' not found Line 1537: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_R_01: there is no connector with such name. Line 1538: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_R_02: there is no connector with such name. Line 1539: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_R_01: there is no connector with such name. Line 1540: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_R_02: there is no connector with such name. Line 1541: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_BACK_R: there is no connector with such name. Line 1542: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_L_01: there is no connector with such name. Line 1543: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_NOSE_L_02: there is no connector with such name. Line 1544: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_L_01: there is no connector with such name. Line 1545: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_CENTER_L_02: there is no connector with such name. Line 1546: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_BACK_L: there is no connector with such name. Line 1547: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_NOSE: there is no connector with such name. Line 1548: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_MIDLE_01: there is no connector with such name. Line 1549: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_MIDLE_02: there is no connector with such name. Line 1550: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_BACK_01: there is no connector with such name. Line 1551: 2020-09-04 17:32:18.171 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_PALUBA_BACK_02: there is no connector with such name. Line 1552: 2020-09-04 17:32:18.172 ERROR wWeaponSystemManager: Can't get the fire position connector FIRE_RUBKA: there is no connector with such name. Line 1553: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (POINT_GUN_ZA_BL): unit type = LHA_Tarawa, ws id=2, ln id=1, br id=1 Line 1554: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_01): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=1 Line 1555: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_02): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=2 Line 1556: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_03): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=3 Line 1557: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_04): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=4 Line 1558: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_05): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=5 Line 1559: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_06): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=6 Line 1560: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_07): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=7 Line 1561: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_08): unit type = LHA_Tarawa, ws id=5, ln id=1, br id=8 Line 1562: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_20): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=1 Line 1563: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_21): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=2 Line 1564: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_22): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=3 Line 1565: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_23): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=4 Line 1566: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_24): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=5 Line 1567: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_25): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=6 Line 1568: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_26): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=7 Line 1569: 2020-09-04 17:32:18.172 ERROR WEAPONS: Invalid connector name (Rocket_Point_27): unit type = LHA_Tarawa, ws id=6, ln id=1, br id=8 Line 1570: 2020-09-04 17:32:18.172 ERROR wWeaponSystem: invalid connector CENTER_RADAR_9 for unit LHA_Tarawa Line 1571: 2020-09-04 17:32:18.172 ERROR wWeaponSystem: invalid connector CENTER_RADAR_10 for unit LHA_Tarawa --- no more message in the log (game crashed) --- I'd like you to test something, even though you have already reinstalled the game. Try deleting the whole content of your \DCS World OpenBeta\CoreMods\ folder, then run a repair. I ask you this because I've already seen users with rare error messages like yours fixing their games this way (example). ---
Kula66 Posted September 6, 2020 Posted September 6, 2020 (edited) Thanks Flappie, I’ll try that today. UPDATE: 39GB downloading :) UPDATE2: been pretty good today, then ... UPDATE3: This is going t osound odd, but since I remove my core dir and repaired, I can't add the F-14 to any missions, it doesn't appear on the drop down ... I can fly it on-line and in existing missions ok, but its not on the list. Neither is the S-3! Did another repair and nothing highlighted.dcs.log Edited September 6, 2020 by Kula66
ACME_WIdgets Posted September 6, 2020 Posted September 6, 2020 (edited) Not applicable Edited September 6, 2020 by ACME_Widgets Didn't mean to hijack thread, just trying to point out timing on Select Slot 5600x, EVGA 3070 FTW, B550 Tomahawk, M.2 Samsung, 32GB CL16, AIO 240mm VKB Gladiator Pro, Freetracker IR 3d printed, TM MkII HOTAS circa 1985 w/USB Asus 27" 2560x1440 60fps (so constrain DCS to 60fps) F-16, F-18 2021 = First year on DCS:
Flappie Posted September 6, 2020 Posted September 6, 2020 Thanks Flappie, I’ll try that today. UPDATE: 39GB downloading :) UPDATE2: been pretty good today, then ... UPDATE3: This is going t osound odd, but since I remove my core dir and repaired, I can't add the F-14 to any missions, it doesn't appear on the drop down ... I can fly it on-line and in existing missions ok, but its not on the list. Neither is the S-3! Did another repair and nothing highlighted. So, no more crashes so far, Kula? About the Tomcat and S-3, I think you have historical mode filter ON. Please try disabling it by clicking on the clock button. Then you should be able to find the units you're looking for. ---
Recommended Posts