didnt have the problem anymore in the current build (Version: 1.69.141382)...

There will be fix in arma 4 :D Its really ridiculus that bugs like this are for so long in this game. People responsilbe for this should be fired right now. How they could apply not working/wrong working physx in game production phase and continue work? This is unacceptable behavior of programmers, specially, beacuse they knew its gonna be unfixable - if they decide to fix it, they gonna break tons of other things. Very inmature and unproffesional behavior, things like this happen in Greenlight, early access, and "forever beta" games, arma 3 is the one for me, that qualify in all 3 groups.

The Jets DLC is bringing engine flame and can only be seen internally from the rear of the aircraft (eg. using 3D view), but not the afterburner thrusters glow which extends beyond the frame of the aircraft during afterburner usage.

I completely agree!

+1, I would absolutely love to see a laser in the Blackfoot AND the Wipeout, a simple addition as well!

Are you able to get into the targeting pod view? (CTRL + RMB)

Cash verfied same issue.

Bump? Even the Xi'an gunship has a laser.

This is still happening after 1.68. The changelog for the update said "Fixed: Inventory weight of loaded magazines was doubled (https://forums.bistudio.com/topic/143930-general-discussion-dev-branch/?page=862#comment-3147196)", but weight is still being doubled when a magazine is loaded into a weapon.

+1
That makes a lot of sense! .. and a long road from:

In T124468#1598120, @chaseschroeder98 wrote:

So my game does crash when I open the targeting pod camera, it looks like a common problem for most people. I expect a patch that will fix it.

So my game does crash when I open the targeting pod camera, it looks like a common problem for most people. I expect a patch that will fix it.

+1000% but this ticket forgotten

In T124463#1598108, @HaseDesTodes wrote:

same here.
crash is recognized by the game, but no dump files are getting created.

Exit code: 0xC0000005 - STATUS_ACCESS_VIOLATION

CLR version: 4.0.30319.42000
OS Version: 10.0.14393.0 (Microsoft Windows NT 10.0.14393.0)
OS 64 bit: True

Exe timestamp: 2017/04/20 00:25:39
Build: Development
Version: 1.69.141362

Allocator: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\Dll\tbb4malloc_bi_x64.dll
PhysMem: 16 GiB, VirtMem : 131072 GiB, AvailPhys : 14 GiB, AvailVirt : 131072 GiB, AvailPage : 15 GiB

16:48:05 Arma 3 Jets | jets | true | GAME DIR | 5e0d999f7c2e93a7d98f2ae881ad98da192ebe34 | fbef4704 | C:\Program Files (x86)\Steam\steamapps\common\Arma 3\jets

can provide full logs if needed.

Tweaked: The isVehicleCargo and canVehicleCargo commands are now working with cargo boxes

Myself and a friend also had this crash happen to us while in a MP session the other night. We both spawned in a couple of the new dev-branch fighters and attempted to use the targeting pods. Crashed our games out multiple times. The night before (19th I believe), everything was working fine with the targeting pods, though.

same here.
crash is recognized by the game, but no dump files are getting created.

+1

Still know this bug from A2 times. As this appears as first google entry to me:
You can prevent your server from crashing by blocking port 80/443 for the arma server until it's properly fixed.

Can be marked as Resolved :)

video is gone so ticket is without real description basically

he decided to work today

Not only fence. Many objects which are in real life semi-rigid and easy to crush are in A3 real road blocks. The entire object data base needs a total testing against interaction with infantry/wheeled/tracked/air and then updated/optimized parameter sets.

add wheel damage modelling. Military wheels have runflat capabilities. Eighter multi-chambering with active inflation system that would keep wheels with bulletholes still rolling or like for HMMV wheels which are partly made of a half rigid framing that forms still a wheel without any air pressure inside.

Happened to me in 1.68 when using "unflip" function contained in crCTI. This function is used to somehow "respawn" vehicles which stuck or flipped over. After using this action on a MBT, one or both tracks were stucking into the ground and MBT could move very slow.
Using "unflip" sometimes more until suddenly the MBT did not appear stucking into the ground.

To be precise:

Confirmed, issue still present as of 04.20 (1.69.141362).:

Sorry, duplicate of: https://feedback.bistudio.com/T124397

1.) The vehicle physics and steering at A3 launch were almost perfect:

Here's my Arma 3 profile vars file which I believe contains my saved loadouts, in case it's caused by something more complex and you need it to reproduce the issue.

Retested with v15 of the performance build https://www.dropbox.com/sh/582opsto4mmr8d8/AAB_t7coofvZH0ot_WBmVsFMa/168perf/perf15?dl=0

same here.

From arma 3 discord:

If you keep your keys than it has none

This one happened while I was in the Virtual Arsenal

Another crush dump

I believe you're stating TrackIR depth translation (eg. XYZ) rather than just tracking X and Y angles.

+1

+1

+1

+1

Yeah I even had this happen to me in P30 Orca

ill do that and get back to you, thanks for responding.

In T124468#1597716, @chaseschroeder98 wrote:

thank you very much for the reply. I am not home at the moment so if you could tell me if it has a default button that would be nice. It's just a question out of pure curiosity. Does it come as a preset? and what is that button just so I know if I've tried it?

thank you very much for the reply. I am not home at the moment so if you could tell me if it has a default button that would be nice. It's just a question out of pure curiosity. Does it come as a preset? and what is that button just so I know if I've tried it?

It schould be in the controls under weapons or general. Its quite at the bottom called switch radar on and off.

I'm currently trying out multiple ways to not crash.

Another crash report, this time with the Wipeout. I switched to stable, and the Targeting Pod Camera worked just fine, switched back over to Dev branch and did the exact same steps, Still crashed when entering the view (CTRL + RMB)

The Camera screen being black was due to having PIP disabled, my bad. But an instant crash still occurs when trying to enter the targeting pod view (CTRL + RMB)

The animate function does no longer work with the third argument being false. This seems to be the core reason for the breakage. Will that be fixed or do we need to change the false to number 1 to stay compatible?