Messages

181

General / Re: Rhino doubts

« on: August 13, 2013, 03:30:00 AM »

The chunk name cannot have any spaces for the .obj files to work properly. I don't think special characters are allowed either.

You may also need to edit the .obj file and .mtl file.

-  In the .mtl file edit the first line "newmtl Textured" Replace "Textured" with a unique name not used by any other texture in Rhino.

-  In the .obj file edit the second line "usemtl Textured"  Replace "Textured" with the same name used in the .mtl file

Agisoft is going to try to change PhotoScan so the file name is used instead of "Textured" which should eliminate the problem.  http://www.agisoft.ru/forum/index.php?topic=1380.0

182

Bug Reports / Disabled photos used to Align Chunks

« on: July 23, 2013, 06:18:39 AM »

Disabled photos are used by Align Chunks when the Camera Based method is selected. This has caused problems for me when I have disabled an obviously incorrectly aligned photo/camera in a chunk.

Is "Disable" for a photo in a chunk intended to only apply to certain tasks? If so what tasks use photos which have been set to "Disable"?

183

General / Re: exporting model to CAD

« on: July 19, 2013, 10:29:56 PM »

I export from Photoscan to Rhino3d using OBJ files. I've successfully exported meshes with over 5 million quad faces. Proceedure is:
1) Build geometry
2) Texture
3) Export chunk as .obj

184

Feature Requests / Re: OBJ Texture Names Chunk Specific

« on: July 11, 2013, 07:04:12 PM »

Using the file name for the material name is a good idea. The file name needs to be unique so that makes the material name also unique. Thanks!

185

Feature Requests / Re: OBJ Texture Names Chunk Specific

« on: July 11, 2013, 04:45:40 AM »

Not sufficient for importing multiple OBJ meshes into Rhino3D.

I'm importing the OBJ meshes into Rhino3D. If I import a single OBJ file into Rhino3D it picks up the corresponding .mtl and .jpg files. Everything works okay.

But if I import another OBJ file with the same material names in the .obj and .mtl files into Rhino3D then the second OBJ file is displayed with the wrong texture. (Geometry is okay). Renaming the material names before import solves the problem.

I'm modeling historic boats and need to be able to import multiple chunks into Rhino3D. This evening I'll be editing the material names in 29 sets of files.

186

General / Re: How to overcome RAM Limitation

« on: July 10, 2013, 03:02:28 PM »

I have only run into memory limitations with build geometry. My work-around in that case is to:
1) Align
2) Duplicate the resulting chunk
3) Adjust the "box" in each chunk so that it only covers a portion of the geometry, with the chunks overlapping.
4) Build Geometry in each chunk.

187

Feature Requests / OBJ Texture Names Chunk Specific

« on: July 07, 2013, 05:23:58 AM »

When OBJ meshes are exported use the chunk name instead of "Textured" for the "material" in the associated .mtl and .obj files.
.mtl file: "newmtl Textured" becomes "newmtl ChunkName"
.obj file: "usemtl Textured" becomes "usemtl ChunkName"

I export multiple chunks as OBJ meshes from a single project. I then have to go in and manually edit the sets of .mtl and .obj files so that the names of the "materials" are different for each mesh.

188

General / Re: Generic Mask

« on: May 09, 2013, 06:11:06 PM »

"Bulk Rename Utility" is a free download which greatly simplifies renaming multiple files. I used it yesterday to rename and renumber over 200 masks. www.bulkrenameutility.co.uk

189

General / Re: Software to analyse exported 3d models

« on: May 09, 2013, 06:03:31 PM »

I export to Rhino3D using .obj format.

190

General / Re: Photography Tips

« on: May 08, 2013, 09:06:52 PM »

I have found a background with good texture can be beneficial during the align stage, particularly when the object of interest does not have a strong texture. The one requirement is the object of interest does not move relative to the background. Using the background during align.

The only time I have masked the background was when the object of interest moved relative to the background.

For build geometry I orient and set the "box" close the object so that little or no geometry is created from the background.

191

General / Re: Can't get any usable results

« on: April 30, 2013, 06:00:12 PM »

Pull the corners of the bounding box so that the box is close to the points in the cloud from the object of interest.

Try using Sharp rather than Smooth in Build Geometry. When I use Smooth on very three-dimensional objects the result is frequently a large blob.

192

Bug Reports / Re: 0.9.1 Build 1647 crashes graphics

« on: April 29, 2013, 07:44:39 PM »

Today I removed AMD software including the driver, and then loaded the latest released software including driver version 12.104.0.0.  I also downloaded and installed the latest Beta build of PhotoScan Standard Edition 0.9.1 build 1667 (64 bit).  I'll report if the problem reoccurs.

193

General / Re: Agisoft PhotoScan 0.9.1 pre-release

« on: April 12, 2013, 02:59:33 PM »

I have a similar problem to Wishgranter. When Batch mode is used Build Geometry always resets to Smooth and 200000 maximum faces and ignores what I set.

194

Bug Reports / Re: 0.9.1 Build 1647 crashes graphics

« on: April 12, 2013, 03:14:35 AM »

The problem first occurred with Build 1647, and occurred every time I used Build Geometry with Open CL on. Previous to installing Build 1647 the problem had not occurred. The graphics drivers had not been changed for quite a while before installing Build 1647. I subsequently updated the drivers to the latest released (non-Beta) version which did not change anything.

With Build 1654 the problem occurs sometimes. When I tested the tutorial datasets they were okay. A project with 240 photos ran okay several times and then the problem occurred. A project with 11 photos had the problem occur every time.

It will be a few weeks before I'm able to do any comprehensive testing. Currently I'm running with OpenCL turned off.

195

Bug Reports / Re: 0.9.1 Build 1647 crashes graphics

« on: April 08, 2013, 05:58:04 PM »

Turns out it is not resolved. The same problem has reoccured, though not every time.