Jump to content

StuardBr

Citizen
  • Posts

    9
  • Joined

  • Last visited

Everything posted by StuardBr

  1. Hahaha, yes... But ok, the best way to learn something is by suffer. I'll NEVER forget this thing hahaha. Thank you for you patience and let's install some thousand mods :)
  2. OK, i think THIS TIME i found the cause of the problem. I reinstalled my system as i do every 6 months and with this, i can know if the problem is something in my PC. Backup, list of programs installed, etc... Reinstalled win10, drivers, steam and Fallout3 (and dependencies). Tested and ok. Installed FOSE, tested and ok, tested MO and... Ok too... So, let's install the other programs to test. After reinstall all previous programs, the problem back. So, closing one after one, i found that a program that i use, OverWolf, is causing the problem with MO. Overwolf provide some functionalities when i'm playing, like automatic gifs, statistics, etc but, to work,it needs to do some type of "overlay", like steam. This overlay is ok for FO3, but apparently is incompatible with MO. Closing the OverWolf in system tray solve the problem. The only thing is in my head is, WTF a third party software will cause problems in the way the MO use the "archives.txt" and with some other mods... I found a post in the Nexus Forums (https://forums.nexusmods.com/index.php?/topic/1550213-freeze-on-startup-seems-to-be-induced-by-awop/) with a similar problem, but with the NewVegas. All is pointing to a mod problem, but in the end, was Overwolf too... I think is a good thing to put in the guide of STEP, close this type of program if problems appear. Anyway, thank you all for the attention and help :)
  3. My problem isn't a crash, is a freeze in controls, like i said in the first post. And as i said in a previous post, i tried enable and disable but same problem.
  4. Like i said, if I open WITHOUT MO, all works fine, but answering you, yes, FOSE was installed manually, in the data folder. As i said in my last post is a MO file that cause the problem. If i use WITHOUT MO, everything works fine. If I use FOMM, works fine too. But, sadly, if i set "achives.txt" read-only as i said before, mods appear to don't work, so my problem persist... I don't know what to try next... Maybe this is more one "Windows 10 x Fallout 3" bugs? I don't want to use FOMM or NMM, but i tink the MO is dead for me in FO3...
  5. Well, i found a WORKAROUND about this problem... For some reason, the "archive.txt" file, generated by MO in the profile folder is the cause of the problem... I tried remove the MO to manage the files, using the workaround option disable "force-enable game files" but NOTHING solve this thing. The ONLY thing that "solved" the problem is, before launch the game, set the file to "Read-Only"... Someone know why this happen?
  6. MO is installed in another HD, with the permission in the folder set to "Everyone" modify. If i delete the "ModOrganizer.ini", reopen the MO, choose Skyrim, Skyrim works fine. Tried some older versions, same problem. PS: Run as administrator, same problem.
  7. Yes. I started Fallout launcher through MO, i can change configs and everyhing, If i hit Play, same issue, freeze on the main menu
  8. 1-Fose works fine when opened alone, without MO; 2- SKSE Folder? FOSE folder right? I have no mods installed, so, the folder is empty; 3- No, this don't happen if i open the original Fallout3.exe/fose_loader.exe WITHOUT MO; 4- Yes, i used BethINI, default ini files, everythine MO open Fallout3.exe or FOSE this thing happens.
  9. Hello guys! I'm starting to play with fo3goty and i'm having some trouble in start. I installed Steam version, started Fallout 3 Launcher, ultra setiings, play, tested a new game, everything ok. So, i installed FOSE. Tested him and ok too. Installed MO 1.3.11, default options, run FOSE and... the game freeze on main menu. I need to "Alt + F4" to exit. Tried open FOSE and Fallout3.exe and same problem. Tried open Fallout 3 Launcher too and it open without problems. Searching what can be happening, i note that, if i go to the MO, create a new profile (test for a ex.), go to the "ModOrganizer/profiles/test" and put ANY ini file under "Read Only" and try to open FOSE or Fallout3.exe the thing start fine. Tried copy the default ini files from "Users/MyUser/Documents/My Games/Fallout 3/" to "ModOrganizer/profiles/test/" and same problem... Anyone can help me with this problem?
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.