That’s a good idea indeed.
But the parameter ’50’ should be driven by the mouse-wheel input from the user.
How do we link the FOV parameter to the mouse-wheel input?
Thanks for the follow-up.
Pd: The attached is an idea that does not work =(
Pd: I got this code from the web (codeFOV.jpg)
Could you explain where to add these lines? Can I call/execute it with the puzzles somehow?
Attachments:
You must be
logged in to view attached files.