Page MenuHomeFeedback Tracker

Bad module info at specific locations
New, NormalPublic

Description

I have this old issue still in middle of 2020, but it seems that under a little bit different circumstances than others:
I am playing the basic campaign "East wind", vanilla no mods or anything. There are specific locations, which ALWAYS crashes the game, those are both during missions and in the camps, right now in GORI camp near the area of map and briefing.

I have tried all of the older advices, but with no effect. I have updated W10 and graphic drivers.

I have suspicion, that it is related to graphics of certain objects:

  1. for example at Gori camp, I tried to go backwards towards the area until I was stopped by the objects there. The game did not crash, until i started to rotate the view towards the objects.
  2. When I go to the same area in editor, no crash occurs.
  3. But, for example another crashing area which is at GPS 070183 on Altis is crashing even on clean map from editor. (there are some objects like two wrecked cars, pile of tubes etc.)

Please check the report and suggest something. The game is generally unplayable with this.

Thanks

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
10.0.18362 Build 18362
Category
Campaign Episode 2: Adapt
Steps To Reproduce

Just go near the specific locations/objects, like the briefing map at Gori camp, some random objects (definitely o mission related) in the middle of the woods etc.

Additional Information

I have suspicion, that it is related to graphics of certain objects, for example at Gori camp, I tried to go backwards towards the area until I was stopped by the objects there. The game did not crash, until i started to rotate the view towards the objects.

Event Timeline

INGSOC created this task.Aug 5 2020, 8:34 PM

Have you tried verifying the game data through Steam?

INGSOC added a comment.Aug 5 2020, 9:18 PM

OK, this solved this, I thought that I started with this few evenings ago, but apparently not. There was one damaged file.

Thanks