Bug #3919
Helicopters loading/unloading mess
| Status: | Resolved | Start: | 2009-08-22 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assigned to: | Dwarden | % Done: | 100% |
|
| Category: | AI Issues | |||
| Target version: | Upcoming version | |||
| Operating system: | Win7 64 bit | Mainboard chipset: | ||
| Graphics card: | System RAM size: | |||
| Graphics card driver version: | GPU VRAM size: | |||
| Affected ArmA II version: | 1.53 BETA | Audio card: | Please specify! | |
| Maxmem parameter: | Size of OS swap file: | Please specify! | ||
| Difficulty: | Not set | I am using some Mods: | No | |
| Reproduced by another DH user: | Yes | I am using: | ||
| CPU: | Please specify! | Reproducible for you: | No | |
| Votes: | 59 |
Description
Helicopters behaviour in ArmA2 are still a complete mess in bata build 58834 ...
It's a shame that in around 9 years some basic things were not fixed. Also new problems arose. :(
I've made some simple tests with a infantry group having "GETIN" an "GETOUT" waypoints sinched to "LOAD" and "TR UNLOAD" waypoints for a heli group
Sometimes things work ok, but most of times problems arise. Here are the major "random" problems that i repeatedly experienced:
LOADING PROBLEMS
- When loading troops some infantry units eventually try "push" the the wrong side of a helicopter trying to get in. Then they die.
- Sometimes helicopers leave the loading point before all units eneter the vehicle
- Sometimes an infantry leader keep endlessly ordering a dead squaddie to get in the heli. The heli is stuck and does not take off.
UNLOADING PROBLEMS
- Often, if a heli is under fire, it's not able to unload troops correctly at all (combat mode, behaviour and AI disabling have no effect). Heli simply stops in mid air and waits endlessly.
- Sometimes a heli reaches the LZ, but cargo units never disembark (probably related to a "setwaypointCompletionRadius" bug ?)
- Cargo units leader endlessly orders his dead units to disembark from heli. Heli is stuck and keeps getting out and in the LZ waiting for these units o disembark.
PLEASE fix these problems.
Related issues
| related to ArmA2 Community Issue Tracker - Bug #3530: setwaypointCompletionRadius bug | Expired | 2009-08-09 | ||
| related to ArmA2 Community Issue Tracker - Bug #1967: Chopper boarding issue with AI | In progress | 2009-06-10 | 2010-11-01 | |
| related to ArmA2 Community Issue Tracker - Bug #6866: Heli "disembark transport" waypoint does not work in MP | Duplicate | 2009-12-12 |
History
Updated by Fireball about 1 year ago
- Due date set to 2009-09-22
- Status changed from New to Feedback
- Graphics card deleted (
times it just) - Maxmem parameter deleted (
Not set)
Thanks for your bug report.
As you know it's endlessly difficult to reproduce these problems without proper reproduction steps - or easier - a mission which exhibits the problem when you start it, or when you execute the repro steps.
Can you maybe make one or multiple reproduction missions for the issues you experience - that will certainly help your (our) case!
Updated by Fireball about 1 year ago
- Priority changed from High to Normal
Updated by fabrizioT about 1 year ago
- File killed_cargo_unit_bug.utes.zip added
Ok, a major problem at least is constantly reproduceable.
Run the attached mission:
- follow your group and board the heli
- during flight the officer sitting near you, that belongs to your group as member "2", is killed by script
- when disembarking you will hear your group leader constantly yelling "2, disembark", but 2 IS DEAD! The heli won't follow its route and your group will be stuck too.
That's a gameplay breaking problem, since it LOCKS both cargo groups and helicopers and stops them from following the planned route.
Updated by fabrizioT about 1 year ago
- File no_getout_bug.utes.zip added
Well, guess i am lucky ... here is your second repro.
This time we are simply trying to have your group disembarking from a heli.
Run the attached mission:
- do nothing, you will simply fly towards the LZ
- when you get near the LZ a single enemy machinegunner will fire on your heli
- most of times you'll see your heli stopping still in mid air, or skipping the LZ and going to stop somewhere around without landing at all...
2 times out of 3 in average you will not be able to disembark. Weird.
BTW: playing with "combatmode" and/or "behaviour" for the heli won't help.
Updated by fabrizioT about 1 year ago
- File no_getin_bug.utes.zip added
My last effort.
Now let's see what happens when a group leader boards a chopper and one of his squaddies gets killed before getting in ... not so strange, LZ get hot sometimes.
Run the attached mission.
- Do nothing. You should see an infantry group leader boarding a heli (he has a GETIN wp synched to a LOAD waypoint of the heli)
- You should see (hopefully) his only squaddie, our well known officer, dying just before getting into the heli.
- Now you will see that the heli won't take off, waiting forever for the dead group member.
3 bugs repro are enough for me this night, bye.
Updated by fabrizioT about 1 year ago
- Assigned to set to Fireball
Updated by Fireball about 1 year ago
- Status changed from Feedback to Assigned
- Assigned to deleted (
Fireball)
Very nice, thanks. Please do not assign bugs yourself.
Updated by ZiiiP about 1 year ago
I have this problem too that the chopper wont unload when attacked. :(
Updated by Dwarden 12 months ago
- Target version set to 1.05 BETA
- % Done changed from 0 to 10
will see what can be done about these ..., WIP
Updated by Dwarden 11 months ago
- Priority changed from Normal to High
- Reproduced by another DH user set to No
- CPU set to Please specify!
Updated by kju 2 months ago
- Due date changed from 2010-03-03 to 2010-07-14
- Status changed from In progress to Feedback
- Assigned to deleted (
Dwarden) - Target version deleted (
Upcoming version) - Affected ArmA II version changed from 1.04.59026 to 1.05.62017
- Size of OS swap file set to Please specify!
Still valid in 1.07 / OA?
Updated by psychobambi about 1 month ago
Despite being reported almost a year ago, and being classed as urgent for 9 months all 3 of these game breaking bugs are still present in OA 1.52 71952.
I have figured out a couple of work arounds to these bugs, hopefully it might help in solving them.
Unit killed during boarding:
I have found 3 ways around this bug
1) If you deletevehicle the dead unit the chopper will take off immediately.
2) If another unit in the same group and not already inside the chopper sees the dead unit he will call "2 is down" and then the chopper will take off.
3) If you use the join command to instruct the dead unit to join another group, upon the leader seeing this new unit is dead the chopper will take off.
My best guess: This appears to be caused by the squad leader and the squad being unable to realise a unit has been killed when inside the chopper and the status of the other units never being checked.
Possible solution: trigger a status check if no responce for a number of seconds.
Unit killed while in cargo:
2 work arounds
1) If you deletevehicle the dead unit the squad will move on and the chopper will take off again.
2) If you use setpos on the dead unit to drop him onto the ground so he can be seen by the rest of the squad "2 is down" will be called and the squad and chopper will move on.
My best guess: This appears to have the same cause as the above bug: The squad cant tell who is dead when inside the helicopter.
Possible solution: After the squad leader has called disembark a couple of times check the status of the squad members.
To sum up how it appears: Units cant see anything when they are inside the chopper and when outside the cant see into the helicopter.
No dropoff underfire
I havent found a guranteed solution to this bug however if you wait untill the chopper gets stuck in the hover and use the setcurrentwaypoint to instruct the chopper to go to the waypoint after the LZ it will start moving and oftern will drop the troops at the LZ.
Please fix these bugs!
Updated by kju about 1 month ago
- Due date changed from 2010-07-14 to 2010-10-01
- Assigned to set to Dwarden
- Affected ArmA II version changed from 1.05.62017 to 1.07.71750
ty
Updated by Dwarden about 1 month ago
- Target version set to Upcoming version
erm some of the bugs were fixed when i tested with OA
other ones are WIP
but i will look into this again ...
Updated by psychobambi about 1 month ago
Thank you for the fast reply.
The bug im really intrested in seeing fixed is the unable to land under fire. It will land underfire sometimes in normal behaviour but being able to force it using careless is necessary for a lot of missions.
Updated by psychobambi about 1 month ago
- File no_getout_bug_demo.utes.rar added
With regards to the no landing under fire bug, Ive done some more research.
The problem appears to be with the transport unload waypoint after the unit has come under fire and not the set behaviour.
I have uploaded a mission to show this, its fabrizioT's mission with a few changes. You can now use the radio to set the behaviour, current waypoint and kill the machine gunner. Heres my findings.
1) If you kill the machine gunner before he shoots the chopper it will land everytime regardless of behaviour.
2) If the machine gunner shoots the aircraft it will do the following 9 out of 10 times:
In careless it will become stuck almost immediately, killing the machine gunner does not get it moving again.
In aware it will go and kill the machine gunner and then become stuck
3) After it has become stuck if you then set the next waypoint it will move again. If you then reselect the Landing Zone waypoint it will fly to it and become stuck again. You can keep cycling it and it will get stuck eveytime.
It appears once the chopper gets shot it no longer knows how to action the waypoint, changing the behaviour just delays the inevitable.
edited to tidy up my wording
Updated by kju about 1 month ago
- Status changed from Feedback to Assigned
Updated by psychobambi about 1 month ago
All 3 are still in OA Beta 72197
Still classed as an urgent bug, Can these please be fixed!
Updated by kju about 1 month ago
- Affected ArmA II version changed from 1.07.71750 to 1.53 BETA
Updated by Dwarden about 1 month ago
- % Done changed from 10 to 50
Updated by kju about 1 month ago
- Due date deleted (
2010-10-01) - Status changed from Assigned to Resolved
- Assigned to deleted (
Dwarden) - Target version changed from Upcoming version to 1.53 BETA
Please confirm fixed.
Updated by psychobambi 30 days ago
I see the one you have tried to fix (unit dies in cargo.)
Sorry to be the bearer of bads news, its still bugged. The helicopter will now land, drop of the alive troops and then depart. Shortly after take off the squad leader will order 2 to disembark. The chopper comes back lands briefly and then takes off again. The cycle continues forever.
Updated by kju 30 days ago
- Status changed from Resolved to Feedback
- Assigned to set to Dwarden
With the demo mission as per above or a new one? If so please attach.
Updated by psychobambi 17 days ago
killed_cargo_unit_bug.utes.zip
All the bugs are still present in OA beta 72716
Updated by Dwarden 17 days ago
- Status changed from Feedback to In progress
really thanks,
seems like i needed to move the test mission on Desert to get this happen (for some reason it was acting like fixed)
now i see the AI copter stuck in endless loop of land, takeoff, land and AI commander demanding unit to dismount each landing ...
Updated by psychobambi 16 days ago
Thats exactly what im getting. On killed cargo unit utes its doing it 100% of the time for me
Updated by Dwarden 14 days ago
- Status changed from In progress to Resolved
- % Done changed from 50 to 100
fixed since 72771
Updated by psychobambi 8 days ago
In beta 72863, OA with patch 1.54.72888 and also patched with the BAF DLC the folling happens:
The killed unit in cargo bug appears to be fixed. I havent been able to trigger it.
The no get out bug is still present, the same with the no getin bug.
Both bugs I have reproduced with the above missions.