1
General / Re: Photoscan textures in ZBrush
« on: April 22, 2016, 01:11:20 PM »
export your model before you do textures in ps, create uv in zbrush and export back
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.
2
General / Re: Extreme distortion of the sparse cloud using masks?
« on: April 19, 2016, 11:15:12 AM »
you can try creating masks from the model you get from the sparse cloud or a dense cloud on low settings, then redo the alignment with the new masks
3
Feature Requests / Re: More efficient UV islands and an 'edge bleed' or 'relief' feature for textures
« on: April 15, 2016, 12:05:12 PM »
you can choose whatever texture format you want on export
4
General / Re: How to conserve sharp egdes in the scan?
« on: April 06, 2016, 06:13:05 PM »
Use higher settings
5
General / Re: Texture artifacts on mesh edges
« on: April 05, 2016, 11:47:15 AM »
Tried doing a custom UV map before texture creation?
6
Python and Java API / Re: Python API run batch file (start process on cluster)
« on: March 23, 2016, 08:28:11 PM »
Awesome!
are there any limitations to this? or is it possible to do all major steps over network via python scripts now?
are there any limitations to this? or is it possible to do all major steps over network via python scripts now?
7
General / Re: Aligning top and bottom of an object
« on: March 09, 2016, 07:51:45 PM »
If you mask all your photos, you shouldn't have any problems aligning your chunks
8
General / Re: Fine-Level Task Distribution for builiding Mesh
« on: March 03, 2016, 01:46:59 PM »
Not possible at the moment, you can split your dense clouds into smaller chunks if you want to distribute the mesh generation step
9
General / Re: Room scan - Getting rough uneven walls on mesh
« on: February 29, 2016, 01:32:17 PM »
Export to fbx, import to maya and do whatever, import back.
10
General / Re: memory and masked objects
« on: February 11, 2016, 01:34:35 PM »
Mesh generation is based only on your dense cloud as far as I know, masking is only used during alignment and (?) dense cloud generation
11
General / Re: Not Enough Memory!!!
« on: February 02, 2016, 06:45:03 PM »
Split your chunk into smaller pieces before mesh generation, there are scripts that can do this for you
12
General / Re: Translate and rotate dense cloud
« on: January 24, 2016, 06:10:23 PM »
Press 5 to go in ortho mode, click 7 then 8 to get a perfect top down view (y-axis pointing up) rotate your model, click 7 again to get a side view and keep aligning your model
13
Bug Reports / Re: Build Texture... 1.1.6 vs 1.2.1
« on: January 20, 2016, 12:40:15 PM »
Is this solved in Version 1.2.3 build 2331?
14
General / Re: Straight to height/color map , without mesh ?
« on: January 19, 2016, 03:32:46 PM »
Another way, if possible, could be to create a camera from the current viewport location in Photoscan, and set a custom resolution if say you want a 4k output. I'm not sure if this could be done through a python script or not though, but we would be interested in this as well. Maybe Alexey knows 
15
General / Re: Straight to height/color map , without mesh ?
« on: January 19, 2016, 12:29:24 PM »
I guess you could import a custom camera. If you export your cameras you get an .xml file with your camera profiles and transformation.
So maybe if you add a custom profile with a square resolution and a custom camera with your own transform maybe that would work out. Ideally you would import your cameras and a proxy mesh into your 3d app of choice and add a new camera there and import that back into photoscan, but not sure if that is possible
Code: [Select]
<sensor id="4" label="Canon EOS 6D (24 mm)" type="frame">
<resolution width="5472" height="3648"/>
<property name="pixel_width" value="0.0065789473684210523"/>
<property name="pixel_height" value="0.0065789473684210523"/>
<property name="focal_length" value="24"/>
<property name="fixed" value="false"/>
<calibration type="frame" class="adjusted">
<resolution width="5472" height="3648"/>
<fx>3753.5223540078168</fx>
<fy>3753.5223540078168</fy>
<cx>2738.2623805545941</cx>
<cy>1807.8852989996785</cy>
<k1>-0.096003340193473383</k1>
<k2>0.090491266178159571</k2>
<k3>-0.022672314154036397</k3>
<p1>-0.00036612279367345148</p1>
<p2>0.00021318275905502101</p2>
</calibration>
</sensor>andCode: [Select]
<cameras>
<camera id="0" label="IMG_6974.jpg" sensor_id="0" enabled="true"/>
<camera id="1" label="IMG_6975.jpg" sensor_id="0" enabled="true"/>
<camera id="5" label="customcam" sensor_id="0" enabled="true">
<transform>-9.8752684113413847e-001 -3.4323850223813929e-002 1.5366395590847953e-001 -2.0584633926248333e+001 1.5731772697203841e-001 -2.5520505827043760e-001 9.5400288836750047e-001 -1.3817692896672533e+001 6.4707665682775389e-003 9.6627752304345549e-001 2.5742159513339813e-001 2.6039842407608546e+001 0.0000000000000000e+000 0.0000000000000000e+000 0.0000000000000000e+000 1.0000000000000000e+000</transform>
</camera>
So maybe if you add a custom profile with a square resolution and a custom camera with your own transform maybe that would work out. Ideally you would import your cameras and a proxy mesh into your 3d app of choice and add a new camera there and import that back into photoscan, but not sure if that is possible
