Redglyph Posted February 25, 2017 Share Posted February 25, 2017 DCS version 1.5.6.1938.247 When I run more than one quick mission with the M-2000C, it crashes to desktop. Isn't that a very old bug? I thought it was solved? To be fair, I don't see the point of those, aren't they just regular missions for which you can't see the briefing summary before launching them? System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR Link to comment Share on other sites More sharing options...
Azrayen Posted February 25, 2017 Share Posted February 25, 2017 It was old, it's been fixed last november, and as a matter of fact I checked it OK not 15 days ago. So it's odd... any logs? Link to comment Share on other sites More sharing options...
cthulhu68 Posted February 25, 2017 Share Posted February 25, 2017 To be fair, I don't see the point of those, aren't they just regular missions for which you can't see the briefing summary before launching them? I think they're set up like that for beginners who don't want to mess around with mission editor. FYI. You can open instant action missions in mission editor and make changes and will also see briefing screen before starting. Link to comment Share on other sites More sharing options...
Redglyph Posted February 25, 2017 Author Share Posted February 25, 2017 (edited) It was old, it's been fixed last november, and as a matter of fact I checked it OK not 15 days ago. So it's odd... any logs? Ah, OK. I tried a few things to bring more information, apparently it's perfectly reproducible when Tacview 1.5.3b is enabled (Scripts\TacviewGameGUI.lua script present) - if I remove TacView, it doesn't crash, - if I leave TacView but do the same test with other aircraft, it doesn't crash. EDIT: see below, does not crash with 1.5.4 So it's not a big problem, the obvious work-arounds are to launch from "Mission" or remove TacView. To reproduce: - launch DCS - launch an Instant mission for the M-2000C, for example "landing" (Caucasus M-2000C Landing.miz) => the mission starts - quit - "fly again" => the initial view is visible with the briefing, the paused sim environment - "fly" => crash Log: 00067.597 INFO EDCORE: # -------------- 20170225-192639 -------------- 00067.597 INFO EDCORE: S:\games\DCS_beta\bin\lua.dll 00067.597 INFO EDCORE: # C0000005 ACCESS_VIOLATION at F23E3882 00:00000000 00067.603 INFO EDCORE: 00000000 00000000 0000:00000000 00067.608 INFO EDCORE: F23E3882 0017EC90 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaS_newlstr()+1292 00067.608 INFO EDCORE: F23D1E2E 0017ECC0 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_rawget()+1E 00067.609 INFO EDCORE: E0A4B087 0017ED20 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll 00067.609 INFO EDCORE: E0A4CF8F 0017EE10 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll luaopen_tacview()+121F 00067.610 INFO EDCORE: E0A4D567 0017EE80 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll luaopen_tacview()+17F7 00067.610 INFO EDCORE: E0A4BD26 0017EEB0 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll 00067.610 INFO EDCORE: F23D7254 0017EEF0 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaD_growstack()+7A4 00067.610 INFO EDCORE: F23E6FB5 0017F070 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaS_newlstr()+49C5 00067.611 INFO EDCORE: F23D7541 0017F0A0 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaD_growstack()+A91 00067.611 INFO EDCORE: F23D684F 0017F220 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_getinfo()+11AF 00067.611 INFO EDCORE: F23D785E 0017F260 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_yield()+9E 00067.612 INFO EDCORE: F23D2440 0017F2B0 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_pcall()+60 00067.612 INFO EDCORE: EA1A8221 0017F310 0000:00000000 S:\games\DCS_beta\bin\edCore.dll ?call_func@Config@Lua@@AEAA_NPEBDPEAV?$basic_string@D@ed@@HH@Z()+E1 00067.612 INFO EDCORE: 400219C5 0017F360 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 40021E5C 0017F410 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4001666E 0017F480 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4001D721 0017F4E0 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4000BBD4 0017F510 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4000BB24 0017F540 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.614 INFO EDCORE: 3FCE71CF 0017FC00 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.615 INFO EDCORE: 4011FE1D 0017FC40 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.616 INFO EDCORE: 77A759CD 0017FC70 0000:00000000 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 00067.616 INFO EDCORE: 77BAA561 0017FCC0 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 There is a minidump, it's a little heavier than the log but I can upload it somewhere if it helps. I think they're set up like that for beginners who don't want to mess around with mission editor. FYI. You can open instant action missions in mission editor and make changes and will also see briefing screen before starting. There is no need to use the mission editor to launch any mission. Just open the mission menu, select a mission and you should see the "situation" part of the briefing. Click OK and you have the whole briefing available, from there you can launch the mission. As said above, it's possible to use that to launch the Instant missions as well. Hope it helps :) The "Instant mission" menu, however, behaves in a non-consistent way and starts the clicked mission file without showing anything. There is no advantage, why this is there is unclear to me. Still, it acts as a category selector, after a fashion, by looking first into the Missions/QuickStart directory. But the main problem reported here is that it doesn't seem to agree with both TacView and the M-2000C. Edited February 25, 2017 by Redglyph System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR Link to comment Share on other sites More sharing options...
Redglyph Posted February 25, 2017 Author Share Posted February 25, 2017 I updated to TacView 1.5.4, had to uninstall / reinstall it a few times and fiddle with it before it actually worked, but now it seems to record the flights and it does not crash anymore! Sorry then, this seems to be a problem with older version of TacView, that occurs for some reason with this strange combination. You can forget about this thread :) System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR Link to comment Share on other sites More sharing options...
Azrayen Posted February 26, 2017 Share Posted February 26, 2017 OK then :) Link to comment Share on other sites More sharing options...
Recommended Posts