Hi,

The factories for such components are registered automatically. The name of a native C++ UClass is of the form /Script/ModuleName.ClassName. We register such classes with the name ModuleName.ClassName. So, most likely reason is that the namespaces are wrong.

Hope this helps!

Did you just rename the DLL and LIB files? They need to be rebuilt with the changed name. The DLL name is in the associated LIB file, so just renaming them won't work.

Hi,

Could you create a ticket for this problem? I have a patch for you to try.

Thanks!

Hi David, I haven't been able to reproduce you exact problem, but I've found a similar one. I think you're right in your assesment: multiple configurations of our dll have to coexist in the same directory. That means that having them called the same in different directories won't work. What we've do...

Hi, I've been looking into this. Turns out the VR template turns off a rendering feature called Separate Translucency that we counted on to render in world space. I believe that simply choosing MSAA as the antialiasing method also disables it. I've figured out how to make it work, but I need to test...

If I understand it correctly, you want to be able to receive the event arguments in a handler function in your ViewModel, which is an UObject derived class. Am I right? In that case, that is not possible at the moment. If all you need is to know the source of the event, that could be done using beha...

Hi, I've created a ticket and attached a patch that fixes the resizing issue. Here's a link: https://www.noesisengine.com/bugs/view.php?id=2918 Regarding the other issue, could you try changing the definition of WITH_CASE_PRESERVING_NAME to be always 1? Right now it's defined to be WITH_EDITORONLY_D...

I'll look into it. Are the actors containing the WorldUIComponents replicated?

Hi David,

I've added a comment to the ticket (to keep the conversation in a single place). Could you please take a look?

Thanks!

Hi David,

Have you updated to 3.2.2? There was a fix for that issue in that release. I've attached a patch for this issue.

Please, let us know if this resolves the problem for you.

Thanks