Hey all,
This thread has been closed as this is currently functioning as designed by The Sims team.
If you feel this was in error, please create a new thread here with as much information as you can provide. Thank you!
From the original post, which has incorrectly been marked as "Sovled", and edited to add additional ways that this bug has yet to be fixed:
When having sims pose for photos using the tripod, we used to be able to move the camera around using the WASD keys and Q + E to freely move the camera around the composed scene. It would work like we were moving the camera around when we press the TAB key in-game - WASD would allow us to move closer and farther away (not by zooming, by moving the camera forward and backward in the scene), and essentially see the subject in almost 360 degrees.
In addition, Q + E would bring the camera up and down, like the rising and falling of an elevator.
Now, six months after it was broken, the W + S keys are only zooming in and out, A + D pan the camera on its' stationary east-west axis, and Q + E is panning the camera on its' stationary north-south axis.
The patch released in 12/2019 completely removed the functionality of moving fully on a horizon and being able to get shots at "eye-level" regardless of where the sims are. For example, taking profile pictures of toddlers is now much more difficult (if even possible at all) as the camera can only "pan down" at them, shooting their photo from above.
The above photo was taken in the glorious few months that this feature actually worked. Using Q+E I was able to move the camera down to the eye level of the short tiny toddler and snap a picture.
Essentially, removing the features advertised in the Twitch play below.
https://clips.twitch.tv/StylishSpinelessHedgehogPunchTrees
Why am I explaining this in extra-deep detail and re-iterating points made before? Because it seems our reports in the past have gone on deafened ears for the past 6mos and I truly am at a loss for what else to do to get this fixed.
@xjfo411xwonderfully said!
This is such a baffling bug because it was a feature that was working. If it was some misunderstanding about a pack's functionality that would be one thing. However, we had the feature for a while. The only thing I can think of is that it had some sort of deep error that would take a while to correct, so they are quietly hoping we forget about it. The "Q and E" patch notes from the June patch almost felt like they were trying to get one over on us. There is no way they really thought that was solving anything.
The fact that they haven't even said: "Hey, we know that a core feature of a game pack is busted, it is just taking a while to fix" makes me think that they aren't going to fix it. I hope that they know that there are enough people who care about that feature to invest the time into fixing it.
