Quote:
Originally Posted by swoboda
Whoa. Wish I knew this last year! I manually reset all my custom camera angles for each Stadium after each patch. Did not enjoy that
|
Here's a little more... Each stadium's camera views are stored in a 6kb file. Example: Wrigley Field file is called "wrigley_field.ootp3d". This is how I first made backups of my views. This is time consuming as you have to do each one at a time. Doing the whole folder is easier and faster but won't work if they make actual changes to a 3d model. IE in the homeplate circle at Wrigley in v19 the grass in front of the plate comes to a point instead of a full circle. If it had been fixed in a patch you would want the new stadium file and lose your views. However..
If they make a change to the 3d stadium model in a patch there is a way around this, at least I think it would work. Each stadium has a folder under models (I think?) and in that folder is a 6kb file that holds your camera views. I think you could copy that file over the file in the new patch stadium folder. It's a bit time consuming though as you have to do each stadium one at a time. But with both your backup folder and "new patch" stadium folder open it would be better than rebuilding everything. Of course I'd backup the new folder before trying this.
Quote:
Originally Posted by eriqjaffe
Honestly, I would love to have a handful of "stock" camera angles that I could apply. OOTP already knows where the bases and plate are in 3D space, it's just a matter of a bit of math to have default cameras at x/y/z coordinates, n feet above ground level aimed at r/s angles. Heck, it's not even something that has to be calculated in real-time, it would just essentially be part of the existing 3d grid.
At the very least, I'd love to have the ability to copy and paste cameras between parks, similar to how we can currently copy and paste 2d coordinates, so I don't have to fiddle with them as much every time I make a new park.
|
I've thought the same about using the diamond as a base for a default set of at least a 1b, 3b, CF behind P in addition to the already default one. After that I think because of the various shapes, heights, distance from diamond others would be hard to implement on a global basis. With this in mind I think copy\paste park to park would be hard. I'd love to be wrong and have Matt and Markus find a way.