Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - macsurveyr

Pages: [1] 2 3 ... 5
1
Bug Reports / Re: Latest 1.8.0 Viewer - continuous renderer_qgl.cpp error
« on: January 11, 2022, 02:51:43 AM »
I am using an iMac running macOS Monterey version 12.1 with Radeon Pro 580 8 GB graphics

Not sure if I see separate driver version?

Tom

2
Bug Reports / Latest 1.8.0 Viewer - continuous renderer_qgl.cpp error
« on: January 05, 2022, 11:26:36 PM »
2022-01-05 13:20:57 Agisoft Viewer Version: 1.8.0 build 13794 (64 bit)
2022-01-05 13:20:57 Platform: Mac OS
2022-01-05 13:20:57 CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (desktop)
2022-01-05 13:20:57 CPU family: 6 model: 158 signature: 906E9h
2022-01-05 13:20:57 RAM: 64.0 GB
2022-01-05 13:20:57 OpenGL Vendor: ATI Technologies Inc.
2022-01-05 13:20:57 OpenGL Renderer: AMD Radeon Pro 580 OpenGL Engine
2022-01-05 13:20:57 OpenGL Version: 2.1 ATI-4.7.101
2022-01-05 13:20:57 Maximum Texture Size: 16384
2022-01-05 13:20:57 Quad Buffered Stereo: not enabled
2022-01-05 13:20:57 ARB_vertex_buffer_object: supported
2022-01-05 13:20:57 ARB_texture_non_power_of_two: supported
2022-01-05 13:20:57 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:20:57 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:20:57 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:20:57 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:04 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:04 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 659: blitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286
2022-01-05 13:21:05 renderer_qgl.cpp line 674: glBlitFramebuffer(0, 0, width, height, 0, 0, width, height, 0x00000100, 0x2600) failed: error 1286

These errors continue if my mouse is over the viewer window.

Tom

3


Delete isn't the right word - I removed them. Isn't disabling them essentially the same thing in terms of data? Though disabling allows me to reenable them later if I need to (which if all goes well I won't...)?
[/quote]

Removing photos is not the same as disabling them. Removing photos removes tie points and can affect the results of the alignment and optimization and will affect future products. The images should be disabled.

Tom

4
I don't think you should delete photos from the duplicated chunks. It would be much better to disable the photos you don't want to use in each of the duplicated chunks. Any products going forward will only use the enabled photos in each chunk.

Tom

5
Andy,

Interesting.

Do you have differences between just GCP checkpoints - results just from the alignment and optimizations? Since the surfaces from depth maps is a different process, as I understand it, from 1.6.5 and 1.7.x I am wondering if the difference is because of the DEMs and how they are created.

Tom

6
General / Re: Agisoft Metashape 1.7.0 pre-release
« on: December 18, 2020, 06:47:09 PM »
Hello Alexey,

I ran a couple of tests on smaller projects and the results are very good with build 11637. The resulting mesh is superior to any I have seen in previous versions.

It is interesting that the depth maps look very different than previous versions but when I choose Export depth, the exported images look basically identical. Not sure what that means, just curious.

I am running a much more complex project now will report any issues, but I am not expecting any.

Excellent progress!

Tom

7
General / Re: Agisoft Metashape 1.7.0 pre-release
« on: December 04, 2020, 01:37:50 AM »
1.7.0 11539

I built a mesh on a project with 371 photos and only had 10 depth maps produced. I then tried a smaller project with only 10 photos and ended up with only 1 depth map.

I reran the 10 photo project using 1.6.5 just to be sure, and have 10 good depth maps. I tried 1.7.0 on medium and on high with the same result - 1 depth map.

My computer

macOS  11.0.1
iMac (Retina 5K, 27-inch, 2017)
4.2 GHz Quad-Core Intel Core i7
64 GB 2400 MHz DDR4
Radeon Pro 580 8 GB

Tom

8
General / GPU tweak
« on: September 29, 2020, 09:27:27 PM »
I am using an iMac with a AMD Radeon Pro 580 with 8 GB. When creating some complex meshes I get the console message

device AMD Radeon Pro 580 Compute Engine ignored because it has 2048 MB limit on allocations, but 2580 MB allocation required

Is there a tweak that can be set to allow more memory to be allocated or is it just a limitation of the system?

Thanks for any advice

Tom

9
General / Re: Agisoft Metashape 1.6.3 pre-release
« on: May 20, 2020, 01:06:27 AM »
Hello Tom,

The signature of Mac OS packages should be fixed in Metashape 1.6.3 build 10638. Can you please try the updated version?

Hello Dmitry,

Everything works now as expected. Thank you.

Tom

10
General / Re: Agisoft Metashape 1.6.3 pre-release
« on: May 17, 2020, 06:07:33 PM »
Hello Alexey,

I have done so in the past but in the recent past, that has actually caused the issue so no, I did not do so with 1.6.3.

I have tried rebooting and a few other things and finally tried using the terminal command "xattr -cr /Applications/MetaBeta/MetashapePro.app" and that has worked.

I am not sure I want to have to continue to do so, but perhaps it helps troubleshoot what may be going on.

Tom

11
General / Re: Agisoft Metashape 1.6.3 pre-release
« on: May 16, 2020, 06:49:54 PM »
Interesting. I always Right-Click on the app the first time to temporarily bypass Gatekeeper but for some reason that is not working. I never get the warning and the option to open anyway - only the message that the app is damaged.

Also running 10.15.4 and I have tried downloading and opening on two different machines.

Anybody got any other advice?

Tom

12
General / Re: Agisoft Metashape 1.6.3 pre-release
« on: May 15, 2020, 05:24:47 PM »
This is the message in case the screenshot does not show.

"MetashapePro.app" is damaged and can't be opened. You should move it to the Trash.

Tom

13
General / Re: Agisoft Metashape 1.6.3 pre-release
« on: May 14, 2020, 04:26:30 PM »
I downloaded 1.6.3 Professional, Mac OS X and copied the MetashapePro.app to the applications folder. When I try to open, I get a message that "MetashapePro.app" is damaged and can't be opened.

I redownloaded and tried again with same results. Perhaps the dmg is corrupt?

Tom

14
Bug Reports / Error: Wrong jacobian size
« on: April 28, 2020, 06:49:12 PM »
I have a project with over 2300 photos that fails alignment. Everything looks like it is going to work but I get

Error: Wrong jacobian size

I am using Version 1.6.2 build 10247.

The project has 6 Station groups as well as many other images. I have aligned the project successfully in previous versions of PhotoScan but was hoping to improve the results with Metashape.

I have tried a couple of different settings but same error.

What does the error actually mean?

Tom

15
Bug Reports / Selected cameras incorrect in camera calibration dialog
« on: February 09, 2019, 12:24:01 AM »
If cameras are selected in the model, workspace pane or photo pane and then open the camera calibration dialog box, the wrong cameras are identified as being selected.

Bug showed up in 1.5 and remains in 1.5.1

Tom

Pages: [1] 2 3 ... 5