Recap 2025 poor performance

[TanguyNed]

Hello,

I have recently updated Recap to 2025 from 2023.1. That update was forced by Autodesk and I didn't have a choice if I wanted to continue using the program.

To my sadness the display performance has taken a huge hit. I've made two videos, one with Recap 2023.1 (glad I made this one while I could still use it), one with Recap 2025:

Recap 2023.1 

Recap 2025 

There are two issues that should be more or less apparent:

1) the framerate with Recap 2025 is much lower (30-40% lower per my rough estimation counting frames from the videos),

2) see me moving the cursor and nothing is happening ? That's because after using orbit or pan, there's a freeze. So I can't quickly "chain" two orbits, I have to wait. 

I've tried the usual: updating drivers, messing around with settings, etc. There's one thing that has an effect, and that's changing the point size. The bigger, the better, at 5 the orbit-freeze issue is reduced, at 10 it's gone completely. No effect on the framerate however.

So, is anyone also affected by this? I've spent a lot of time testing (and making this post), would a developer be so kind to give some of their and have a look?

Thanks

My specs:

Windows 10

Intel(R) Core(TM) i9-9940X CPU @ 3.30GHz

RTX 2080 Ti
64.0 Go RAM

SSD Samsung 970 PRO 1TB

[TanguyNed]

No answer? I've taken the liberty to try my luck here (I hope it's not rude to link to another forum), and it seems that I'm not the only one having problems with Recap 2025 (and 2024).

So, are the devs aware of this? Any communication on their part would be appreciated.

[Pointdump]

Hi Tanguy,
Have you started a support ticket with Autodesk? If they don't know about it they can't fix it.
Dave

[TanguyNed]

@Pointdump 

I'm using the free version of the software, and AutoDesk doesn’t provide technical support with free software.

So how are free users to report bugs?

Besides, posting on the forum has more reach, and developers seem to have a presence (one of them answered one of my posts not long ago).

[barmanr]

Hi @TanguyNed ,

Sorry you're facing this issue.

Would it be possible to share your dataset with us for validation? If Yes, I will PM you an Autodesk confidential link.

I have tried some large datasets and I am unable to reproduce the issue so far. I am not sure if this could be hardware / machine related yet. Since 2023 version there have been various component updates to meet security standards as well.

Thanking You.

Warmest Regards,

[TanguyNed]

Thank you for your answer. I have the issue with every dataset, but here is an example:

Recap example.7z  (4.9 GB, 308 million points, 23 scans).

How bad it is depends on the pointsize (so try putting it at 1), the total number of points, but also the number of scans (something I just noticed).

I subjectively compared the lag on a few projects to give you an idea (point size 2):

- 19M points, 1 scan (unstructured): barely perceptible

- 247M points, 1 scan (unstructured): barely perceptible

- 511M points, 1 scan (unstructured): barely perceptible

- 72M points, 5 scans (structured): barely perceptible

- 308M points, 23 scans (structured): annoying to work with

- 248M points, 58 scans (structured): annoying to work with

- anything with more scans : too frustrating to work with

At point size 1, the lag becomes very perceptible for all of the above.

[Pointdump]

Now THAT is a dataset!

Dave

[TanguyNed]

@Pointdump In what sense? From my point of view this is a fairly standard one. Rather small.

[barmanr]

Hi @TanguyNed ,

Thanks for the dataset and a detailed overview of your test cases. We'll take a look and validate the same.

Thanking You.

Warmest Regards,