Running an AMD system? Post your specs for the devs to fix...

[naomha]

Asus Sabertooth 990FX Gen 3 mobo
Dual Sapphire Tri-X R9 290s in Xfire (have tried with Xfire disabled as well)
AMD FX 8350 BE
8GB Gskill Ripjaw
Win7-64
Logitech G510
Logitech G502

Won't get past "log-in" screen. Constant crash after crash.

[dangus mcgrangus]

OS: Windows 10
GPU: Geforce GTX 650 Ti Boost
CPU: AMD FX-6300 (I'm aware of the issue with AMD GPU's, but I'd like to know if the problem extends to processors as well)
RAM: 8 GB
Motherboard: MSI 970A-G43

Takes 5-10 minutes to load the main menu, even on lowest settings game rarely reaches 30 FPS, and FPS will still drop to single digits for no apparent reason.

[TrixAre4FatKids]

I7 5960X @4.8ghz
32GB corsair vengance
500gb samsung evo ssd
crossfire x3 R9 390's

I play just fine! im wondering if its a AMD cpu prob

[Old Man Light]

Ursprünglich geschrieben von Kubin:

AMD Athlon II x4 641 2,8GHz
8GB DDR3 1600MHz
Sapphire Radeon R9 280 3GB Dual-X

holy crap dude, that CPU is bottlenecking that GPU.

[mschol]

Intel Core I7 6700k 4,0Ghz
24GB 2100Mhz DDR4
GIgabyte GA-Z170XP-SLI
Sapphire Tri-X OC R9 290 4GB

Seems to be running fine while walking and some shooting until i start creating big chaos (for example: somewhere half way in the vis electra mission it crashes)
i dont have a screenshot of the exact error but it is something like: (Again: This is NOT my exact error message)
[img]http://images.vfl.ru/ii/1426503536/3692dc09/8095599.jpg[/img]

i'm going to try the beta driver to see if that helps..

Update
I installed the beta driver from AMD and that seems to have solved my crashes..
no other problems noticed so far..

[thekaiser33]

Here are my computer specs. Game is so slow I can't play it.

Corsair XMS3 CMX8GX3M2A1600C9 8GB Desktop Memory Module Kit - DDR3, 2x 4GB, PC12800, 1600MHz

Gigabyte GA-880GM-D2H AMD 880G Motherboard - Micro ATX, Socket AM3, AM 880G Chipset, 1600MHz (O.C.), SATA 3.0 Gb/s, RAID, 8-CH Audio, Gigabit LAN

AMD Phenom II X4 965 Black Edition AM3 CPU HDZ965FBGMBOX - 3.40GHz, Socket AM3, 6MB Cache, 2000MHz (4000 MT/s) FSB

Galaxy 55NGH8HX4NXK GeForce GTX 550 Ti Video Card - 1024MB, GDDR5, PCI-Express 2.0 (x16), 1x HDMI, 1x DVI, 1x VGA, DirectX 11, SLI Ready

I have no problems with Just Cause 2.

[Gandalf the Grey]

i7 4790, R7 370 4 gig, 16 gig RAM.

[Big Rhonda]

i54430

HD 7870

G.SKILL Ares Series 8GB

I downloaded the most recent drivers today and at about 200 meters out, I only see triangles of land....

[Internet Explorer]

i7 4770K @ 4.2GHz, 16GB RAM, 2x Sapphire R9 290 4GB each, game on SSD, Windows 8.1, 15.11.1 drivers.
Suprisingly no problems other than non working Crossfire, and ocasional FPS drops to ~30.

[Geheimen]

FX-8120 3.1 Ghz
R9 280 3GB
8 GB RAM
7200 RPM HDD
Windows 10

Before booting the game, my pc was using only 2 gb of RAM. While ingame, it uses nearly 6.5 gb, and I also noticed that Windows compresses some of that memory. There's a process named "System and compressed memory" which was using 200 mb before opening the game; when ingame its memory usage went up to 1.5 gb, while the game itself was at 2.8 gb.

The game runs at 35-40 fps. It drops below 30 to like 25 fps for a couple seconds when there is an explosion in an open area. It drops to 25 and STAYS like that for 10 seconds when I destroy a bridge. Also, changing my graphics settings didn't seem to change anything at all. I'm running at the lowest configs right now pretty much like I ran in very high. Cutscenes run great though, averaging 52-60 fps with 60% gpu utilization (the game itself uses 24% of the gpu).

Also, when I'm moving "fast" (e.g. using wingsuit or driving a car) the game stutters and drop to as low as 20 fps. I'm guessing texture streaming problems.

[Slpater]

amd fx-6300
amd raedon r9 280
8gb ram

[Lacadis_Skren]

Running:

OS: Windows 10, 64-bit
CPU: AMD 9590 x8 (slowed to 4.2 gHz)
GPU: AMD R9 295x2
RAM: 32 Gig

Running the Beta AMD Drivers; Landscape in game is best described as Triangle Hell. Did have a CTD while storming a base, however the game ran for hours without issue (aside from Triangle Hell) in a sitting prior.

[Tohur]

Intel Core i5-4460
SAPPHIRE Vapor-X Radeon R9 280X 3GB
CORSAIR Vengeance 16 GB DDR3 1600
Windows 10 Pro

Game most the time runs at or around 60fps with most settings on Very high or high. sometimes though a get stuttering on reward screens after completing missions ETC and also with the leaderboard crap. also seems to me the cutscene's are runing at 30FPS as i can see a big FPS difference between the game and its cutscene's

[†AMD Prophet†]

AMD FX8350 @ 4.5 Ghz
AMD R9 380 4GB
8GB 1600Mhz DDR3 Ram CL9 G.Skill Aegis
Gigabyte 970 UD3P
500 Gb Seagate Sata3
Be Quiet L8 630W
WIndows 10 Pro

Game runs fine, driver version 15.11.1 Crimson Beta.
Playing on high/very high settings, getting 60-85 FPS (heavy explosions around 40FPS).
Disabled Vsync (30FPS lock?)

[FRUIT B]

Game works well for me at first, but FPS is a bit low and after a longer play session the game starts to stutter.

AMD 7950 (Gigabyte Boost edition with 3gb of VRAM)
8GB DDR3 RAM
Intel i5-4670k

[naomha]

Ursprünglich geschrieben von thekaiser33:

Here are my computer specs. Game is so slow I can't play it.

Corsair XMS3 CMX8GX3M2A1600C9 8GB Desktop Memory Module Kit - DDR3, 2x 4GB, PC12800, 1600MHz

Gigabyte GA-880GM-D2H AMD 880G Motherboard - Micro ATX, Socket AM3, AM 880G Chipset, 1600MHz (O.C.), SATA 3.0 Gb/s, RAID, 8-CH Audio, Gigabit LAN

AMD Phenom II X4 965 Black Edition AM3 CPU HDZ965FBGMBOX - 3.40GHz, Socket AM3, 6MB Cache, 2000MHz (4000 MT/s) FSB

Galaxy 55NGH8HX4NXK GeForce GTX 550 Ti Video Card - 1024MB, GDDR5, PCI-Express 2.0 (x16), 1x HDMI, 1x DVI, 1x VGA, DirectX 11, SLI Ready

I have no problems with Just Cause 2.

Dude, I don't think you even meet minimum specs for Just Cause 3. You may, but it's definitely the bottom of the barrel here. I know people play with what they have and can afford but I'd definitely be saving up for a cpu upgrade first. I love the old Phenom X4 cpus. I still have my 955 BE in an extra computer I use for testing, etc. You're definitely the low spectrum though.