plumpblumpkin
Member
The camera controls and fov for Vehicles is an absolute abomination. They better give us better control over that in the patch...
The official blog made a post about the performance issues people are having and are committed to improving as much as they can.
https://justcause.com/en-us/blog/a-message-for-our-players
Anyone know how to disable the intro movie with Rico sitting on the beach? It was cute at first but has since become annoying.
Anyone know how to disable the intro movie with Rico sitting on the beach? It was cute at first but has since become annoying.
The camera controls and fov for Vehicles is an absolute abomination. They better give us better control over that in the patch...
What kind of swollen asshole looks at that and says "Yep this is great!" then signs off on it.
Anyone know how to disable the intro movie with Rico sitting on the beach? It was cute at first but has since become annoying.
Probably the same clown that thought it was a good idea to force integrate online leaderboards for a Single Player game. I don't think the public was really asking for this feature?
I assumed it was loading in the background. Are you sure it isn't?
If it's not loading, I'd love a way to disable it.
For anyone wanting borderless windowed mode, just add these to the Steam launch options for Just Cause 3:
Code:/windowed /borderless
Anyone here tried it with a 2 GB 660ti?
I probably won't buy it until I change my GPU but I'm curious
2600k @ 3.8ghz and MSI Gaming 980Ti
3440x1440, max settings with FXAA. For some reason I can't get Bandicam to show FPS but it's butter smooth.
It was NEVER cute. I have a very rational hate of un-skipable logos and intros, and this is the worst one in recent memory. It'd be one thing if it was masking a load to the seamless main menu, but no, it just takes FUCKING FOREVER to pan out from that DUMB. FUCKING. LOGO. Then the waiting for the explosion, the "cheers" then more waiting before it tries to connect to the server which then takes you to a loading screen.
HOLY. SHIT.
What kind of swollen asshole looks at that and says "Yep this is great!" then signs off on it. It's a technically demanding game on PC, that means I have driver level settings that need changing, bits that need testing, statistical overlays that need configuring, all of which need a fucking restart of the game leading to me spending more time in loading screens than in game.
FUCK.
OFF.
Yep I hear you. I stare at my HDD light and see no signs of activity. Also as I mentioned many times in this thread, the game has a pathetic FoV that makes everything moot for me anyways.The state it was released in is still disappointing. I've yet to play more but I fully expect my game to crash at some point like many other people are reporting.
I've tried quitting and restarting to see if the initial loading time (once to get to the menu and launch the game) is still as long as sadly it is. No disk activity, strange.
This makes me feel nostalgic for a time when games did not ship with so many issues.
I'm almost positive the game is loading behind that screen.
A 2015 AAA game with no SLI support is abysmal. There is simply no excuse for it. Was really expecting performance similar to Mad Max but man was I in for a surprise! The game performs horrendously on one GPU at 5K (doh!). This Avalanche (of shit) Studios is a sell out like most studios.
Not only that, the game for some odd reason doesn't seem to sync saves across my rigs - I had to restart the game on my RoG Swift rig - sitting through that terrible intro.
Also, Afterburner OSD doesn't work - whenever I try to take a screenshot, I get a black screen instead.
Just Cause = Just Shit.
This is game is really a buggy mess.
1.) Soundbug. Every time the game starts I get loud static like noises on my headphones for a couple of seconds. First time they 'shocked' the shit out of me.
I was able to fix that issue by starting the game in windows 7 compatibility mode + admin.
2.) Vsync isn't working. Screen tearing all over the place. Extremely annoying, even unplayable.
Fixed by locking the framerate to 60 with RTSS and setting Vsync via drivers.
3.)No borderless window mode... This is a crime in the modern day 'n age.
Tried to fix the problem by adding /windowed /borderless to the start options. Works for some time but then the game decides randomly to switch back to fullscreen mode. For whatever reason.
4.)Annoying texture flickering from time to time.
Apparently global illumination is causing this... *sigh*
5.)Unsteady performance. I am not even sure it's CPU related. I can't even reproduce the issue. Sometimes the fps drop to 30 for one, two seconds, sometimes it doesn't.
6.) First time loading takes long, even on a ssd.
This game feels extremely rushed to me, I wouldn't recommend it.
I5 3570k @ 4.3 ghz
970 @ 1400mhz
16gb ddr3 2400
samsung 830 ssd (granted old, but I had no reason to upgrade so far)
Win 10
Based on the screenshots I've seen in the PC Screenshot thread, Just Cause 3 does not look very good at all, and certainly not good enough to justify its performance issues.
I don't understand why people expect similar performance to mad max?
This game is doing so much more than mad max so why would you expect your performance to be the same?
Granted, it's not optimal at the moment and there are some visual bugs but it's far from the hyperbole being thrown about on this page.
If you expect a GAF thread like this to be without hyperbole, I have bad news for you.
Has anyone else had the game just not load the entire ocean? Like, it's still there, you can still swim, but it's completely invisible; you just see straight through to the seafloor. That happened to me for an entire play session![]()
Go to ProfileTemplates dir in RTSS folder and copy any GameWorks profile cfg (BatmanAK.exe.cfg for example) to JustCause3.exe.cfg. JC3 being a GW title uses the same (strange I gotta say) mix of both D3D10 and D3D11 rendereing and this freaks out the AB overlay.
No idea how anyone can using the wingsuit for more than 5 minutes and call this game anything other than gorgeous.
Nah, it's far from a "buggy mess". All the issues you've described are really minor and have easy solutions. A couple of patches will fix all of this.
wat?Just Cause 2 was very problematic for many users back in the day because of its very detailed visuals.
I don't think the case we have here is very different
Impressive looking games have steep hardware requirements, nothing new.
Only thing I'm bitter about is the flickering when GI is enabled.
wat?
Just Cause 2 ran fine on launch day on my old laptop with a Core 2 Duo P7350 at 2.0 GHz and a 512 MB 9600M GT
For an old laptop, you may have wanted the low-quality chart instead:
However, it's still only 20 fps.
It's 20 fps on a 9600GT not on a 9600M.
I tried to enable MFAA from the Nvidia control panel as well. I'm pretty new to the PC scene but I swear it looks slightly better, call me out if I'm crazy.
I would like to think that people who have the ability to purchase hardware capable of playing at resolutions at 4K and beyond would have the ability to use logic and reasoning.
Apparently not...
You can't. It doesn't upload saves to the steam cloud. Something that even JC2 did...Thanks for that - got it working!
However, I cannot get the game to sync the saves through Steam?!?
Any idea how to fix that?
For an old laptop, you may have wanted the low-quality chart instead:
![]()
However, it's still only 20 fps.
If I remember correctly I played it at 1280x800 (native resolution) at medium settings and I'm pretty sure I got around 30 FPS lolActually, it looks playable and can manage 40-60 fps at low resolution, which that person might have been using: https://www.youtube.com/watch?v=N2xM81n40V0
This is correct, MFAA only works if the base AA applied in game is MSAA.I could be wrong, but I'm pretty sure MFAA only works in conjunction with MSAA not SMAA.
Nvidia MFAA pageNvidia MFAA page said:Simply select 2xMSAA in a compatible game and enable MFAA in the NVIDIA Control Panel.
For an old laptop, you may have wanted the low-quality chart instead:
![]()
However, it's still only 20 fps.
They bolded this:He was disagreeing with the notion that it was a demanding game, so I figured max settings benchmarks were more appropriate and included the 1280x1024 results for good measure.
And replied with this:Just Cause 2 was very problematic for many users back in the day because of its very detailed visuals.
My interpretation was, they were disagreeing with the notion that it was "very problematic" for many users. As shown in the video earlier, 40-60 fps could be reached even on a laptop with the same (or similar?) graphics card. To me that means it's not really "very problematic" since turning down the settings produces a smooth experience. Maybe I'm misunderstanding, though.wat?
Just Cause 2 ran fine on launch day on my old laptop with a Core 2 Duo P7350 at 2.0 GHz and a 512 MB 9600M GT
...which was at everything low, 1280x800 resolution. That's more problematic in my view since merely lowering settings and resolution can't bring the framerate up enough.Seems like 2500k at the base 3.3ghz clockrate isn't enough for this game. After noticing the odd freezes I describes on the first page I monitored my CPU and GPU usage and noticed the cpu reaches 100% and then the game freezes down to 0-1 fps for like a second. So I decided to try Overclocking it a bit and just increasing it to 3.5ghz made the stutters down to 0-1 dissappear, still got sub 10 drops sometimes but it seems to be actually playable now.
Albeit a bit worried about my cpu temps since I just got the basic cooler it runs at around 80C now which should be fine right? Really need to get an aftermarket cooler.
Thanks for that - got it working!
However, I cannot get the game to sync the saves through Steam?!?
Any idea how to fix that?
The new definition of a triple A game with graphical issues like not working vsync and buggy in game graphical options and sound issues: It's not a buggy mess cause a couple of patches are going to fix them. Okay then... everything is fine.
I could be wrong, but I'm pretty sure MFAA only works in conjunction with MSAA not SMAA.
GameGPU revisited JC2.