Fix #3440: Moving domain bug

[StasJ]

Fix #3440

[sgpearse]

Follow the steps in the bug report, then disable the Volume and Image renderers. The Flow region is incorrect.

[StasJ]

Follow the steps in the bug report, then disable the Volume and Image renderers. The Flow region is incorrect.

I get correct results when following your directions:

[sgpearse]

That's really strange. When I load domain.vs3 in the zip file from the bug report, and disable all renderers but flow, something goes awry. I'm definitely on issue3340.

[StasJ]

That's really strange. When I load domain.vs3 in the zip file from the bug report, and disable all renderers but flow, something goes awry. I'm definitely on issue3340.

1. Loading domain.vs3 is not one of the steps in the bug report:

Follow the steps in the bug report, then disable...

2. That session file was generated using a bug. The bug was fixed, but it does not retroactively repair bad session files, especially since we never released a version containing this bug.

[sgpearse]

That's fair, however when not using the session file I see the following which is the incorrect behavior from my screenshot 3 days ago :(. The domain is too long on the Y axis and the northern region of the flow renderer is truncated.

I'm not sure how we're seeing two different things. Would it be useful to do a screen share?

[StasJ]

That's fair, however when not using the session file I see the following which is the incorrect behavior from my screenshot 3 days ago :(. The domain is too long on the Y axis and the northern region of the flow renderer is truncated.

I'm not sure how we're seeing two different things. Would it be useful to do a screen share?

Just a sanity check: Are you using the pre-release installer or building from this branch for your tests?

[sgpearse]

Just a sanity check: Are you using the pre-release installer or building from this branch for your tests?

I'm building on issue3440 in debug mode with all other defaults applied. But I don't think there's urgency since we've agreed to postpone this edge case until after release. I'd like to do a screen-share when we meet on Tuesday though, just for sanity.