Dolphin, the GameCube and Wii emulator - Forums

(12-23-2013, 10:38 AM)Shonumi Wrote: [ -> ]

' Wrote:Dolphin's a bad software for this game, in fact Dolphin's a bad emulator for most Wii games: if you don't have a super overclocked CPU you'll never get good performance because Dolphin sucks at using more than two cores and it fails at fully utitlizing even that two. I'm sorry but if you have a quad core CPU running at 3.5 ghz and someone says you have to overclock more you know you've stepped into badly programmed territory. So don't let the flashy design and the high version number fool you: Dolphin still has a very long way to go. Maybe in five years we'll be able to brute force its shortcomings with awesome new computers or maybe the devs will get it right, who knows, but right now the only option to play Wii games is to play them on an actual Wii. Basically the only games that are running well on Dolphin for me as of now are the 2D oldschool titles like PoP 92 or Castlevania Rebirth.

Oh wow, that's just... ill-informed, to say the least. In the future, it would be advisable not to talk about the merits of an emulator's performance unless you 1) know how emulators work on a fairly low-level 2) know how the GC and Wii hardware differ from consumer PC hardware and 3) know how Dolphin specifically goes about emulating GC/Wii hardware. The fact of the matter is that it does take ridiculous amounts of hardware power to accurately emulate the GC and Wii systems on your computer. The FAQ explains this phenomenon pretty clearly. There's a very specific and technical reason why Dolphin doesn't make use or more than 3 threads to do the vast majority of its processing. The short answer is that emulating the GC/Wii is for the most part a very linear task that cannot ideally be broken down into many smaller, separate parallel tasks. Splitting the workloads for the emulated CPU, GPU, and DSP is possible, but anything further would likely be detrimental to Dolphin's performance. The FAQ explain this in detail as well.

In the meantime, you're free to try out all of the other viable GC/Wii emulators.

Look, I knew that an admin won't agree with me. What you refer to as the strength of the emulator is a weakness in my book: accuracy. Accuracy hurts the performance so focusing on that right now is stupid. As far as the required hardware for accurate emulation is not available to consumers the focus should be on finding a good middle ground between accurate emulation and performance, you can dedicate your efforts for that stuff after PC's catch up to the task. Anyway talking about accuracy as an excuse is pretty weird when we're in the topic of a game that just gives you the Dolby logo instead of starting up properly on half the emu settings for years now.

Don't misunderstand what I've said, I don't mean this as disrespecting the tremendous amount of the great job you guys have done, I just think of it as a bit of a loss when most people have no hardware for Dolphin and its requirements just keep going higher and higher. Just look at my example: I want to play this game on my PC for 3 years now and I always seem to be just under the hardware requirements with whatever PC I have (and I won't overclock because I don't do that shit to my machine) so for me accuracy doesn't really help. I'm sure I'll buy a Wii dirt cheap before I could actually run this game on PC.

Quote: Ever tried PCSX2? That's even slower than Dolphin if you want to have the games look anywhere near what they're suppose to look (AKA software rendering).

I regularly use PCSX2: it's awesome and it does the job at maintaining the 50 or 60 fps I need for most games.

Zaxx Wrote:What you refer to as the strength of the emulator is a weakness in my book: accuracy. Accuracy hurts the performance so focusing on that right now is stupid. As far as the required hardware for accurate emulation is not available to consumers the focus should be on finding a good middle ground between accurate emulation and performance, you can dedicate your efforts for that stuff after PC's catch up to the task.

I never said accuracy was Dolphin's strength. I just explained that to emulate the GC/Wii accurately, it takes a lot of hardware resources. You said it was essentially poor programming ("badly programmed territory" as you said). That's simply not the case. I said nothing about accuracy vs. speed though.

Zaxx Wrote:Anyway talking about accuracy as an excuse is pretty weird when we're in the topic of a game that just gives you the Dolby logo instead of starting up properly on half the emu settings for years now.

What are you referring to? The fact that Dolphin skips the GC BIOS? You can run BIOS if you have dumped the correct files. Dolphin has done this for quite a while, but it's not exactly a widely talked about feature.

EDIT: nvm, didn't read that you were talking about this game specifically. If you search YouTube a bit, you'll see people have gotten this game to boot just fine, like this person: http://www.youtube.com/watch?v=bczdWzMh9xk

Zaxx Wrote:I just think of it as a bit of a loss when most people have no hardware for Dolphin and its requirements just keep going higher and higher. Just look at my example: I want to play this game on my PC for 3 years now and I always seem to be just under the hardware requirements with whatever PC I have (and I won't overclock because I don't do that shit to my machine) so for me accuracy doesn't really help. I'm sure I'll buy a Wii dirt cheap before I could actually run this game on PC.

We already offer a decent compromise. No one's forced to use the latest revision or revisions that don't run well on their PCs. If someone wants to use r6xxx for whatever reason, they can. We just don't support anything below 4.0, but people can still use older revisions. Newer and better hardware requirements are nothing new when it comes to software; modern PC gaming is a prime example, and to an extent operating systems used to be like this as well. This sort of pattern isn't unusual. Nothing is stopping other interested developers from making a fork of Dolphin that focuses on performance; the code is licensed under the GPL.

[quote='Shonumi' pid='305681' dateline='1387764946']
[quote=]
What you refer to as the strength of the emulator is a weakness in my book: accuracy. Accuracy hurts the performance so focusing on that right now is stupid. As far as the required hardware for accurate emulation is not available to consumers the focus should be on finding a good middle ground between accurate emulation and performance, you can dedicate your efforts for that stuff after PC's catch up to the task.
[/quote]

I never said accuracy was Dolphin's strength. I just explained that to emulate the GC/Wii accurately, it takes a lot of hardware resources. You said it was essentially poor programming ("badly programmed territory" as you said). That's simply not the case. I said nothing about accuracy vs. speed though.

[quote=]
Anyway talking about accuracy as an excuse is pretty weird when we're in the topic of a game that just gives you the Dolby logo instead of starting up properly on half the emu settings for years now.



What are you referring to? The fact that Dolphin skips the GC BIOS? You can run BIOS if you have dumped the correct files. Dolphin has done this for quite a while, but it's not exactly a widely talked about feature.

EDIT: nvm, didn't read that you were talking about this game specifically. If you search YouTube a bit, you'll see people have gotten this game to boot just fine, like this person: http://www.youtube.com/watch?v=bczdWzMh9xk

[quote=]
I just think of it as a bit of a loss when most people have no hardware for Dolphin and its requirements just keep going higher and higher. Just look at my example: I want to play this game on my PC for 3 years now and I always seem to be just under the hardware requirements with whatever PC I have (and I won't overclock because I don't do that shit to my machine) so for me accuracy doesn't really help. I'm sure I'll buy a Wii dirt cheap before I could actually run this game on PC.



We already offer a decent compromise. No one's forced to use the latest revision or revisions that don't run well on their PCs. If someone wants to use r6xxx for whatever reason, they can. We just don't support anything below 4.0, but people can still use older revisions. Newer and better hardware requirements are nothing new when it comes to software; modern PC gaming is a prime example, and to an extent operating systems used to be like this as well. This sort of pattern isn't unusual. Nothing is stopping other interested developers from making a fork of Dolphin that focuses on performance; the code is licensed under the GPL.
The fact that the practice is not unusual doesn't really make it right and as for the "decent compromise": that is very case sensitive. If a game runs okay on an old version no one in their right mind would switch to a newer one to start the whole frustrating config process all over again but if you're waiting for a game to be playable you can only pray that one version will be able to play it. And let's not forget the point because the way you described the situation makes this stuff sound okay instead of ridiculous or idiotic which in fact it is: a high system requirement does not equal to overclocking the shit out of your computer, simple as that.

As for PoP yes you can get it to work but basically all the tips found on the wiki page are false or maybe that stuff was true some years ago but now it's obsolete. Maintaining a solid 60 fps on that game is hopeless on a non-overclocked CPU so all I can say to the OP is to try the PAL version and aim for 50, my machine can maintain that if every setting that hurts the accuracy are cranked up. The sad thing is that I can't really play the game because of a bug you didn't give two shits about for at least a year now because "you can still use a Wiimote if emulating the swing motion doesn't work" but guess what: I have no intention to use a Wiimote when I'm sitting at my computer.

So to end my rant right here and now, here's a suggestion: focus on what is useful for a whole lot of people instead of thinking of yourselves as some kind of tiny target audience.

Oh and a last bit: change this sentence in the description on the Dolphin main website:
[quote] Most games run perfectly or with minor bugs. Games are playable at HD quality, with 1080p and more.[/quote]
Saying they are "playable" is a lie, it should be something about how accurate Dolphin is. Anyway isn't actually achieving full speed should be the first criteria in reaching an accurate emulation? I don't know a thing about this but the notion of "it's running slow for you because it's ACCURATE" seems pretty ridiculous to me.

Edit: Well, that last edit messed up the quotes. Sorry, too late to fix that.

Zaxx Wrote:If a game runs okay on an old version no one in their right mind would switch to a newer one to start the whole frustrating config process all over again but if you're waiting for a game to be playable you can only pray that one version will be able to play it.

How long have you been a part of the Dolphin forums (as a user or a lurker)? We get people like that all the time. People upgrade from 3.5 or older to 4.0 or newer frequently. Skim through the Support forum. A lot of the issues recently stem from people trying to upgrade to 4.0 from something older, even when old versions "just work" for people.

Zaxx Wrote:The fact that the practice is not unusual doesn't really make it right and as for the "decent compromise". And let's not forget the point because the way you described the situation makes this stuff sound okay instead of ridiculous or idiotic which in fact it is.

It's a decent compromise because 1) people can still use what they want if it works for them and 2) the devs don't have to support it, and they can carry on development in the direction they see fit. If people using old revisions have issues, they're on their own for support. It wouldn't be fair to force the devs and forums to support issues in old builds that new builds fix, just as it wouldn't be fair to force everyone to upgrade their version of Dolphin and their hardware if necessary. It also isn't fair to expect the developers to add and support speedhacks for lower-end hardware if they feel it would complicate the code base and involve further effort in the project's overall maintenance. Please explain in detail how you feel the current situation is ridiculous.

Zaxx Wrote:a high system requirement does not equal to overclocking the shit out of your computer, simple as that.

A "high-end system" is entirely relative depending on the current hardware available at any given time and the application in question. Something like Sandy or Ivy Bridge 3.3GHz CPUs are considered fairly high-end for PC games, almost overkill. For Dolphin, it's not going to be enough for games like The Last Story. A GTX 550 Ti is a mid-range GPU for PC gaming, but for Dolphin it's almost in the upper tiers for performance. Ivy Bridge CPUs used to be king for Dolphin, until Haswell provided a 20~30% increase in performance. Now a high-end system usually means any Haswell CPU that is clocked at 3GHz or above. For Dolphin, a high-end system means any GPU with sufficient bandwidth to play games at a given Internal Resolution and Anti-Aliasing without bottlenecking emulation and any CPU with sufficient single-threaded IPC performance for a given game. Some games do not require a lot of hardware resources to emulate, others do. This happens because different games require Dolphin to emulate different instructions, some of which take longer and require more hardware resources to complete.

Zaxx Wrote:As for PoP yes you can get it to work but basically all the tips found on the wiki page are false or maybe that stuff was true some years ago but now it's obsolete.

What stuff on the wiki page? It's practically empty. All it has is a single testing entry that was performed years ago. The bit about "This game doesn't need specific settings to run properly." is generated automatically for new wiki pages, and remains there until someone edits the wiki describing their problems. All it means is that no one has bothered to add any data for this game.

Zaxx Wrote:Maintaining a solid 60 fps on that game is hopeless on a non-overclocked CPU so all I can say to the OP is to try the PAL version and aim for 50, my machine can maintain that if every setting that hurts the accuracy are cranked up.

An i5-4670 (non-K model) at 3.4GHz stock is equivalent to your i7-2600 if it were clocked to ~4.3GHz when it comes to Dolphin performance. I'm sure it would do just fine without any overclocking. Haswell CPUs are just that fast when it comes to Dolphin (we've done benchmarks proving this).

Zaxx Wrote:Saying they are "playable" is a lie, it should be something about how accurate Dolphin is. Anyway isn't actually achieving full speed should be the first criteria in reaching an accurate emulation? I don't know a thing about this but the notion of "it's running slow for you because it's ACCURATE" seems pretty ridiculous to me.

Playable isn't the same as enjoyable; enjoyable means many things to many different people. Before I had a decent machine (something that didn't rely on Intel GMA IGPs) half-speed was fine for me. For others, anything that dips 5% below fullspeed is unacceptable. Some people don't mind the slowdowns, others do. Playable means just that: you are able to play the game. The stipulation is that you need a certain level of hardware in order to make it enjoyable, but that's true of any emulator or gaming software. Requiring a higher level of hardware than other software in order to reach enjoyable levels doesn't mean the emulator isn't playable at all. Having bugs, crashing a lot, or just refusing to run makes an emulator unplayable.

(12-23-2013, 03:52 PM)Shonumi Wrote: [ -> ]

' Wrote:If a game runs okay on an old version no one in their right mind would switch to a newer one to start the whole frustrating config process all over again but if you're waiting for a game to be playable you can only pray that one version will be able to play it.

How long have you been a part of the Dolphin forums (as a user or a lurker)? We get people like that all the time. People upgrade from 3.5 or older to 4.0 or newer frequently. Skim through the Support forum. A lot of the issues recently stem from people trying to upgrade to 4.0 from something older, even when old versions "just work" for people.

' Wrote:The fact that the practice is not unusual doesn't really make it right and as for the "decent compromise". And let's not forget the point because the way you described the situation makes this stuff sound okay instead of ridiculous or idiotic which in fact it is.

It's a decent compromise because 1) people can still use what they want if it works for them and 2) the devs don't have to support it, and they can carry on development in the direction they see fit. If people using old revisions have issues, they're on their own for support. It wouldn't be fair to force the devs and forums to support issues in old builds that new builds fix, just as it wouldn't be fair to force everyone to upgrade their version of Dolphin and their hardware if necessary. It also isn't fair to expect the developers to add and support speedhacks for lower-end hardware if they feel it would complicate the code base and involve further effort in the project's overall maintenance. Please explain in detail how you feel the current situation is ridiculous.

' Wrote:a high system requirement does not equal to overclocking the shit out of your computer, simple as that.

A "high-end system" is entirely relative depending on the current hardware available at any given time and the application in question. Something like Sandy or Ivy Bridge 3.3GHz CPUs are considered fairly high-end for PC games, almost overkill. For Dolphin, it's not going to be enough for games like The Last Story. A GTX 550 Ti is a mid-range GPU for PC gaming, but for Dolphin it's almost in the upper tiers for performance. Ivy Bridge CPUs used to be king for Dolphin, until Haswell provided a 20~30% increase in performance. Now a high-end system usually means any Haswell CPU that is clocked at 3GHz or above. For Dolphin, a high-end system means any GPU with sufficient bandwidth to play games at a given Internal Resolution and Anti-Aliasing without bottlenecking emulation and any CPU with sufficient single-threaded IPC performance for a given game. Some games do not require a lot of hardware resources to emulate, others do. This happens because different games require Dolphin to emulate different instructions, some of which take longer and require more hardware resources to complete.

' Wrote:As for PoP yes you can get it to work but basically all the tips found on the wiki page are false or maybe that stuff was true some years ago but now it's obsolete.

What stuff on the wiki page? It's practically empty. All it has is a single testing entry that was performed years ago. The bit about "This game doesn't need specific settings to run properly." is generated automatically for new wiki pages, and remains there until someone edits the wiki describing their problems. All it means is that no one has bothered to add any data for this game.

' Wrote:Maintaining a solid 60 fps on that game is hopeless on a non-overclocked CPU so all I can say to the OP is to try the PAL version and aim for 50, my machine can maintain that if every setting that hurts the accuracy are cranked up.

An i5-4670 (non-K model) at 3.4GHz stock is equivalent to your i7-2600 if it were clocked to ~4.3GHz when it comes to Dolphin performance. I'm sure it would do just fine without any overclocking. Haswell CPUs are just that fast when it comes to Dolphin (we've done benchmarks proving this).

' Wrote:Saying they are "playable" is a lie, it should be something about how accurate Dolphin is. Anyway isn't actually achieving full speed should be the first criteria in reaching an accurate emulation? I don't know a thing about this but the notion of "it's running slow for you because it's ACCURATE" seems pretty ridiculous to me.

Playable isn't the same as enjoyable; enjoyable means many things to many different people. Before I had a decent machine (something that didn't rely on Intel GMA IGPs) half-speed was fine for me. For others, anything that dips 5% below fullspeed is unacceptable. Some people don't mind the slowdowns, others do. Playable means just that: you are able to play the game. The stipulation is that you need a certain level of hardware in order to make it enjoyable, but that's true of any emulator or gaming software. Requiring a higher level of hardware than other software in order to reach enjoyable levels doesn't mean the emulator isn't playable at all. Having bugs, crashing a lot, or just refusing to run makes an emulator unplayable.

Half speed was fine back then? Well it would still be fine if the sound wouldn't stop when the FPS dips below a certain amount. I can't imagine anyone could tolerate that. Anyway: why was that messed up? Also: why is the Wiimote swing emulation bugged out when one purpose of an emulator should be to make playing games on a PC possible (like by not swinging like an idiot at your computer but performing a swing only by pushing a button)? During one of my times of lurking (I don't really stick around here, I just come back from time to time to see what's up, usually when I have another go at trying to make Forgotten Sands playable) I remember some dev saying "it is not a priority because you can use a Wiimote". It's like a game dev saying "hey, why should we fix the keyboard+mouse controls when you can use a controller?" Don't be assholes, please.

But to be honest I don't really care enough to continue this conversation, you can create all kinds of ideology behind some of the idiotic choices of Dolphin development, but at the end I still view it as a sign of incompetency in creating a useful product.

So to get back on topic: in order to get the game working properly you need half a million things. Here are the settings that worked for me, I write these down because the OP's machine is similar to mine:

1. Use the PAL version because in order to bypass the graphical glitches that occur you need to turn on some settings that hurt the performance!
2. Don't use the 4.0 Dolphin found on the site because it's slow as f**k, use the 4.0-315-x64 Master instead!
3. On the "Configure..." part go to General:
- put a tick next to all the stuff that says "speedup" at the end
- set your Framelimit to "Audio" and put a tick next to "Limit by FPS"
4. On the Wii tab turn off "EuRGB60 mode"
5. Go to "Graphics Settings"
6. On the General tab select the OpenGL backend and turn off Vsync
7. On the "Hacks" tab put a tick next to "Ignore Format Changes", set EFB Copies to RAM and put a tick to the Enable Cache box
8. Disable External Frame Buffer and on the "Other" part put a tick next to Fast Depth Calculation and Vertex Streaming Hack
9. Set the Texture Cache Accuracy slider to "Fast"
+1 optional step: you can turn on Scaled EFB copy and you can set your internal resolution to 2x Native, this had very minimal effect to my performance and made the game look much better.

Zaxx Wrote:Half speed was fine back then? Well it would still be fine if the sound wouldn't stop when the FPS dips below a certain amount. I can't imagine anyone could tolerate that. Anyway: why was that messed up?

I already told you, my hardware at the time was weak (E2200 @ 2.2GHz, Intel G33/G31 Express Chipset). I was just happy to be able to play Sonic Adventure 2 again, and I was glad to see that GC emulation wasn't stuck in some infantile state (many games were playable even in r7xxx when I got into Dolphin). Different people have different standards. You'll still find people here that are perfectly okay with 80% if that's as fast as their hardware will let them emulate a game.

Zaxx Wrote:Also: why is the Wiimote swing emulation bugged out when one purpose of an emulator should be to make playing games on a PC possible (like by not swinging like an idiot at your computer but performing a swing only by pushing a button)? During one of my times of lurking (I don't really stick around here, I just come back from time to time to see what's up, usually when I have another go at trying to make Forgotten Sands playable) I remember some dev saying "it is not a priority because you can use a Wiimote". It's like a game dev saying "hey, why should we fix the keyboard+mouse controls when you can use a controller?" Don't be assholes, please.

I dunno why it isn't working for you, since it's always worked for me. File an issue report here: https://code.google.com/p/dolphin-emu/issues/list to properly get the devs to address it. At any rate, you're misunderstanding what the dev meant. "Not a priority" doesn't mean no one feels it should be worked on at all, just not presently, especially if the devs want to work on other areas first. Dolphin's development style is one where every dev works on what he or she wants to at any given time. If no one feels Feature XYZ is a priority for them, it simply doesn't get addressed right away. That's completely different from saying it won't ever be addressed. Everyone's just working on what they feel they want to work on, and no one's being an asshole for working on something other than what you want added to the project.

Zaxx Wrote:But to be honest I don't really care enough to continue this conversation, you can create all kinds of ideology behind some of the idiotic choices of Dolphin development, but at the end I still view it as a sign of incompetency in creating a useful product.

Again, Dolphin is FOSS (Free and Open Source Software). Anyone can do anything with the code. Even if you're not a developer, nothing is stopping you from generating interest among people who can code so that some new group can make a better emulator. Every dev has his or her own goals for what they want Dolphin to be, and it just happens a lot of them want to make something that accurately preserves GC and Wii games. You and anyone else are free to start a fork (or another project from scratch) that avoids "idiotic" developmental choices and creates "useful products".

Holy shit dude, this thread was RIP until you bumped it. OP won't even read the stuff you just posted. Chill down.

Quote:

Quote:

(12-24-2013, 01:33 AM)Shonumi Wrote: [ -> ]Half speed was fine back then? Well it would still be fine if the sound wouldn't stop when the FPS dips below a certain amount. I can't imagine anyone could tolerate that. Anyway: why was that messed up?

I already told you, my hardware at the time was weak (E2200 @ 2.2GHz, Intel G33/G31 Express Chipset). I was just happy to be able to play Sonic Adventure 2 again, and I was glad to see that GC emulation wasn't stuck in some infantile state (many games were playable even in r7xxx when I got into Dolphin). Different people have different standards. You'll still find people here that are perfectly okay with 80% if that's as fast as their hardware will let them emulate a game.

Quote:Also: why is the Wiimote swing emulation bugged out when one purpose of an emulator should be to make playing games on a PC possible (like by not swinging like an idiot at your computer but performing a swing only by pushing a button)? During one of my times of lurking (I don't really stick around here, I just come back from time to time to see what's up, usually when I have another go at trying to make Forgotten Sands playable) I remember some dev saying "it is not a priority because you can use a Wiimote". It's like a game dev saying "hey, why should we fix the keyboard+mouse controls when you can use a controller?" Don't be assholes, please.

Quote:I dunno why it isn't working for you, since it's always worked for me. File an issue report here: https://code.google.com/p/dolphin-emu/issues/list to properly get the devs to address it. At any rate, you're misunderstanding what the dev meant. "Not a priority" doesn't mean no one feels it should be worked on at all, just not presently, especially if the devs want to work on other areas first. Dolphin's development style is one where every dev works on what he or she wants to at any given time. If no one feels Feature XYZ is a priority for them, it simply doesn't get addressed right away. That's completely different from saying it won't ever be addressed. Everyone's just working on what they feel they want to work on, and no one's being an asshole for working on something other than what you want added to the project.

Quote:But to be honest I don't really care enough to continue this conversation, you can create all kinds of ideology behind some of the idiotic choices of Dolphin development, but at the end I still view it as a sign of incompetency in creating a useful product.

Quote:Again, Dolphin is FOSS (Free and Open Source Software). Anyone can do anything with the code. Even if you're not a developer, nothing is stopping you from generating interest among people who can code so that some new group can make a better emulator. Every dev has his or her own goals for what they want Dolphin to be, and it just happens a lot of them want to make something that accurately preserves GC and Wii games. You and anyone else are free to start a fork (or another project from scratch) that avoids "idiotic" developmental choices and creates "useful products".

Seeing how many "modded" versions exist for Dolphin (almost zero) I don't view that opinion as realistic, sorry.

As for my problem let me elaborate because you did not get it: if you say "Feature XYZ" and you mean the shake emulation by that (I'm only guessing because in the controller config screen the letters XYZ are written under the Shake settings) then you're right, that is working. What is not working is the swing emulation that I guess is supposed to emulate the swinging motion of the Wiimote. In Forgotten Sands the Prince attacks when you swing the Wiimote, if you use shake instead it barely works, you're just basically standing still, mashing or holdin the shake button and pray that an attack will come out of it at then. Feels like playing and RNG based TBS to be honest.

I won't file an issue report about this because I've already seen a ton:
https://code.google.com/p/dolphin-emu/issues/detail?id=5310
https://code.google.com/p/dolphin-emu/issues/detail?id=6304

The first one is from the middle of 2012, that's ONE AND A HALF YEARS. D I know what "not a priority" means and it certainly isn't "we absolutely don't care about that". The issue is there for sure since 3.0 and it's possible it was always a problem. And that really reflects to my main point: what is the point of putting exrteme amount of work into something when not even the controls are fully emulated. I understand it has to be a tough job to do that since the Wii has a unique controller but the PC has a mouse and a keyboard and shaking works almost perfectly so with some work it's possible. I'm not saying to do it right now, I just say that development should switch a bit of its focus to get some of the more practical stuff working, then you can make your awesome accurate emulator.

Quote: Holy shit dude, this thread was RIP until you bumped it. OP won't even read the stuff you just posted. Chill down.

Maybe bumping a thread that is 5 months old is considered to be raising the dead but here's a story. I wanted to open a thread about this game so I used the search function and voila', I found an already existing one about the same problem I am dealing with so people can still find this topic. Anyway my habit is that I check on the emulators I follow every half a year if I want to play a game on that platform so if the OP is like me, he'll read it eventually.

Edit: So it seems like two separate quotes break a post. Why am I not surprised? I'm sure there is some illogical way to use quotes correctly but anyway: sorry again, I'm still learning.

Zaxx Wrote:Seeing how many "modded" versions exist for Dolphin (almost zero) I don't view that opinion as realistic, sorry.

So, because no one's done it yet, no one will ever do it? That isn't logically sound. Nothing is stopping people from forking Dolphin or taking the bits they do like and making something else. It happens all the time in FOSS.

Zaxx Wrote:As for my problem let me elaborate because you did not get it: if you say "Feature XYZ" and you mean the shake emulation by that (I'm only guessing because in the controller config screen the letters XYZ are written under the Shake settings) then you're right, that is working. What is not working is the swing emulation that I guess is supposed to emulate the swinging motion of the Wiimote. In Forgotten Sands the Prince attacks when you swing the Wiimote, if you use shake instead it barely works, you're just basically standing still, mashing or holdin the shake button and pray that an attack will come out of it at then. Feels like playing and RNG based TBS to be honest.

Yeah, I'm not talking about shake emulation, I'm talking about swing emulation. I've never had an issue with it in Twilight Princess. It may just be an issue with certain games.

Zaxx Wrote:what is the point of putting exrteme amount of work into something when not even the controls are fully emulated. I understand it has to be a tough job to do that since the Wii has a unique controller but the PC has a mouse and a keyboard and shaking works almost perfectly so with some work it's possible. I'm not saying to do it right now, I just say that development should switch a bit of its focus to get some of the more practical stuff working, then you can make your awesome accurate emulator.

The work on accuracy has to be done sooner or later. The devs contributing to Dolphin feel that they would rather work on it now than later. I know when I work on an emulator, I like to get things like accurate CPU instructions, GPU renderings, timings, and interrupts done before I tackle other aspects like scaling filters. Scaling filters (even nearest neighbor) are very practical in an emulator, especially 2D systems with small screen (it also makes graphical debugging much easier) and people who use my emulator would find it a very useful option (as opposed to squinting at their screens) but I don't add things like that until I'm finished working on other areas that have my priority. I'm only just now tackling sound in my current project because I've finished just about everything else. The devs can only work on one thing at a time; even if something seems "practical" to you, that doesn't mean they feel it's worth their time to work on it before they take care of other business.

Okay, so if swing is supposed to work then how do you configure it? There is no explanation on it so maybe it's me who's doing something wrong. Which buttons should I set it up with? How to configure the movement or something like that? Can I do those things or is it supposed to just work?