Mass-closing resolved issues not updated in 10 days.

Just so you know, resolved state allows for feedback right now.

can someone give a feedback if my patch works?

Was fixed yesterday.. patch will be distributed soon

Confirmed, no duped backpacks any longer.

Sure, I have.
What is situation in version 1.10?
Did you try other display mods? Fullscreen window for example.
Did you try latest graphic drivers?
Thank you for more info.

I have recently done a complete system rebuild, with everything new (cpu, memory, m/b, even the psu) except the gfx card. So i have tried again, and it's the same crash, running the latest version of Arma, and the error has now occurred in World Of Tanks, so it's not a problem with the software.

I have spent a long time on this, and I now believe it to be a hardware fault on a memory module. The reason it's taken so long to pin down is that arma is a heavy user of the memory on the card due to the details in high quality modes, and most other games were not at the time, but are starting to catch up now, so it's only hapenning in other games now.

The card is 16 months old, but the company I bought it from have confirmed they will still RMA it as it's a hardware fault, so assuming that goes ok, I think we ca close this issue.

Thanks for your help with trying to get this sorted out, and hopefully, I won't be raising another one in a few weeks when I have a new card!

Thank you for info.

Yes, just tried it, started playing the scuba showcase, and when i pressed M to bring up the map, it locked up.

Do you have still this issue after last patch? Thank you for info.

I had just tried Heroes and Generals, and I experienced the same crash as in Arma III, so I have tried experimenting again.

The crash seems to be related to resolution, when I run a full resolution (2650x1440) version of the benchmarking test you recommended it crashes, but at 1920x1080 it's stable. Heroes and Generals also seems stable at this resolution, but Arma still crashes. I have tried dropping it right down to 1600x900 but it locked up on loading, and I couldn't even get into the game.

Other games seem to run fine at the full resolution.

I'm guessing you have no more suggestions for me on this issue?

Right, cancel my last, it still crashes, but it takes longer. I was able to play through a whole showcase mission, for the first time. Then crashed on the scuba one.

Ok, benchmarking failed on test 22 (I think), so did some more investigating.

It looks like if I have FSAA turned on (at any detail level) it crashes every time (usually when changing to a map).

All other graphics settings appear fine so far.

Any other suggestions for this issue?

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.

Unable to reproduce and nothing is helpful in .rpt files. Do you have hw overclock? Did you try some DX11 benchmark?

No, all HW is stock. What DX11 benchmark would you like me to run? I can try anything if you think it'll help.

Files uploaded here as requested. Just tried the game again, still the same issue.

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.

http://feedback.arma3.com/how-to-user.html.html

OMFG

I suppose the fifth one is the one on the dry lake. That's just a runway, not a whole airport.

You can make pretty much everything disappear, from buildings to a huge rock formations by turning slightly.
An old "feature" we have had since the early ages (iirc this was a problem in OFP as well, 100% it was in Arma-series). Nevertheless, voted up.

@AD2001
You haven't roamed enough. There are 5 airports on Altis. ;)

AD2001
Intl airport, aac airport locted south of intl airport, one on the mountains, one in SE and one in NE. I don't count the salt lake, it's just a placeholder for me. ;)

O.o A fourth airfield. I didn't know it was there. Now you have solid proof that Altis is goddamn huge.

Big thank you, Astaroth! Drivers has re-installed completely, problem solved.

Astaroth helped me solve the problem.

Hi, try disconnect gamepad before start of Arma. It looks that is issue with gamepad or software for your gamepad.

Error: JoystickDevices - CoInitilizeEx return 80010106
Invalid Joystick Axis!

type=602 (6), dwOfs=0, name=Îńü 6
GUID = a36d02f3, c9f3, 11cf, ...
wUsagePage = 1, wUsage = 0

Detected Joystick: PS(R) Gamepad

0 ... Ось X [1,30]
1 ... Ось Y [1,31]
2 ... Ось Z [1,32]
5 ... Вращение вокруг оси Z [1,35]

Ok, i have disconneted the gamepad, but in new .RPT file i've got this error:
Error: JoystickDevices - CoInitilizeEx return 80010106

P.S. Have no more gamepads/joysticks is connected to my PC. Report file attached.

This is from my .rpt file, when game starts correctly. Sound and PhysX initialization is next step. Try reinstall sound drivers and PhysX drivers.
DX11 - Initializing DX11 engine.
DX11 - Using DXGI adapter 0 (detected in config).
DX11 - Using DXGI adapter 0.

• adapter description : NVIDIA GeForce GTX 660
• adapter vendor ID : 4318
• adapter device ID : 4544
• adapter subsys ID : 2216759363
• adapter revision : 161
• dedicated video memory : 2086993920
• dedicated system memory : 0
• shared system memory : 2147807232

Error: JoystickDevices - CoInitilizeEx return 80010106
Error: CoInitilizeEx (XAudio2-1st trial) return 80010106
PhysX3 SDK Init started ...
PhysX3 SDK Init ended.

DxDiag attached successfully. Folder in "AppData\Local" shared here: http://www.mediafire.com/download/r9e6ag9xh6n5tg4/Arma_3.zip

27.09.2013 - Reinstall not helped :(

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.

http://feedback.arma3.com/how-to-user.html.html

Firstly this is NOT the place for that, secondly what you are asking is a very serious matter, if you want any action taken then you're going to need prove in some form or another of this persons activities.

Seems to be fixed with latest patch/dev build.

Mass-closing resolved issues not updated in 10 days.

Sweet!

@ProGamer

"KA-56" would not make factions identical. It would make OPFOR more different from BLUFOR as it is focusing for attack power, while maintaining well the current roadmaps and designs.

The problem actually is currently in ground vehicles. Like BLUFOR has same turrets in many vehicles as OPFOR and same turrets are used then in many vehicles as well, what makes them very same kind. Even having a turret from Tunguska attached to OPFOR AA vehicle would have been more interesting than the current designs.
But mods will fix that probably fairly quickly. At least there is a change someone would present a new helicopters for both sides.

Why do you guys want each side to have the same vehicle classes? Variety is key. It is unlikely two major factions would have a counterpart for each vehicle they have.

PO-30 "Orca" is for transportation what has just small amount of unguided rockets and 6.5mm gatling gun (what has no use as it is too accurate and has too small caliber) and it is meant to be only for transportation and possibility to suppress enemy AA vehicle if suddenly such pops up front. There is a normal camo-variant and then there is black for "black-ops" missions.

Mi-48 "Kajman" is non-existing attack/transport helicopter what Kamov would never manufacture. Its main weapon is the 30mm gatling gun what is as well non-existent design. For secondary armament it has Scalpel unguided rockets (non-existent AFAIK) and Skyfire ATGM missiles.
Russia has abandoned the Mi-24 kind design where transport helicopter is used as attack helicopter. But for some reasons (probably because Mi-24 is so famous) BIS developers added a 8 person cargo space inside it. Mi-24 rarely fly with infantry inside and most times they are empty or on more un-common missions it is filled with extra-rockets and missiles for crew to load on mission area.
It as well includes a Kamov design contra-rotating rotor what gives better maneuverability, lift and speed than traditional rotor design with a tail rotor.

The picture in ticket is a illustration of the future Kamov design of Russia future helicopter plans, as Russia is focusing to update the helicopter fleet with newer doctrine in three steps. Finally transport helicopter is responsible for troop transportation and attack helicopter is responsible to support them.

The Mi-48 in game is clearly wanted to be Russian origin, but on 2035 Russia will have totally different plans than what Mi-48 presents.

It is not just about "game balance" that east side (OPFOR) needs a KA-56 kind helicopter by amounts, but because Mi-48 doesn't fit to future and its combination, even being interesting, is out of focus.
Even when today Kamov say they are searching contracts where buyer can have customization for helicopters, Mi-48 design just doesn't make a sense in current changes in doctrine on any east country.

The KA-56 would be a real attack helicopter on east side: Having a 16 Optically guided missiles (like Vikhr), 40x 80mm unguided rockets and 30mm autocannon (maybe dual) or 12.7mm gatling gun in rotating head and air/ground search radar top of the mast, pilots sitting side by side instead in tandem.

Mi-48 could be given even to independents if really a must.

If wanted to compare helicopters,
KA-56 would not be like AH-99 as it is not trying to be a "stealth helicopter" but a actual attack helicopter.
Even todays radar the AH-99 would shine on radar like Christmas tree in night. You can not hide the main rotor at all and even todays radars can pick up the air disturbances what rotors cause, so having a radar reflecting design and plating doesn't help against radars and you would need to counter them only by flying behind terrain and other objects what actually blocks the radar waves.
And KA-56 would not yet have a A-A missiles like what AH-99 has, while attaching a pair of IGLA-M to its wing tips wouldn't be bad addition ;)

AH-9 is used for attack and it has just rockets and miniguns, more firepower than what the Orca has.

MH-9 is used for transporting over a squad (6+2).

Orca is more like MH-9 but with weapons for emergency defense.

Then there is AH-99 what is more than what the Mi-48 is. Guided rockets and autocannon, anti-air missiles and more agile and it is alone more effective than Mi-48 with its only benefit of its AT missiles what has just more penetration than AH-99 rockets but still not much.

BLUFOR has then ghosthawk what is a bonus.

OPFOR is missing one helicopter class totally and KA-56 would fit to that category.

What we need is a massive transport helo for both blufor and opfor.
Chinook or Mohak for blufor and Mi8 or M17 for opfor properly modernized.

Both Blufor and Opfor require of new aircraft, it seems that 2 CAS aircrafts are coming, but nothing more. We should get some heavy vtol transport (Mv-22? V-280?) and a cargo vtol (C-130 vtol version, v-44 quad tiltrotor?).

apart form that as arziben have said they are practically balanced, despite that it's Opfor the one that has more options and advantages (Attack helicopter available to transport infantry while blufor's not, chopper has rockets while blufor's not etc...so maybe it's blufor the one that should get new aircraft, v-280 for example).

yup, forgot the xh 9s
the orca and ah 9 have the same armament, the ah 9 has double the rockets which is fine since the orca has missiles

to compare the roles:
BLUFOR _ OPFOR

ah 9 _ orca
mh 9 _ orca (black)
ghosthawk _ mi 48 kajman
blackfoot _ mi 48 kajman

the "advantages" of the blackfoot over the kajman are easily counterable by the big hunk of armor and armament that this aircraft can provide

and no, ka 56/58 wouldn't fill the missing category since this category is transport helicopter which is currently filled by the multi role attack helicopter that the mi 48 is

also this game isn't supposed to be balanced (which bis seems to have forgotten) so it's normal AND fine that the number, type and role of vehicles in each faction is different

what I get from this ticket is that you want to have the mi 56/58 in game in which case you should make a "feature request" ticket

BLUFOR has ghosthawk and blackfoot
OPFOR has orcas and kajman
GREENFOR has mohawk

and the kajman is far superior to the blackfoot as a ground attack helo

+1

Terminology corrected: the problem appears to be sound aliasing. The sound samples are bad. Why are the explosions these long sounds that sound like tyres bursting, rather than short, hard, explosive bangs?

Confirmed. Also happens when you are close to the tank.

Mass-closing resolved issues not updated in 10 days.

Recoil is too far through the model. The end of the gun will hit the ground.

Fixed in internal files.

I think your issue is because you have set autocenter=0 in the geo lod. Remove this.

Also I started a wiki entry here based on community knowledge, still WIP

https://community.bistudio.com/wiki/Arma_3_Ships_Config_Guidelines

My issue is not related to this one. I swapped USB hub with a different one and have not been able to reproduce the problem. No more issues with disconnects. Thanks for all the support!

From my past experience, either a faulty USB hub or under-powered USB hub. No pun intended, but the Saitek hubs long ago were faulty for some odd reason. The Saitek hubs were also non-powered hubs.

Ever since, I've only purchased powered USB hubs and those from well known manufacturers. (Which reminds me, I'm missing a powered hub around here. Shrugs.)

May be a completely different issue. The one we were dealing with in this ticket was about loosing controllers after entering the Configure - Controls menu.

If a controller is lost mid-game, please create a new ticket for that.

Thanks for the response. This is still occurring for me. All joysticks become unresponsive after several minutes of simulation. Then about a minute later they come back. TrackIR is not affected. I'm on the latest Steam dev branch.

For example,
In editor I create a helicopter and play the scenario. After about 5-10 minutes, stick and throttle not longer function but TrackIR still works. If I hit escape and wait about a minute, the stick and throttle become available again. The same will happen without hitting escape and waiting about a minute.

I wonder if it is related to Saitek. I will try an old Logitech controller tonight and see if it does the same thing.

https://forums.bistudio.com/topic/140837-development-branch-changelog/page-34#entry2939525

The game should no longer re-initialize the controllers when opening the controls options. Instead now there's a "Refresh" button in the controllers tab that allows you to re-init. the controllers manually.

Means the loss of controllers shouldn't be happening anymore :/
Could you please also try the RC branch?
https://dev.arma3.com/rc-branch
Steam branch access code: Arma3Update156RC

Still happening to me in 1.54.133597.

And, words fail to describe my level of sadness when it does.

This is still happening. Any chance for a fix?

Will be fixed on devbranch in coming days.