Imported FBX file makes selection impossible. #52826

New Issue

Ejnar Brendsdal · 2017-09-19T08:42:04+02:00

Ejnar Brendsdal commented

2017-09-19 08:42:04 +02:00

System Information
File System File attached
Windows 10
NVIDIA Quadro M2000

Blender Version
2.79 Official Release

Short description of error
While importing FBX files generated by Autodesk Revit has greatly improved and all geometry seems to com intact with instances and everything, something seems off with selecting objects. When I click on an object where other geometry is behind it it will always select random geometry in the background instead of the geometry closest to the screen.
This is not affected in wireframe mode. Nor is it an issue when I open a clean blend file. It is only with the scene where imported geometry is present.
Note it also happens when creating new geometry in the same scene as the imported geometry.Wrong Selection Bug.zip

Exact steps for others to reproduce the error

Open the attached .blend file or alternatively import the attached .fbx file (Y forward).
Try and select an object.
Notice the selection is never the object clicked upon if anything else was behind it.

**System Information** File System File attached Windows 10 NVIDIA Quadro M2000 **Blender Version** 2.79 Official Release **Short description of error** While importing FBX files generated by Autodesk Revit has greatly improved and all geometry seems to com intact with instances and everything, something seems off with selecting objects. When I click on an object where other geometry is behind it it will always select random geometry in the background instead of the geometry closest to the screen. This is not affected in wireframe mode. Nor is it an issue when I open a clean blend file. It is only with the scene where imported geometry is present. Note it also happens when creating new geometry in the same scene as the imported geometry.[Wrong Selection Bug.zip](https://archive.blender.org/developer/F822044/Wrong_Selection_Bug.zip) **Exact steps for others to reproduce the error** - Open the attached .blend file or alternatively import the attached .fbx file (Y forward). - Try and select an object. - Notice the selection is never the object clicked upon if anything else was behind it.

Ejnar Brendsdal commented

2017-09-19 08:42:04 +02:00

Changed status to: 'Open'

Ejnar Brendsdal commented

2017-09-19 08:42:04 +02:00

Added subscriber: @EjnarBrendsdal

Sergey Sharybin commented

2017-09-19 08:50:25 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2017-09-19 08:50:25 +02:00

Don't think it is anything to do with FBX, sounds more like OpenGL selection issue. Things to try:

Make sure you don't override FSAA or other antialiasing-related settings in driver settings.
Try disabling multisample in Blender (User Preferences -> System), this requires Blender restart.
Try various selection methods in User Preferences -> System

So far i can not confirm the issue, but i'm on Linux.

Don't think it is anything to do with FBX, sounds more like OpenGL selection issue. Things to try: - Make sure you don't override FSAA or other antialiasing-related settings in driver settings. - Try disabling multisample in Blender (User Preferences -> System), this requires Blender restart. - Try various selection methods in User Preferences -> System So far i can not confirm the issue, but i'm on Linux.

Ejnar Brendsdal commented

2017-09-19 09:43:16 +02:00

Hi Sergey. My first thought was in agreement with you on the OpenGL conclusion as I am on a new machine and haven't set up my own preferences yet. None of the options you suggest solve it though.
But on further inspection I have done the following:

Opened the attached file with the bug.
Saved it as startup file. -> This resulted in any new empty blend file opened suffering the same problem. Even with just copies of the default cube. Always the geometry in the background being selected.

I then did following:

Select everything from bug file and copy to clipboard.
Reset to factory settings (Load factory settings in File menu)
Paste everything in the new file.

This solved the problem and now the geometry is selectable as normal.
So importing the FBX file did something to the settings of the file that a factory reset solved.
I will dig further later.

Hi Sergey. My first thought was in agreement with you on the OpenGL conclusion as I am on a new machine and haven't set up my own preferences yet. None of the options you suggest solve it though. But on further inspection I have done the following: - Opened the attached file with the bug. - Saved it as startup file. -> This resulted in any new empty blend file opened suffering the same problem. Even with just copies of the default cube. Always the geometry in the background being selected. I then did following: - Select everything from bug file and copy to clipboard. - Reset to factory settings (Load factory settings in File menu) - Paste everything in the new file. **This solved the problem and now the geometry is selectable as normal.** So importing the FBX file did something to the settings of the file that a factory reset solved. I will dig further later.

Sergey Sharybin commented

2017-09-19 09:48:15 +02:00

If you open attached .blend file, does the selection issue happens in there? (or is it REQUIRED to actually import attached fbx?)

Ejnar Brendsdal commented

2017-09-19 09:53:52 +02:00

No it happens in the attached file on opening.
As if the file is corrupted somehow.
As a note the only thing I did before importing the FBX and causing the trouble was to add a couple of selection options in the keymap according to this link:
https://twitter.com/Leukbaars/status/908992634324004864

No it happens in the attached file on opening. As if the file is corrupted somehow. As a note the only thing I did before importing the FBX and causing the trouble was to add a couple of selection options in the keymap according to this link: [[ https://twitter.com/Leukbaars/status/908992634324004864 ]]

Sergey Sharybin commented

2017-09-19 10:19:00 +02:00

Added subscriber: @LazyDodo

Sergey Sharybin commented

2017-09-19 10:19:00 +02:00

I do not see any corruption in the file and can't reproduce the issue. It might be that copy-paste things to a new file changes pointers, which could potentially cause different order of selection queries.

@LazyDodo, @mont29, mind giving it a try here?

I do not see any corruption in the file and can't reproduce the issue. It might be that copy-paste things to a new file changes pointers, which could potentially cause different order of selection queries. @LazyDodo, @mont29, mind giving it a try here?

Sergey Sharybin commented

2017-09-19 10:19:10 +02:00

Added subscriber: @mont29

Ejnar Brendsdal commented

2017-09-19 11:36:10 +02:00

When you open the file does it keep the preferences setup as on my machine or is it defaulted to your settings?
It seems it only happens with files that have imported FBX geometry in them.
I have just tried to import the original FBX into Rhino and then export from Rhino into Blender through a new FBX file, but same issue happens.
Could it be a floating point precision issue between the programs? Both Rhino and Revit runs with fairly large double precision scales. (CAD files with kilometers of scenes as default)

When you open the file does it keep the preferences setup as on my machine or is it defaulted to your settings? It seems it only happens with files that have imported FBX geometry in them. I have just tried to import the original FBX into Rhino and then export from Rhino into Blender through a new FBX file, but same issue happens. Could it be a floating point precision issue between the programs? Both Rhino and Revit runs with fairly large double precision scales. (CAD files with kilometers of scenes as default)

Bastien Montagne commented

2017-09-19 14:47:28 +02:00

That FBX file has two issues from Blender POV: unsupported Normals mapping (by polygons), and invalid material indices. But importer knows how to work around that to some extent.

Other potential cause of issues (especially under crappy windows OS) are usage of unicode chars like å and such maybe (should not, but could explain the issue), can you try to change those names to pure ASCII ones, re-export FBX from rhino or whatever, and see what happens once imported in Blender?

Besides that, I see nothing that could explain the issue, and cannot reproduce it under linux so far. FBX importer does not touch to user preferences settings and such at all.

That FBX file has two issues from Blender POV: unsupported Normals mapping (by polygons), and invalid material indices. But importer knows how to work around that to some extent. Other potential cause of issues (especially under crappy windows OS) are usage of unicode chars like `å` and such maybe (should not, but could explain the issue), can you try to change those names to pure ASCII ones, re-export FBX from rhino or whatever, and see what happens once imported in Blender? Besides that, I see nothing that could explain the issue, and cannot reproduce it under linux so far. FBX importer does not touch to user preferences settings and such at all.

Ejnar Brendsdal commented

2017-09-19 15:25:16 +02:00

@mont29 and @Sergey

Actually I have just reinstalled from scratch and I can no longer reproduce the issue with neither the original FBX or new from the same setup.
I dont know what the issue was but I suspect a bad installation on my machine for some reason. Untill further notice I think you can close this task. I will keep an eye out for the issue though as I work a lot with pipeline between revit and rhino.

@mont29 I can open a couple of new bug reports related to the normals and material indices with simpler blend / fbx files?

Thanks for the suggestions and feedback.

@mont29 and @Sergey Actually I have just reinstalled from scratch and I can no longer reproduce the issue with neither the original FBX or new from the same setup. I dont know what the issue was but I suspect a bad installation on my machine for some reason. Untill further notice I think you can close this task. I will keep an eye out for the issue though as I work a lot with pipeline between revit and rhino. @mont29 I can open a couple of new bug reports related to the normals and material indices with simpler blend / fbx files? Thanks for the suggestions and feedback.

Bastien Montagne commented

2017-09-19 15:49:42 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2017-09-19 15:49:42 +02:00

Bastien Montagne self-assigned this 2017-09-19 15:49:42 +02:00

Bastien Montagne commented

2017-09-19 15:49:42 +02:00

Yes, think we can archive for now.

Re normals and mat indices, yes please, having basic files to reproduce and investigate will be simpler (normal mapping is just a matter of implementing it, just never found any FBX file using that one so far, matindices I cannot say without seeing basic file with the issue ;) ).

Yes, think we can archive for now. Re normals and mat indices, yes please, having basic files to reproduce and investigate will be simpler (normal mapping is just a matter of implementing it, just never found any FBX file using that one so far, matindices I cannot say without seeing basic file with the issue ;) ).

Ejnar Brendsdal commented

2017-09-20 13:29:45 +02:00

HI @mont29

I have created two new reports.
Hope these can help. If you think I can send anything else that can help please dont hesitate to write.

https://developer.blender.org/T52847
https://developer.blender.org/T52846

Best regards.

HI @mont29 I have created two new reports. Hope these can help. If you think I can send anything else that can help please dont hesitate to write. https://developer.blender.org/T52847 https://developer.blender.org/T52846 Best regards.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Imported FBX file makes selection impossible. #52826