I need to export my input to a text file (or MS Excel file).
The format should be similar to the spreadsheet which look like that:
Frame - Buttons (pressed) - IR coordinates (nothing else needed).
Dolphin shows all that if I enable "Show frame counter" and "Show input display", but I can't write down on a list ALL the needed input.
Yet Another Input File Editor instead of IR coordinates shows Data and a long set of address code like in Cheat Engine. Please help!
.dtm is here: http://tasvideos.org/userfiles/info/34546688997717013
TASing is like making a film: only the best takes are shown in the final movie.
The biggest news of the month regarding Wii emulation has nothing to do with Dolphin. The vehicle for many of our hardware tests and much, much more, The Homebrew Channel, has gone open source. In its heyday, it was stuffed to the brim with anti-reverse engineering code to prevent nefarious entities from selling the free program. Unfortunately, some of those tricks were also designed to prevent Dolphin from running it. This isn't due to a dislike of Dolphin; in recent years, we've even been tipped off to what we'd need to do to get past the anti-Dolphin checks.
On the 22nd of November, Marcan of Hackmii.com released the Homebrew Channel as an open source application, removed the anti-emulation hooks, and fixed a few bugs in Dolphin so that it could run properly! Nearly a decade after its inception, the homebrew channel is finally emulated! Admittedly, it has very little use for Dolphin, but, it is extremely cool to have. Some packed Wii homebrew elfs (such as Not64, openTTD) will only run in Dolphin from the homebrew channel currently. This is due to Dolphin being unable to detect them as Wii homebrew.
I know the anti-emulation hooks were removed, but how did it work and why did it worked? Just curious, since it seems like there's something that makes the emulator noticeablely different enough from the console to be detectable.
Sorry if I ask because this must have been asked before or somewhere else, but what does the code for debug mode on Dolphin look like on Windows? I can't find any useful stuff on the internet.
Sorry if I ask because this must have been asked before or somewhere else, but what does the code for debug mode on Dolphin look like on Windows? I can't find any useful stuff on the internet.
If you mean the debug mode you get by running Dolphin with a /d flag, most of the code is here: https://github.com/dolphin-emu/dolphin/tree/master/Source/Core/DolphinWX/Debugger
EDIT: Or are you asking how to launch the debug mode on Windows? If so, the answer is to write the following in cmd when the folder is set to the folder that Dolphin is in: Dolphin.exe /d
Sorry if I ask because this must have been asked before or somewhere else, but what does the code for debug mode on Dolphin look like on Windows? I can't find any useful stuff on the internet.
If you mean the debug mode you get by running Dolphin with a /d flag, most of the code is here: https://github.com/dolphin-emu/dolphin/tree/master/Source/Core/DolphinWX/Debugger
EDIT: Or are you asking how to launch the debug mode on Windows? If so, the answer is to write the following in cmd when the folder is set to the folder that Dolphin is in: Dolphin.exe /d
dolphin-master-5.0-3334-x64
Test movie: 55508 inputss ~ 5:08.
3x native internal resolution, 1080p, anti-aliasing 8x msaa, 8x anisotropic filtering
without FFV1, crappy video dump ~ 100mb (2 730 kb/s), horribly pixellated.
with FFV1, good video dump ~6.76gb (189 mb/s), good, obviously..
Since when dumping without FFV1 become so crappy?
A few months ago, I don't remenber what rev, rendering without FFV1 was very good.
Here is a quick comparative encode, at 9000 kb/s (~334mb each)
see @ ~2:00
Link to videoLink to video
dolphin-master-5.0-3334-x64
Test movie: 55508 inputss ~ 5:08.
3x native internal resolution, 1080p, anti-aliasing 8x msaa, 8x anisotropic filtering
without FFV1, crappy video dump ~ 100mb (2 730 kb/s), horribly pixellated.
with FFV1, good video dump ~6.76gb (189 mb/s), good, obviously..
Since when dumping without FFV1 become so crappy?
A few months ago, I don't remenber what rev, rendering without FFV1 was very good.
Here is a quick comparative encode, at 9000 kb/s (~334mb each)
see @ ~2:00
Link to videoLink to video
Ffmpeg was updated to latest stable version. This fixed a bug in Windows where the bitrate settings didn't affect the quality of the dumped video.
To account for this, I added a new configuration option in the GFX ini called BitrateKbps. To get the best quality out of XviD encodes, set this to some really high number like 50000 (it won't actually do 50000kbps, it just puts it in a really high quality profile).
Ffmpeg was updated to latest stable version. This fixed a bug in Windows where the bitrate settings didn't affect the quality of the dumped video.
To account for this, I added a new configuration option in the GFX ini called BitrateKbps. To get the best quality out of XviD encodes, set this to some really high number like 50000 (it won't actually do 50000kbps, it just puts it in a really high quality profile).
Thanks for your answer Fog
In the latest release, 5.0-3354, I have just this in GFX.ini
# GFXE5D - Freestyle Metal X
[Core]
# Values set here will override the main Dolphin settings.
[EmuState]
# The Emulation State. 1 is worst, 5 is best, 0 is not set.
EmulationStateId = 4
[OnLoad]
# Add memory patches to be loaded once on boot here.
[OnFrame]
# Add memory patches to be applied every frame here.
[ActionReplay]
# Add action replay cheats here.
Should we just add a line with the desired BitrateKbps?
Ah in "C:\Users\Documents\Dolphin Emulator\Config", found, thanks!
It was at 2500 kbps.
Does this affect only the non-FFV1 dump or both?
Thanks again Fog!
I try to update 1-2 times per week when I use Dolphin, so in the 2 last months, I've used 5.0-2191, 5.0-2538, 5.0-3202, 5.0-3305, 5.0-3334, 5.0-3354, 5.0-3463 and some others that I didn't keep.
I've tried 5.0-2191 wich is older than the version you linked, it desync at ~50000 frames, but with DSP LLE, I will try later with DSP HLE. (Although I have never had problems in LLE with this game before.)
Will test eventually with older versions too.
