Sounds like the local saved config could get messy over time, especially with lots of edits.
I’ve added some safeguards so bad or oversized saved data shouldn’t cause slowdowns or startup issues anymore.
Also moved the config from the registry to a local file (BepInEx\config\CubiLink.cfg) so it’s easier to manage and reset if needed.
This is an excellent plugin. It would be even better if it had a mapping or limiting function for the axis output range, like we see in most plugins or script players. While this can be achieved by adjusting the axis mapping in the template, the final output range adjustment should be template-independent. The template settings should only indicate how to map the parameters to the corresponding percentages, which would be safer and more convenient, since the actual usage range of each axis depends on the user and device.
I’ve created a file that integrates the Succubus Casino templates I previously submitted.
It has been adjusted so that the gameplay portion of the slot section switches automatically.
Due to the character limit for Offset, only the Extra section accessible from the menu is not functional, but I don’t think it has much impact.
When you set the parameter ranges for Live2D in the plugin, you are already defining the axis output range (you can simply expand the range a bit to limit its actual motion range). Adding an extra option to restrict the axis output range would be functionally redundant.
I can see the advantage of having separate output control without having to mess with the templates (or expressions).
I’ll probably add per-axis range sliders in the next update
Some values appear to change in the list, but when I actually assign them, they do not work. What could be the reason for this?
Also, when I set them as items and load them from Offset as Display, they do work. Does this mean that Display is referencing the values shown in the list?
In this case, the indicator responds, but the actual device does not reflect the changes.
When specifying something like p_ParamN as a function, would it be possible to add a specific modifier or function so that it behaves the same way as when referenced via Display?
For example, I’m imagining something like p_Param*display, d_ParamN, or p_ParamN+AAA.
If this is already possible and I simply haven’t noticed, could you please let me know how to write it correctly?
I am Japanese, and after doing some research on BepInEx, it seems that if there are full-width characters (such as Japanese) in the path below the directory where BepInEx is installed, the plugins folder and other folders will not be automatically generated. (Although there seem to be rare cases where they are automatically generated, it generally doesn’t happen.)
This may not be the case for Falafel, but in my case, “Somnia Short Story – Rose-Colored –” was downloaded in Japanese, and that seems to have caused the folder not to be automatically generated.
I changed the Japanese folder name to a suitable English name, and then it was automatically generated.
I was using the X86 version of BepInEx, thank you.
I usually work while monitoring the indicator and only test after finishing. However, I realized that while the indicator responds when using Display, it is not actually reflected in the device’s behavior. Conversely, some items where the indicator does not respond are in fact properly reflected in the device’s operation.
I deeply apologize for the trouble caused due to my lack of proper verification.
It seems that what I should have reported instead is that there are cases where certain items function correctly, but their behavior is not reflected in the indicator.
I am truly sorry for the confusion and inconvenience caused. Please accept my sincere apologies once again.
Additional note: The issue where the indicator does not reflect the behavior appears to have started occurring from v2.6.1.
Thanks again for the feedback.
One of the recent updates changed the T-Code output to a proper 0–9999 (D4) range, but looks like it wasn’t fully reflected in the preview bars.
That UI-mismatch should now be fixed in the latest version.
There’s no direct sync/delay setting. The output is based on real-time movement from the game.
You can try different connection methods (like Serial port) for lower latency.
Hz controls how often the device gets updates. Higher = smoother and more responsive, but too high can cause unnecessary load or even worse stability.
Working
Partial
