New RC version 1.5 do no longer export to Csys 0 0 0 /grid center

General Feedback & Requests
,
1

After upgrading to latest Version 1.5, I noticed my FBX exports to Blender no longer go to coordinate 0 0 0. They are moved far away from Csys/grid center, so I cannot use the new 1.5 version to export to my Blender assemblies made with RC version 1.42

This also goes for exporting from other formats like .glb, and others. Same problem with exporting to 3DCoat.

I verified the problem reinstalling version 1.42. IT WORKS with 1.42, object go to grid center.
Then I reinstalled latest version 1.5, and the problem returned.

Also tripple/quadrouple checked export-settings, and even made an .XML export settingsfile. The .XML settings file behaves different in the 2 versions

2

Hello Teslacoiler77,
this is really strange and we are not able to reproduce this issue.
What are your coordinate system’s settings? Are you working in local coordinate system?
What are your export settings?
Is it possible to share your export settings with us?
I tested one simple model in local CS and exported in Grid plane CS and the model is placed on the same spot in the grid centre.
RC:

image
image608×484 79.9 KB

Blender:
image
image615×515 45.3 KB

3

Blender_Import_to_same_scene
Blender_Import_to_same_scene1920×1080 86 KB

Placement in RC
Placement in RC1920×1080 260 KB

Screenshot_export-settings_v1.5-v1-42
Screenshot_export-settings_v1.5-v1-421003×1442 139 KB

Install-uninstall_common_route
Install-uninstall_common_route1945×806 132 KB

Hi Otrhan, thanks for quck reply!

Yes, very strange. I went through reproducing the problem one more time, and took some screenshots and exports along the way. Here is what I did:

  • Started in RC v1.5

  • Opened a recent project (created in v1.5)

  • took screenshot of model position (attached)

  • exported FBX with Grid Plane CS and standard Blender/Maya transformation preset. (screenshot and XML attached)

  • exported .XML export settings (attached below)

  • exported Global settings (attached below)

  • imported model into Blender. MODEL INCORRECTLY PLACED

  • uninstalled RC version 1.5 from Epic Games Launcher

  • rebooted computer

  • downloaded and installed RC v1.4.2 from Epic Games Launcher

  • (did not import or change any settings)

  • opened same project in RC. (had to redirect image-paths due to non realive paths in v1.4.2)

  • exported FBX with standard Blender/Maya transformation preset, and Grid Plane CS.

  • exported .XML export settings (attached below)

  • exported Global settings (attached below)

  • opened the same Blender scene saved from before

  • imported model into Blender. MODEL CORRECTLY PLACED (image attached)

  • saved screeenshot of same model in different positions

As to your questions:
-Coordinate system settings are set to local for both versions (screenshot attached)

Csys-set-to_Local
Csys-set-to_Local1503×1798 200 KB

-I am working in local:1 Euclidean in RC. always

Export settings from both versions:
exportsetting_Blender_From-v1.5.xml (1.8 KB)
exportsetting_Blender_From-v1.42.xml (1.8 KB)

GlobalSettings exported from both versions used:
Global_settings_from_v1.5.rcconfig (32.7 KB)
Global_settings_from_v1.42.rcconfig (32.7 KB)

Hope this can be resolved somehow since update to v1.5 has some really practical features for me!

Sincerely, Per Kristian Faldet
3D Scan Design

4

Hello Per,
thank you for your additional info.
Unfortunately, I am still not able to reproduce this issue (but I found another bug, as the config file needs to be import twice for its implementation).
Can you try to export the file using the Transformation preset set to Default (as there is no change in the Scene and Normal transformation between Default and Blender, Maya for FBX format)?
Also, can you try apply the application reset as is described here: Reset RealityCapture (probably you will need to use the CLI’s way).
And as we are not able to reproduce this, would it be possible to share your project with us? If so, can you please send me your email (you can use PM).
When you check the location for 1.5 model, what does it says?

image
image892×342 35.1 KB

Thanks and sorry for the inconveniences.

5

Thanks,

Blender Transfor location for v1.5 model is also: X Y Z, 0 0 0 (as for both imports)
Also, did the Transormation preset to Default, which still is the same.

Did a Reset RealityCapture (frist reset conmfig & UI, then “make like Clean install”, and reboot PC)
still same

AND Check this! I decided to try on my workstation laptop, which has not been opened for a month. Upgraded RealityCapture to v1.5 (from v1.3), and guess what! SAME PROBLEM THERE!!

Also on that computer I also tried importing the file into 3DCoat,so not only coming into Blender!

So I have 2 different computers, both exporting perfect on earlier versions (v1.4.2 and v1.3), but not when upgrading to v1.5. AND, downgrading to previous versions fixes the problem.
Does not matter if the project is created inside v1.5 og v1.4/3, exporting from v1.5 gives a misplaced coordinate-system…

I really don’t know, but now I am thinking, maybe you should try a clean install now?? How can I be experiecing a version issue on 2 computers, when downloading and installing directly from Epic Launcher, and be the only one experiencing this? just saying… (or maybe it has something with keyboard-setup for norwegians… dont think so)

I will be happy to share a simple project with you (though I cannot see how the project is the issue)
I have prepared a simple project and got it down to 29MB.

My email adress is pkfaldet@gmail.com

sidenote:
(as for the config files you mention, I noticed 3 of the lines have changed places, info in lines is the same) You’ll see it if you switch between them in file explorer with preview activated.

6

As it is 0,0,0 for model from 1.5, it seems moved then in the 3D view.
I sent you the invitation for the data upload already. It can be in your spam folder. Can you also upload the exported models there?

After reset, have you computed a new project or used the original one?

I tested this after a clean install. Hard to say how it is that you are the only one, but until now the similar issue wasn’t reported.

Thank you for a sharing, it can bring a light into this issue.

Yes, I checked the config files, but that shouldn’t be the issue. It is only the order for some values. They should be read properly.

7

Thanks, I uploaded a folder with a project and exports. No images included, but view and export works tha same.

Yes, did two projects from scratch within the new “clean install”. After reboot. still same

Clean reset that is, from holding shift while executing RC, and select “make like clean install”
For some reason CLI did not respond to -reset All or -reset resetOption command…

Hope you can figure it out, I’m out of ideas for now.

Good luck :slight_smile:

Sincerly, PK Faldet

8

Thank you for your data.

It is probably a bug, but I suppose it is related to your process somehow.
I see you used Set ground plane. Is that right?

Also, you are using GCPs, but only two. To define the plane correctly, you need to use at least three points. Also, if this is for a scaling the project, you should use a longer distance.

But you are right, this shouldn’t be happening and I am creating a bug for it. Again, thank you for sharing and we are sorry for the inconveniences.

To solve this issue for now try to use more GCPs and export the model in Project output CS.

PS: regarding the reset commands, have you used the values in quotes, like -reset "all"?

9

Hey. I found the problem, and it has nothing to do with GCP’s or my process. Or maybe it does, if I am the one one in the whole World scaling my projects??

I always scale my projects, for all reasons, and always BEFORE positioning on the grid. Otherwise I’ll have to reposition again after scaling, and positioning was the whole point of this topic, wasn’t it?!

I went through the steps for the simplest way to create a project, systematically exporting OBJ’s one by one between operations, and found this:

In RC version 1.5, scaling the model throws exported models of the grid!!
It is correctly exported until after you add control points, but once you “define distance” and hit “Allignment update” it gets thrown away from the origin!

Recentering the model at Csys origin makes it even worse, and even deleting distance and CP constrains does not help after this.

Now I’d say that’s a pretty severe bug, not beeing able to scale a project without loosing control over positioning. And I am really surprised I am the only one on the planet noticing this!

Here is from Blender: imports of OBJs throughout the process of a normal workflow:

Csys_Scaling-problem_RCv1.5
Csys_Scaling-problem_RCv1.52483×1396 400 KB

Now try it yourself, I have tested on 3 differnt PC’s now.

Sincerely PK Faldet,
3D Scan Design

10

Hi, thank you for additional tests.

I checked it again and it seems like there is issue only for grid coordinate system. There is a workaround using local CS. But for that you need to have placed at least 3 GCPs, not only 2. After exporting the model in the local system, it is still placed on the same position as in RealityCapture.

In your project, how was the model scaled? Have you used Define distance tool or the GCPs? Because it looks like the GCPs were used to scale the model.

11

Never mind the (G)CPs!! They have nothing to do with the problem, I just happended to have some april tags in the images, and used TWO of them for scaling. ONLY scaling (define distance), they don’t have a set coordinate in the project you recieved. Just forget about them!

Now here is how you replicate this issue, very very basic standard procedure, NO GCP’s involved:

-import images
-allign
-set reconstruction region
-Create model Normal/High detail
-Add two control points anywhere on model (for scaling)
-define distance (the two points for scaling)
-accept at least 3 images for each control point
— (UNTIL THIS POINT, model is exported correctly)
-Hit Allignment Update
— (Now, exported object is thrown away from origin)
-Reposition model at grid center and problem gets even worse
-You can now no longer position object Csys/Grid center and export in that position

I normally don’t use GCP’s in my projects. I scale them manually using two markers 1.00162 meters apart, and then carefully allign rotate/postion the object (usually boats and ships) on the grid.

GCP’s I only use for a CLI script I have written for batch-production of several smaller objects at once. The CLI-script masks and merges all sides of the individual objects, and exports them out to seperate directories, scaled and textued and placed at Csys origin. Thats how I discovered this; after update to RC v1.5 the objects were no longer found in their original position, and were sometimes very hard to locate.

I’ve been using RealityCapture since early beta in 2016, (gradually replacing Photoscan/Metahshape.) and this is the first time this behaviour of the software has changed.

Like I said, I dont have GCP’s for my big scans (cant use “Project Output” CS), so using v1.5 becomes cumbersome. For difficult scans I usually export for surface treatment in 3DCoat and MeshInspector, and import back to RC for texturing. This work now has to be done sometimes very far from origin. And working with meshes in CAD becomes a “one-way road” as it has to be re-centered to do any meaningful work.

-I rarely use “project output” CS, but exporting that way demands 3 GCP’s

For now, I will use RC version 1.4.2, and await an update with a fix this issue.

Sincerly Per Kristian Faldet,
3D Scan Design

12

I am sorry that I mentioned GCP so often, but they are in the project you sent me. Therefore I was suggesting that as a possible solution:

image
image353×580 47.2 KB

But you are right, the bug is not related to CPs or GCPs, but to the grid CS and it was already created.