All the settings are on ultra and the FSAA cannot be turned on alongside with all ATOC settings otherwise its a complete blackscreen with no way out but a hard reset.
No error message either. {F22726} {F22727} {F22728}
All the settings are on ultra and the FSAA cannot be turned on alongside with all ATOC settings otherwise its a complete blackscreen with no way out but a hard reset.
No error message either. {F22726} {F22727} {F22728}
I have ASUS P6T motherboard, ASUS 7970, i7 920 (3.6ghz OC) and 6gb RAM.
No SSD only a normal HD.
Replicate by playing around with the FSAA and ATOC settings.
Strange thing is, I can load the game (showcase/multiplayer) with FSAA off, then while in game enable both FSAA with ATOC and it'll work. But when I quit the game it will freeze just like before or give me vertical lines.
Prior to this 7970 I owned a 5870 and that could run the game fine with FSAA and ATOC on, it ran slower but at least it was 100% stable. However that was prior to the 'Survive' update.
Other games like Metro Last Light, BF3, Serous Sam 3 etc, which have FSAA as well all work without issues. I have tried different drivers, re-installed the game and also formatted my pc.
We need dxdiag and files from this folder for solve your problem. C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package please?
When package will be smaller than 2,097k, so you can attach here. When package will be bigger, please use some free sharing service and post link here. Thank you.
I see only .rpt files. Do you have some .bidmp or bidmp files in this folder?
Thank you.
I only have .rpt files. I did a search for .bidmp files within my whole computer and none were found.
By the way I really appreciate the effort and response time from you guys.
Do all .rpt files correspond with this issue or only some .rpt files? I need some file, where you are 100% sure, that this issue correspond with this issue. If you are not sure, which .rpt file is correct, so could you reproduce this issue and upload last .rtp after this issue will happen.
Thank you.
I deleted all the old .rpt files then opened the game, changed the FSAA to x4 and ATOC settings to All trees/Grass.
Loaded a showcase and then the game froze with a plain blue screen. Hard reset was the only way out.
Checked the folder for new .rpt files and only one was found.
Yes, I have overclocked my CPU from 2.6ghz to 3.6ghz (with Noctua NH-D14 cooler) and my RAM from 1333mhz to 1580mhz (rated at 1600mhz).
It can be problem, because Arma 3 is very sensitive for overclock hw. Could you try some DX11 benchmark? One of the best is this benchmark http://unigine.com/products/heaven/ [^]
Free version is enough for test. Set DX11, tesselation and some high settings and let run it 20-30 minutes or more. Thank you.
I ran the test for around 25 minutes everything seemed fine. I have also benchmarked/stress tested with 3Dmark 11/Prime95 and they also ran without issues. Results for the Heaven Benchmark are below.
FPS:
36.4
Score:
917
Min FPS:
18.9
Max FPS:
84.7
System
Platform:
Windows 7 (build 7601, Service Pack 1) 64bit
CPU model:
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (3665MHz) x4
GPU model:
AMD Radeon HD 7900 Series 13.250.18.0 (3072MB) x1
Settings
Render:
Direct3D11
Mode:
1920x1080 8xAA fullscreen
Preset
Custom
Quality
High
Tessellation:
Extreme
As per the similar thread, I have the same problem:
Asus r9-280X Direct CU TOPII.
To make the problem "go away" and actually be able to play the game,
disable SSAO and Tree\grass option in the advanced options.
This doesnt "fix" the problem, just stops the crashes :O
I am debating RMA'ing my card.
Yeah I have seen a few forums with people having the same problems.
If you do RMA your card, and you get a new one and the problem remains the same. Then that will confirm that the problem must be Arma 3 not working with these ATI cards.
I still have hopes that Arma 3 will get a new optimization patch that will fix this. Only time will tell.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.