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

Pages: [1] 2 3
1
See below a part of the log. It says: GPU 2 and GPU 1. I guess one of them is Intel UHD?


2022-12-25 11:55:24 BuildModel: quality = Low, depth filtering = Mild, PM version, source data = Depth maps, surface type = Arbitrary, face count = Medium, volumetric masking = 0, OOC version, interpolation = Enabled, vertex colors = 0
2022-12-25 11:55:25 Generating depth maps...
2022-12-25 11:55:25 Preparing 41030 cameras info...
2022-12-25 11:55:42 91 cameras skipped (due to <=2 tie points)
2022-12-25 11:55:42 40939/41030 cameras prepaired
2022-12-25 11:55:42 cameras data loaded in 16.697 s
2022-12-25 12:01:24 cameras graph built in 342.142 s
2022-12-25 12:01:24 filtering neighbors with too low common points, threshold=50...
2022-12-25 12:01:24 Camera 1875 has no neighbors
2022-12-25 12:01:24 Camera 1876 has no neighbors
2022-12-25 12:01:24 Camera 2716 has no neighbors
2022-12-25 12:01:24 Camera 2994 has no neighbors
2022-12-25 12:01:24 Camera 3027 has no neighbors
2022-12-25 12:01:24 Camera 4501 has no neighbors
2022-12-25 12:01:24 Camera 4502 has no neighbors
2022-12-25 12:01:24 Camera 4503 has no neighbors
2022-12-25 12:01:24 Camera 4500 has no neighbors
2022-12-25 12:01:24 Camera 4885 has no neighbors
2022-12-25 12:01:24 Camera 4886 has no neighbors
2022-12-25 12:01:24 Camera 5626 has no neighbors
2022-12-25 12:01:24 Camera 5849 has no neighbors
2022-12-25 12:01:24 Camera 6058 has no neighbors
2022-12-25 12:01:24 Camera 6254 has no neighbors
2022-12-25 12:01:24 Camera 6349 has no neighbors
2022-12-25 12:01:24 Camera 5791 has no neighbors
2022-12-25 12:01:24 Camera 5876 has no neighbors
2022-12-25 12:01:24 Camera 5687 has no neighbors
2022-12-25 12:01:24 Camera 5943 has no neighbors
2022-12-25 12:01:24 Camera 5957 has no neighbors
2022-12-25 12:01:24 Camera 6070 has no neighbors
2022-12-25 12:01:24 Camera 9498 has no neighbors
2022-12-25 12:01:24 Camera 10118 has no neighbors
2022-12-25 12:01:24 Camera 5544 has no neighbors
2022-12-25 12:01:24 Camera 11388 has no neighbors
2022-12-25 12:01:24 Camera 11391 has no neighbors
2022-12-25 12:01:24 Camera 9499 has no neighbors
2022-12-25 12:01:24 Camera 11449 has no neighbors
2022-12-25 12:01:24 Camera 9500 has no neighbors
2022-12-25 12:01:24 Camera 9845 has no neighbors
2022-12-25 12:01:24 Camera 5050 has no neighbors
2022-12-25 12:01:24 Camera 9927 has no neighbors
2022-12-25 12:01:24 Camera 12370 has no neighbors
2022-12-25 12:01:24 Camera 10138 has no neighbors
2022-12-25 12:01:24 Camera 6140 has no neighbors
2022-12-25 12:01:24 Camera 10240 has no neighbors
2022-12-25 12:01:24 Camera 10557 has no neighbors
2022-12-25 12:01:24 Camera 11129 has no neighbors
2022-12-25 12:01:24 Camera 11302 has no neighbors
2022-12-25 12:01:24 Camera 11309 has no neighbors
2022-12-25 12:01:24 Camera 11358 has no neighbors
2022-12-25 12:01:24 Camera 6706 has no neighbors
2022-12-25 12:01:24 Camera 11661 has no neighbors
2022-12-25 12:01:24 Camera 11647 has no neighbors
2022-12-25 12:01:24 Camera 12210 has no neighbors
2022-12-25 12:01:24 Camera 9958 has no neighbors
2022-12-25 12:01:24 Camera 14024 has no neighbors
2022-12-25 12:01:24 Camera 15537 has no neighbors
2022-12-25 12:01:24 Camera 15643 has no neighbors
2022-12-25 12:01:24 Camera 15685 has no neighbors
2022-12-25 12:01:24 Camera 15686 has no neighbors
2022-12-25 12:01:24 Camera 15682 has no neighbors
2022-12-25 12:01:24 Camera 15681 has no neighbors
2022-12-25 12:01:24 Camera 13204 has no neighbors
2022-12-25 12:01:24 Camera 15540 has no neighbors
2022-12-25 12:01:24 Camera 15728 has no neighbors
2022-12-25 12:01:24 Camera 15726 has no neighbors
2022-12-25 12:01:24 Camera 15683 has no neighbors
2022-12-25 12:01:24 Camera 16298 has no neighbors
2022-12-25 12:01:24 Camera 16355 has no neighbors
2022-12-25 12:01:24 Camera 16306 has no neighbors
2022-12-25 12:01:24 Camera 15684 has no neighbors
2022-12-25 12:01:24 Camera 16603 has no neighbors
2022-12-25 12:01:24 Camera 17239 has no neighbors
2022-12-25 12:01:24 Camera 13188 has no neighbors
2022-12-25 12:01:24 Camera 17549 has no neighbors
2022-12-25 12:01:24 Camera 17597 has no neighbors
2022-12-25 12:01:24 Camera 21220 has no neighbors
2022-12-25 12:01:24 Camera 21237 has no neighbors
2022-12-25 12:01:24 Camera 16566 has no neighbors
2022-12-25 12:01:24 Camera 21333 has no neighbors
2022-12-25 12:01:24 Camera 16624 has no neighbors
2022-12-25 12:01:24 Camera 16372 has no neighbors
2022-12-25 12:01:24 Camera 17255 has no neighbors
2022-12-25 12:01:24 Camera 17315 has no neighbors
2022-12-25 12:01:24 Camera 21709 has no neighbors
2022-12-25 12:01:24 Camera 17461 has no neighbors
2022-12-25 12:01:24 Camera 16369 has no neighbors
2022-12-25 12:01:24 Camera 17622 has no neighbors
2022-12-25 12:01:24 Camera 16370 has no neighbors
2022-12-25 12:01:24 Camera 16373 has no neighbors
2022-12-25 12:01:24 Camera 16622 has no neighbors
2022-12-25 12:01:24 Camera 22263 has no neighbors
2022-12-25 12:01:24 Camera 21710 has no neighbors
2022-12-25 12:01:24 Camera 17451 has no neighbors
2022-12-25 12:01:24 Camera 24007 has no neighbors
2022-12-25 12:01:24 Camera 27797 has no neighbors
2022-12-25 12:01:24 Camera 29401 has no neighbors
2022-12-25 12:01:24 Camera 29923 has no neighbors
2022-12-25 12:01:24 Camera 21666 has no neighbors
2022-12-25 12:01:24 Camera 30698 has no neighbors
2022-12-25 12:01:24 Camera 32788 has no neighbors
2022-12-25 12:01:24 Camera 33471 has no neighbors
2022-12-25 12:01:24 Camera 33999 has no neighbors
2022-12-25 12:01:24 Camera 22217 has no neighbors
2022-12-25 12:01:24 Camera 33998 has no neighbors
2022-12-25 12:01:24 Camera 34944 has no neighbors
2022-12-25 12:01:24 Camera 35274 has no neighbors
2022-12-25 12:01:24 Camera 35500 has no neighbors
2022-12-25 12:01:24 Camera 35501 has no neighbors
2022-12-25 12:01:24 Camera 37080 has no neighbors
2022-12-25 12:01:24 Camera 37558 has no neighbors
2022-12-25 12:01:24 Camera 37627 has no neighbors
2022-12-25 12:01:24 Camera 29922 has no neighbors
2022-12-25 12:01:24 Camera 38007 has no neighbors
2022-12-25 12:01:24 Camera 38664 has no neighbors
2022-12-25 12:01:24 Camera 38701 has no neighbors
2022-12-25 12:01:24 Camera 38677 has no neighbors
2022-12-25 12:01:24 Camera 37569 has no neighbors
2022-12-25 12:01:24 Camera 39919 has no neighbors
2022-12-25 12:01:24 Camera 39967 has no neighbors
2022-12-25 12:01:24 Camera 40027 has no neighbors
2022-12-25 12:01:24 Camera 40594 has no neighbors
2022-12-25 12:01:24 Camera 41694 has no neighbors
2022-12-25 12:01:24 Camera 43127 has no neighbors
2022-12-25 12:01:24 Camera 44011 has no neighbors
2022-12-25 12:01:24 Camera 44065 has no neighbors
2022-12-25 12:01:24 Camera 38659 has no neighbors
2022-12-25 12:01:24 Camera 45612 has no neighbors
2022-12-25 12:01:24 Camera 46399 has no neighbors
2022-12-25 12:01:24 Camera 46601 has no neighbors
2022-12-25 12:01:24 Camera 38709 has no neighbors
2022-12-25 12:01:24 Camera 46791 has no neighbors
2022-12-25 12:01:24 Camera 46611 has no neighbors
2022-12-25 12:01:24 Camera 38708 has no neighbors
2022-12-25 12:01:24 Camera 46728 has no neighbors
2022-12-25 12:01:24 Camera 48103 has no neighbors
2022-12-25 12:01:24 Camera 48702 has no neighbors
2022-12-25 12:01:24 Camera 48780 has no neighbors
2022-12-25 12:01:24 Camera 46800 has no neighbors
2022-12-25 12:01:24 Camera 48797 has no neighbors
2022-12-25 12:01:24 Camera 49476 has no neighbors
2022-12-25 12:01:24 Camera 50189 has no neighbors
2022-12-25 12:01:24 Camera 50788 has no neighbors
2022-12-25 12:01:24 Camera 50848 has no neighbors
2022-12-25 12:01:24 Camera 50825 has no neighbors
2022-12-25 12:01:24 Camera 51074 has no neighbors
2022-12-25 12:01:24 Camera 51147 has no neighbors
2022-12-25 12:01:24 Camera 51229 has no neighbors
2022-12-25 12:01:24 Camera 46602 has no neighbors
2022-12-25 12:01:24 Camera 51575 has no neighbors
2022-12-25 12:01:24 Camera 51581 has no neighbors
2022-12-25 12:01:24 Camera 51099 has no neighbors
2022-12-25 12:01:24 Camera 51589 has no neighbors
2022-12-25 12:01:24 Camera 51685 has no neighbors
2022-12-25 12:01:24 Camera 51688 has no neighbors
2022-12-25 12:01:24 Camera 51712 has no neighbors
2022-12-25 12:01:24 avg neighbors before -> after filtering: 55.0101 -> 9.9775 (82% filtered out)
2022-12-25 12:01:24 limiting neighbors to 16 best...
2022-12-25 12:04:01 avg neighbors before -> after filtering: 9.98116 -> 2.08355 (8% filtered out)
2022-12-25 12:04:01 neighbors number min/1%/10%/median/90%/99%/max: 0, 1, 4, median=9, 16, 16, 16
2022-12-25 12:04:01 cameras info prepared in 516.736 s
2022-12-25 12:04:16 saved cameras info in 14.289
2022-12-25 12:04:16 Partitioning 40939 cameras...
2022-12-25 12:04:16 number of mini clusters: 3150
2022-12-25 12:04:16 1050 groups: avg_ref=38.9895 avg_neighb=55.9429 total_io=243%
2022-12-25 12:04:16 max_ref=39 max_neighb=126 max_total=165
2022-12-25 12:04:16 cameras partitioned in 0.098 s
2022-12-25 12:04:16 saved depth map partition in 0.009 sec
2022-12-25 12:04:19 loaded cameras info in 0.778
2022-12-25 12:04:19 loaded depth map partition in 0.001 sec
2022-12-25 12:04:19 already partitioned (38<=50 ref cameras, 36<=200 neighb cameras)
2022-12-25 12:04:19 group 1/1: preparing 74 cameras images...
2022-12-25 12:04:19 point cloud loaded in 0.18 s
2022-12-25 12:04:21 Found 2 GPUs in 0.009 sec (CUDA: 0.002 sec, OpenCL: 0.007 sec)
2022-12-25 12:04:22 Using device: NVIDIA GeForce RTX 3070 Laptop GPU, 40 compute units, free memory: 6815/8191 MB, compute capability 8.6
2022-12-25 12:04:22   driver/runtime CUDA: 12000/10010
2022-12-25 12:04:22   max work group size 1024
2022-12-25 12:04:22   max work item sizes [1024, 1024, 64]
2022-12-25 12:04:30 group 1/1: cameras images prepared in 10.547 s
2022-12-25 12:04:30 group 1/1: 74 x frame
2022-12-25 12:04:30 group 1/1: 74 x uint8
2022-12-25 12:04:30 group 1/1: expected peak VRAM usage: 88 MB (48 MB max alloc, 1000x1125 mipmap texture, 12 max neighbors)
2022-12-25 12:04:30 Found 2 GPUs in 0 sec (CUDA: 0 sec, OpenCL: 0 sec)
2022-12-25 12:04:30 Using device: NVIDIA GeForce RTX 3070 Laptop GPU, 40 compute units, free memory: 6815/8191 MB, compute capability 8.6
2022-12-25 12:04:30   driver/runtime CUDA: 12000/10010
2022-12-25 12:04:30   max work group size 1024
2022-12-25 12:04:30   max work item sizes [1024, 1024, 64]
2022-12-25 12:04:30 Using device 'NVIDIA GeForce RTX 3070 Laptop GPU' in concurrent. (2 times)
2022-12-25 12:04:30 Camera 51575 skipped (no neighbors)
2022-12-25 12:04:30 Camera 51589 skipped (no neighbors)
2022-12-25 12:04:30 [GPU 1] group 1/1: estimating depth map for 1/36 camera 48718 (9 neighbs)...
2022-12-25 12:04:30 [GPU 2] group 1/1: estimating depth map for 2/36 camera 48719 (5 neighbs)...
2022-12-25 12:04:30 [GPU 1] Camera 48718 samples after final filtering: 51% (2.05146 avg inliers) = 100% - 3% (not matched) - 16% (bad matched) - 2% (no neighbors) - 9% (no cost neighbors) - 13% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 7% (speckles filtering)
2022-12-25 12:04:30 [GPU 1] Camera 48718: level #3/3 (x8 downscale: 500x375, image blowup: 1000x750) done in 0.063 s = 24% propagation + 33% refinement + 25% filtering + 0% smoothing
2022-12-25 12:04:30 Peak VRAM usage updated: Camera 48718 (9 neihbs): 73 MB = 36 MB gpu_tmp_hypo_ni_cost (49%) + 12 MB gpu_tmp_normal (16%) + 8 MB gpu_neighbImages (12%) + 4 MB gpu_tmp_depth (5%) + 4 MB gpu_tmp_avg_cost (5%) + 2 MB gpu_tmp_cost_ni_inliers_masks (3%) + 1 MB gpu_mipmapNeighbImage (1%) + 0 MB gpu_neighbMasks (1%) + 0 MB gpu_refImage (1%) + 0 MB gpu_depth_map (1%)
2022-12-25 12:04:31 [GPU 1] group 1/1: estimating depth map for 3/36 camera 48720 (4 neighbs)...
2022-12-25 12:04:31 [GPU 2] Camera 48719 samples after final filtering: 54% (1.7128 avg inliers) = 100% - 3% (not matched) - 16% (bad matched) - 2% (no neighbors) - 7% (no cost neighbors) - 12% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 6% (speckles filtering)
2022-12-25 12:04:31 [GPU 2] Camera 48719: level #3/3 (x8 downscale: 500x375, image blowup: 1000x750) done in 0.046 s = 26% propagation + 24% refinement + 20% filtering + 0% smoothing
2022-12-25 12:04:31 [GPU 2] group 1/1: estimating depth map for 4/36 camera 48721 (6 neighbs)...
2022-12-25 12:04:31 [GPU 1] Camera 48720 samples after final filtering: 47% (1.7595 avg inliers) = 100% - 2% (not matched) - 22% (bad matched) - 3% (no neighbors) - 8% (no cost neighbors) - 11% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 7% (speckles filtering)
2022-12-25 12:04:31 [GPU 1] Camera 48720: level #3/3 (x8 downscale: 500x375, image blowup: 1000x750) done in 0.057 s = 32% propagation + 26% refinement + 21% filtering + 0% smoothing
2022-12-25 12:04:31 [GPU 1] group 1/1: estimating depth map for 5/36 camera 48722 (8 neighbs)...
2022-12-25 12:04:31 [GPU 2] Camera 48721 samples after final filtering: 52% (2.20245 avg inliers) = 100% - 2% (not matched) - 19% (bad matched) - 2% (no neighbors) - 7% (no cost neighbors) - 11% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 6% (speckles filtering)
2022-12-25 12:04:31 [GPU 2] Camera 48721: level #3/3 (x8 downscale: 500x375, image blowup: 1000x750) done in 0.043 s = 23% propagation + 26% refinement + 16% filtering + 0% smoothing
2022-12-25 12:04:31 [GPU 2] group 1/1: estimating depth map for 6/36 camera 48777 (4 neighbs)...
2022-12-25 12:04:31 [GPU 1] Camera 48722 samples after final filtering: 54% (2.33461 avg inliers) = 100% - 3% (not matched) - 15% (bad matched) - 1% (no neighbors) - 7% (no cost neighbors) - 13% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 7% (speckles filtering)

2
Feature Requests / Pause/play button for background processing
« on: December 15, 2022, 04:23:07 PM »
I often process big projects and they run in the background for a few days. Every time I want to pause processing and use my computer for something else, I first need to re-open the project to pause it. It would be so much easier if I caould just pause/resume background processing with one click without loading the project abck into the memory.

3
Hi,

It has actually been happening for the last few versions and sometimes is quite annoying. I have an integrated Intel UHD and Nvidia RTX 3070. So obviously I only want to use the Nvidia adapter and this is the only one switched on in the preferences. Hovewer, from time to time, quite randomly, I see in the console that Metashape uses both GPUs. Then I go to preferences and see both GPUs ticked. So I untick one and work on the project for several days and then it happens again.

Also, even when Intel GPU is switched on, it still seems to be used during depth maps generation alog with the NVIDIA GPU. Is it normal?

4
Feature Requests / Add UNDO support for accidently deselected selections
« on: February 01, 2022, 09:22:39 PM »
Sometimes I use the selection tools on a mesh, creating a quite complicated selection using SHIFT and CTRL keys. But if I accidently do not press either of the keys, all the selection gets lost and I need to start again. UNDO does not work in this case. Can you please change it? So next time I accidently deselect what I have spent 20 minutes on selecting, I will just undo deselection and continue selecting.

5
I use intelligent scissors a lot and I have a high DPI screen. So the points created with the tool are very small. It does not affect the process so much, but when I want to close the poligon, I actually need to zoom in a few times and it is still difficult to click exactly where the starting point is. If the points were bigger or it was possiible to click near the point to auto close, it would be so much easier.

Also, the auto close option should be available in the right click menu. So every time I wanted to close the selection created with the tool, I would just use the option auto-close and Metashape would just connect the last point with the first a straight line, even if they were far apart. So much easier.


6
I use the magic wand tool for maskig a lot. And since the beginning, to change the tolerance of the tool, I have to go to a separate tool/window, set the new value and come back to using maric wand. Can you please make the tolerance setting available every time the wand is used, so I can easily readjust the tolerance each time I need it?

7
I had 1.8.0 very briefly. I started processing one of my bigger model and it kept crashing. Never got to the stage of texturing. So I downgraded to 1.7.6 to be able to work on it.

8
Quite often, when processing textures, I end up with some low quality patches. It happens only because Metashape chooses a more distant photograph to use in that particular spot. Could you pleas add a tickbox to texture generation box that would prioritise the closest and therefore most detailed photos. It would save a lot of manual work I need to do with disabling the farthest photos at texture generating stage.

9
Bug Reports / Standard 1.8 crashes windows during mesh generation
« on: January 19, 2022, 11:26:57 PM »
Hi,

I tried to proces a mesh(from depth maps) under Standard 1.8 in a project that I had processed multiple times under earlier versions. The project has 3652 photos aligned. It crashed windows twice exactly at the same stage of the process.

2022-01-19 19:30:55 Marching cubes: part #3/7...
2022-01-19 19:31:11 Data preloaded in 16.411 s (1381 MB -> 4738 MB, 288.766 MB/s)
2022-01-19 19:31:55 cubes part marched in 32 mini parts: 1.56597e+06 avg cubes -> 547732 avg faces -> 158021 avg decimated faces = avg ratio x3.46619, done in 60.381 s (28% cubes IO + 2% sorting + 50% marching + 19% decimating + 0% saving)
2022-01-19 19:31:55 Marching cubes: part #4/7...
2022-01-19 19:32:14 Data preloaded in 18.668 s (1663 MB -> 5703 MB, 305.517 MB/s)


The full log from that session is attached as a ZIP file, because it is over 5MB. The log from previous session is exactly the same. Crash happens during part #4/7.

There is no trace of a problem in Windows event log and at both times I was not looking at the screen when it happened. I just came back after an hour and my computer has already rebooted.

So I unistalled 1.8 and re-installed 1.7.5 and run the same process. The problem did not occur.

I have Nvidia 3070 and 32GB of RAM. I have successfully used this setup for projects that have 45000+ photos under 1.7.5 and earlier vesrions. So it is not the matter of my computer or the number of photos. It is just some issue with version 1.8. I cannot be more precise, because there is no trace what went wrong.

10
General / Re: Processing a massive underwater photoset without GPS
« on: October 23, 2021, 04:26:33 PM »
Thank you guys for your lengthy responses.

I have been doind underwater photogrammetry for several years now and processing 20 000 - 30 000 photos in one chunk is not new to me. I know how generic preselection works and how to scan my underwater sites. I already have my workflows for my very precise underwater work and I really know what I am doing with almost all the options I use... Apart from the Reference preselection SEQUENTIAL and ESTIMATED that are not really described in detail in the manual. Furthermore, the way these work have changed over the last few years, so I really need information from someone who is sure.

The difference between this project and my previous big projects is that I will probably end up with around 120 000 photos and I want to find an optimal way before I just click "Generic Preselection" and "Reference preselection" and then wait for a week to see what happens. Also, gathering photos will take a while and I need to be able to quickly do some preview alignments to double check the coverage.

So my questions are very specific and technical and only about the alignment parameters. Let me rephrase them then:

Does anyone know how Reference Preselection Sequential and Estimated work without GPS and how they work in combination with Generic preselection?
Which one is applied first?

If Generic is as second, then does it take into consideration pairs already found by Reference preselection or does it do its thing to all photos anyway?
If does take into consideration the pairs found by reference preselection, what happens then? Does it only use generic for photos without pairs?

I really need to understand the algorytms behind each of these options and their combination. Anyone?

11
General / Processing a massive underwater photoset without GPS
« on: October 23, 2021, 09:57:39 AM »
Hi,

I am processing a massive underwater photoset (so far 50 000 photos) and I keep taking 10 000 photos every day. There is no GPS data and I am looking for a solution to speed up the matching part of the process. Therefore, I need to understand how each of the following work.

1. Reference preselection set to sequential + generic preselection. What is it going to do? Will the program do the sequential preselection first and only the photos that have no pair will have generic preselection applied? Or will it do the generic preselection for all photos, finds all matches and then also add sequential preselection on top to find even more matches and actually extend the length of the process?

2. Reference preselection set to seqential while every second photo disabled, so only half of the photos are being aligned. Provided that they will align somehow... Then I enable the other half of the photos and what are my options then? Sequential again? Or perhaps Estimated? With generic preselection on or off?

Any other ideas how to match only the photos that should be matched?

12
General / Re: Agisoft Metashape 1.7.0 pre-release
« on: January 30, 2021, 08:55:00 PM »
In the changelog I found this a few build back: "Added Save camera track option for Sketchfab uploads." But for some reason I do not see this option under Metashape Standard 1.7.1.

Anyway, I always save a 3d file manually and upload it to Sketchfab. How can I then save and .fbx file with animation, so sketchfab can use the camera track as animation?

13
Bug Reports / 1.7.1 Mesh colour disappears when closing holes
« on: January 29, 2021, 12:07:11 AM »
Now when I now close holes on a coloured mesh, the colours disapear and I have to reprocess them again. It used to close the hole and the new faces had colours from neighbourhood triangles. But now all colours are gone and I need to colorize again.

14
Bug Reports / Re: Avi file wrong duration when exporting animation in 4K
« on: January 28, 2021, 08:56:38 PM »
Update

The noise only happens when I process some models, only those with many detailed 4096px textures, like buildings. When the camera comes closer to one section of a model and the texture becomes bigger, the noise disappears.

I have now ticked "Enable mipmap generation" under Advanced preferences and there is no more noise in Full HD video, but everything seems less detailed. In 4K also no more noise (there actually was some small noise before) and also everything bit less detailed, but acceptable.


15
Bug Reports / Re: Avi file wrong duration when exporting animation in 4K
« on: January 28, 2021, 06:16:32 PM »
All of them are from a 2-minute animation and are 2 minutes long when played under windows built in player.

1. Full HD 60fps is 4.6 GB (seen as 2 sec long)
2. Full HD 30fps is 2.3 GB (seen as 16 sec long)
3. 4K 60ps is 15.2 GB (seen as 1 sec long)

I have run several tests and the display length of the videos is always the same.

I have also noticed that if I now render a FULL HD video on my 4k system, eaach frame is poorly downscaled, so I get weird noise on my full HD videos. Rendering in 4k gives much better result, but some small noise is still there, like there was incorrect anti-aliasing setting.

I rendered the same video a year ago in Full HD 60fps and there was no problem with it. The displayed length is 2 minutes and the file size is 3.39 GB. There is no noise on the old video, only on the new ones.

Pages: [1] 2 3