The statement was the revive system will get in as a module when its finished.

Does it mean it is going to be included as a payware module (or freeone one)? An advance module?

The whole issue is the same like in the other tickets the Server(or what ever) does not render the glass as broken so the doors are destroyed bu you cannot walk through. Same at the windows where you cannot shoot through because they are rendered as if they were there.

Still the same in this last update of 2mb. One rare thing was that I saw how it was ok in a moment in a version before this last patch.. but later I tried and was the same. Maybe the situation changes with time.

worth noting: I have read in other issue-tickets this seems to be related and vary according to whether or not the building has it's door open....

there's something comical about it... blast through window with a machinegun, nope - gotta open the door first XD

but it's indeed a bug - we're not shooting windows just for giggles (sometimes)

we got a war to win (or lose)

The 2mb was not a Arma update it was a BattleEye update.....

Known already.

added same error.

added second error. same error black screen

Thank you for the reply, after downloading those files this occured.

"Arma 3 Launcher Emergency Log

Arma 3 Launcher is unable to start due to corruption in a configuration system.
http://arma3.com/launcher/troubleshooting
http://feedback.arma3.com/

-----------------------------

System information

Date: 2015-12-07 03:54:57 / 2015-12-06 22:54:57 -05
Current dir: C:\Games\Steam\steamapps\common\Arma 3
Command line: "C:\Games\Steam\steamapps\common\Arma 3\arma3launcher.exe"
Version: 1.3.133.597
CLR version: 4.0.30319.42000
OS Version: Microsoft Windows NT 6.3.9600.0
OS 64bit: True
Process 64bit: False
Personal dir: C:\Users\Jacob\Documents
Local App Data dir: C:\Users\Jacob\AppData\Local
Culture: en-US
UI Culture: en-US

-----------------------------

Errors

Message: Configuration system failed to initialize

Message: Unrecognized configuration section startup.
File name: C:\Games\Steam\steamapps\common\Arma 3\arma3launcher.exe.Config
Line: 11

-----------------------------

Trace

System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section startup. (C:\Games\Steam\steamapps\common\Arma 3\arma3launcher.exe.Config line 11)

   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
   --- End of inner exception stack trace ---"

I tried verifying the game cache and it did not fix itself.

Hello,
seems that the main configuration file of your .NET Framework is still corrupted. You can replace it by using a backup file (providing that it is not corrupted as well):

1. Go to the folder C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\
2. There should be 3 files:
   • machine.config
   • machine.config.comments
   • machine.config.default (note: you have to disable hiding extension to see the extensions)
3. Move file 'machine.config' somewhere else (e.g. to desktop).
4. Make a copy of 'machine.config.default'
5. Rename that copy to 'machine.config'
6. If you could pack the original 'machine.config' to ZIP and upload it here so we can investigate the way it is corrupted it will be helpful to us.

Hello,
according to the log you're missing one of the files from Microsoft .NET Framework. You should be able to fix the issue by re-installing the .NET Framework, the latest version 4.6.1 can be downloaded from here: https://www.microsoft.com/en-us/download/details.aspx?id=49982

Same for all tracer.

some new crash logs, with system malloc, before i used standard mallorc.
now it crashed with different error but same with 20 players and about 1-2h uptime of the dedicated server.

uploaded new rpts.

system malloc new error screen: https://www.dropbox.com/s/n1b5bhkvvynqcn0/Unbenannt.PNG?dl=0

uploaded some more Crash logs

The Game crash mostly with around 20+ Players on it and around 60-90 minutes uptime. with less then 10 people on it no problems..

The same bug is also present for a running soldier without weapons.

Yea. Seen lots of people complaining about this bug since 1.54, it's completely broken right now... Just hate to play with sway enabled, would love to see fix for this ASAP.

the "player setCustomAimCoef 0.20" command will also reset itself back to 1 on a mission "RESUME".

Hello,
could you please generate Arma Troubleshooting Report from the Options menu in Launcher (it's a menu item next to the Export Launcher logs to desktop) and upload it?

I have been able to play this game before on the exact same setup.
I have validated my game files and also tried recreating the profile.
I have tried of different settings, including recommended.

I have attached the troubleshooting log.

As this is Guerrilla Offroad, sometimes it might not have driver door :) This is by design, not a bug.

Only tried it once and got the following issues.

[
_veh,
["guerilla_03",1]
["HideBackpacks",0,"HideBumper2",0,"HideConstruction",0,"Proxy",0,"Destruct",0]
] call BIS_fnc_initVehicle;

missing , after ["guerilla_03",1]

If there was a unit in cargo it crashed the code so I removed that.

And the gunner spawns on foot not in the gunner position.

I know it's work in progress so I'm not too bothered, I can at least spawn with the doors now.

Not at all. Its for missionmakers to make vehicles look better. For example a Offroader without doors for a Guerilla mission.

Thanks I never tried virtual garage before, it seems very buggy though.

Go Virtual Garage and spawn the Offroader. Im quite sure the door is optional. When you spawn a Offroader its usually random if he has doors or other stuff like backpacks.

Hi BIS Wizard

Thanks for input i have changed DPI settings though this is a small solution fix for the launcher it makes other DPI features to small to read not good and even with this DPI change the launcher is still too big for any screen/DPI settings, Good for short sighted people thumbs up.

Hello,
Launcher minimal size is 690 px but it is also scaled up because your system DPI settings is more than 100 %. For now you can solve the issue by enabling the option "Disable display scaling on high DPI settings" in properties of Launcher executable on Compatibility tab.

Q: How do I know that this is the case of this crash? If i reproduce it without mods.

Q2: I need to reproduce it in the mission editor?

I can ask my players to reproduce it without mods. But I'm not sure that they succeed. Need more time.
If i understand - that mods can't contain direct processor instructions (physical machine code), they performed some kind of "virtual machine." Or I am wrong?
If the problem is the mod error, let this machine correctly handles the error rather than crash. =)

I can't add gzip archive as attachment. Is it correct security policy in this site?

Could you please try reproducing the issue without mods?

Please update your game to current version and see if the issue persists.

Can you please attach a demo repro mission?