Reply to thread

Message

<blockquote data-quote="hwahrmann" data-source="post: 664979" data-attributes="member: 10391">So what's the problem?Simply use Milkdrop 2.2Ok, so i found the problem with those ini files. When you press Config, it write the Ini file into the same folder, where vis_milk2.dll resides.But as we all know, it isn't taken from there.When executing the vis, it looks into a folder named Plugins, which is located as a subfolder to the exectuable, Mediaportal.exe in our case.We have a Plugins subfolder directly under the MP root and this is the folder where all MP Plugins reside.If you look into this folder when Milkdrop has run once, you will find a mini milk2.ini in there.Simply move/copy the one which you find in the Vis folder over there and you have what you need to achieve.I'll search a bit, if i can change that.If not, i will simply copy the milk2.ini file over, when the config has done.</blockquote>

[QUOTE="hwahrmann, post: 664979, member: 10391"] So what's the problem? Simply use Milkdrop 2.2 Ok, so i found the problem with those ini files. When you press Config, it write the Ini file into the same folder, where vis_milk2.dll resides. But as we all know, it isn't taken from there. When executing the vis, it looks into a folder named Plugins, which is located as a subfolder to the exectuable, Mediaportal.exe in our case. We have a Plugins subfolder directly under the MP root and this is the folder where all MP Plugins reside. If you look into this folder when Milkdrop has run once, you will find a mini milk2.ini in there. Simply move/copy the one which you find in the Vis folder over there and you have what you need to achieve. I'll search a bit, if i can change that. If not, i will simply copy the milk2.ini file over, when the config has done. [/QUOTE]

Verification