Graph Editor: Incorrect nodes position and inability to auto-arrange

[zicher3d]

The attached file was created by an old version of LookdevX. The format and content seem ok. it's an example of an issue I run in once in a while.
When opening the file in Graph Editor the nodes are scattered all over the place.
Trying to re-arrange them using Auto Layout result in some of them not being arranged properly or at-all.

Looking at the ones that are initially scattered or not rearranged I can't seem to see a difference or anything wrong compared to others.

After opening the file:

After Auto-Layout:

Only some are correctly re-arranged:

The file: (Ignore the content, this is a debug/WIP file)
Note that this file requires the nodes in PR
pat_herringbone2x6_test01.zip

[zicher3d]

Xpos/Ypos values in the original file might be high. Not sure what is the right range here.

[lfl-eholthouser]

Hi! @zicher3d thanks for flagging this issue. I'll take a look and try to find the issue. Just glancing at the Xpos/Ypos the initial position is (1200, 0) and so some of the node's position's seem a little large but none of them immediately seemed like an issue.

[zicher3d]

I'm not sure what the right range for the positions is. The old LookdevX seems to go in the hundreds, while the Graph Editor uses much lower numbers. Bot work fine when loading their own saved files.
The main concern here is the inability to get Auto-Layout to rearrange them.

If the range difference is an issue when exchanging files with other graph editors (like Quiltix, or Houdini), I would suggest adding a scale option, as Auto Layout might not be what is needed in these cases.

[kwokcb]

If it is doing what I think it's doing LookdevX is probably saving using absolute screen doors. Could be this is messing up the math used to place nodes inside the editor so my guess is to check what's going on there.

Another possibility is to perform a remap on load based on the bounds of the coordinates to try and normalize it.

If this is fractional node size then that info I assume is unknown for an arbitrary file created in an external editor where node size may differ?

Just some noisy thoughts :-).