Niall Flinn

Thanks for the tips, Tomas!

I'll see where the OnCreated route gets me, because I'd like to have the camera itself be a standard camera, just with some internal stuff driving the transforms and other parms. That way artists adding it to their ROPs, etc can just grab it straight from /obj without having to dive down another level to find the "real" camera.

Niall

Hey Tomas! Long time no see, hope you're well

I just found this discussion because I'm working on creating a custom camera node. I've tried both of the methods you described, but in the second method, the new "camera" just seems to be an empty object that has a camera icon. There aren't any of the usual camera parameters and none of the nodes you'd expect to find inside:



... so I'm probably better off starting with a vanilla camera and making my HDA from that.

In both cases, however, there doesn't appear to be any way to set up expressions or otherwise set camera parameters (like transforms) with the Edit Operator Type Properties window: all the parameters are greyed out:



I guess this is because these are part of an internally defined node. That being the case, what is the best way to add expressions to these parameters? Use an onCreated Python script?

Any advice gratefully received,

Niall

Barrett Meeker
Unreal doesn't have any native volume data ability so you need to fit the volume into something else, either image slices or if you want it for gameplay elements you could export it as a csv file which unreal can read.

This won't be for realtime use, so within reason performance isn't a huge consideration. I was aware of csv but had assumed that was just for things like rbd collision data etc. If I can export the volume as csv, how will it appear in Unreal?