Topics

1

Bug Reports / error Kernel failed: an illegal memory access was encountered (700) at line 143

« on: September 27, 2023, 11:50:18 AM »

hello,
I have this error since 4 days and i'm competely stuck into my work and dead line is approaching.
During the alignment between photos and laser scans.
I have a lots of laser scans (72) to align with 3500 photos. the danse cloud from all the scans are about 2 billions about points 50 millions points each. I have 256 go ram, dual xeon cpu E5 2640 V4, and a Quadro RTX 8000.
Mabe point cloud from laser scans is too big ?
I'm working with windows 10 up to date and Nvidia driver is 537.42 desktop / notebook driver for quadro (up to date too)
i'm working with the latest metashape build 2.0.3 16915

the error :
2023-09-27 10:10:06 Detecting points...
2023-09-27 10:10:06 Found 1 GPUs in 0 sec (CUDA: 0 sec, OpenCL: 0 sec)
2023-09-27 10:10:06 Using device: Quadro RTX 8000, 72 compute units, free memory: 47686/49151 MB, compute capability 7.5
2023-09-27 10:10:06   driver/runtime CUDA: 12020/10010
2023-09-27 10:10:06   max work group size 1024
2023-09-27 10:10:06   max work item sizes [1024, 1024, 64]
2023-09-27 10:10:12 Warning: cudaStreamDestroy failed: an illegal memory access was encountered (700)
2023-09-27 10:10:13 Finished processing in 307.578 sec (exit code 0)
2023-09-27 10:10:13 Error: Kernel failed: an illegal memory access was encountered (700) at line 143


Thanks for the help !

2

General / texture glitch on low poly model

« on: October 29, 2022, 09:58:02 AM »

Hello,

i'm experiencing some glitches on my low poly model after transfering it from my high poly model,

here is the model :

https://sketchfab.com/3d-models/citadelle-de-corte-54a6311bce6d432f817729d2fcb594be

how can i avoid this situation ? is my mesh too diffrerent from the source mesh ?

thanks a lot

3

Bug Reports / VK error GPU textures generation

« on: April 15, 2021, 03:56:57 PM »

Hello
I have this error during textures generation on my model. Here is the console detail :
do you have any ideas ?
Is it a bug or should i reduce the polycount ?
Thanks !

Parameterizing texture atlas...
Model size: 196461271 faces, 98219395 vertices
Decimated to 1000000
Performing initial subdivision...   
Division threshold 100000
chart  0 faces: 97663
chart  1 faces: 84181
chart  2 faces: 78613
chart  3 faces: 77074
chart  4 faces: 72911
chart  5 faces: 72035
chart  6 faces: 66696
chart  7 faces: 65985
done. (in 3.505 sec). Got 373 initial parts.
top 8 mean: 76894.8 stddev: 9681.93
*************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
Scaling charts... 
done. (in 1.42 sec)
Concatenating charts... 
done. (in 0.046 sec)
Packing... 
Parametrization contains 30152 charts
Pack iteration 0 ratio 0.525
Pack iteration 1 ratio 0.3875
Pack iteration 2 ratio 0.45625
Pack iteration 3 ratio 0.490625
Pack iteration 4 ratio 0.473437
done. (in 1667.53 sec)
Retrieving mesh
Parameterizing done in 2280.41 sec
Blending textures...
Found 1 GPUs in 0.147 sec (CUDA: 0.034 sec, OpenCL: 0.113 sec)
Using device: NVIDIA Quadro RTX 8000, 72 compute units, free memory: 47721/49152 MB, compute capability 7.5
  driver/runtime CUDA: 11030/8000
  max work group size 1024
  max work item sizes [1024, 1024, 64]
  got device properties in 0 sec, free memory in 21.68 sec
All cameras are fine
Initializing context...
Found device NVIDIA Quadro RTX 8000 driver version 1954725888, API version: 1.2.168, location 129::0
calculating mesh connectivity... done in 69.737 sec
Initialized texture renderer
Configuring pipeline...
Initialized memory broker
Configuring mosaic pipeline with outliers filtering
Constructed pipeline
Relaxed precision enabled
Collecting memory requests...
Allocating memory requests...
Estimated required video memory: 13297 MB
Estimated device memory: total 48708 MB, used 221 MB, available 47940 MB
Allocated 13319 MB of VRAM
Allocated memory requests
Configured pipeline
Processing cameras...
Loading mesh...
Cannot use GPU. Reason: VK Error : VkResult is "ERROR_OUT_OF_DEVICE_MEMORY" at line 12
Performing blending on CPU...
calculating mesh connectivity... done in 67.325 sec
detecting outliers...

4

Bug Reports / Freenas local network processing

« on: October 31, 2020, 12:40:13 PM »

Hellow !

I build a nas running freenas to work and store on my metashape projects, i've been struggling with apparently small network glitch during depht map processing : 'Can't read file error 59' that made the whole process crash. So i'm currently trying to do the workflow using my workstation as self server and node to do the job. So far the process is running despite the errors without totally crashing. My question: Will metashape be able to correct the errors by recalculating the parts that had the network glitch or not ?

Thanks !

5

Bug Reports / Pack iteration Texture generation

« on: March 10, 2020, 02:25:14 PM »

Hello,

Since the last update, texture generation is taking a really long time, i have a considerable number of iteration packs. Can someone explain the reason ?
Thanks a lot

6

General / Measure shape DEM generation

« on: November 25, 2019, 03:22:23 PM »

Hello,

Is there any way to extract a correctly scaled Shape from a DEM ?
Im trying to overlay severals measures for now im trying to fix it manually on illustrator but mabe there is a better solution 
thanks !

7

General / Graphic card Quadro RTX 6000-8000

« on: October 11, 2019, 05:23:31 PM »

Hello,

I'm considering buying a quadro RTX 8000 to work on really large workflows, (without considering the price), will the 48 Go of VRAM be able to load a larger model ?
I'm actually working with two GTX 1080 ti and it's lagging so much when i work on 70 mio poly models (i'm working on really large datasets), i hope it would be more fluid !

8

Feature Requests / Seam Lines Photos identification on textured model

« on: November 23, 2017, 12:40:13 PM »

Hello !

I may have a suggestion that could be usefull :
the other day i needed to clean a textured model on a complex
archaeological survey full of rocks, a pain in the ass to have
sharp photographs due to the depth of field. After the Build texture process i wanted to easily identificate the pictures i wanted to remove or partially remove the unwanted bad areas : the easy way should be to show the id of the photos's inside the seam lines view and / or select with a polyline parts that are unwanted (blur etc).
what do you think ?
thanks a lot

9

General / Seam Lines Photos identification on textured model

« on: November 20, 2017, 12:57:02 PM »

Hello !

I may have a suggestion that could be usefull :
the other day i needed to clean a textured model on a complex
archaeological survey full of rocks, a pain in the ass to have
sharp photographs due to the depth of field. After the Build texture process i wanted to easily identificate the pictures i wanted to remove or partially remove the unwanted bad areas : the easy way should be to show the id of the photos's inside the seam lines view and / or select with a polyline parts that are unwanted (blur etc).
what do you think ?
thanks a lot

10

Bug Reports / Export Pdf, ply

« on: April 30, 2015, 11:44:01 PM »

Hello,

I'm a new user of the application (in regular version) and im experiencing a problem with export in pdf.
I would like to export my work with better quality textures (more than 4096 which is too pixelised). When i set textures in 8000 or 10000 the rendering is excellent inside the app, but export in pdf fail... (i can only see a white screen on my pdf3d, and when i select my object it's a transparent solid version), and if i set 4096 for texture size and more than 2 for count it slows my computer too much...
The export with 4096 set in texture size works
i think i'm missing something...

Thanks for the help
(working with a mac pro 2008 with amd radeon 5800)