Speed is a function of total frames, and the playback frame rate (frames per second).
If you preview a flythrough with OpenGL, there is NO control over the frames per second as there is when you save the movie (either from OpenGL or render).
With the Path dialog, you can set the number of frames between cameras. With the compression options for saving the movie from the fly-through dialog, you can change the frames per second.
So... if you have frames/second at 25 and 25 frames between cameras, then however far apart the cameras are ... you'll move between them in 1 second.
There are various standard frame rates for incorporating a movie into a video editing timeline - e.g., 24 for film, 25 I think for PAL, 29.96 for NTSC, etc. But, if the target it just for computer viewing (e.g., with QuickTime), none of that matters. A frame rate as low as 15 fps can be adequate, and allow both faster rendering (fewer frames) and smaller files (again, fewer frames).
So... you have to play with both. ArchiCAD's fly-through technology is quite primitive relative to all competitors as you have only the one parameter - frames between cameras on a path ... rather than being able to specify the number of frames between each pair of cameras (= along each path segment).
Thus... if you want a very slow motion between two cameras and then faster between the next two... there is no control in AC. Instead, you have to fake it by placing additional cameras along the first path to force the generation of additional frames. (Or you can generate multiple movie segments with different paths - e.g., from the first to second camera as one movie, from a copy of the second camera to the third as another path, with different frame count - and then combine them all later.)
Hope that helps.
Cheers,
Karl
One of the forum moderators
AC 28 USA and earlier • macOS Sequoia 15.2, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB