CloudCompare forum

Issues, bugs, etc. • Re: Shortcut conflict with multiple “Create” actions after restarting CloudCompare

2026-09-23T17:07:58+00:00

Hi, I created a github issue so as to give more visibility to the other CloudCompare's developers: https://github.com/CloudCompare/CloudCo ... ssues/2411

Statistics: Posted by daniel — Wed Sep 23, 2026 5:07 pm

Issues, bugs, etc. • Shortcut conflict with multiple “Create” actions after restarting CloudCompare

2026-09-23T01:35:16+00:00

I frequently use the Plane Create function.

In the Shortcut Settings, I found three different actions named “Create”, and the third one corresponds to Plane Create.

I assigned Ctrl+1 to this action, and it works correctly during the current session. However, after restarting CloudCompare, the shortcuts for all three “Create” actions become merged into the same shortcut.

As a result, the shortcut conflicts with the other “Create” actions and can no longer be used properly.

I have attached a video showing the issue.
https://youtu.be/ENWUnjwrjsY
I am currently using:

CloudCompare v2.14 beta (Sep 17, 2026)

As always, I really appreciate the work of all the developers and contributors to CloudCompare.

I would greatly appreciate it if this issue could be fixed.

Thank you!

Statistics: Posted by Jay_Ki — Wed Sep 23, 2026 1:35 am

Issues, bugs, etc. • Re: 2.14 beta can't read .glb file.

2026-09-03T13:22:33+00:00

Ran into the same thing on 2.14. Until GLB support is back, the workaround that costs the least effort: convert the GLB to OBJ first and open that instead. furnimesh.com/convert/glb-to-obj does it in the browser, no install, and the scale came through correctly for me, so measurements in CloudCompare stay trustworthy. PLY via a converter also works if you need vertex colors, but for a textured mesh the OBJ route was the cleaner import.

Statistics: Posted by JSNM — Thu Sep 03, 2026 1:22 pm

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-08-28T08:15:35+00:00

Yes, it's a pity that it doesn't work out of the box... It would be good to understand the issue, but codec issues are very hard to debug.

Statistics: Posted by daniel — Fri Aug 28, 2026 8:15 am

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-08-24T13:41:23+00:00

Yea, i tought it could be something with codecs, it's always something with them :D
like i said, frames export works, so there is a way around it: merge frames as image sequence in third party software.
but it still takes a lot of additional time and disk space to merge, for example, 6 sequences in one orbit
https://www.youtube.com/watch?v=a63xHMR9j6Y

Statistics: Posted by I&R_Digital — Mon Aug 24, 2026 1:41 pm

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-08-16T20:25:17+00:00

Yes, I guess it's a codec issue then. And sadly there are many codecs, and it's hard to know what they like or don't like. Do you have this issue with all codecs/formats?

Statistics: Posted by daniel — Sun Aug 16, 2026 8:25 pm

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-08-12T10:31:36+00:00

you mean like not full screen? i did it just now, same message.
i did it provisionally, maybe there is some methodology?
i tried other options than super resolution, only one available is zoom, and it is the same with it
like i said, frames are exported in selected folder, preview works, just Render is the issue

Statistics: Posted by I&R_Digital — Wed Aug 12, 2026 10:31 am

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-08-10T17:10:43+00:00

And have you tried to change the window size? (by actually reducing the CloudCompare window size)

Statistics: Posted by daniel — Mon Aug 10, 2026 5:10 pm

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-08-10T11:31:59+00:00

we didn't tried that before, but it is same issue

Statistics: Posted by I&R_Digital — Mon Aug 10, 2026 11:31 am

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-08-06T15:41:08+00:00

Does it work better if you try with a output path that has no space/blank character?

Statistics: Posted by daniel — Thu Aug 06, 2026 3:41 pm

Issues, bugs, etc. • Re: FAILED TO OPEN FILE FOR OUTPUT: INVALID VIDEO SIZE

2026-07-31T12:38:27+00:00

hi, I would also like to bump this, we get same message.

Preview is working ok, Export frames is working also, but when you click Render, that message apperas
we tried with MOV and other video formats, same message.

frames can be exported and processed in third party software, but it would be much easier if Render work

Statistics: Posted by I&R_Digital — Fri Jul 31, 2026 12:38 pm

Issues, bugs, etc. • Re: Points have RBG color on PC but not mac

2026-06-12T12:54:41+00:00

Which file type are you loading?

Statistics: Posted by daniel — Fri Jun 12, 2026 12:54 pm

Issues, bugs, etc. • Re: Sensor transformation is wrong for registered PTX files

2026-06-09T00:38:07+00:00

Hi Daniel, I think the point is that the transformation matrix is not being applied to the sensor when importing a PTX file, but looking at various recent Register360 exports, it appears that they all have 1s & 0s in rows 3-7. This seems to be different export behaviour compared to other software.

Statistics: Posted by framed — Tue Jun 09, 2026 12:38 am

Issues, bugs, etc. • Points have RBG color on PC but not mac

2026-06-02T18:23:30+00:00

I installed CC on both a mac and pc. When I load the same .las file on the Mac (v2.14) the points are all white, while on the PC they are colorized by the image files. Is there off about the Mac version? I have RGB selected.

Statistics: Posted by jenyquist — Tue Jun 02, 2026 6:23 pm

Issues, bugs, etc. • Re: Sensor transformation is wrong for registered PTX files

2026-05-29T14:04:18+00:00

So referring to the code and to https://paulbourke.net/dataformats/ptx/, the sensor position and orientation is stored in rows 3-6 (row 3 is the sensor center, and the next 3 rows are the X, Y and Z vectors).

Rows 7-10 store the global transformation matrix that applies to the points (and I would assume to the sensor as well). At least that's what I could see in samples files such as some files found on http://www.libe57.org/data.html or Paul Bourke's site.

ptx_header.jpg

So in your case, I would expect row 3 to equal the 3 first values of row 10, and rows 4 to 6 equal the 3 first values of rows 7 to 9 (or something totally different depending on how the cloud was registered). Otherwise, this means that the points have been registered, but there's no 'sensor' associated.

Statistics: Posted by daniel — Fri May 29, 2026 2:04 pm