You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AI pathfinding/simulation is broken and it's impossible to finish the game.
The most obvious example is Mission 4.2, where dropping friendlies on the battlefield results in them being stuck.
Seen here.
Reproduction Steps
Reach/Load Mission 4.2. Drop allies on the battlefield.
Potential fix for this specific instance is: your second wingman is stuck on the second carrier and thus not triggering the script on landing. The reason for this is the tank it's supposed to load is lying on its back on the carrier deck. Overturning the tank or straight up destroying it will both solve this issue and allow the mission to continue.
I am currently encountering a similar issue in the last mission, 4.5. The second wingman is landed on the starting base and refuses to take off. However I see no vehicles around for it to load and I suspect it either didn't spawn or spawned under the ground. Destroying the wingman does not seem to allow the script to move on. I have no current solution for this mission...
Describe the Bug
The AI pathfinding/simulation is broken and it's impossible to finish the game.
The most obvious example is Mission 4.2, where dropping friendlies on the battlefield results in them being stuck.
Seen here.
Reproduction Steps
Reach/Load Mission 4.2. Drop allies on the battlefield.
Memcard for the mission in question.
Dropship.zip
Expected Behavior
Ally units start moving towards the enemy fortress immediately.
Seen in here
PCSX2 Revision
v.1.7.5862
Operating System
Windows 11
If Linux - Specify Distro
No response
CPU
Ryzen 9 5950X
GPU
GTX 1070
GS Settings
Settings used were close to default.

Emulation Settings
GS Window Screenshots
No response
Logs & Dumps
No response
The text was updated successfully, but these errors were encountered: