CTD in SP campaign: "Rats over Tobruk" mis.01

[Rostic]

I started single player campaign "Rats over Tobruk" mission 1 twice already and game crashes to desktop twice in same place.
When I'm reaching pre-last waypoin (last left turn from east to north) game crashes.

I put *.dmp files and broken *.trk file to this archive:
https://drive.google.com/file/d/1rbz...ew?usp=sharing

Interesting that I have two *.dmp files. Probably that "5018_20_03_21__09_11_53_384_796.dmp" created when I tryed to open broken *.trk file, but game did not crashed.



UPDATE:
Looks like it is EVENT dependent.

To replicate CTD do next steps:
1) Caches cleared.
2) Run mission.
3) Recording ON.
4) Autopilot ON for full mission.
4) Run it with x16 speed. AI will succesfully do their job, RTB and stop engine on the parking.
5) Wait for a few minutes for CTD.

Whole test should take about 5-7 minutes

[Josef]

Hi Rostic,

do you have a log file for those crashes? It's a file called log.txt which is located in the "\1C SoftClub\il-2 sturmovik cliffs of dover" folder in your Documents folder.

Look inside this file and if you find records related to those crashes (each record contains date and time), add this log to your dmp files. It can provide additional information about the problem. The more information you provide, the better chance the problem will be solved.

And you can report this problem also in the Bug Tracker. I don't know how often the developers check this forum. If it's reported in the Bug Tracker too, there is a better chance it will be spotted sooner.

Josef

[ATAG_Ezzie]

Hi Rostic - which mission# does the CTD occur in?

I started single player campaign "Rats over Tobruk" twice already and game crashes to desktop twice in same place.
When I'm reaching pre-last waypoin (last left turn from east to north) game crashes.

I put *.dmp files and broken *.trk file to this archive:
https://drive.google.com/file/d/1rbz...ew?usp=sharing

Interesting that I have two *.dmp files. Probably that "5018_20_03_21__09_11_53_384_796.dmp" created when I tryed to open broken *.trk file, but game did not crashed.

[Cybermat47]

Hi Rostic - which mission# does the CTD occur in?

Mission 01.

[ATAG_Ezzie]

Mission 01.

Ok - thanks Cybermat. May be another one caused by a recent change as i think players have played it OK before and gotten beyond mission #1.

I'll see if i can take a look tomorrow

Ezzie

[Rostic]

Hi Rostic,

do you have a log file for those crashes? It's a file called log.txt which is located in the "\1C SoftClub\il-2 sturmovik cliffs of dover" folder in your Documents folder.

Look inside this file and if you find records related to those crashes (each record contains date and time), add this log to your dmp files. It can provide additional information about the problem. The more information you provide, the better chance the problem will be solved.

And you can report this problem also in the Bug Tracker. I don't know how often the developers check this forum. If it's reported in the Bug Tracker too, there is a better chance it will be spotted sooner.

Josef

No... I did not know about "log.txt" so info about crash lost, because I restarted game and that file was overwritten.
May be I'll give it a try again this evening...

[Rostic]

Due to next posts text in this post doesn't matter, so hided in spoiler...

Spoiler: 

Well I crashed it again but when I almost ended mission. Looks like it is time dependent (duration)...

I replayed this mission three time.
1) Recoding OFF. Autopilot ON for full mission. Played with x16 speed and AI succesfully did their job, RTB and stopped engine on the parking... But the route AI did was a bit shorter, so I started mission again (game restarted caches cleared).
2) Recoding ON. Autopilot ON for take off until AI shotdown enemy AI, then manually flown by my initial route. Also with time multiplier (varying x4 - x16). And no crash again... but in log I saw some messages about errors with sound engine. I did not done copy for that log because game not crashed so no logs ((( So I guess maybe proble with sound engine so I decided to fly mission with constant time speed (x1).
3) Caches cleared. Game restarted.Recoding ON. Autopilot ON for take off until AI shotdown enemy AI, then manually flown by my initial route. When I arrived to airfield I switched on autopilot an AI laned aircraft, taxied to the parking... and second later CTD.
No usefull info in log. Look like it is not saved to disk on crash and cached data lost. Only this were in log from moment I ran mission

------------ BEGIN log session [2021-03-20 14:22:43] -------------
[14:23:10]
[14:23:10] =================================================
[14:23:17] Loading mission $home/parts/tobruk/mission/campaign/campaign02_Rats_Tobruk_29_jun/73Tbk_msn_1_rel.mis ...
[14:23:18] Load landscape...
[14:23:23] Load bridges
[14:23:23] Load static objects...
[14:23:27] [0] ERROR [VEHICLE] RoadSegment: Two waypoints are too close at next-x[111883.53] next-y[193717.23] x[111883.53] y[193717.23]
[14:23:27]
[14:23:27] =================================================
[14:23:27] RoadSegment: Two points are too close..
[14:23:27] =================================================
[14:23:31] Server: ACG_Rostic will fly for the Red forces.
[14:23:34] Mission loaded. time = 16.675
[14:23:36] Battle starting...

This is my route:

P.S. By the way. Why not force flush data to log files on exception before game ends running?
I mean to do something like:

main () {
try {

// all game code here...

} catch() {

// Unknown exception....
// flush all opened log files here

}
}

[Rostic]

Hmm..... I ran it 4th time and new CTD.

Caches cleared. Recording ON. Autopilot ON for full mission. Played with x1 speed and AI succesfully did their job, RTB and stopped engine on the parking. Then I just went for a tea break, and when I returned I saw windows desktop, instead of Hurricane cockpit.

Will try the same with time speed x16....

[Rostic]

Well 5th run and another CTD. And looks like it is EVENT dependent.


To replicate CTD do next steps:
1) Caches cleared.
2) Run mission.
3) Recording ON.
4) Autopilot ON for full mission.
4) Run it with x16 speed. AI will succesfully do their job, RTB and stop engine on the parking.
5) Wait for a few minutes for CTD.

Whole test should take about 5-7 minutes

[TWC_Birdtail]

Hi Rostic,

do you have a log file for those crashes? It's a file called log.txt which is located in the "\1C SoftClub\il-2 sturmovik cliffs of dover" folder in your Documents folder.

Look inside this file and if you find records related to those crashes (each record contains date and time), add this log to your dmp files. It can provide additional information about the problem. The more information you provide, the better chance the problem will be solved.

And you can report this problem also in the Bug Tracker. I don't know how often the developers check this forum. If it's reported in the Bug Tracker too, there is a better chance it will be spotted sooner.

Josef

Just out of curiosity.....how does this file work.....just looked at mine and the record starts Aug 2018 and ends Jan 2020. Should one delete this from time to time, should it be logging new every game start?????

[Josef]

Just out of curiosity.....how does this file work.....just looked at mine and the record starts Aug 2018 and ends Jan 2020. Should one delete this from time to time, should it be logging new every game start?????

Hi TWC_Birdtail,

there are several modes for this file. You can set them using several parameters in your confs.ini file which is located in the "Documents\1C SoftClub\il-2 sturmovik cliffs of dover" folder. These parameters are in the section called [Console].

LOG=0 - This setting turns logging off. Nothing will be recorded in the log file.

LOG=1 - This setting turns logging on.

LOGKEEP=0 - I suppose this setting forces the game to remove entire contents of the log everytime the game is started. Data from previous game sessions is not preserved. The log file is much smaller then.

LOGKEEP=1 - This setting should do the opposite - older records from previous sessions are not deleted, new records are appended at the end of the log. The history is kept but the log can become quite big after some time.

This log is not necessary. If there are no problems, it can be turned off. This may increase game performance slightly. But if some problem appears, the information recorded in this log can help to find the cause of the problem.

This is how I understand what has been explained to me by more experienced users. I may be incorrect in something here.

Josef

[ATAG_Ezzie]

Well 5th run and another CTD. And looks like it is EVENT dependent.


To replicate CTD do next steps:
1) Caches cleared.
2) Run mission.
3) Recording ON.
4) Autopilot ON for full mission.
4) Run it with x16 speed. AI will succesfully do their job, RTB and stop engine on the parking.
5) Wait for a few minutes for CTD.

Whole test should take about 5-7 minutes

Hi Rostic

I played mission 1 on AI and the AI landed / taxies / shut down at the end of the mission. The 'hit esc to exit' message came on and i changed the speed to 16x. After maybe 30 - 60 seconds of 16X i had a CTD.

Not sure how to approach this issue. It doesnt sound like an FMB issue and if most players hit esc when the message come up they wont get the CTD it seems.

Are you able to replicate the same issue on Mission 2 or any other mission (ie land, shut down, wait for the hit esc message and then go to 16X speed?

I've flown Mission 1 several times now and cant replicate the first CTD you mention in post 1.

If anyone else is willing to assist could they play mission 1 of the SP Rats over Tobruk campaign and see if they can replicate Rostic's CTD pls?

Thanks

Ezzie

[Rostic]

Did it even simplier way.

1) Started the mission.
2) Set time speed x16.
3) 4-5 minutes an CTD.

[Rostic]

Did it even simplier way.

1) Started the mission.
2) Set time speed x16.
3) 4-5 minutes an CTD.

Same with the mission 2 of this campaign. 4 mins on parking with time speed x16 and CTD. Will try the same with time speed x1.

[Rostic]

Same with the mission 2 of this campaign. 4 mins on parking with time speed x16 and CTD. Will try the same with time speed x1.

Did the same with normal time speed (x1). Just started the game (mission 2). Waited more the 70 minutes and nothing happened.

Then I restarted PC. Started only steam and game. Started mission 2. Switched on AI autopilot. Game time speed normal (x1). Since 15 minutes my aircraft was damaged and it fall down in to the water. I switched view to friendly AI (wellington) and since 5 minutes CTD happened.

Probably other missions should be tested but this process are so time consuming.....

[Rostic]

And new test.
1) Remove game.
2) Remove everything from "C:\Users\Rostic\Documents\1C SoftClub"
3) Reinstall game
4) Reinstall latest graphics drivers (with option "clear/fresh install" (not sure how this option written in english version of drivers)).
5) Restart PC
6) Run game
7) Run first mission, game time speed normal (x1)
8) AI autopilot switched ON
9) Wait about 30-60 minutes and CTD.

[Rostic]

Additionally ran first missions from "Cliffs od Dover" and "Desert Hawks" with time speed x4. No problems...
Maybe problem some how related to assets used in "Desert rats"????

[Josef]

Hi,

I tried the first mission of the Rats over Tobruk campaign 4 times with the latest version 5.018 today.

I experienced a game crash in first three runs. It happened shortly after the mission start in two cases, I guess after some 4 or 5 minutes. The third crash came much later in the mission. The fourth try was running without problem. I stopped it after some 120 minutes. All these runs were made in the time x16 mode.

I can just guess but the problem may be related to some event which may or may not happen. I mean something random, for example that some object is destroyed or something like that. When this event doesn't happen, the game doesn't crash.

I noticed one thing during 2 of my 3 crashes. A message saying something like "Bombardier was dispatched by some zwilling AA gun" was displayed shortly before the crash. I can't say what that message was saying exactly because it was shown just briefly. The crash followed immediately after this message appeared. I didn't see any reference to some aircraft which that bombardier was in. That's strange because the game always shows aircraft code when a crewmember is killed. So I'm thinking if this can be a trace leading to the cause of this problem. It may be. Or it may be a complelely wrong direction.

There was no useful information in the game log in this case.

I'm afraid this will require someone from TFS to look at it. Artist probably. He was investigating game crashes during the beta testing.

Josef