Reply to thread

Message

<blockquote data-quote="MARKFNZ" data-source="post: 415134" data-attributes="member: 54617">I noticed with MP 1.0.1 it initialises Milkdrop on startup, as there was an old problem in the earlier versions that Milkdrop would crash MP the first time it ran after a reboot. You could then just restart MP and it would work fine. I think perhaps they have decided to initialise Milkdrop on startup to maybe fix this.When I run MP, I get the Milkdrop window pop up for a couple of seconds at startup and then dissapear.I wonder if perhaps the settings changes you have made to Milkdrop have caused an issue, and because MP only sees these changes when the ini is in .\plugins\plugins the issue only shows when you have the new milkdrop2.ini file in there?Can you try a fresh install of Milkdrop, to recreate the milkdrop2.ini file, copy that to the .\plugins\plugins and see if that works...then change one thing at a time, and copy the .ini file to see if a certain setting is causing the issue? Maybe even just delete the .ini file in the viz folder and see if it creates a new one?Mark</blockquote>

[QUOTE="MARKFNZ, post: 415134, member: 54617"] I noticed with MP 1.0.1 it initialises Milkdrop on startup, as there was an old problem in the earlier versions that Milkdrop would crash MP the first time it ran after a reboot. You could then just restart MP and it would work fine. I think perhaps they have decided to initialise Milkdrop on startup to maybe fix this. When I run MP, I get the Milkdrop window pop up for a couple of seconds at startup and then dissapear. I wonder if perhaps the settings changes you have made to Milkdrop have caused an issue, and because MP only sees these changes when the ini is in .\plugins\plugins the issue only shows when you have the new milkdrop2.ini file in there? Can you try a fresh install of Milkdrop, to recreate the milkdrop2.ini file, copy that to the .\plugins\plugins and see if that works...then change one thing at a time, and copy the .ini file to see if a certain setting is causing the issue? Maybe even just delete the .ini file in the viz folder and see if it creates a new one? Mark [/QUOTE]

Verification