Using incompatible archives may cause your game to crash on load., Some of the archives in your load order are incompatible with Fallout 3. suggestion to add a button to "view log file" when being prompted that i should attach one to the bug report. )Īs a side note, i'd be more willing to send a log file IF i could see what was being sent in it.
( vortex has flagged 3 of my mods, all of which were installed months ago and work fine so there is no reason for me to have a red super serious looking error message that i can't dismiss. i should be able to suppress the error so i don't see it again, or otherwise tell it to not check this mod. all i want to do is tell vortex to stop showing me a red error every time i deploy. but i do know the mod was last updated so likelyisn't being updated anymore, and it's been working for quite a while without any problems. it may be intended for oblivion, i didn't make the mod and don't have any way to verify what it was intended for. bsa is intended for oblivion i have no way to tell vortex to ignore the error. there needs to be a dismiss or ignore button! i have skyrim LE, it says the. (We will not offer support to users who opt for this option)Ī red box is appearing that says "incompatible mod archive" it gives me the option of "more" which shows details, and "check again".
Report this issue to the mod author and ask him to update his mod using the correct archive packing tool.Ignore the warning and play as you usually do but please keep in mind that any irregularities in the game are potentially due to the incompatible archive.Please read more about Bethesda mod archives here: The mod may appear to be working correctly in-game in some scenarios, but bottom line is Vortex's warning is correct and the mod archive has an incorrect header value! Vortex's archive checker functionality is designed to read the archive's header to ascertain the target game for the archive - there is absolutely NO way this check would give false results - your mod archive has probably been created using outdated tools which were meant to be used with a different (older) game and therefore the fault lies with the mod archive and the mod author for not using the correct archive packing tools!
Your report has been added to this GitHub page as you've recently reported that Vortex is "erroneously" reporting your game archive as incompatible. *Yes, I am going to continue to repeat that it's awful every time I mention it.This issue has been created to collate all "Incompatible BSA/BA2 archive" bug reports. fomm has also been updated to 0.10.3, which improves archive invalidation, the save game list and the bsa browser. The (rubbish*) multiplayer mode is now functional and the client is included, there's control over premade characters, (including the ability to add more than 3 options,) and the usual batch of new script functions and hook scripts.
(That was also the reason why fomm and sfall's check for update options haven't been picking up on the new versions until yesterday I wasn't able to upload the version data files.) The only particularly annoying thing I lost was some better documentation I was writing for sfall I'd actually gone through all the code and made a list of exatly what it was capable of doing, and how to use everything. I lost all my scripts for building and publishing file releases and webpages, and hadn't got around to recreating them until now.
The problem came because of a slight difference in the behaviour of windows explorer between win xp and win 7 which led to me deleting one of my backup folders instead of copying it. My computer failed on me shortly after christmas, which wasn't too much of an annoyance since it was getting a bit old and I was intending to replace it soon anyway, and the failure gave me an excuse to get it over with. If it's fallout mod manager you're after, then click here.Īnd another very long time without updates.
Are you lazy, and just want to download oblivion mod manager without having to look for it? If so, then click here.