Magnum

Fairly fresh install of Windows and the dedicated server(within the last few weeks). All drivers are up to date and I am running tacview 1.8.6 but will try updating to 1.8.7 Beta1.

I've added debug via autoexec.cfg, hope this helps... dcs.log-20210510-145520.zip

dcs.log-20210510-115707.zip

dcs.log-20210509-161438.zip

Haven't changed a thing and issue still occurs on 2.7.0.5659 dcs.log-20210509-130514.zip

dcs.log-20210428-211953.zip dcs.log-20210429-174635.zip dcs.log-20210429-204204.zip dcs.log-20210501-154200.zip dcs.log-20210501-221221.zip dcs.log-20210502-091743.zip dcs.log-20210503-041455.zip dcs.log-20210503-203918.zip dcs.log-20210504-055232.zip dcs.log-20210505-004049.zip dcs.log-20210505-030205.zip

I would be better to have an official solution rather than all these third party solutions that are either outdated or easily broken by constant updates. Or perhaps some improvements and added functionality to the already existing logbook. I can also see why this would be a low priority as I'm sure there are some that could care less about have every single statistic recorded somewhere as if this was one of those AAA games.

Surely I can't be the only one seeing crashes like "C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;". Crash logs: dcs.log-20210411-153600 - This was before the 2.7 update dcs.log-20210415-024639 - This was after the 2.7 update. Oddly there is a lot of garbled text in the .crash file and I also had to remove the .trk file as it was too large to upload here. I've tried windows updates, dcs repairs, complete re-installs. Not sure if websymbols is something my OS is just missing and the MS documentation is quite vague on how to ensure its installed. 2.7 has it's own issues, but hopefully my logs can show this was existing before and after dcs.log-20210411-153600.zip dcs.log-20210415-024639.zip

Dedicated server was consistently crashing on me so I blew it up and did a fresh re-install. I can no longer see nor connect to my dedicated server using DCS open beta. It does however show up via DCS stable. What gives? Nevermind, I guess now there is a stable and open beta version for the dedicated server.

I'm seeing these errors quite often in my dcs.log and it looks to be this script as it's the only one where the line count matches: 1:39:03 PM.376 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: attempt to concatenate field 'target_name' (a nil value) 1:39:03 PM.376 INFO SCRIPTING stack traceback: [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000040CA.lua"]:8063: in function <[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000040CA.lua"]:8059> [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: in function 'EventFunction' [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000040CA.lua"]:8408: in function <[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000040CA.lua"]:8407> [C]: in function 'xpcall' [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000040CA.lua"]:8406: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11> 10:16:30 PM.115 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000000F7.lua"]:182: attempt to index a nil value 10:16:30 PM.115 INFO SCRIPTING stack traceback: [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis00000D9A.lua"]:8063: in function <[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis00000D9A.lua"]:8059> [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000000F7.lua"]:182: in function 'EventFunction' [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis00000D9A.lua"]:8408: in function <[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis00000D9A.lua"]:8407> [C]: in function 'xpcall' [string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis00000D9A.lua"]:8406: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11> 1:38:50 PM.644 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: attempt to concatenate field 'target_name' (a nil value) 1:38:54 PM.140 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: attempt to concatenate field 'target_name' (a nil value) 1:39:03 PM.376 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: attempt to concatenate field 'target_name' (a nil value) 1:39:05 PM.317 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: attempt to concatenate field 'target_name' (a nil value) 1:39:07 PM.267 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: attempt to concatenate field 'target_name' (a nil value) 1:39:19 PM.707 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000034C4.lua"]:203: attempt to concatenate field 'target_name' (a nil value) 10:16:30 PM.115 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000000F7.lua"]:182: attempt to index a nil value 10:19:14 PM.472 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000000F7.lua"]:182: attempt to index a nil value 10:21:21 PM.637 INFO SCRIPTING Error in SCHEDULER function:[string "C:\Users\xxxxxxx\AppData\Local\Temp\DCS.openbeta_server\/~mis000000F7.lua"]:182: attempt to index local 'PlayerUnit' (a nil value)

It was not a throttle issue. Something must have been corrupted. I just re-ran the world install 1.2.1.5970 without un-installing, then ran the update again. Now it works.

Yup

tried it...nothing.

they are

I cannot seem to start the SU-25 anymore. I use shift+L to turn on the electronics, then neither alt+home, Ctrl+home, or shift+ home start the engines for me. I've checked the key bindings and there good. I've even tried assigning diff keys and still nothing. I have noticed tho, that the two little lights under the tach on the dash board come on briefly when I repeatily press the engine start keys, but the engines just wont start.

I feel it's way to easy to lock up the engine on the P-51 without any warning. Yes, you can glue your eyes to the temp gagues which is what real P-51 pilots did back in thier day. But it seems there is almost no warning audible until "clunk", and the prop/engine lock up. If you ever get the chance, check out A2A's P-51 for FSX. Your able to hear the bearings wear out, there is a loss of power, steam pours out the radiator, heavy engine smoke, maybe fire, and then the engine slowly grinds to a halt. Looks and sounds great!

Every time the updater runs, I have to re-do my view.lua file and re-apply the NvidiaSurround fix. I run a resolution of 5760x1080. This is somewhat annoying, but it's much bettter than having to uninstall and reinstall the whole damn thing. I'm really looking forward to patch notes with the updater.

It happens with or without SLI turned on.

Here is my thread on this issue. http://forums.eagle.ru/showthread.php?t=93279 I am able to recreate it reliably every time.

Looks like weather.dll is listed here: Log Name: Application Source: Application Error Date: 8/24/2012 8:14:03 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: John-PC Description: Faulting application name: dcs.exe, version: 1.2.0.3205, time stamp: 0x4ff3450d Faulting module name: Weather.dll, version: 1.2.0.3205, time stamp: 0x4fe3652d Exception code: 0xc0000005 Fault offset: 0x000000000000890c Faulting process id: 0x15e4 Faulting application start time: 0x01cd8266fa145a20 Faulting application path: D:\SystemFiles\Games\DCS World 12\bin\dcs.exe Faulting module path: D:\SystemFiles\Games\DCS World 12\bin\Weather.dll Report Id: 89df1c3d-ee5a-11e1-a85c-001fbc0169b9 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-08-25T02:14:03.000000000Z" /> <EventRecordID>58138</EventRecordID> <Channel>Application</Channel> <Computer>John-PC</Computer> <Security /> </System> <EventData> <Data>dcs.exe</Data> <Data>1.2.0.3205</Data> <Data>4ff3450d</Data> <Data>Weather.dll</Data> <Data>1.2.0.3205</Data> <Data>4fe3652d</Data> <Data>c0000005</Data> <Data>000000000000890c</Data> <Data>15e4</Data> <Data>01cd8266fa145a20</Data> <Data>D:\SystemFiles\Games\DCS World 12\bin\dcs.exe</Data> <Data>D:\SystemFiles\Games\DCS World 12\bin\Weather.dll</Data> <Data>89df1c3d-ee5a-11e1-a85c-001fbc0169b9</Data> </EventData> </Event>

It was the p-51 instant action mission "Intercept" that created this crash log. All the p-51 instant action missions crash on me. The su-25 missions do not do this. All system driver are up to date. My system spec are as follows: EVGA X58 3-Way hydro-copper motherboard Intel Core i7 965 2 EVGA GTX 480 in SLI pushing a resolution of 5760x1080 across 3 monitors 24GB 1333MHz ram Windows 7 64bit

Any kind of single player mission/campain/or instant action generates one of these. Any ideas? # -------------- 20120822-022155 -------------- # C0000005 ACCESS_VIOLATION at E8C9890C 00:00000000 00000000 00000000 0000:00000000 E8C9890C 0030E7B0 0000:00000000 ?getTurbulenceInLayer@IAtmosphere@Weather@@IEBA?AV?$Vector@$02N@Math@@AEBV34@N@Z()+17C E8C9B273 0030E8D0 0000:00000000 ?getAtmoWind_w@StandardAtmosphere@Weather@@UEBA?AV?$Vector@$02N@Math@@AEBV34@N@Z()+233 EB5D53F8 0030EA20 0000:00000000 ?calcInlet@JetInlet@EagleFM@@UEAAXPEAVDynamicBody@2@NAEAN111PEAN2@Z()+1F8 EB5D70E6 0030ED50 0000:00000000 ?doSimulate@PistonEngine@EagleFM@@MEAAXXZ()+96 E7799BB0 0030EE10 0000:00000000 EB5ADE19 0030EE40 0000:00000000 ?simulate@Optimizable@@QEAAXN@Z()+29 E7797FB2 0030F2E0 0000:00000000 3F29F35F 0030F440 0000:00000000 3F2E3D4E 0030F6C0 0000:00000000 3F2DC89F 0030F710 0000:00000000 F59A8361 0030F7A0 0000:00000000 F59A882A 0030F7F0 0000:00000000 3F3D4199 0030F880 0000:00000000 3F3D624D 0030F8E0 0000:00000000 3F3EC964 0030F910 0000:00000000 3F3EC848 0030F940 0000:00000000 3F4708E8 0030F9B0 0000:00000000 3F471853 0030FE80 0000:00000000 3F474107 0030FF30 0000:00000000 773D652D 0030FF60 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 77ACC521 0030FFB0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

I cant seem to figure out the crash logs. This happenes everytime I'm a few seconds into a training mission. Crash to desktop saying DCS has stopped working. This was the instant action for the P-51 Final Approach Lochini that generated this crash log. System specs: Win7 64bit EVGA x58 3-way hydro copper motherboard intel core i7 965 extreme 24GB ram 2x EVGA GTX 480 SLI # -------------- 20120821-193215 -------------- # C0000005 ACCESS_VIOLATION at EAA9890C 00:00000000 00000000 00000000 0000:00000000 EAA9890C 0031E350 0000:00000000 ?getTurbulenceInLayer@IAtmosphere@Weather@@IEBA?AV?$Vector@$02N@Math@@AEBV34@N@Z()+17C EAA9B273 0031E470 0000:00000000 ?getAtmoWind_w@StandardAtmosphere@Weather@@UEBA?AV?$Vector@$02N@Math@@AEBV34@N@Z()+233 EB0553F8 0031E5C0 0000:00000000 ?calcInlet@JetInlet@EagleFM@@UEAAXPEAVDynamicBody@2@NAEAN111PEAN2@Z()+1F8 EB0570E6 0031E8F0 0000:00000000 ?doSimulate@PistonEngine@EagleFM@@MEAAXXZ()+96 E7189BB0 0031E9B0 0000:00000000 EB02DE19 0031E9E0 0000:00000000 ?simulate@Optimizable@@QEAAXN@Z()+29 E7187FB2 0031EE80 0000:00000000 3F90F35F 0031EFE0 0000:00000000 3F953D4E 0031F260 0000:00000000 3F94C89F 0031F2B0 0000:00000000 F62B8361 0031F340 0000:00000000 F62B882A 0031F390 0000:00000000 3FA44199 0031F420 0000:00000000 3FA4624D 0031F480 0000:00000000 3FA5C964 0031F4B0 0000:00000000 3FA5C848 0031F4E0 0000:00000000 3FAE08E8 0031F550 0000:00000000 3FAE1853 0031FA20 0000:00000000 3FAE4107 0031FAD0 0000:00000000 7725652D 0031FB00 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7794C521 0031FB50 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21