Let me start by saying, I am not a programmer by any means, but I thought I'd give this a shot. I believe I followed the directions, but I may be missing something. I downloaded the files to a directory, installed MSYS2, started it, changed directory to right location, ran the script, but I keep getting this error:
./conflict_detector.sh: line 265: dos2unix: command not found ./conflict_detector.sh: line 265: dos2unix: command not found ./conflict_detector.sh: line 265: dos2unix: command not found ./conflict_detector.sh: line 265: dos2unix: command not found ./conflict_detector.sh: line 265: dos2unix: command not found, etc. etc. etc.
Eventually it completes, but no output files. Not even an error log.
dos2unix is an utility to convert an annoying different way to detect and manage an end-of-line in a text file between Unix and DOS (Windows, that is to say).
I'll try to detect whether a system has that utility or not and, if the case, to implemet a simple replacement. Don't hold your breath, anyway...
Thanks for drawing my attention to the issue. Regards,
Well, I cannot understand a single thing about this mod, tool, or whatever it should be termed - not your instructions period, or it use. With respect, this seems as yet another of those things one needs to be a coder, programmer, etc. to be able to know how to use. I wish folks could just explain things in laymans' terms that people who have never been able to figure out XEdit, CK, etc, could actually understand. I am pretty sure this is a great tool for those with the savvy to use it - for myself, nope!
I get this error when I run ./Conflict_Detector.sh. I'm on Windows 11 using Ubuntu with Windows Subsystem for Linux. this is where it's being ran corleon@godfather:/mnt/g/Fallout 4 Tools/Conflict Detector and Mapper 1.2-40600-1-2-1571168668$
Sorry for the late response. Yes, this is a problem related to Windows Subsystem for Linux, as reported by other users too. I don't use WSL so I'm afraid I can't fix it.
Script takes time long as f*#@) I have total 450 mods and not so bad notebook(12700h+3070ti+64gb ddr) and it's take for now something like 6 hours without consumption merely one core) and did only 1/3 of work. Idk if this problem with msys2 or script itself, but if you get a lot of mods, better use this when you get to sleep)
I am unsure but I thought Mod Organiser showed conflicts (both loose and BA2?) I don't understand most of what I read tbh, lol But if MO2 is not showing archived conflicts then I can see how this would be very handy for load order organisation. If it does though, It's odd that that feature is not present in Vortex?
Frankly I don't know. I'm using Vortex right now. I used Mod Organizer in a Skyrim setup when it was the, well, how to name it? the "old" Mod Organizer. I don't use MO2 and I can't say anything about it. This feature is not present in Vortex yet, anyhow: see eg https://github.com/Nexus-Mods/Vortex/issues/3396.
Developers are working on this feature but, in the meanwhile, I developed this tool for myself and I thought it was somewhat useful and worth to share. My two cents, so to speak.
With reference to Ubuntu. Conflict Detector does not run in it's bash shell.
Go to http://www.mingw.org/ At top of Page is a "Download" button, click to get to next page At the bottom of the next page is a list of files, you want the 1st one called
MinGW Installation Manager (mingw-get) This is just an installer for the MinGW program
Download MiniGW Installer and install program following instructions, I found it best to install to C:\MinGW, as stated in the instructions, you do have an option to change the directory if you want to, I had problems using another directory, you might not.
When the program is installed go to C:\MinGW\msys\1.0
Make a short cut to desktop or a directory of your choice of the file named msys
Click twice on the msys shortcut and a shell will open,
Now you can think about running Conflict Detector.
Even though Gaznevada states "Create a directory of your choice and unpack the archive " all that happened with me was just lines in the shell stating Files/Directory not found.
So I tried moving Conflict Detector and unpacking it in the directory where my Fallout 4 game was installed H:\Fallout\steamapps\common\Fallout 4 (My installation, use your own)
I double clicked on Conflict Detector itself and it checked 1009 conflicts in about 4-5 minutes.
The above is how my setup went, yours might be different when you come to install and run Conflict Detector, well pleased with it, now all I have to do is try and sort out 1000+ conflicts, I have so many as I have managed to get 408 Mods up and running.
First of all thanks for taking your time to check the script. So i assume that my script, as it is, does not work under the bash shell of Ubuntu distribution in the Windows Store. Time to check why...
Few lines of comment: "Download MiniGW Installer and install program following instructions, I found it best to install to C:\MinGW, as stated in the instructions, you do have an option to change the directory if you want to, I had problems using another directory, you might not."
Yes, better to stick on "C:\MinGW". MinGW is quite picky about whitespaces, better to install it on a root directory with no spaces in the name.
"Even though Gaznevada states "Create a directory of your choice and unpack the archive " all that happened with me was just lines in the shell stating Files/Directory not found."
Did you change the line in which "GAMEDIR" variable is stored? It's the fourth line of the script and it's the only line to edit to reflect your game setup.
Glad to hear that you managed to have it working but please keep in mind that the scrip just point out conflicts, no directions or hints on how to solve them if and when it would be necessary.
Thanks so much for the extra Details and your time. If it was not for this I would have failed.
I have over 800 Mods and everything that can help to find and resolve issues are always useful. I know Vortex well, use FO4Edit and its conflict detection and many other tools But this does seem very useful addon for finding those elusive texture and mesh issues between multiple BSA files and also loose file interaction.
For the ones not using these Bash tools or Unix commands often here is a bit extra that worked for me. My GITBASH did not run this script smoothly, it had all sorts of errors and produced log files about 20% smaller or less complete.
This portion of the install "Download the mingw-get-setup.exe" and follow the instructions." I must have either missed something, not read enough or I am very slow. Clearly I did not "follow the instructions part" because it did not leave me with this folder and its files. It was missing after the install. "C:\MinGW\msys\1.0\msys.bat". So it had me stumped for a bit. It is just sad if you get stuck on the install of all things
I had to add this bit to my install which was probably due to some reading I did not do.
After installing "mingw-get-setup.exe" run MinGW Installation Manager Select and install everything under "Basic Setup" (Which might not all be needed but it worked for me) then top menu>Installation>Apply Changes.
Had to quickly sharpen up on my unix syntax commands to do drive and folder change to install folder with this command cd "/D/Games/Steam/SteamApps/Common/Fallout 4/Conflict Detector and Mapper/" then run the the script "Conflict_Detector.sh"
It ran clean and and worked perfectly Thanks "Gaznevada" for a great Tool. You can never have enough Tools With Fallout. Maybe this will help some other Slow folks like me out there.
I'm afraid the real meaning of my tool has been misunderstood. Let my try to explain with an example from MO2 and SSE, which I use right now for my SSE gameplay (btw: my tool DOES NOT work with MO2, it is intended to work along with a real file system, not a virtual one. Main issue arises from the shell, of course...).
I have two mods, 'Birds of Skyrim', load order number 4E, and 'Birds and Flocks SSE', load order 60. Both mods load a .bsa archive showing no conflicts in MO2: an empty field in the 'Conflicts' column. Both of them. If I right click 'Information' and open the Conflict tab, nothing appears. No conflicts at all.
But if you browse the archives (Information - Filetree - right click on 'preview') you can see that BOTH ARCHIVES has the very same file in the very same position, namely 'fxbirdflockfleepine.nif' under Data/meshes/effects. Well, this is a hard-to-see conflict (I mean: it is undetected by Vortex and MO2). Being a conflict, there will be just one and only one winner: 'fxbirdflockfleepine.nif' coming from Birds and Flocks SSE, load order 60, will be the Chosen One.
More: under MO2 'Data' tree there are no instances of 'fxbirdflockfleepine.nif' where it is supposed to exist. Now what?
This is the meaning of my tool: to detect conflicts stemming from archived files, not from loose files only. Being there, why not mapping all the conflicts? and why not trying to write down a 'reverse map'? My tool try to address those issues with a complete map of your installation. Which takes its time, a shell script is not exactly like greased lightning.
So said, my tool does not 'already exist', not in Vortex at least, set aside whether Vortex works better than MO2 or not.
If MO2 has a way to detect (and resolve) conflicts by scanning archives, well, forgive my clumsiness and please show me the way.
Where do I find a Bash shell program Leave links man You can't have a website that doesn't have the link some people don't know what the are doing so they rely on the modder to show them. It' like a giant f*#@ you to the people who don't know what to do man.
I will try to make it as short as possible but please note that a mingw installation is out of the scope of both this mod and the Nexus as well, I think.
So said,
1) go to http://mingw.org/ (MinGW stands for "Minimalist GNU for Windows") 2) Very important: read carefully all the relevant documentation. It takes time and a little bit of effort but it is worth of it. 3) On the left bar you will find a "Download" link which will take you on the page in which Installers are stored 4) Download the "mingw-get-setup.exe" and follow the instructions.
Please note that this is not a course on how to setup a bash shell, not even a crash-course. I'm not aware of bash shells "standalone", maybe others could help you.
Try communicating politely mate. This guy took the the time to make a mod, for other's benefit and has literally just released it in the last few minutes. You sound like an entitled child.
@ ohara321 Having premium doesn't give you the right to speak to people how you want. I would use a more level tone without the expletives a long-standing member has been banned not too long ago because despite many friendly warnings he couldn't be civil when commenting.Being friendly and asking politely is much more likely to get you what you want in the longrun...
39 comments
./conflict_detector.sh: line 265: dos2unix: command not found
./conflict_detector.sh: line 265: dos2unix: command not found
./conflict_detector.sh: line 265: dos2unix: command not found
./conflict_detector.sh: line 265: dos2unix: command not found
./conflict_detector.sh: line 265: dos2unix: command not found, etc. etc. etc.
Eventually it completes, but no output files. Not even an error log.
I'll try to detect whether a system has that utility or not and, if the case, to implemet a simple replacement. Don't hold your breath, anyway...
Thanks for drawing my attention to the issue. Regards,
Well, I cannot understand a single thing about this mod, tool, or whatever it should be termed - not your instructions period, or it use. With respect, this seems as yet another of those things one needs to be a coder, programmer, etc. to be able to know how to use. I wish folks could just explain things in laymans' terms that people who have never been able to figure out XEdit, CK, etc, could actually understand. I am pretty sure this is a great tool for those with the savvy to use it - for myself, nope!
Regards,
this is where it's being ran
corleon@godfather:/mnt/g/Fallout 4 Tools/Conflict Detector and Mapper 1.2-40600-1-2-1571168668$
Regards,
Developers are working on this feature but, in the meanwhile, I developed this tool for myself and I thought it was somewhat useful and worth to share. My two cents, so to speak.
Regards,
Go to http://www.mingw.org/
At top of Page is a "Download" button, click to get to next page
At the bottom of the next page is a list of files, you want the 1st one called
MinGW Installation Manager (mingw-get)
This is just an installer for the MinGW program
Download MiniGW Installer and install program following instructions, I found it best to install to C:\MinGW, as stated in the instructions, you do have an option to change the directory if you want to, I had problems using another directory, you might not.
When the program is installed go to
C:\MinGW\msys\1.0
Make a short cut to desktop or a directory of your choice of the file named
msys
Click twice on the msys shortcut and a shell will open,
Now you can think about running Conflict Detector.
Even though Gaznevada states "Create a directory of your choice and unpack the archive " all that happened with me was just lines in the shell stating Files/Directory not found.
So I tried moving Conflict Detector and unpacking it in the directory where my Fallout 4 game was installed
H:\Fallout\steamapps\common\Fallout 4 (My installation, use your own)
I double clicked on Conflict Detector itself and it checked 1009 conflicts in about 4-5 minutes.
The above is how my setup went, yours might be different when you come to install and run Conflict Detector, well pleased with it, now all I have to do is try and sort out 1000+ conflicts, I have so many as I have managed to get 408 Mods up and running.
Few lines of comment:
"Download MiniGW Installer and install program following instructions, I found it best to install to C:\MinGW, as stated in the instructions, you do have an option to change the directory if you want to, I had problems using another directory, you might not."
Yes, better to stick on "C:\MinGW". MinGW is quite picky about whitespaces, better to install it on a root directory with no spaces in the name.
"Even though Gaznevada states "Create a directory of your choice and unpack the archive " all that happened with me was just lines in the shell stating Files/Directory not found."
Did you change the line in which "GAMEDIR" variable is stored? It's the fourth line of the script and it's the only line to edit to reflect your game setup.
Glad to hear that you managed to have it working but please keep in mind that the scrip just point out conflicts, no directions or hints on how to solve them if and when it would be necessary.
I have over 800 Mods and everything that can help to find and resolve issues are always useful. I know Vortex well, use FO4Edit and its conflict detection and many other tools But this does seem very useful addon for finding those elusive texture and mesh issues between multiple BSA files and also loose file interaction.
For the ones not using these Bash tools or Unix commands often here is a bit extra that worked for me. My GITBASH did not run this script smoothly, it had all sorts of errors and produced log files about 20% smaller or less complete.
This portion of the install "Download the mingw-get-setup.exe" and follow the instructions." I must have either missed something, not read enough or I am very slow. Clearly I did not "follow the instructions part" because it did not leave me with this folder and its files. It was missing after the install. "C:\MinGW\msys\1.0\msys.bat". So it had me stumped for a bit. It is just sad if you get stuck on the install of all things
I had to add this bit to my install which was probably due to some reading I did not do.
After installing "mingw-get-setup.exe"
run MinGW Installation Manager
Select and install everything under "Basic Setup" (Which might not all be needed but it worked for me)
then top menu>Installation>Apply Changes.
Had to quickly sharpen up on my unix syntax commands to do drive and folder change to install folder with this command
cd "/D/Games/Steam/SteamApps/Common/Fallout 4/Conflict Detector and Mapper/"
then run the the script
"Conflict_Detector.sh"
It ran clean and and worked perfectly Thanks "Gaznevada" for a great Tool. You can never have enough Tools With Fallout.
Maybe this will help some other Slow folks like me out there.
I have two mods, 'Birds of Skyrim', load order number 4E, and 'Birds and Flocks SSE', load order 60. Both mods load a .bsa archive showing no conflicts in MO2: an empty field in the 'Conflicts' column. Both of them. If I right click 'Information' and open the Conflict tab, nothing appears. No conflicts at all.
But if you browse the archives (Information - Filetree - right click on 'preview') you can see that BOTH ARCHIVES has the very same file in the very same position, namely 'fxbirdflockfleepine.nif' under Data/meshes/effects. Well, this is a hard-to-see conflict (I mean: it is undetected by Vortex and MO2). Being a conflict, there will be just one and only one winner: 'fxbirdflockfleepine.nif' coming from Birds and Flocks SSE, load order 60, will be the Chosen One.
More: under MO2 'Data' tree there are no instances of 'fxbirdflockfleepine.nif' where it is supposed to exist. Now what?
This is the meaning of my tool: to detect conflicts stemming from archived files, not from loose files only. Being there, why not mapping all the conflicts? and why not trying to write down a 'reverse map'? My tool try to address those issues with a complete map of your installation. Which takes its time, a shell script is not exactly like greased lightning.
So said, my tool does not 'already exist', not in Vortex at least, set aside whether Vortex works better than MO2 or not.
If MO2 has a way to detect (and resolve) conflicts by scanning archives, well, forgive my clumsiness and please show me the way.
Regards,
So said,
1) go to http://mingw.org/ (MinGW stands for "Minimalist GNU for Windows")
2) Very important: read carefully all the relevant documentation. It takes time and a little bit of effort but it is worth of it.
3) On the left bar you will find a "Download" link which will take you on the page in which Installers are stored
4) Download the "mingw-get-setup.exe" and follow the instructions.
Please note that this is not a course on how to setup a bash shell, not even a crash-course. I'm not aware of bash shells "standalone", maybe others could help you.
Thanks for your suggestions. Regards,
UBUNTU
This will allow you to run a bash shell, follow the instructions to use.
Having premium doesn't give you the right to speak to people how you want. I would use a more level tone without the expletives a long-standing member has been banned not too long ago because despite many friendly warnings he couldn't be civil when commenting.Being friendly and asking politely is much more likely to get you what you want in the longrun...