Experienced Forum User, Published Author, Experienced player
(626)
Joined: 4/5/2014
Posts: 459
JosJuice wrote:
I really wish we had a better description of the change than that one I wrote up here... Unfortunately the change never made it into a Dolphin progress report. Fog, do you have anything to add to what I said?
Not really, that seems to have summed up everything.
Porting the VFW stuff into 5.0 would not work straight on, as there are some additional changes which need to be accounted for.
Perhaps I can revisit VFW to see what can be done. My most recent encode of 007 Agent Under Fire originally used VFW, and I found that adjusting the framerate to 59.94 FPS made it sync up. Perhaps there is something missing in the original implementation?
Experienced Forum User, Published Author, Experienced player
(626)
Joined: 4/5/2014
Posts: 459
This is the screenshot I'm getting at the recommended input count, is this correct?
If not, could you double check numbers and/or possibly provide what the screenshot should be?
Experienced Forum User, Published Author, Experienced player
(626)
Joined: 4/5/2014
Posts: 459
CoolKirby wrote:
I posted this earlier, but I timed it badly and it probably wasn't noticed:
TAS input window doesn't work for about half of Wii games, including Mario Party 8. When the main menu or a similar screen is reached, the window will press and hold every button on the Wiimote, usually preventing any progress in the game. Closing the window is the only way to stop it. This prevents precise TAS input for these games.
Some games like Mario Party 9 work fine though, for whatever reason. This appears to have been a problem for as long as Wiimote TAS input has been around.
What version of Dolphin are you using? Have you tried the latest version?
Experienced Forum User, Published Author, Experienced player
(626)
Joined: 4/5/2014
Posts: 459
Tangent wrote:
I posted something in the thread regarding the rule change a while back that's relevant here. If this is aiming for fastest time, it doesn't achieve it. The celebration for holes in one are just under 10 seconds long. It takes about 3-4 seconds to take a shot plus 3-4 seconds for the lesser Albatross or whatever fanfare. Time could be saved by adding a stroke to those holes. Since this is (presumably) under consideration for the Vault, there's a rule clarification/exception needed, unless the goal really is lowest time for these kinds of things.
A hole in one animation takes 9 seconds. The animation after each shot made is roughly 4 seconds. Multiply that by two, you get 8 seconds. If you take into account additional wind up time and travel time, it's actually not faster to take two shots on a par 3 course in this scenario.
Experienced Forum User, Published Author, Experienced player
(626)
Joined: 4/5/2014
Posts: 459
MUGG wrote:
I started recording frames while in a screen transition (white screen) and the avi was messed up. Every 4th frame or so, the frame was messed up.
I'm thinking the frames that have been messed up are lag frames (where screen doesn't update). And the point I started recording - the screen transition - is where the game also doesn't update screen. Needs looking into, maybe.
XviD? Are you using a video editor to combine the audio and video?
Experienced Forum User, Published Author, Experienced player
(626)
Joined: 4/5/2014
Posts: 459
theruseman wrote:
I have tried that, but I'm running into an issue where it is extremely choppy for some segments. (Around 3 frames a second). I can post a vid if that will help with troubleshooting.
You can also try to dump with XviD to see if that works for you.
Experienced Forum User, Published Author, Experienced player
(626)
Joined: 4/5/2014
Posts: 459
theruseman wrote:
Pac-Man world 2.
Dolphin does play the lag frames when I'm dumping the video, but when I play it back there arent any lag frames. Because of that I think its something in the codec settings
Try using Lagarith Codec instead if you're looking to dump a lossless file.
Why does the rule apply only to sport game franchises and not all game franchises?
Maybe rather than have a strict rule that's blindly applied to everything, it should be considered on a franchise-by-franchise basis (and perhaps even game-by-game basis)? Clear rules are nice, but not if some games get unfairly hit by them.
Sport franchises usually only have variable rosters, and minor variances in mechanics. Other franchises have many more variances (story, maps, mechanics, etc.).
This is the screenshot I'm getting at the recommended input count, is this correct?
If not, could you double check numbers and/or possibly provide what the screenshot should be?
