GrandesBollas Posted January 6, 2021 Share Posted January 6, 2021 Guys/gals! First time poster here. I have the vanilla version of FNV installed on, yes, an M1 Mac mini. I have no mods installed. I am also running the game in a virtual machine. I have no problems starting the game (character creation), and starting the quest with Sunny Smiles. My problems begin after heading out to hunt the geckos. This is a strange issue in that it repeatable about 90% of the time. Once in a blue moon, the issue doesn't occur in the same scene. Here is a video of my problem (occurs around time marker 2:40 of the video). https://www.youtube.com/watch?v=dAM9GcbNAFg&t=3s I know the engine here is very similar to Fallout 3. I have no problems running Fallout 3 on the M1. I am really stumped as to what is going on and how to fix. Link to comment Share on other sites More sharing options...
GrandesBollas Posted January 6, 2021 Author Share Posted January 6, 2021 (edited) I went ahead and added the mods described in this video: I re-ran the game with the mods, including creating a character made after the mods were installed. The graphic anomaly is still present. I made two videos describing the behavior - with and without windowed mode: Full screen 1280x720 - glitch is still apparent Full screen 1280x720-glitch is still present but greatly mitigated I really don't understand what is causing this anomaly. I seem to have plenty of cores and RAM. Every once in awhile, the game behaves like the glitch did not exist (e.g., 10 quit games with glitch; 11th restart works with no glitch). The emulation provided by the VM seems to be able to handle the translation from ARM to x86 without problem. I really don't know what else to do except play the vanilla game on my OP desktop PC. Edited January 6, 2021 by GrandesBollas Link to comment Share on other sites More sharing options...
dubiousintent Posted January 8, 2021 Share Posted January 8, 2021 We REALLY need to see a sorted "load order" (such as produced by "LOOT"); to include the main game and DLC files. (Screenshots don't work so well for the purpose.) With modded games its the sequence, not merely the list of mods, which is the cause of many problems. LOOT's sort gives a good first approximation, correcting the most obvious issues and is sufficient for most players. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata". Instructions on how to copy it's list for posting are in the "How to ask for help" article, and "Checklist Item #11' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.In the meantime, please see the 'Vanilla Load Order' entry in the 'First Timer Advice' section; as well as the 'Towards Game Stability' and the 'Common Game Problems' sections of the wiki "FNV General Mod Use Advice" article. There are many things that can cause problems if you do not setup the base game and then install mods correctly. Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so. Here is just a small sample:* Did you install Steam to it's default location? (GOG is not a problem as it places the game correctly.) If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" or "C:\Program Files(x86)" folder tree was bad (they learned better, and don't do that any more but didn't change it for older games); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. Among other things, later versions of Windows (since the game was released) force files in "system protected" folder trees to be "read only" regardless of how you set them manually. It includes instructions on how to correctly move the Steam folders out of that folder path.Don't move it to a folder under "User\Documents" either, as "executable" files are not permitted to run from there for similar "anti-malware" reasons. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. With the game moved out of the default location you will not need to be running it as an "Administrator Account", which is safer. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.* Do you have "New Vegas Stutter Remover" (NVSR) installed? If so, please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. Note the default NVSR settings do not work with Win10, but there are some recommended by the author for Win10 further down in the article.If the problem persists, then work through either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last set it up. It is designed for someone who has never played a modded PC game before, so it tries to avoid making any assumptions, is kept "up-to-date", and covers years of "lessons learned" by a retired Technical Support expert. It is NOT a list of various mods to install that happen to work on the author's machine; only "the essentials". It addresses fundamentals underlying how to get the basic game and mods to work together. At least 90% of everything I post in the "Technical Support" sub-forum is already in that article. Once you can play a test game to at least Primm, only then should you try adding other mods from some other "guide".-Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts