Global Exposure

Every time I import an object through datasmith, it creates a Global Exposure Node which causes my scene to go dark. How can I keep this from happening?

Something that ticks me off about UE is that I need an RTX card to use the path tracer even though I can use the same card to render with engines that use a path tracer.

I guess what you are trying to import actually, contains that “global exposure node” because perhaps is a scene

1 Like

Unfortunately Ive checked all export and import options on both programs. I dont export anything other than geometry and materials and only import the same. I wonder if its a datasmith import setting in UE.

Can we have more information:

  • how does this global exposure node looks like in your world outliner? is it an actor?
  • which version of Unreal are you using
  • what is the file format your are importing? udatasmith? if yes from which software does that file come from?
1 Like

It’s a Global_Exposure Post Process Volume and it’s located in the immediate folder that the new item is located in.

UE 5.0.0-16682836 Early Access

Importing datasmith from 3dsMax 2020

image

Hi DustinM-000 !

You can either use the Global Exposure and tweak it to your liking in 3dsMax (see the doc’s global exposure settings ) or disable Global Auto Exposure by setting your scene Exposure Control to “No Exposure Control”, creating your own Post Process volume and tweaking Exposure directly in Unreal.

image

Cheers,
Antoine

1 Like

I am experiencing the same.
I haven’t been able to check yet, but might this be caused by camera settings inside the program you are exporting from?

A friend of mine exported from 3dsMax and I had the same GlobalExposure Volume appear and turn my entire scene into a black mess.

Ill check both of these settings but that’s strange. I would assume if my export options were to only export Geometry and Materials, then Exposure Controls should not transfer.

1 Like

Well how did it turn out, did tweaking any Exposure Settings inside of 3dsMax help?
I was able to verify that in my case it was the aforementioned Exposure Control in the scene.

(Thanks @Antoine_Guillo )

1 Like

Its seems to have been fixed in v 5.02.

1 Like