Official Patch Notes:
- Made a number of stability fixes to improve the quality of the MyPARK experience, and online as a whole.
- Controller/Keyboard bindings will now properly function in MyPARK.
- Addressed an issue where the game would experience frame rate stuttering in certain situations.
- The correct animation will now be shown in Edit Player when scrolling through the available list of animations.
- Fixed an issue where the user who invited would sometimes hang at the conclusion of a playoff game in Online Leagues.
- Fixed an issue where some users were experiencing hangs when attempting to create/join an Online League with a custom roster.
- Addressed an issue in MyGM/MyLEAGUE where the user wouldn't be able to waive players to go below 13 in the offseason.
- The keyboard should now properly detect input game-wide when a controller is also being used simultaneously.
- Fixed an issue where in-game models would appear green/yellow on certain GPUs.
- Fixed a rare hang that would occur when changing the in-game language from the Options menu.
- Corrected an issue where black ‘blobs’ would appear in replay on certain system configurations.
- Fixed a rare occurrence where Doris Burke would warp off the screen prior to an on-court interview with a player/coach.
- Users are now able to re-watch 2KTV episodes that have already been watched to completion.
- Added support for users attempting to play with a GeForce 320M GPU.
Other Notes:
- Under "%appdata%\2K Sports\NBA 2K15\" you'll find a file called VideoSettingsHelp.txt, containing instructions on how to mess around with the VideoSettings.cfg file if you're feeling adventurous. A set of new tweaking options was added to the file, and all settings, new and old, have descriptions in the help file along with the values and what each one does, as well as helpful recommendations based on your system.
- Small correction to VideoSettingsHelp.txt (thanks jay-r): The explanation for the EFFECTLOD setting is reversed. 0 is ON, 1 is OFF.
- If the game crashes, you should now see a CrashReport.txt file under the same folder. Posting it as an attachment in a reply should help us track down the issue.