This has resulted in two things I've personally experienced and is around in a variety of other issues - basically older software engines don't handle the new way of dealing with low-level drive formatting right because they assumed MBR forever. ![]() ![]() Skyrim was always sensitive to this probably due to some core code in the engine looking to the MBR master boot record drive to find sounds fast forward to 2016 macbook pro - you can't have an MBR type drive format - the SSD in it is a new type and only supports EFI ![]() So the issue may be a new iteration of the original sound problem in skyrim when it wasn't on the root c: drive - which is almost always the boot drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |