Hello :)
This looks like an oversight on the logic for ensuring XeLL remains on during any time XeFG is enabled, but if you set via UXeLLBlueprintLibrary::SetXeLLMode it never updates the "r.XeLL.Enabled" CVar, so the logic in FXeLLModule::Tick() never applies. It arguably would be better if all this logic was done in the core FXeLLModule::SetXeLLMode() function and/or via CVar sinks rather than allowing you to directly change the value to Off when it never should be the case/performing an unnecessary Tick.
Let me know if I've missed something :)
Best of luck,
Billy Fletcher
Hello :)
This looks like an oversight on the logic for ensuring XeLL remains on during any time XeFG is enabled, but if you set via
UXeLLBlueprintLibrary::SetXeLLModeit never updates the "r.XeLL.Enabled" CVar, so the logic inFXeLLModule::Tick()never applies. It arguably would be better if all this logic was done in the coreFXeLLModule::SetXeLLMode()function and/or via CVar sinks rather than allowing you to directly change the value toOffwhen it never should be the case/performing an unnecessary Tick.Let me know if I've missed something :)
Best of luck,
Billy Fletcher