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 - Hamish

Pages: [1] 2
1
General / Re: Attempting to merge manually aligned chunks
« on: December 19, 2023, 02:23:45 AM »
Thanks Alexey,

That seems to work, although the scale value should possibly be to three decimal points as I'm getting around ten steps between x1.00 & x1.01, I'm also curious why both chunks should need to have the scale transformation applied to successfully complete the merge - surely the process is to scale one chunk to the other not adjust the scale of both.

It would be helpful to be able to adjust the chunk transparency when manually aligning to see what is happening at all points of a joint.

2
General / Attempting to merge manually aligned chunks
« on: December 16, 2023, 07:11:05 PM »
I’m not sure if this is a bug or if I’m trying to use metashape incorrectly

I have a model of a medieval effigy of a lady. It is broken into two parts, one stacked on top of the other and placed in a wall recess in a church. My aim is to reunite the head in the correct position.
I have duplicated my original model into two new chunks, then disabled the original model.
In each of the two new chunks I have carefully trimmed each model to the areas that I need.
Select “Show Aligned Chunks” on toolbar, then repositioned and reorientated the chunks using the transformation tools “Move object” and “Rotate Object” – “Scale Object” doesn’t need to be changed since both chunks are from the same source.
When I merge the chunks then deselect “Show Aligned Chunks” - I’m left with one chunk with its region on a different alignment and no merging having occurred.

I’m loosely following these instructions using a model rather than point cloud. https://agisoft.freshdesk.com/support/solutions/articles/31000157701-manual-chunk-alignment-standard-edition-

Metashape 2.0.4 build 17434 (standard)
i7-13700k, 64GB Ram, RTX 3080 12GB (driver version 545.84)


3
Thanks Alexey I see my mistake, I was expecting to find the functions in the workspace pane in the chunk menu rather than the 3d model menu

4
From the changelog https://www.agisoft.com/pdf/metashape_changelog.pdf

Version 2.0.2 build 16334 (5 June 2023)
Standard and Professional editions
Added Remove Texture, Remove UVs, Remove Vertex Colors and Remove Confidence commands to
model context menu.

These remove functions are not present in build 16404 standard edition Windows x64

5
I have a project open, with resize region selected.
I select the "File" menu and "New"

I would expect the model view to be blank, but in the center of the screen is one of the blue dots from corners of the region (when resizing), when I click and drag the dot a region appears although there are no point clouds or anything.

It does not cause me any problems (although initially a little confusion) but seems to be a bug I am able to easily repeat.

Metashape Std v2.0.1.15986 -- i7-13700K, 64GB Ram, Nvidia RTX 2060 (driver 531.18), Win 11.

6
Bug Reports / Re: Sketchfab upload from version 2 not working
« on: March 11, 2023, 04:17:43 PM »
I have the same problem uploading from Metashape standard (2.0.1.15925) to Sketchfab.

On the occasions in the past where I export a file from Metashape for manual upload to sketchfab, I use the FBX file format, but this currently throws the same error, although the files open fine in Meshlab (2022.02)

PLY file exported from Metashape and manually uploaded to Sketchfab works fine.


I've just tried uploading a FBX file exported from Metashape almost a year ago (version 1.8.2), Sketchfab did not have any problems with this file.


Hamish

Metashape Std v2.0.1.15925 -- i7-13700K, 64GB Ram, Nvidia RTX 2060 (driver 531.18), Win 11.

7
Thank you for reporting the problem, we are working on this issue.

if there is to be a fix for this issue will it come in 1.8.x version of metashape or will we have to wait for the stable 2.0.x ?

8
Bug Reports / Upload Data crash
« on: July 24, 2022, 10:52:10 PM »
Upload Data (to in my case Sketchfab) Source Data: Model, Parameters: Draft Model > OK

if the process is cancelled during the following two progress stages then metashape crashes/closes at the start of or during the upload stage:
Processing in Progress - Packaging Model
Processing in Progress - Uploading 37.23MB

if cancel during final stage
Processing in Progress - Processing Model > Aborted by User > OK (no crash) and model finishes processing on sketchfab.

I have consistently managed to repeat the bug with multiple different models.

-- If anyone is interested in why I might cancel an upload - sometimes I try to upload the most detailed high resolution model I can, the limitation being the upload size (MB) according to my account level, if the packaged model size is too large I cancel the upload, make adjustments and try again.

Metashape Standard 1.8.4.14671
Nvidia RTX2060 driver 516.40
Windows 10

9
General / Reduce Overlap 1.7.0
« on: January 20, 2021, 12:37:50 AM »
How do you use the reduce overlap feature in 1.7.0 ? I'm familiar with this feature in previous versions now I'm a bit confused.

I have aligned cameras to build sparse cloud (206 Cameras), built mesh from sparse cloud, reduce overlap.

Select camera model, There is a choice of six cameras - what should I select? and what is the difference?:
DMC-GF3 (14mm) - which is the camera and lens combination I used to take the photos, Same Physical camera, same lens, 2 different apertures and 8 different shutter speeds, yet it appears five times in the list.
Default camera (50mm)

Surface Coverage ??

In the absence of an updated manual for version 1.7, is there some help on this





Metashape 1.7.0.11736 - Windows 10 Pro 1909 - AMD FX8350 - 32GB Ram - RTX2060 6GB (v457.51)

10
Bug Reports / Re: reduce overlap -> empty bbox
« on: September 21, 2020, 09:57:17 AM »
I had this problem earlier this year (when I first tried to use reduce overlap), amongst other issues.

I was using:
AMD FX-8350, 32GB ram, SSD
2x Nvidia GTX760 4GB (with driver version 388.71)
Windows 8.1 Pro

The graphics cards are right old now, I downloaded driver 388.71 in January 2018, that was the last driver version that cuda worked on for these cards. when cuda doesn't work metashape either can't see the cards properly or throws up errors all the time. That driver only had cuda support to v9.0

In April 2020 I upgraded to 1x Nvidia RTX2060 6GB (latest drivers) & reluctantly to Windows 10 Pro and not had the problem since with reduce overlap -> empty bbox.
I'm normally using the latest stable version of Metashape (not preview releases) Standard.

11
Feature Requests / Re: Remove Vertex Colors
« on: January 27, 2019, 10:24:39 PM »
Thanks Alexey

H

12
Feature Requests / Re: Remove Vertex Colors
« on: January 27, 2019, 06:50:03 PM »
I'd normally create a mesh with vertex colours because it aids cropping and tidying up a mesh. Sometimes I don't want or need the colours in the final mesh.
Normally in my work flow I duplicate chunks before doing any major editing so it is easier to go back if I make any mistakes - then have chunk for the finished mesh. Ideally the mesh should represent what I export.
I realise that when you export you can select/deselect vertex colours in the export parameters - but often I upload a model to Sketchfab - where there are no such options, when pushing a 50MB upload limit the model can have more faces if it doesn't have any colours.
Metashape does a better job at packaging/compressing models than I can achieve by exporting a model then zipping it then uploading.

13
Feature Requests / Remove Vertex Colors
« on: December 01, 2018, 11:45:13 PM »
When building a mesh, one of the Advanced options is Calculate Vertex Colors

But once a mesh is created I can't see a method of removing vertex colours from a mesh, could this option be added to the menu when you right click on a chunk

thanks
hamish

Photoscan Standard 1.4.4 (6848)

14
Feature Requests / Re: Shutdown or email when the task is done
« on: December 01, 2018, 11:20:37 PM »
Would it be possible to have a selectable option to make the computer shutdown or sleep as a final batch processing step in the standard version of photoscan?

When I leave photoscan processing overnight I often find it still working when I leave for work in the morning, then when I get home 13 hours later discover that the processing completed twenty minutes after I left the house.

15
Bug Reports / Re: CUDA problem
« on: May 12, 2018, 01:18:44 PM »
I have had the same problem, when I first encountered it back in early March I just rolled the graphics driver back to an earlier version as it was installing the latest graphics driver that had caused the problem. I've recently installed the latest build of PhotoScan and upon installing the latest graphics driver the issue has re-emerged - and sort of solved by going back to the earlier graphics driver.
After each install I restart the computer before running PhotScan.

CPU: AMD FX-8350 8 core 4ghz x64
Motherboard: MSI 990FXA-GD65
Ram: 32GB
Graphics Nvidia GTX 760 4GB x2
Windows 8.1 Pro

Photoscan Standard x64 1.4.1 (5925)
Photoscan Standard x64 1.4.2 (6205)

cudaGetDeviceCount failed: unknown error (30)

using Nvidia driver Versions
391.01-desktop-win8-win7-64bit-international-whql
397.64-desktop-win8-win7-64bit-international-whql

---
The only way I have got around the problem is using an earlier Nvidia driver, everything seems to work fine.

388.71-desktop-win8-win7-64bit-international-whql (downloaded 6 January 2018)

---
Update 01/2019, I've explored the problem a little further - For me this is an NVIDIA driver problem not a photoscan/metashape issue.
Other software isn't able to access cuda either. I'm using a couple of GTX 760 cards - reading across various forums others are also having driver problems with nvidia 700 series cards and recent drivers.
As long as Metashape doesn't require Cuda above v9.0, hopefully I should be fine.

Pages: [1] 2