I setup a different computer to use with my printer. It never had any 3D printer stuff installed on it. In printer setup, I set it for one heater for all extruders, defined two virtual extruders and brought over all my Slic3r profiles from the original setup. The firmware is set up for a MIX extruder.In my test cases, I am using 0/1 and 1/0 ratios for the test virtual extruders, so I can easily see what is being driven. When I ran my quick test print with no filament, it behaved as before, when I select the first virtual extruder, stepper motor #2 is driven. If I select the second virtual extruder and slice it, then stepper motor #2 will drive as you would expect it to. I added a third virtual extruder, such that extruders number 2 and 3 select stepper motors 1 and 2. It works as it should!If I slice an object with virtual extruder 1 it drives stepper 2 no matter whether the script is 0/1 or 1/0. Virtual extruders 2 and 3 work as the script describes. This is beginning to look like a real bug somewhere. Depending upon how people define their extruders, I wouldn't be surprised that it hasn't been detected before now, if there is something in my setup that is aggravating things. In my case when I had a 13 extruders defined for a cyclops, I probably couldn't have realized the difference between the first mix setting and the second. In the present and the recent past, I am only using 0/1 or 1/0 ratios because I replaced the mix hotend with a Y in the path between the steppers and hotend. I'll switch the FW to a shared heater when this gets sorted out. I want to get to some sore of resolution, even if it involves making virtual extruder 1 a dummy, so that I can switch back to a cyclops if a need arises.
