did the trick. Not sure if thats the right why to go but it worked.
Generally speaking if i have a actor and i have some functions that does a lot of calculating that i want to seperate from the actor and be able to call from the actor.
Is it ok to create a object this way that i can get the data from, instead of having it all in the same class as the actor ?
Yep that’s the correct way to initialise the UOBJECT, and yes it’s completely fine to separate stuff into a UOBJECT like that, although you may want to look into making it an ActorComponent which can be easily added to actors via blueprints etc.