Site Login

This Months Donations

$545.03
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
SiesMAN01
$2.00
André Philipi da Silva
$2.00
lookingglassties
$2.00
Keanu Allridge
$5.00
Sven Eckelmann
$10.00
Number of donations
25
Highest donation
$500.00
Average donation
$21.92

[Profile plug-in] Crash when saving loaded profile

3 years 3 months ago #1 by Zwip-Zwap Zapony
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).

Any more information required, do ask.

Please Log in or Create an account to join the conversation.

3 years 3 months ago #2 by Wobbles
Obviously a lot of stuff going on here since then, im sure I asked before but need a refresher, could you upload one of the profiles giving you problems?

Please Log in or Create an account to join the conversation.

3 years 3 months ago #3 by Zwip-Zwap Zapony
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).

Example profile which crashes? [LINK]

Also, as I can imagine you'd probably like a new crash log... [LINK]

Please Log in or Create an account to join the conversation.

3 years 3 months ago #4 by Wobbles
So I was able to load then re-save without issue. One difference I found was a difference in version for the color channel injector plugin. Try the attached.
Attachments:

Please Log in or Create an account to join the conversation.

3 years 3 months ago #5 by Zwip-Zwap Zapony
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.

Please Log in or Create an account to join the conversation.

3 years 3 months ago #6 by Wobbles
um ok, so the updated plugin does not work for you then?

Please Log in or Create an account to join the conversation.

3 years 3 months ago #7 by Zwip-Zwap Zapony
(Please fix clicking "Submit" without checking the "I'm not a robot" security check thing wiping what one wrote, as that security check thing some times doesn't even pop up.)

Provided I install it by overriding ColorChanelInjector.imp in %appdata%\InputMapper2\downloads and booting up Input Mapper 2, doing nothing beyond that, no, it didn't help.

Please Log in or Create an account to join the conversation.

3 years 3 months ago #8 by Wobbles
If for whatever reason the imp extension is not bound meaning you cannot just double click it to install it, use the PluginInstaller.exe located in the InputMapper application folder.

Please Log in or Create an account to join the conversation.

3 years 3 months ago #9 by Zwip-Zwap Zapony
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.

Please Log in or Create an account to join the conversation.

3 years 3 months ago #10 by Wobbles
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.

Please Log in or Create an account to join the conversation.

Powered by Kunena Forum