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.


Topics - macsurveyr

Pages: [1]
1
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

2
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

3
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

4
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

5
General / macOS Mojave
« on: September 26, 2018, 07:33:36 PM »
Is there any word on compatibility with the just released macOS Mojave?

I have to upgrade for several reasons but can put it off for a bit if PhotoScan has issues.

Tom

6
General / Replacing photos in a project
« on: May 18, 2017, 10:13:06 PM »
Is there a way to get PhotoScan to fully recognize photos if they are changed, replaced that is?

For instance, if I create a project with 3 band TIF images, align, refine things, add GCP’s etc. and then decide that I would like to swap out the 3 band imagery for 4 band, PhotoScan does not show anything other than the original 3 bands.

The images are exactly the same dimensions and all found tie points, markers, and camera calibrations have not changed and everything should work fine. If only I could get the new images fully recognized.

Thanks,

Tom

7
Bug Reports / Capture View save issues
« on: June 17, 2016, 09:01:35 PM »
With version 1.2.5 when trying to Capture View there are issues with both .jpg and .tif

The behavior is a bit different on a Mac and on Windows. On a Mac a ; is appended to the .jpg and .tif and the system complains about not being able to save or an invalid extension. Entering jpeg and tiff works. On Windows, it does not seem possible to save a jpg or tif even as jpeg or tiff

Tom

8
Bug Reports / 1.2.4 Duplicate Chunks
« on: March 31, 2016, 09:31:23 PM »
The latest version 1.2.4 can take several minutes to duplicate a chunk. Not always, but by far most of the time. That was an issue in some previous version that went away and seems to be back.

Also, maybe related, saving - even in .psx - can take several minutes as well. Not always, just sometimes.

9
Bug Reports / PLY export coordinates no decimal places
« on: March 12, 2016, 01:41:15 AM »
It seems that all versions after 1.2.0 build 2198 do not export any decimal places for the X and Y coordinates when exporting a text PLY file - that is uncheck binary coding.

Actually it looks like 6 digits are exported no matter what - if local coordinates are exported you might get 123.456 but if say UTMs are exported you get 123456 or 1234560

Tried it in 1.2.1 1.2.2 and 1.2.3

Tom

10
Bug Reports / Large coordinates truncated in PLY
« on: March 13, 2013, 02:41:46 AM »
Many projected coordinate systems have coordinates that exceed 1,000,000

PLY files are exported with the coordinates as property float which means that the coordinates are truncated.

Perhaps with most data sets that goes unnoticed, but a building placed in UTM coordinates that exceed 500,000,4,000,000 it is pretty obvious.

If any coordinate exceeds 1,000,000 it should be stored as property double.

Tom

Pages: [1]