Cannot resolve symbol 'Cable'. Cannot resolve symbol 'ERenderCommandPipeFlags'
Even with a global search I’m not able to find any occurrence of ERenderCommandPipeFlags anywhere in the engine, are you using a source build?
However, it is enough to delete the OnUpdateTransform function from CableComponent .h and .cpp, now it’s pretty clear to me why it didn’t work in the editor and it did in the packaged build…
Yes, it doesn’t work like that anymore, it looks like the guys from epic added raytracing support to the component, I tried it about half a year ago, and it worked, try an older revision from branch 5.4 where Raytracing Support is not implemented for the Cable Component , Or switch your project to 5.4 source build, and version 5.4 will be released soon. Good Luck.
Would you be able to say how you rebuilt the solution with the altered code?
By simply removing “OnUpdateTransform” from the .h and .cpp files, nothing happens.
I’ve tried to rebuild and regenerate project files, but it always runs the old version.
I then tried first deleting the Intermediate and Binary files from the CableComponents plugin folder, thinking that would ensure they are regenerated - this just leads to me not being able to launch unreal, with the error message “The following modules are missing or built with a different engine version: CableComponent”. Building and regenerating the project’s and UE5’s files on VS studio has no effect here as well.
I have also tried utilizing the batch tools in Engine/Build/BatchFiles, but they close as soon as i open them (maybe im supposed to use them with specific arguments?)
For information, I am using version 5.3.2, directly downloaded and installed through the Epic Games Launcher. Does this stop me from being able to modify and regenerate source code?
THANK YOU! This works perfectly! After 20 straight hours of trying to debug this, it finally works.
For anyone who encounters a similar issue: You can always move the plugin folder back to its original location, after it has rebuilt itself on launch! This ensures that all your different projects have the updated binaries.
This is something that I sometimes do, but only for solo projects.
It’s not a “good practice” if you work with a team, that’s why I avoid recommending it to other people. I prefer to have it in the plugins folder and pushed to the Git repo, just to ensure that everyone is working with the same version of the plugin!