Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Nvidia GTX 1060 W10 x64
It worked a month ago....
When I started the game today, there were bizarre graphics issues. The game ran with constant flickering and tears and stayed windowed no matter what the setting. I reset all graphics to default and that seemed to fix the display issues, but then the crashes started, immediately preceded by intermittant second long freezes.
Nothing had an effect and the problem persists.
Oh and OBVIOUSLY it goes without saying that you should make sure your video drivers are all up to date, right? ;)
__________________________
Miscellaneous Instructions:
I. Running Game On Windows 8:
Step 1: (avoiding Fatal DirectX Error)
Right click on the steam icon of JC2 and go to properties>Set Launch Settings
Type the following:
/dxadapter=0
And it should work. The problem occurs when your system has two graphics cards installed and JC2 gets confused. (Edit: ***by the way, this worked for me even though I only have one video card installed!***)
Step 2:
1.4 validate the game files.
Go to your steam library, right-click on Just Cause 2, select ‘Properties’ -> click on the ‘Local files’ tab and select ‘Verify the integrity of game cache’
Step 3: This is to get your graphics card to render the game
1. Download Nvidia Inspector from: http://tinylink.net/nvidiainspector
2. Open Nvidia Inspector
3. Click the button to the right of DRIVER VERSION.
4. From the PROFILE menu, select JUST CAUSE 2.
5. Scroll down the window until you find: Shim Rendering Mode Options per application for Optimus.
6. Click the text to the right, scroll to the top of the dropdown, and select SHIM_RENDERING_OPTIONS_DEFAULT_RENDERING_MODE
7. Click APPLY CHANGES in the top right-hand corner.
8. Run your game
**Note: Program is copied to a folder in the directory this .word file is in.
Something apparently happened in the last month or so to break the game for a number of us. It's extremely unlikely that there has been a JC2 update given its age. An OS update may have done it, but the OP and I are on different systems - Win 7 and Win 10 respectively. Driver updates could also be at issue, but given that the OP is AMD based and I am Nvidia, this seems very unlikely. I don't know what else could be at play.
BTW, the tinylink above results in a 404 error on tinylink.net. It was otherwise easy enough to find with a Google search.
My best guess is that the issue could be related to an update of a core Microsoft service, such as Directx or a .net redistributable. That could be both OS version independant and graphics driver independent. It would put me at the mercy of either Microsoft or Avalanche to address in a future update and I'm not holding my breath for that to occur.
It is a shame because, before the release of JC3, JC2 was my all time favorite game.
I hear you and I am not sure what to say. Have you tried running the game on another PC, maybe one a little older? What bothers me about this is that JC2 is one of my all time favorite games, but Avalanche does not have a history of good support for this game. Making me wonder if, unlike games like Saints Row titles, or any of the GTA PC games (even the old ones like III, VC, and SA) as technology advances, games like JC2 may simply become unplayable, never to be supported again.
Part of me thinks there has to be a solution, but if MS updates Windows to new versions or even just updates to current versions, and NVIDIA/RADEON are also constantly changing, then it becomes dependant on the developers of these games to tweak them to make them compatible.
If Avalanche is unwilling to make minor changes to insure compatibility, then games like JC2 won't just be relegated to "past their prime cult followings" anymore, but simply and completely be dead.
The two things which cause consistent crashes for many people are:
Decals
Bokeh Filter
I see lots of people claiming they tried disabling decals, but not so many who have done both. Personally it was Bokeh that caused issues, not a single crash (or wierd red lines on the screen) since I disabled it.
I hear you! You know, I understand if they don't maintain games aggressively, like online games that go inactive and eventually serves get shut down. But to have a high profile development company like Avalanche just abandon perpetual maintenence at the most basic level is despicable. The thing is that in order to keep a game like this running on new machines, as tech increases, probably requires the most BASIC and easy tweaks that could be done by one or two guys in minutes. Obviously I am just guessing here, and basing a lot of this on the fact that ALL Rockstar games run on machines today, even a game like GTA III, which came out on PC way back in 2002, 14 years ago.
I am sure Rockstar has people that take a few minutes away from whatever projects they are working on to address bugs from even their oldest PC games on new rigs.
I never expeienced a red line, so they seem to be different issues. I still find it strange that the crash behaviour experienced by the OP and me was identical, though he says he tried disabling decals and it did not work for him. It was this crash behavior that pointed me to decals as a possible cause.
For those still experiencing crashes, the following may help confirm if it is a decal issue. Once the crashes started, I did not perceive a pattern. With enough play time a pattern began to emerge. The crash was always preceded by a one second freeze, followed by a game resumption for a few seconds and then the crash and error dialog box. Over time. I realized that the one second freeze was always triggered by a shot taken by me. However, the shots had to be close range to a game assett where a decal would normally drawn to represent a bullet hole. Shots from a distance would not trigger a crash. Similarly, shots from vehicles generally would not trigger a crash because you are normally firing from a distance. However, firing from a helicopter at low elevation and close range to an NPC did trigger a crash because he was standing in front of a building that would normally have decals drawn for the missed shots.
If any of this sounds familiar to those experiencing crashes, then turning off decals under advanced graphics options should work. This still remains a workarouind to a root cause that continues to be unknown. I would love to know what changed in the past month to make this an issue after six years of problem free play.