Wwe 13 Iso For Dolphin Emulator

0 views
Skip to first unread message

Dorian Aldrege

unread,
Aug 4, 2024, 7:38:33 PM8/4/24
to reaftaicrysaw
Dolphins users are always looking for new ways to play their favorite games. And when a project called "RetroAchievements" started gaining popularity for adding achievements into retro games, users started wondering if Dolphin would ever add support for the project. Unfortunately for them, Dolphin isn't a retro game emulator. We're a modern emulator that emulates two recent Nintendo consoles! RetroAchievements wouldn't make sense-

On the 24th of June, 2016, Dolphin 5.0 was released. The product of a long and hard transition period, the fundamental inaccuracies that plagued Dolphin for over a decade had successfully been undone, and Dolphin was now free of its burdens to swim forward into a new era of accuracy and performance.


I'm trying to run Dolphin Emulator on Kubuntu 21.04 using the recommended PPA. However, when I try to install it using sudo apt install dolphin-emu-master, I get an error about it not having a release file for 21.04/Hirsute. On the PPA, there is only a release file up to 18.04/Cosmic which is still being updated. I decide to edit the apt sources file to make it say cosmic rather than hirsute, however I just get an error about broken packages. I either need a way to ignore the broken packages that occurred due to me having to change the release name in the sources file, or a proper PPA that works with 21.04 that I can use. I know there is one in the default repositories, but that version is outdated and I need something from the beta or development channel for the additional features.


I recently bought a device with an Intel Core m3-7y30 with Intel 615 graphics, and it would seem that the iGPU is incompatible with the Dolphin emulator when using Vulkan as the renderer under Windows.


Under OpenGL and Direct3D 11, the Starfield demo seems to render correctly. Under Vulkan, Dolphin appears to completely crash. Developers of Dolphin seem to have indicated this is likely a driver problem.


When Dolphin supported Direct3D 12, it ran much faster than under OpenGL or Direct3D 11 as expected, but since that is no longer an option in current builds, we need Vulkan to work to provide the same performance.


I can provide more logs and system information if required. I can also test drivers and configuration settings on an Intel Core i5-7200U w/620 graphics and an Intel Core i7-7700k w/630 graphics if that would help as well.


By now the only thing left to do from our side is wait for the fix to be checked-in an upcoming 'Production version' driver release, so it becomes published in downloadcenter.intel.com. The whole process might take some time since the entire driver release has to go through extensive testing, but rest assured that help is coming.


Recent developmental builds of Dolphin Emulator make use of a feature called "Ubershaders", and it's such builds that experience these crashes. The previous stable release (5.0) without Ubershaders will not experience this crash.


I still believe this is a driver-related problem as every other Vulkan platform I'm aware of will at least start with this application (including the same device under Linux), but we can agree to disagree. The other backends do still seem to work correctly at the moment, albeit slower than if Vulkan was an option.


Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.


It sounds like the package conflicts, and they should probably update their package to properly mark it as conflicting with dolphin-emu. You could probably edit the pkgbuild to point -DCMAKE_INSTALL_PREFIX to somewhere else other than /usr, maybe /opt would be viable. Also remove the line from package() about the udev rule, because you'll already have that file there from the official dolphin-emu package.


When utilizing the dolphin emulator to emulate wii/gamecube commercial games and homebrew, I am getting graphical corruption on screen through a horizontal rapidly moving black bar. A short clip of the issue is attached. The issue only happens with the Vulkan backend and is not present on other hardware I have tested (RADV MESA drivers, lNTEL MESA drivers, AMD/Intel Windows gpu drivers, and r32.3.1 on Tegra-X1. The issue is independent of vsync being enabled or disabled.


You will need to test emulation with any legally aquired Nintendo Wii or GameCube game dump. There is also plenty of Wii homebrew games that you should be able to test with if you are unable to aquire any Wii/GC game dumps legally (List of homebrew games - WiiBrew).


Dolphin is an emulator for two recent Nintendo video game consoles: the GameCube and the Wii. It allows PC gamers to enjoy games for these two consoles in full HD (1080p) with several enhancements: compatibility with all PC controllers, turbo speed, networked multiplayer, and even more!


With that said, in my quest to get the most accurate, console-like experience out of the emulator and the monitor I came across an issue that probably doesn't bother a lot of people, but I felt it was worth mentioning anyhow.


I don't really know what the proper place to post this finding is, but I'll put it here for now. Also, I'm by no means an expert on any of the things I'm about to show, so I'd appreciate it if someone more knowledgeable could correct me.


By taking a screenshot, I figured out that the native resolution of the game is 584x480, so I tried the "Force 4:3" and "Stretch To Window" modes and the poor scaling went away on the stretched image:


I took a screenshot of Mario Sunshine and found out its resolution is 640x476, which means that a couple of lines of pixels are cut from the top and bottom part of the screen. This doesn't sound like a big deal at first. However, with how Dolphin's video modes work, this ends up messing up the entire image.


I'm guessing all of this could probably be fixed by implementing a Pixel Perfect / Integer Scaling mode. This way, all the pixels that aren't used would simply be black, and all the active pixels would line up with the scanlines or the pixel grid of the display. This wouldn't just benefit CRT users, but also owners of 480p LCDs and people who use HD TVs / monitors who don't mind having black bars around the image.


First, a real console simply doesn't output perfect pixel like you are expecting from dolphin. In-fact dolphin outputs significantly "cleaner" pixels, as it skips several steps of blur. The clean image quality you are striving for simply never existed. By default, games always do both vertical and horizontal bluring, and most games do horizontal scaling. All PAL games apply a vertical scaling.


Even in the games that go out of their way to offer a mode that minimise this (like Melee's disable AA filter mode), the vertical blurring incurred from the YUVU framebuffer is impossible to disable on real hardware.


Second, The video used by the GameCube and Wii (REC.601) has non-square pixels. 0.91:1 in NTSC and 1.09:1 in PAL. It's simply impossible to accurately portray this on a video mode with 1:1 square pixels, like 640x480 @ 60HZ VGA. Either you need to do some form of scaling (like dolphin currently does) or you end up with an incorrect aspect ratio.


However, I admit the experience could be better for this kind of usecase. At the very least, it should be easy to configure dolphin to a mode that actually showed the correct number of vertical lines with overscan/padding. Such a video mode would still need scaling along the horizontal for the majority of games, but at least you would only have scaling along one axis, and it happens to same axis that composite video really struggles with (and that a real console always has some amount of forced blur).


To be clear, my goal isn't to get hard pixel edges like in a 2D game (I apologize if there was a misunderstanding), I just want the scanlines to line up properly with the game resolution and the pixels to be horizontally even like real hardware displayed on a CRT (with whatever blur might be applied by the console). In short, no post-scaling artifacts.


My proposal here (as much as it's worth) would be to implement something along the lines of what Nintendo did with the SNES mini, which (iirc) offered a 1:1 pixel perfect mode with no shimmering (albeit with an incorrect aspect ratio), and a 4:3 mode with pixel interpolation (which minimized shimmering). I seem to remember the SNES also had non-square pixels.


The reason I'm saying this is that CRT displays could do without any form of horizontal scaling, since they can adjust the image after it has been sent to the screen, due to them not having a fixed pixel structure. So the correct aspect ratio could be achieved without the emulator doing any scaling (when set in 1:1 PAR). To my knowledge, LG OLEDs also have this "resizing" feature, and while they do have a fixed pixel structure, the pixel density is so high that you wouldn't notice any scaling.


As far as 480p LCDs are concerned, a 1:1 pixel mapping would definitely have an incorrect aspect ratio, however it would arguably be more "CRT-like", meaning that the vertical lines in excess would be vertically cropped and there wouldn't be any horizontal scaling since the pixels would be square (as opposed to having a forced aspect ratio where there would be scaling all over the place).

3a8082e126
Reply all
Reply to author
Forward
0 new messages