3DF Zephyr Beta - Road to Blueberry

[Roberto]

Because the checkbox manages the "visibility", while the yellow text means that the object has been "selected". You can also select multiple object with ctrl and shift, and for example, delete an entire selection with right click. Or you can open the context menu or with a slow double click change the name of the currently selected object. (just a few examples )

[Nedo]

I have a question (see pic) lets say i selected Mesh 2, but why it is possible to yellow select Mesh 1 even its not selected? this allways confuses me, makes me insecure
about what is selected now and what not, maybe a dumb question?
Its feels like playing chess anyone playing chess?

[cam3d]

Importing an OBJ sends it directly to the Textured Meshes Category, not the Meshes Category as expected.

[sam3d]

Could you look at adding a Pause/Cancel option to the Add Photos? I've got a lot of images that are part way through merging and I can't find a way to stop it without terminating the application.

[3Dflow]

4.125 is out

Nedo Bounding box selection Status saved only if you mantain the same visible objects
yoli The undo/redo of the bounding box now works correctly. Bounding box action are committed/grouped when you close the dialog.

[Roberto]

Zephyr completed the generation of the dense point cloud and showed the window to click "Finish" on after it autosaved. It hung at that point with that window up. Restarting the program offered to restore the autosaved project which opened in Zephyr with both the sparse and dense point clouds.

The only thing I can add is that I do switch to another application, or two, or three or four, , while Zephyr is working. At this point, I can't reproduce it at will. I've had maybe three hangs on over 10 new projectsin the last few days with the current beta. As I said previously, I might have had one or two hangs with the previous beta too.

There aren't know issues, but other conflicting dlls might also cause it. For example, the old versions of Dell Backup Update and Recovery made Qt application crash. Are you using Zephyr from a Remote Desktop? Have you tried on a different machine? Have you tried to make a clean display driver installation? Unfortunately, this kind of problems are complicated to track down as it might be hanging on an internal Qt or Windows call and might be related to the specific configuration.

[Roberto]

Yup, got it! Save the bounding box state on selection. We can do it similarly to the orthophoto page. The parameters are saved only at runtime if the project hasn't changed.

[Nedo]

first i am very impressed with the new speed Zephyr calculate stuff !!!
I also like the new bounding box selection, but i have a small question, when selecting with bounding box,
and exit the select menue and entering again the select menue, the bounding box reset itself and you have to begin
to select complete new, you can't start from the bounding box last position, i hope you understand what i mean hmmm..

[Roberto]

4.123: issue with mesh naming, a "(2)" is appended at the end of the mesh name, see picture.

This might be a "feature". Zephyr forbids objects in the workspace to have the same name. If Zephyr automatically added the (2), there might have been another object (maybe a dense point cloud or a textured mesh) with the same name.

[Roberto]

Thanks a lot for the feedback, we are adding the fixes to the dev build.

Yesterday we have release v. 4.124 with some further fixes, an improved workspace merge, add photos to existing project and bundle adjustment managements. Other fixes/improvements will follow next week

[cam3d]

Import custom UV model. OBJ files don't appear in the 'meshes' selection (which should include OBJ files) - But does if you select OBJ+MTL. (Images attached)

Don't mind the .obj.obj file naming - I was just testing to see if it was a problem with naming structure - I don't usually do that

The speedups are insane! Well done

[ZazMMM]

This might be a feature request, as the behavior is the same between the beta and the released version. However, with the changes to the selection UI, it might fit here.

1) I'd label the button "Manual", or maybe "By Hand". Right now the button is labeled Hand which strikes me as a bit odd. This feels like an Italian to English translation issue which I'm a bit sensitive to as I've been working on Japanese and make poor choices myself sometimes or see Japanese picking bad English words. "Manual Selection" or "Selection by Hand" would be common ways to say what the action of that button does. This isn't a big issue, most would figure it out, I'm just sensitive to things like this from my own experience with Japanese.

2) I prefer to use the Lasso most of the time. The window that the "Hand" button brings up always defaults to Rectangle as the selection type. However, that same window remembers whether Add or Remove were picked. I would expect the window to remember the state of everything that makes sense to remember or to remember nothing. Remembering one state and not the other state is a bit odd and causes me to constantly switch to Lasso every time.

Keep up the good work, it's been fun playing with features I don't normally have in the Lite version.

[ZazMMM]

OK, I had the hang again and remembered to get the App Hang info:

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:    AppHangB1
  Application Name:    3DF Zephyr Beta.exe
  Application Version:    4.1.2.3
  Application Timestamp:    5bf2dcbd
  Hang Signature:    b599
  Hang Type:    0
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Hang Signature 1:    b599ae905e332878a1f0b3206d030a1e
  Additional Hang Signature 2:    32ce
  Additional Hang Signature 3:    32ce6694b6deafd9200a228d3892c137
  Additional Hang Signature 4:    b599
  Additional Hang Signature 5:    b599ae905e332878a1f0b3206d030a1e
  Additional Hang Signature 6:    32ce
  Additional Hang Signature 7:    32ce6694b6deafd9200a228d3892c137

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Zephyr completed the generation of the dense point cloud and showed the window to click "Finish" on after it autosaved. It hung at that point with that window up. Restarting the program offered to restore the autosaved project which opened in Zephyr with both the sparse and dense point clouds.

The only thing I can add is that I do switch to another application, or two, or three or four, , while Zephyr is working. At this point, I can't reproduce it at will. I've had maybe three hangs on over 10 new projectsin the last few days with the current beta. As I said previously, I might have had one or two hangs with the previous beta too.

[ZazMMM]

I've had a few hangs while using the recent beta, build 2018.11.19.16.49.02. I might have had a similar hang or two on the previous version.

The hangs have happened at least during the first Workflow->Dense Point Cloud Generation use in a project. They happened after the Save Workspace successfully autosaved as when I restarted Zephyr it offered to load the autosaved project and the Dense Point Cloud was in that project.

If it happened on the previous beta I think it happened after a mesh generation with similar results, i.e. the autosaved project contained what it was generating at the time of the hang.

In all the hangs, the windows for the app just hung, i.e. WIndows added the "(Not Responding)" text to their title and the windows wouldn't repaint. One core of my CPU was fully utilized by 3D Zephyr Beta.exe.

I waited 10 minutes or more for the operation to complete, but it appeared that it wouldn't because what I had asked the program to do was already complete and the autosave had even fired off and completed. The GPU was not active at the time, but had been active during the actual computing part of the operation.

I wish I had more information to offer you on this, but there was no crash to allow sending a report and I haven't found a precise way to duplicate the problem.

I'm running Windoze 7 SP1, 16G of memory, i5-3570K, 1080ti with 416.81 drivers. My C drive, where the autosaves are going, has 40G free and the D drive where the project and images are stored has 100G free. Games, rendering, tensorflow and other CPU and GPU activities on my computer are running without any problems.