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

Pages: [1] 2 3 4

Two additional questions :-):

1)Is the removl of lighting only single threaded? Regarding the CPU, it uses only one core (and not all available cores)?
2) Is there a way to export the AO map the program automatically generates ("in the background") while delighting?


Just a quick question, Agisoft offers Delighting in Metashape and in standalone Agisoft Delighter, how does it offer with other Delighting methods that are there...? Mainly i know (and talking about) Delighting in Unity engine and delighting using the Substance Alchemist aplication... ARe they more or less the same or is one significantly better/worse?


thank you for reply

Is there any reason why full functionality of Deligter (including removing cast shadows and painting on geometry) is not defaultly present right in Metashape itself too?

Also, even though you say remove shading from Delighter is something like the remove lighting feature directly in Metashape; Remove Lighting in metashape offers you an option to use AO map (that you have to bake in other application like Xnormals for example)... "Remove Shading" in Delighter doesnt have the option to choose an ambient occlusion map. But i noticed somewhere in the info/console displayed information that during processing it says something like "calculating" Ambient Occlusion... So... do i understand it correctly that Delighter actually computes its own AO map on the fly and uses it for deligting...? Thus its "easier" to use then Remove lighting in Metashape since there you have to use and external aplication (Xnormals) to bake the AO map? When in comparison Delighter computes the AO map "in-house", internally?

Thank you

For example, i read the tutorial for delighter that is here:

But when i downloaded and run Delighter it seems that the tutorial is made for some "older" version, since the one i downloaded (1.6.4) seems to have additional feature for removing lighting.

While the version in tutorial has "Parameters" under its control "Tab" window. The version i downloaded seems to have two separate "features" under its control tab (right side), and not just one as the tutorial describes. These are "Remove Cast Shadows" (which is quite self explanatory) and "Remove Shading" (with AO "tickable" option). My questions are:

1) What is this new feature "Remove Shading"?
2) The version of Delighter in the tutorial didnt yet have this feature? (or did you take the original process and splitted it into two separate functions?)
3) This "RemoveShading" feature doesnt requite you to draw on the model, right?


I would like to know whats the difference between the standalone (free) aplication "Agisoft Delighter" and the "in-built" tool/feature named "Remove Lighting" in Agisoft Metashape...?
Both "tools" seem quite different (in agisoft delighter you have to directly pain in the model), in agisoft metashape "Remove Lighting" feature you dont have to paint on the model (or to be precise- you CANNOT even if you wanted)).

So... What are the differences? Why have two "different tools", why not include delighter "painting" directly in agisoft metashape please?

Thank you

Ah interesting... so if im a scanning a "normal object" = rich texture and a lot of photos, theres really no reason the use the camera calibration?

BUT... if i have a model that failed to allign the photos (for reason that i have few photos or that the texture of the object is rather "plain" (missing details) than i could think about the camera calibration and it might help to allign the photos (that didnt allign originally).

Do i understand this correctly?

Thank you

Nobody knows; can answer that please :)?

Im not sure how to generate points with confidence...? I dont see that option ("tick") there when generating dense point cloud (in that dialog window)

The only options in the "Build Dense Cloud" options window i see, in the "advanced section" are Depth Filtering, Reuse Depth Maps and Calculate Point Colors.... I dont see any "Calculate point confidence" or whatever there... (im using 1.5.5 Metashape)...

In Agisoft metashape (photoscan), is there a way how to clean a mess of (not just) floating points? After generating dense point cloud you get a lot of "mess points" (pictures below) - some are floating, some are "connected" to the main shape... These are "garbage points", is there some "automated" solution/feature of how to get rid of them...? Sure i do it by hand but it costs a lot of time... Any feature/worfklow/function in agisoft how to get rid of them quickly/automaticaly...? (at least partially)...?
If agisoft doesnt have such feature (in which version?) is there some other software that can clean this easily?


I have camera Nikon D3200 with default kit lens (18-55mm), i useto scan smaller objects (like around 20x20 cm for example) (nothing TINY (insect) nothing HUGE).
I shoot around 50-150 photos per scan lets say. I use studio lights (cheap) and a cheap tripod.

I have NEVER done any camera calibration... I dont know anything about it

My question is simple - how much does camera calibration help in regards to increasing the final quality of the scan? (the dense point cloud, the resulting mesh, the texture)...?

THank you

Hello, i have been using some old version of agisoft metashape, now im using some newer but still older version (than the current one is). Its 1.5.5.

With this "newer but still old version" i got new error messages pop up here there, these didnt pop up EVER in previous versions.

They say:

Warning! The following problems can lead to suboptimal results:

- Images with variable zoom are added to the project. It is strongly recommended to avoid zooming as much as possible.

Happens when i upload images with "zoom" (or different Focal lenght in other words).

I have ALWAYS done this and never had this warning pop up before... DOes using different Focal Lenght ("zoom") really negativelly affect the final quality of the scan...? I have never noticed that...? IS that true? Or is that true only with never versions of metashape and older could handle it and newer give worse results? Or is it in all photogrammetry software that using different focal length leads to bad results...? I would swear i did some tests with this back in 2015 (or whatever) when i started with 3D scanning and never saw bad results...?

Is it worse? How much worse is it...? Zoom is sometimes necessary i feel... Should i really avoid it like the plague?

And another one:

Warning! The following problems can lead to suboptimal results:

- Images with different orientation are added to the project. It is strongly recommended to disable auto rotation in the camera or photo processing software.

Again...? Does different rotation matter? (in this example i scanned some leaf and few photos had the same leaf, the same side of the leaf, just aprx. 90 degree rotated...

I have dont this before i think and no problem. No it gives me this warning and also the point cloud looks weird... (like wrong, "normals" flipped).

So how is?

    Is using different Focal length really THAT BAD? Should i avoid it at all cost...? (any pictures of tests for this...?)

    Is using different rotation (mainly switching holding the camera verticaly or horizonatally; but even rotations like 30% only for example)... Is this also BAD...? How MUCH bad... should be avoided at ALL COSTS...?

(camera i use: Nikon D3100)

Im sorry in the original post i posted wrong question (on wrong forum) about zbrush :-D... I have updated the first post with the originally intended question about agisoft photoscan - how to temporary hide selected points in dense point cloud...


Im sorry i posted the wrong question... my question was: Is it possible to hide selected points in dense point clouds in agisoft photoscan? If one needs to hide selected points so he can better cleanup hard to acces parts of the model (which were previously blocked by hidden points)...

And once the cleanup (deleting on unwanted HARD to acces points) is done, than re-hide (show again) the previously hidden points (in dense point cloud)? Does agisoft has such functionality? (if not, why :-)? seems like a usefull feature)?

Thank you

General / Re: Performance diff. GTX 1060 vs GTX 1070 in photoscan...?
« on: March 01, 2017, 02:46:37 AM »
Thank but im not an idiot :-). There many game benchmarks, but sadly, gtx 1070 performs worse in profi applications, where there are NOT many (or any?) tests at all...

I didnt find practicaly any, thats why im askign here, if someone didnt test them already?

General / Performance diff. GTX 1060 vs GTX 1070 in photoscan...?
« on: February 28, 2017, 06:42:20 PM »
Does anybody have an idea or actual numbers, whats the speed improvement in photoscan when using GTX 1060 6 GB vs GTX 1070 8 GB?

Thank you

Pages: [1] 2 3 4