So for a while I've been wondering "what happened", since the last reply I got on "this" thread was "will look into it later when I get home and such", after which I got no reply at all. Apparently, what happened is the forum was wiped, due to switching to a different forum type and such.
Thus I hereby re-post this thread (as I still have the issue, even after deleting the old profile and making a new one, where only the most important-to-me plug-ins have even been downloaded).
Need a refresher? Well, basically, if I at any time load a profile in Input Mapper 2 and then attempt to save a profile, it crashes. Whether the profile load is from the "load last profile on start-up" option of the profile plug-in or going to the profiles and loading one after booting Input Mapper 2 doesn't matter, both things cause a crash (where-as if no profile has been loaded in a session of Input Mapper 2, it won't crash).
Please pretend this is a long descriptive post telling you to make a profile on your own, using a DS4 input over wireless BlueTooth and an XBox output, where the XBox output's rumble is hooked up to make the DS4 input rumble, and the DS4's touch one X, one Y, and two X are respectively mapped to the DS4's light bar's red, green, and blue colours (without the rest of the DS4 mapped to anything, not even the XBox output), save that, reboot Input Mapper, load it, and try to save it again, as the long descriptive post was completely destroyed just as I tried to post it.
I opened up PluginInstaller, dragged ColorChanelInjector.imp into it, let it install, booted InputMapper 2, checked the plug-ins (the "installed" version of Color Chanel Injector is newer than the "available" version), made a new profile with just a wireless BlueTooth DS4's touchpad one X, one Y, and two X mapped to red, green, and blue of the light-bar, saved the profile (worked fine), loaded it, and clicked save again (crash).
By the way, there's something I've thought about I haven't mentioned, which I suppose is probably very relevant... When mapping the DS4, is there supposed to be a "True"/"False" or 0.0-1.0 value beneath the DS4's control's name, depending on whether I'm pressing (or how much I'm pressing) a given button (or axis), and beneath THAT is another "False" value? I know the former is supposed to be there, but the latter... I'm beginning to think I or Input Mapper have/has done something stupid, which is causing the crashes.
In case that's confusing for you (it probably is), I'm trying to say that beneath the DS4's mapping's control names, it shows a boolean as "True"/"False" and a float as 0.0-1.0, to show what the current value is, but beneath that value is another always-boolean value, always saying "False" (even for float values). I can provide a screenshot tomorrow if you want, but right now it's way too late for me to think well anymore.
I'm still thinking it has to be a version discrepancy, ill double check your versions again against what I have when I get back to my computer. That error is the exact error that you would get if you had an old version of ODIF floating around or one of the plugins was expecting an older version of ODIF.