Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I would suggest a steady 60 FPS, if possible.
Disable PhysX (set to Low) if it is enabled, as it tends to mess with the way loot interacts with the world.
I believe the loot that Wilhelm drops usually flies perpendicular to Wilhelm's right hip(?) so make sure his right is towards an inward wall when you land the final hit.
Other than that, this is typically what happens with Wilhelm's loot for some reason. It's not easy to mitigate otherwise.
They might be referring to Son of Mothrakk(?), which is a mini-boss that spawns in place of Bloodwing if you return to the preserve again. Their drop does indeed depend on where Mothrakk flies as you kill it, so that's another situation where you need to plan when to finish them off to get the loot.
Running anything from 30-90 FPS is fine as long as you do not get wild swings.
Kinda, kinda no. You can easily run PhysX on max as long as you have an nvidia card and make sure it runs on the GPU.
The reason why it causes so many problems is that the game uses a very old version that has a single-threaded CPU-fallback targetting x87 (yes, 87, not 86) that is really inefficient and will cause extreme FPS-fluctuations.
And BL2 has many bugs with the settings, which often leads to the config getting corrupted and PhysX then running on the CPU (in a game that was already single-threaded and CPU-bound ). manually fixing the ini-files or geforce expeirence can fix that, using the pyhsx-overlay also helps identifying the problem.
(and there are areas like the tower in TTAoDK - totally buggy)
Well, it's possible I'm just confusing her with the replacement boss from subsequent runs Son of Mothrakk. That one definitely does have drops, and ... you can watch as they fall .... outside ...
Annoying too, because it's the Skullmasher, a Legendary I'm not sure I've ever gotten, but would like to try.