![]() |
|
#1
|
||||
|
||||
![]()
ok thanks cause thats the same error before the hot fix your campaign might be corrupted.
have you updated your java latley?
__________________
71st Eagle Squadron www.anon6.com - Blogger on DCS Series 71st Mastiff's You-Tube " any failure you meet is never a defeat; merely a set up for a greater come back " Asus||i7x5930k||16gb3200||GTX10808gb||ATX1200Corsa ir||CBTitanium7.1||Win10x64||TrackIr4Pro/ir||gladiator pro mkII||siatekpedals||X52Throttle||G15Keyboard/RazerMouse|| 32"LCD||2x7" lilliputs,1x9inc Last edited by GF_Mastiff; 01-17-2012 at 05:41 AM. |
#2
|
||||
|
||||
![]()
@Kittle
Can you clarify what do you mean by this: "I had a CTD at the end of a campaign mission." Did you click stop mission when it happened? Can you confirm that there was some fighting going on with AI involved anywhere on the map? And last but not least, are you sure that this is the correct error log, cause it states that it is dated: Local Time = Sat Jan 14 09:17:15 2012 Was hotfix even published before that?
__________________
A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away. |
#3
|
||||
|
||||
![]() Quote:
In the mission, there was fighting with the AI. I do not think the hotfix was published prior to that, it is possible I had the wrong file. I am pretty sure it was when I clicked on apply at the end of mission that it CTD. |
#4
|
||||
|
||||
![]() Quote:
Was there a log.lst file generated (filesize could have been 0)? Try this: Code:
LOG=1 LOGTIME=0 LOGFILE=log.lst LOGKEEP=1 You might want to delete this file from time to time if it grows to large.
__________________
A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away. |
#5
|
||||
|
||||
![]()
It was a DGEN campaign. Here is the eventlog.lst file that was created.
[Jan 17, 2012 2:28:59 AM] Mission: campaign/de/DGen_C_Rzhev42doe3/21230.mis is Playing 10:45:00 Mission BEGIN 10:45:00 II_JG54001(0) seat occupied by Player at 33262.945 72234.586 10:45:00 II_JG54001 loaded weapons 'default' fuel 100% 10:45:00 II_JG54001 in flight at 33284.09 72199.55 10:57:10 296IAP011(0) was wounded at 46299.49 72372.9 10:57:10 296IAP011 damaged on the ground at 46299.49 72372.9 10:57:10 296IAP011(0) was killed by II_JG54000 at 46299.49 72372.9 10:57:27 296IAP010 damaged on the ground at 48685.582 71940.91 10:57:27 296IAP010(0) was killed by II_JG54001 at 48685.582 71940.91 10:57:38 296IAP011 shot down by II_JG54002 at 45619.98 74680.22 10:57:52 296IAP010 shot down by II_JG54001 at 48487.125 71040.23 11:00:20 g01000 landed at 33096.383 73270.81 11:02:36 34BAP001 damaged on the ground at 42663.426 87380.07 11:02:36 34BAP001 damaged by II_JG54001 at 42663.426 87380.07 11:02:41 34BAP001(0) bailed out at 42689.414 86997.3 11:02:42 34BAP001(1) bailed out at 42701.605 86888.18 11:02:42 34BAP001(1) was killed in his chute by 34BAP001 at 42707.61 86841.73 11:02:42 34BAP001(0) was killed in his chute by 34BAP001 at 42705.793 86850.38 11:02:42 34BAP001 shot down by II_JG54001 at 42707.914 86838.72 11:05:05 34BAP011(1) was killed by II_JG54001 at 43597.44 78548.836 11:05:06 II_JG54001 damaged by 34BAP010 at 43552.016 78563.45 11:05:09 Mission END I figured this was just the things that took place in the mission. The actual CTD took place in the debrief screen, after the mission had ended, but only a few seconds after. Will add this to my conf.ini to see if I can catch any future errors. Thx! |
![]() |
Thread Tools | |
Display Modes | |
|
|