Yes vote because I was entertained, and because I want to see the 2600 section populated. It's likely that only people that owned or played an Atari will be interested in watching movies in that section
That's always true, imo. I have yet to find a movie that sparked an emotional interest that wasn't on a system I played myself.
By the way, the encoding hides E.T.'s health at the beginning because of the TASVideos message. This should be fixed if this is published.
There's no easy way to fix that - putting subtitles on the map would cover E.T. at times, putting them at the top would cover the symbols there, and translucency would make them somewhat less legible. Out of the available options, obstructing the number at the bottom seems good to me.
Is D3D a better API to use, or would GDI be better instead?
No, GDI is much slower and only a fallback if you don't have hardware acceleration for some reason.
I don't see how you can use OpenGL when the emulator doesn't offer it (from what I've seen).
the_randomizer wrote:
I haven't tried special chip games, but all games I tried have noticeable screen tearing
Do you have VSync forcefully disabled in your graphics card's video driver options?
and I also noticed that there's still no option to force bilinear filtering in the filters options
But the difference for the common user is negligible
No, it's really not.
- bsnes is a stable platform, unlike SNES9x where every new version could lead to desyncs
- it's closer to the hardware (some may feel that incorrect emulation adds a flair of 'fake' to runs)
- being able to play back runs on the console is almost a certainty.
If you want a correct emulator, use bsnes' compatibility core. If you want a fast emulator, use SNES9x. The performance core is neither.
Since then I've switched to the performance core, and it's worked a lot better, but I honestly have no idea what the trade-offs are in terms of emulation accuracy and all that stuff.
Performance core is old and not very accurate. Maybe halfway between "proper" bsnes (compatibility core) and SNES9x/ZSNES?
(for DSS2 see here)
If things don't appear to move correctly (frames being in the wrong order), try AssumeTFF or AssumeBFF before SeparateFields.
If the picture appears to bob up and down, try QTGMC(ediThreads=1, preset="slow").
Creating a new directory does nothing, can you send me your config file and see if it works? The Read Only attribute cannot be disabled, it never saves.
I disabled UAC on my system so it works anywhere for me, but you probably shouldn't do that.
Did you extract it in C:\Users\User\Downloads\ ?
EDIT: Themaister would like an official bug report...
Yeah, 0.97 is the latest. Where did you extract it to? Maybe it works when run as administrator.
These are my steps:
- download 0.9.7, extract it and run retroarch-phoenix.exe
- select "menu | RetroArch | Update RetroArch"
- click "Check version"
- select "SNES / bsnes / 089 compatibility" ("Full" checkbox checked) and click "Download core"; click "Yes" in the message about using the core
- go to "menu | Settings | Video" and enter the frequency I get with FreqTest 1.6 (for bsnes I use this)
- in the Audio window, switch to XAudio (on Vista/7)
- (plus some unrelated settings like bilinear filtering and 4:3 aspect ratio)
- in the main window, select the ROM and click "Start RetroArch"
EDIT: Maybe change the graphics driver?
audio synchronization issues (audio popping) still exist when trying to sync with 60 Hz monitors
Have you tried the latest bsnes and RetroArch builds? They have new techniques for synchronizing; if they work better for the majority of people then maybe they could be adopted.
Is using LShift and RShift not possible?
In SNES9x I'm using W/S/A/D for directions, End/Del/Home/Ins for A/B/X/Y, and LShift/PgDown for L/R.
RShift would be ideal for Select.
Bilinear is very important to me too, almost as much as 4:3 aspect ratio correction.
zeromus wrote:
In Windows XP, the BizHawk window frame is 69 pixels. The taskbar is 28 pixels, at least. Both of those things are more bloated, if anything, in Windows 7. Most SNES games are 224 pixels tall. Now for the math: 69 + 28 + 224*3 = 769. Therefore, 3x scale wouldn't fit on your screen. That's why the client is preventing it.
And that's why I set my taskbars to auto-hide (with no animation), or even hide it completely.
DSS2 (needs avss.dll, which is e.g. in CCCP)
Btw. there's no need for a LoadPlugin call if you put your DLLs and *.avsi scripts into Avisynth's "plugins" subdirectory.
DSS2("00.avi")
i = Height / 2
top = Crop(0, 0, 0, -i)
bottom = Crop(0, i, 0, 0)
StackHorizontal(top, bottom)
- What kind of glitching? If that area can be copied from previous or following frames then fixing it is relatively easy.
- It's very annoying. I'd say just avoid it.
- You could create a second run that uses it, but it's probably not as entertaining.
Cores aren't comparable to each other. For example GB will be faster than SNES, and more accuracy will generally be slower. It also depends on what features the game uses (e.g. cartridge coprocessors - see the grid in Megaman X2's intro, it gets my Phenom X6 down to 20fps).
