If it's a movie I'm particular eager to see or learn how things were done I'll watch it on emulator. Otherwise I'll watch or wait for an encode.
I don't care quality, I just want to watch, but if you suggest it, I can download Matroska encodes when watching in my PC :D
3: Download MP4 for use internet once and watch the times I want (based in how much I liked the movie)... or for watch later.
My primary is Movie file in Emulator and secondary MP4 compatibility. I have a very limited internet and I can't watch in YouTube and less if 360p or higher. Thank god movie files are very small sized.
@Memory Right, there would certainly not be any clear ending for this game, as you can keep playing for as long as you want, but i thought the first bullet point under the score guidelines, "There is no better way of defining full completion in the game" would best fit this game's case.
Maximum points or score is allowed as a full-completion category, provided that:
- There is no better way of defining full completion in the game.
- The maximum score is easily defined and absolute - it must not be possible to gain a higher score, even theoretically. It must be definable without being dependent on precise time, speed, or similar requirements.
- The maximum score is limited by not being able to gain any more points, not by hitting a score cap or overflow. If it is possible to score points infinitely, score cannot be used to define full completion.
In reference to your argument on completing a single game, there's actually three other card games you can play besides Blackjack, would winning one game of each be a more suitable goal or is that still too trivial?
I'd like the option to be able to submit an improvement to a run using the same CPU Divider setting as the currently published run, even if it is higher than the game was intended to run on. Otherwise, none of the work done previously would be reusable, and all work would have to be done from scratch.
My time in MAME-RR:
Mihoru's time in MAME-RR:
<feos> yeah okay. this question appears in different forms every once in a while. it takes looking at actual gba to tell how accurate the pallete is
<EZGames69> I mean looking at dkc2 specifically (not the title screen but actual movie), Bizhawk GBA pallet is super dark
<feos> super dark is subjective
<EZGames69> With vivid it makes it at least watchable without increasing the brightness
<EZGames69> Maybe im just so used to vivid
<EZGames69> Also how do we get a screenshot of gba? The only method I can think of is on a game cube with the game boy player
<feos> screenshot of internal gba image won't help
<feos> you have to actually look at the thing
<feos> and then we're entring the grey area
<EZGames69> Right
<feos> like lack of crt artifacts in encodes that are supposed to represent the authentic TV look
<feos> (we force 4:3 after all)
<feos> lack of those artifacts leads to n64 looking like shit at native resNobody seems to have tested x265 either, after I brought that up 3 years ago. HEVC is way popular now than VP9, and I've been using x265 for my The Simpsons encodes, and the result is much better than x264.
Edit the file to set the Amiga model you want to use and the game you want to use. Right now the emulator resolution (window_width and window_height) is set to native 1x, set it to 752x572 or anything you like. Other options are explained here. If some are missing, try docs source. https://fs-uae.net/keyboard-shortcuts Launch FS-UAE again to see the game recognized, try playing. By default arrow keys and Ctrl seem to do the main job, but mouse also works. Launch libTAS, set the Game executable to /usr/bin/fs-uae. Uncheck Runtime -> Backup save files in memory if you want it to use your configuration. Alternatively, pass the config as command line parameters. Everything related to TASing should be working in the newest libTAS release.Language: ini[config] amiga_model = A500 # seeks in Documents\FS-UAE\Floppies floppy_drive_0 = put_your_floppy_image_name_here.adf # needed for every floppy used floppy_drive_0_sounds = off # casual convenience automatic_input_grab = 0 # required for libTAS hooking video_sync = full video_sync_method = swap # fs-uae defines Amiga width and height as 752x572 # https://github.com/FrodeSolheim/fs-uae/blob/bfa0c7522c6c5f73cceb340d677491d056febd01/src/fsuae/fsuae-video.c#L23-L24 # so we divide by 2, which makes "Zoom: Full Frame" fit pixel-perfectly # a demo-scener measured Amiga display area as 384x285, but fs-uae doesn't use that # http://eab.abime.net/showpost.php?p=566175&postcount=16 # TODO: hires modes? window_width = 376 window_height = 286 # fs-uae defines "Zoom: Full Frame" as 752x572 # https://github.com/FrodeSolheim/fs-uae/blob/bfa0c7522c6c5f73cceb340d677491d056febd01/src/fsuae/fsuae-video.c#L39 # "full" displays the framebuffer as is, including overscan # this exposes that Amige doesn't center the image # this is accurate, and it's supposed to be centered manually # http://eab.abime.net/showthread.php?t=67165 # "auto" stretches the framebuffer to the window size # this hides overscan, but distorts the image # fs-uae window can't be configured to match the cropped FB size, so just use "full" zoom = full
- Next-gen codecs provide 50% bitrate improvements over x264, but are 10-20x as slow at the top settings required to accomplish such results.
- Normalized for CPU usage, libvpx already has some selling points when compared to x264; x265 is still too slow to be useful in most practical scenarios except in very high-end scenarios.
- ffvp9 is an incredibly awesome decoder that outperforms all other decoders.
Here is the improved version: User movie #52821885141911372, and the version with extra inputs for the epilogue: User movie #52821896824952159. The new TAS uses the up-to-date version of the game (v1.2.6.1). Sorry for the delay.