-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch breaks enemy and companion AI during Virmire mission #4
Comments
I can confirm this, but doors worked for me. The Repairing/Fatigued is an ME1 bug, it happens if you get fatigued after repairing the mako, it's not caused by this patch. |
JensDA
changed the title
Patch breaks enemiy and companion AI during Virmire mission
Patch breaks enemy and companion AI during Virmire mission
Oct 8, 2020
riverar
added a commit
to riverar/SilentPatchME
that referenced
this issue
Nov 7, 2020
…finite (fixes CookiePLMonster#4) This change better aligns our implementation with behavior found in d3dx9_31!c_D3DXMatrixInverse.
CookiePLMonster
added a commit
that referenced
this issue
Nov 7, 2020
Return early if the inverse of determinant is not finite (fixes #4)
How in the heaven could AI be affected by graphics? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During the Virmire assault mission, if the
d3dx9_31.dll
is in the Binaries directory, there is a point where enemies stop attacking (but are still moving) and the companions are getting stuck and don't get reset when the player moves on.Progression into the base is not possible, as the doors are unable to be opened.
I have also noticed, that the UI says
Repairing
instead ofFatigued
after sprinting.I have confirmed that simply removing the SilentPatch DLL from Binaries fixes this issue.
Talinn00_AutoSave.zip
The text was updated successfully, but these errors were encountered: