Nixeh

Comparing the working RPT to the crashed RPT it looks as if the crashed one crashes out due to the following: Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/Offroad_SPG9_Gue/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/HMMWV_Ambulance/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/HMMWV_Avenger/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/USMC_Soldier/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/USMC_Soldier_AT/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/Profiteer2/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/M119/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/DSHkM_Mini_TriPod/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/SearchLight/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/Igla_AA_pod_East/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/RU_Soldier/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/2b14_82mm/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/M252/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/M2HD_mini_TriPod/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/MK19_TriPod/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/C130J/ Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/T34/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseWeakYellow/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseMediumOrange/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseMediumPale/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseStrongPale/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_EP1/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/Land_Lamp_Cable_EP1/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/Land_Lamp_Street1_decor_EP1/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/Land_Lamp_Small_EP1/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/Land_Lamp_Street1_EP1/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/Land_Lamp_Street2_EP1/ Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/Land_Lampa_Ind_EP1/ Couldnt find the files related to these vehicles, and was wondering what would cause them?

I have done the above to no avail, even tried to Beta drivers with no luck. 101480 still works fine. 101747 and versions since still hang the process. It doesnt feel like a graphically caused issue. What changed between these 2 patches? The only 2 things i can think it to be are changes to networking/NAT which would explain why it crashes at 'waiting for host' or selecting mulitplayer. Or a memory change which would explain why the process hangs and a restart is required. I have also tested my RAM overnight and it whizzed through those fine.

Deleted the files, retried and hung/crashed at 'Waiting for Host' It generated the RPT file but due to it not actually 'crashing' it hasnt generated the other 2. I have resent you the updated RPT file.

Im using ESET Smart Security 5 Yes the bidmp and mdmp files have not been accessed as the game doesnt really crash. The game hangs, i cannot kill the process and therefore have to restart the system to launch any other game or to relaunch Arma2. It does not allow me to use my desktop either as acts if like it is part of the Arma2 menu (default Win7 mouse cursor overridden with Arma2 mouse cursor). Restarting the system is the only way i have to resolve this as it currently stands.

Hmmm, not sure what happened there. They should have been the crash files from the correct version. Anyhoo i have updated to the newer patched and retried and had the same luck. I have just sent you the updated files. If it helps it appears to be crashing at 'Waiting for host' if i connect via Dayzcommander, and if i try via the game lobby, it hangs after i click 'Multiplayer' on the 'receiving' screen. Thought it might be down to my firewall, but i have removed and recreated the firewall exceptions which didnt resolve the issue. Cheers again for the help.

I have resent the email with the files requested.

Still having issues with hanging at 'waiting for host'. Completely hangs my Arma2oa.exe so much so that i need to restart. Forum Post regarding issue.

New beta drivers do not resolve the issue. Have tried all beta versions up to the current (102285)

I have the same issue. Since updating to beta 101747 i have not been able to join a game without the game hanging at 'waiting for host'. It hangs my ARMA2OA.exe to the point that i cant kill the process or its tree, via task manager or any other kill process program. The only way i am able to resolve it is by restarting my system and rolling the beta back to 101480. I have tried with all betas after 101747 and have had the same crash happen to me again. For the time being its not much of an issue as the servers i play on run the earlier patches so i can roll back, but i feel that they will be updating soon and i will be caught out and wont be able to join. I have sent my copies of the file to the same address in the hope that it helps resolve this issue. Let me know if you need any further arma2 reports as a friend of mine is having the same issue.