I switched to the utmost excellent 2022.2.11 which swapped for CM 2.9.5 which broke upvector, so yeah, that regression is still not fixed, reverting back to 2.8.6
What do you mean “broke upvector”? Can you be more specific?
the one you already reproduced a few month back
when you do this
and this
if spiderman is upside down then the camera won’t work right and keeps gimbal locking since 289
worked perfect in 286 so the camera up was the reference up
Thanks but I need more context than this. Can you show the inspector for the virtual camera to which this is attached? If you have a link to the issue from “a few months back” that would be helpful.
Sure, I found the bug# it’s IN-30920 and the project is included.
1 Like
Thanks. I found this issue, downloaded the project, followed the repro steps, but am unable to repro any problem.
Note: the repro steps in IN-30920 are extremely unclear. You say “select a creature”. You mean click on it in the Hierarchy window? Nothing happens. Nothing is expected to happen. Do you mean to select it in some other way?
Looking at the scene, I see that the vcam is a passive one (do nothing in Aim and Body) so overriding the up is not expected to have any effect - except on a camera blend. And blending is not part of the repro steps. Can you provide me with more info about this problem, or a clearer repro case?
in the game mouse click the creature either by press CTRL and then using the mouse cursor to click on it or center your view on the creature.
blending happens programmatically when you click the creature in the game
What creature? Where is the creature? What do I click on? Please give clear instructions.
Everything sent via the bug reporter, this is confidential, please remove the image.
My apologies. Deleted. Please DM me with answers to my questions.
1 Like
Thanks. Will do.