You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using both mods, OpenPeripheral Addons makes the sensor turtles sensor no longer recognizable for openCCsensors as an attached peripheral.
So wrapping the sensor fails. "Attemp to call nil"
This occurs with V0.1.3 and V0.1.4 and possible earlier versions of OpenPeripheral Addons in conjunction with OpenCCsensors V1.6.4.3 (and earlier).
As soon as OpenPeripheral Addons gets removed, the sensor works again.
And this is NOT an ID conflict.
The text was updated successfully, but these errors were encountered:
OpenCCsensors is so old that can crash with some new peripherals from CC and his addons. Forget it, Openperipheral sensor and peripheral drivers ( you don't even have to install modules on sensors anymore ) are 1000x better.
@ TorakWolf - that's more about your opinion than fact though (and no offence meant) - I prefer OpenCCSensors' sensors usage (there's more of them for a start) and lyqyd is still actively developing it/ adding fixes.
the problem is that OpenPeripheralsAddons also uses Upgrade ID 180 , which on the wiki is allocated to cloudy [openCCSensors] et al, not to this mod.... so OpenPeripherals need to change their ID to something else... a lot of people like to use both mods, as they respect both applications and how they work... and since OpenCCSensors had this Upgrade ID first. it's OpenPeripherals that respectfully should change their ID to something that wasn't already documented on the official page as being used already.
When using both mods, OpenPeripheral Addons makes the sensor turtles sensor no longer recognizable for openCCsensors as an attached peripheral.
So wrapping the sensor fails. "Attemp to call nil"
This occurs with V0.1.3 and V0.1.4 and possible earlier versions of OpenPeripheral Addons in conjunction with OpenCCsensors V1.6.4.3 (and earlier).
As soon as OpenPeripheral Addons gets removed, the sensor works again.
And this is NOT an ID conflict.
The text was updated successfully, but these errors were encountered: