My install seems to be feeding the filenames twice: https://i.imgur.com/NzNvm6J.png
diziet edit: the problem seems to be here: function previewHandler(api, winmergePath, files) { return new Promise((resolve, reject) => { try { const proc = child_process_1.spawn(winmergePath, [files[0].filePath, files[1].filePath]); proc .on('error', err => { reject(err); }) .on('exit', () => { resolve(null); }); } catch (err) { reject(err); } }); } playing with [files[0].filePath, files[1].filePath] shows that each files[x] results in both filepaths but in swapped orders:) Perhaps Vortex has changed its api for referring to files? or a bug in Vortex, my versoin is 1.10.6.
I am glad I found this. With all the loose files in Starfield, this allows me to make educated decisions! Alas, now they are moving to the esm format, and I guess it will be harder to see the differences unless there is another tool I do not know about.
Tannin thank you!!! You have some amazing extensions for Vortex. I didn't even know about Winmerge. This thing even tells me if the images are identical so I'm not psyching myself out trying to compare.
but what made you choose to keep them out of the main build? ..was it just to keep Vortex modular or?
This extension is great for comparing .dds texture files, however, it comes with the unfortunate side-effect that it also tries to compare .nif model files, even though WinMerge can't display them properly.
Is there a way to stop this plugin from attempting to preview .nif files, and let them go to the default program like normal? NifSkope does a much better job at it.
9 comments
https://i.imgur.com/NzNvm6J.png
diziet
edit: the problem seems to be here:
function previewHandler(api, winmergePath, files) {
playing with [files[0].filePath, files[1].filePath] shows that each files[x] results in both filepaths but in swapped orders:)return new Promise((resolve, reject) => {
try {
const proc = child_process_1.spawn(winmergePath, [files[0].filePath, files[1].filePath]);
proc
.on('error', err => {
reject(err);
})
.on('exit', () => {
resolve(null);
});
}
catch (err) {
reject(err);
}
});
}
Perhaps Vortex has changed its api for referring to files? or a bug in Vortex, my versoin is 1.10.6.
This thing even tells me if the images are identical so I'm not psyching myself out trying to compare.
but what made you choose to keep them out of the main build? ..was it just to keep Vortex modular or?
Is there a way to stop this plugin from attempting to preview .nif files, and let them go to the default program like normal?
NifSkope does a much better job at it.
Edit: Changed "NifScope" to "NifSkope"
Would it be possible to change the button text to "Same" when both files are the same?