I’m setting scale in RC with Define Distance tool, understand “9.0000” to mean nine meters. When I export the fbx and import to UE4, which defaults to meters in World Space (though transforms appear in cm), this model comes in way big, have to scale it .4 or so to what looks right and what falls into range with lighting capability. When I set no scale and export as is, the model in UE4 shows up yet bigger, but interestingly it’s .1 scaling that brings it into line. UE4 documentation states that for scale to travel with a model those settings have to be enabled during export of the fbx. I’m curious what standard RC is using in writing the meter scale into fbx and if others working in UE4 have encountered similar experience and how they’ve worked around it. Thanks.
Benjy
P.S. I just read a possibly related post about coordinate systems, how to change from meters to feet. I’m in meters in UE4, but possibly that uses a different system, see a slew of options for there. I’ll look into what system UE4 uses, surely this is the issue.
Hi Benjamin
METER is used as the default. if you want to use different UNITS, you need to change the COORDINATE system from LOCAL to something that uses IMPERIAL units. I highly recommend you to stay on METERS and look for the unit conversion inside UE4. use google and search for “ue4 units to meters” to find your answers…
Hi Wishgranter, just wanted to ask a question in elation to what Benjamin posted, I’m in need to pass off processing of lidar scans out of RC to a client already in feet in an .obj file format.
If I process the lidar scans, which where capture in meters, how do I setup my RC scene to export/convert the meshed scans from Meter to Feet - I understand that I need to choose an appropriate coordinate system such as NAD83/California - us(ft) int he project settings, but would there be any other settings I would need to change (and where?)
I did a test out of RC to .obj, and opened it up in Maya but my “1 foot” test object in Maya did not match the scene scale I was expecting - there seems to be very little information about this and I know not too many people convert meters to feet, but this is what I need to pass off the client.
Any help or information would be greatly appreciated - thanks
Yes changing the outputs coordination system to US one with feet should convert your units.
If there is a defined distance somewhere in your project and you will change the project coordinate system to the US one you will notice the defined distance will change to feet and will convert the numbers as well so everything should be just fine. You can try this by navigating to Workflow tab - Settings - Coordinate systems and changing the “Project coordinate system”.
Sorry for the silly question, I’m assuming that I need to change the coordinates settings to US (ft) BEFORE I process the lidar data inside of RC is that correct?
As mentioned, In my current situation, the software that we use here is set to 1 UNIT = 1 FOOT, so I’m particularly looking for a way to export out of RC so that when imported into our software 1 unit = 1 foot too.
Also what is the difference between having the PROJECT coordinates system and the OUTPUT coordinates system? is that so that RC can process in one coordinate and export out in anoterh like PROJECT = meter and OUTPUT = feet?
I did try to look for some detailed documentation but I did not find any that answered these questions.
Yes Patrick, it should work just as you stated, project coordinates for affecting in RC coords and output for converting on export. Everything should work just fine, just test it with your software and you should be good.