Dolphin, the GameCube and Wii emulator - Forums

Full Version: Improving the player polygons and LOD
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
thanks for the update!
Sounds good, we are really lucky you are so clever Smile I'm still not sure which alternative for the centre face-offs is better, whether its the 1st one, with the extra zoom or the cleaner one with the top-down right from the beginning. What would you prefer? I kinda like both for the different reasons Smile

I think we just make the final decision after we have all the cams set and functional.
Could you estimate what you want each timer to be to prevent zooming at each zone?
Let me think...

In the real world, these close-up camera cuts are quite short, around 2 seconds. And don't occur that often. So we' got 5 zones, right? So I think every zone should be "OFF" around 2-3 minutes before can trigger again? It might need some testing tho.

edit: actually it might be even longer before the next trigger. Just to make sure there is at least 1-2 minutes regular side view before these close-ups/zooms 
So should each zone be locked out for the same amount of time, but on individual timers? Plus a universal timer to prevent two zones triggering back-to-back?
I think that's how it should work, as you described it. It will be interesting to really see it, because it is the puck that really triggers the zone, right? And as it's driven by the physics, you never know where and how long the puck will be.

There might be instances when the play is on one side (thus in one or 2 zones) for quite a long time. So ya, I'm curious to see that in action.
But man, how deep we got with the game! Love it Smile
One more day... still need to find the values, label the things that can be changed, etc. Also haven't looked into custom camera positions yet.

If you want to take another crack at the debugger to help find zone values, you just need some extra steps from what we did before.

Load practice game, pause game.
Go to the code tab, in the upper left address box put in 80bd04b4
Click to the left of 80bd04b4 in right panel to make a red circle appear (breakpoint).
Click play. The game should pause again instantly and 80bd04b4 should be highlighted.
View -> Registers. In registers tab copy what's in the box to the right of r3.
We now have the memory location of the puck position, so go to the memory tab and paste it in the upper right box. Add 4 to the end (it'll proabbly be a 0 you change to 4).
When you pause the game, the memory tab will update the values. The left side is the address (the one you pasted will be there). The middle is the hexadecimal we use for codes. And if you click on the float button, the right side will be what the float value is of the hex in the middle.

Don't do this in DolphinQT. Use DolphinWX (might just be Dolphin.exe in ishiiruka's build).
Thanks for the news!
I was testing some other sports games yesterday, looking for how they handle the broadcast camera. Not just in hockey, but also in Fifa and PES. So Fifa has a very basic camera. Basically, just side view that pans left and right. Same stuff as in their latest hockey game.
PES from Konami offers very few very basic close-ups/ zooms. But still very trivial, nit realistic nor organic.
So if everything goes as planned, our broadcast/side camera will be the most advanced gameplay camera system in any sports video game, ever made Wink

I'll try to dive in the debugger again, if possible. But I'm at work today, just on notebook and a lot of people around, so it won't be easy to keep needed focus for something so complicated (for me) as this.
Will do my best Smile
https://imgur.com/a/g3GxyKd

3 + 4 will have a different value for you.  Game should be paused in practice mode for 1 and 2. Then Play, it'll auto-pause itself and you can do 3 + 4.  After you do 4, remove the breakpoint (click red dot).
Use with $Enhanced Zoom From Position Check. Also the Parametric Position one. Those two should be unchanged.

I noticed if the puck is flying across the screen, the camera tracking won't keep up with it well. Either need to undo zoom at that time or increase tracking. I'll look at the camera values next if this code is bug free.
$Enhanced Zoom Camera Pos TEST
C284E578 00000006
389B0070 80A2FFC0
2C050000 40A10020
3CC08000 80A61870
90A40000 80A61874
90A40004 80A61878
90A40008 00000000
04001870 c5354000 //In/out
04001874 449c4000 //Up/Down
04001878 44fa0000 //Rotate around puck

Hmm the screen goes black sometimes, but other than that bug, how is it? Is the cutting between sideview and custom position okay? If you edit the values at the bottom, can you get the camera where you want it? Those labels are just guesses, it's not easy to get the camera where you want it.