You may not want to do this - this can interact poorly with graphics driver threads which pin themselves to a specific hardware thread as well. If you do do it, I highly recommend doing it by just unchecking "use multiple cores" in options (this is mainly what that option does), *not* by using the native OS affinity tools, because then Myth knows not to launch a separate GUI thread and so on (which is necessary to enable continuous resizing among other things).dac wrote:(because myth affinity is set to 1 processor only).
If you are already using the ingame option (unchecked), try checking it instead.
Milk: do you have specific repro steps or does it happen seemingly randomly? When it happens, do you need to switch maps and switch back or something? Does launching the game still work as expected even when it says ERROR? Would it show the "error" in the preview in the game setup screen itself, or just when you clicked OK and go back to the game lobby?
