Camera configuration display on first load is incorrect

[mwestphal]

Describe the bug
When loading a file with --camera-position=1,1,1 --verbose, f3d displays something like:

Camera position: 0.776126, -0.438658, 24.556
Camera focal point: 0.776126, -0.438658, 0
Camera view up: 0, 1, 0
Camera view angle: 17.3889

However this information is BEFORE the camera configuration takes place in the app, so it does not correspond to what is being displayed and the cli options

Indeed, using print_scene_info interactively display another (correct) information:

Camera position: 1, 1, 1
Camera focal point: 0.776126, -0.438658, 0
Camera view up: -0.17794, 0.580166, -0.794824
Camera view angle: 17.3889

To Reproduce
Steps to reproduce the behavior:

1. Open the file using f3d --no-config --camera-position=1,1,1 --verbose cow.vtp
2. read the log, it is incorrect
3. print_scene_info
4. read the log, it is correct

Expected behavior
F3D should display the correct information right away

System Information:

• OS: Any
• GPU and GPU driver: Ant

F3D Information
Paste the content of f3d --version or f3d-console.exe --version on Windows: 3.5.0

Additional context
I took a quick look and there is no simple fix for this.

The callstack is as follow:

scene::add
scene::Load
scene::Internals::DisplayAllInfo
window::PrintSceneDescription
vtkF3DRender::GetSceneDescription

There is no way to control this display from f3d application and this display makes sense from a libf3d pov.

A possible fix (to be discussed) could be:

• Add a libf3d option to control the behavior of display the scene description on load
• Add an API to recover or to display the scene description
• Use the option and the API in f3d application to control the temporality of the displays

[srividya-77]

Hi, I’d like to try working on this issue.

I can reproduce the behavior with:
f3d --no-config --camera-position=1,1,1 --verbose cow.vtp (F3D 3.5.0).

The initial camera description printed on load does not match the CLI camera position.

Calling print_scene_info afterwards shows the correct camera configuration, as described in the issue.

I’ve started looking at the callstack you mentioned (scene::add → scene::Load → scene::Internals::DisplayAllInfo → window::PrintSceneDescription → vtkF3DRender::GetSceneDescription) to understand when the scene description is printed relative to when CLI camera options are applied.

Before I go further, I’d like to ask a couple of questions:

Is the preferred solution to add a libf3d option/API so the application can control when the scene description is displayed on load (as suggested in the issue)?

Or would a smaller change to the call order / conditional logging be acceptable as a first step?

If this aligns with what you have in mind, could you please assign the issue to me? I’m happy to iterate based on your feedback and follow the contributing guidelines.

[mwestphal]

HI @srividya-77

First and foremost, pelase read the AI policy and agree to it, thanks.
https://f3d.app/dev/AI_POLICY

[srividya-77]

Hi, thanks for the link. I’ve read the AI policy and I agree to follow it when contributing to F3D. As I’m a beginner, I sometimes use AI to support my research and learning, but I always verify and understand my contributions myself.

…

On Fri, 17 Jul 2026 at 20:46, Mathieu Westphal ***@***.***> wrote: *mwestphal* left a comment (f3d-app/f3d#3374) <#3374 (comment)> HI @srividya-77 <https://github.com/srividya-77> First and foremost, pelase read the AI policy and agree to it, thanks. https://f3d.app/dev/AI_POLICY — Reply to this email directly, view it on GitHub <#3374?email_source=notifications&email_token=BPGLCXBQIZFCJQL6CIJBC635FI7M3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGQ3TCNRUGE22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5004716415>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPGLCXBSL5EMXA7IO5ASEMT5FI7M3AVCNFSNUABFKJSXA33TNF2G64TZHMZDIMJRG44DMNZTHNEXG43VMU5TIOBYGEYDOMJTGI42C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BPGLCXGCMD3F66CCHFYEKML5FI7M3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGQ3TCNRUGE22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BPGLCXE643JLGHDOBMLMSMD5FI7M3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGQ3TCNRUGE22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[mwestphal]

Hi, thanks for the link. I’ve read the AI policy and I agree to follow it
when contributing to F3D. As I’m a beginner, I sometimes use AI to support
my research and learning, but I always verify and understand my
contributions myself.
…

Thanks for checking.

Please note this issue should be discussed first with other maintainers (and you already started to ask questions, perfect!)
We usually use discord for such discussion, would that be possible ?
https://discord.f3d.app

If not, we can stay here.

[srividya-77]

Thanks for assigning the issue.Yes, I can join the Discord and continue the discussion there.I’ll start exploring the relevant code to understand the current behavior.

[mwestphal]

Unassigned after discussion on discord.