In addition to my previous post, as i kept shadow lines errors (black lines or triangles) on some modded units (RHS, Unsung), I downgraded to 355.60 ! No error with this "old" version of NVIdia's drivers. All versions above induce weird shadows on these units at each shadow setting.
Not sure to understand how compatibility works NVidia? BI? or NVidia/BI?
The facts are here!

I finally downgraded to 355.98 to get a stable durable NVidia config on my laptop.
I guess a problem with last W10 update + last NVidia drivers. These configs don't manage the 2 graphic cards in a laptop and probably try to enable stereoscopic 3D.
No need to downgrade W10 but NVidia driver.
355.98 works with many mods like RHS CUP R3F and more.

NB: Just remaining bugs on mod such RHS: Black line or triangle comming from primary weapon or RHS unit depending on distance and terrain mask.

I am getting this too. Did everything as said. No difference. Attaching my .rpt.
I have even totally reinstalled the game.

I have this error aswell, but it didnt fix that for me @Borgli

Fixed.
Rolled back game / graphic & content mods - no change.
Rolled back video / graphic drivers - no change.

BUT did find a little steam workshop mod (Russian Music) that was the cause of all my drama's.

Get rid of Russian music mod - Game works again.

Cheers.

Hello,

The game is unable to initialize a graphical subsystem. Possible solutions:

Update the graphics card drivers to a newer version.
Rollback the graphics card drivers to an older version.
Check the temperature of your GPUs and CPUs.
Disable the Steam Overlay.
Also try updating / reinstalling directx

I found out that last Windows Update enabled stereoscopic 3D in the Nvidia settings. That caused all my problems. Now that I turned it off everything works as before!

I have the same problem. Everything worked fine until 13th. I want to point out that I have Windows 10 Education and that I updated the OS (through Windows Update) between the game working (around the 11th-12th Dec) and not working (13th Dec). On startup the splash screen turns slightly red and it crashes. At the same time my graphics card driver will crash. All drivers are up to date. Maybe worth mentioning that I use 3 monitors.

DXGI removed also. I downgraded to 358.91 NVidia driver and it seems better. I don't know who is playing the tightrope walker, NVidia or BI, but it's very hard to get a stable non-regressive game!

Confirmed It isn't crashing to desktop any more thanks.

Should be fixed in tomorrow's dev, please check

Hey Everyone.

I have been doing quite a bit of testing with this issue, and so everyone is aware I host OzzyGaming.com Altis Life server. We have been plagued with these crashes. On average from 10 minutes to an hour at best.

I have done quite abit of research into what has been happening and One thing stands out, Windows.

As such I wanted to confirm my findings by setting up a server hosted under linux. So I purchased a VPS with Ubuntu pre-installed and installed my server on that. And the results were shocking to say the least.

Not one crash at all. Desync just as you'd expect from a low grade VPS server but that server survived without a crash for upto 7 hours where it was restarted normally.

This issue has been around since late July. Not sure why but there was evidence of this issue back then. So Bohemia Interactive this has something to do with the way ARMA is trying to store data to memory under a Windows Based environment.

Also anyone experiencing this issue. grab a VPS server with what you afford and or use HyperV to run ARMA under Ubuntu or other linux based OS

Uploaded crashes with performance v6 (Crash_withV6.rar).

addMagazines is the wrong command to be used on ammo boxes. Use addMagazineCargoGlobal instead

Okay, thanks for help!

Hello,
we're sorry for the inconvenience. This issue is caused by the Windows update KB3078601 and there is nothing we can do to prevent the issue at this time. You can either uninstall the update or wait for Microsoft to release a fixed version of the update.

BTW; If i'm not mistaken, AI crews have problems with detection enemies very close/next to the tank. This would help with that i think, beacuse this zone can be named "dead zone" as well. Please, do not ingore this ticket,
please fix this.

Still no reaction....

Please stop creating duplicate tickets, using allcaps, making assumptions of how things work and what it takes to change or fix something. It doesn't help us in any way to solve the issue faster.

Hello,
your system or graphic card can't render Launcher window. First thing you may want to try is to update your graphic card drivers.

If that doesn't work, try to run Launcher in safe-mode (press and hold Ctrl+Shift while you starting Launcher) and let it disable the hardware acceleration, or disable the hardware acceleration directly by using -nohwa command line parameter.

Just added Crash 6 and Crash 7 of the 12th December

Logs Uploaded Titles:
Crash 6 - 2pm 12th.rar
Crash 7 - 3pm 12th.rar

I havent got time unfortunately to upload any more logs but the server is crashing hourly.

Please fix this asap as alot of time is being spent checking on the servers and supporting the players effected by these crashes who mainly bought arma 3 just to play our servers (feedback we hear daily)

If you require anymore help please take time to speak with us and the servers directly (dwarden has me on skype), Unfortunately after Wednesday this week we will be reverting back to 1.52 and advising our players to do so also as this version was very stable.

Many Thanks

Next time try Ctrl + w

Any time I play on a KoTH server, or any server with tall towers. Once I open the hatch ( the windows you can open ) to shoot out of it the bullets just hit an invisible barrier near the bottom of the hatch without actually going outside.

Cannot reproduce had yesterday a firefight in a small tower had no problems. Please more information.

Please try reproducing the issue without the system allocator. Thank you.

I had this problem this fix seems work it did for me

https://steamcommunity.com/app/107410/discussions/1/523898291492147215/

Another reason is a game-technical one: sometimes your character puts the rifle on its back, for instance when using binoculars or pistol. The rifle goes on the right side which would interfere if the launcher was there.

So in the game you have 3 visible weapon slots, rifle on the right, launcher on the left and pistol on the leg.

Even though Arma3 looks very realistic sometimes, these weapon slots are the result that the Arma soldier is still a computer guy which needs some simple places to put stuff without these things clipping (visually overlapping) or using complicated weapon sling simulations.

It nice to find out though that launcher-left is realistic as well for r-handed people.

Cool! I figured there had to be a good reason for that -- Kudos to BIS for getting that right then! :D

Hi Moach,
The reason why you would carry the launcher or any other shoulder fire weapon on the opposite shoulder is it will interfere with you placing your rifle to your shoulder to fire it. Also in real world combat the weight of the launcher would pull your shoulder down and cause you to fire low and to the right of the target you are trying to shoot at. If you are on patrol and come under fire the first thing you would do is find cover and take the launcher off your shoulder so you could move easier under cover, and then return fire. You can pickup the launcher if you move or need to use it. In the game you are given a freebie and you can fire standing, kneeling or prone with the launcher never interfering with your movement or firing your weapon. I'm left handed in the "real world" and would carry everything opposite of everyone else. So I was always hitting someone with my rifle barrel in the head. Or while on the range during training I would have to use firing point #1 or I would end up with hot brass cartridges hitting my neck, and several times going down my shirt. The animation is correct for a right handed solider carry a launcher.

Note: I spent 6 years in the US Army 68mike and then 16 years in the US Air Force as a CATM Instructor. That is a Combat Arms Training and Maintenance Instructor/Range Master. I'm very familiar with both US, NATO and Foreign weapons, how to use them, repair them and of course carry them.

I don't even see how you could carry a NLAW on one shoulder like that. It would fall of constantly.
In FDF we're simply taught to carry it across the body on left shoulder with the nose pointing down.
It doesn't get in the way of your rifle and to take it off your back you simply swing it around to your right arm and push the clips in to release the strap.
Example in these pictures http://www.puolustusvoimat.fi/wcm/a09eb4804fb6dd9c9431b700a50fdfac/1/kuvitus-7924.JPG?MOD=AJPERES&CACHEID=a09eb4804fb6dd9c9431b700a50fdfac/1
http://www.army.mod.uk/images/central-panel/fusilier_and_nlaw_502x335.jpg

mega:///#!9s8VQRLD!qBdC1qreDdBogOcCO0UjtfBRoKKSUzS8D6H-KtzAiEg

The file is password protected. Could you please post the password? Thanks.

I am afraid, that is your personal problem.

Try to check and tweak your router-modem-connection or get another (new) router.

The developers can't do anything about your instable connection.

Hello, we are sorry you are experiencing issues with our game.
Could you please export your game log files from the launcher?

Steps on how to export logs from ARMA 3 Launcher:

1. Start ARMA 3 Launcher
2. Click Options menu
3. Drop down menu will appear
4. Select: Prepare Arma Troubleshooting error and save those files
5. A notification will pop up with the name of the generated file

Please note that the files might take a while to collect.

Attach the generated files to the ticket. If the files are too big please use some free file sharing service.

rgr that commy2 that is a bit smaller but that is still 3 commands and 2 more commands than we should need to accomplish this task.

BI devs, if this is not subject to change please close the issue. Otherwise could you please look into adding a way to at least suppress the errors so we can use param(s) as it was originally implemented?

I thought the whole purpose of param/params was to get rid off these errors in case of a wrong input. That alone made them one of the strongest commands I've had pleasure working with.

Now they are pretty much useless.

For those who are looking for alternatives - use BIS_fnc_param, it is slower than it's binary cousin, but will not give you errors.

@vbawol

params "_value", 13;

if !(_value isEqualType 0) then {

_value = 13;

};

This was done intentionally. The same happens with paramS.

"Since Arma 3 v1.53.132691, onscreen errors are displayed for when the input is of the wrong type or size."

See: https://community.bistudio.com/wiki/param

The alternative is to use the isEqualType familiy of commands.

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

Thanks, I see the note on the wiki now. It makes sense but would have been nice to keep it down to only one command vs three. Basically if there is any chance that a function will get invalid data you should not use param(s) anymore as it will work but throw errors.

This is what I came up with, for now:
_data = [];
_newData = _this select 0;
if (_newData isEqualType _data) then {

_data = _newData;

};