Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GameIni: Force LLE Audio on Star Wars Rogue Squadron II & III #3919

Merged
merged 2 commits into from Jun 23, 2016

Conversation

Catarax
Copy link
Contributor

@Catarax Catarax commented Jun 22, 2016

Force LLE audio output on all Star Wars: Rogue Squadron releases in order to fix the constant glitchy noise audio ouput.


This change is Reviewable

Force LLE audio output on all Star Wars: Rogue Leader releases in order to fix the constant glitchy noise audio ouput.
@Catarax Catarax changed the title GameIni: Force LLE Audio on Star Wars: Rogue Leader GameIni: Force LLE Audio on Star Wars Rogue Squadron II: Rogue Leader Jun 22, 2016
@phire
Copy link
Member

phire commented Jun 22, 2016

This is probably a good idea.
On Jun 23, 2016 10:55 AM, "Catarax" notifications@github.com wrote:

Force LLE audio output on all Star Wars: Rogue Leader releases in order to

fix the constant glitchy noise audio ouput.

You can view, comment on, or merge this pull request online at:

#3919
Commit Summary

  • GameIni: Force LLE Audio on Star Wars: Rogue Leader

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3919, or mute the thread
https://github.com/notifications/unsubscribe/AAIc9GTftcIS0EzoE5X90gICKDUhTt-Nks5qOb1ygaJpZM4I8TZq
.

@RisingFog RisingFog added this to the Dolphin Release 5.0 milestone Jun 22, 2016
@RisingFog
Copy link
Member

If this is being done, it should be done with RS3 as well.

@RisingFog RisingFog removed this from the Dolphin Release 5.0 milestone Jun 22, 2016
@Catarax
Copy link
Contributor Author

Catarax commented Jun 22, 2016

I'll do it for the other episode if merged, yes.

Force LLE audio output on all Star Wars Rogue Squadron III: Rebel Strike releases in order to fix the constant glitchy noise audio ouput.
@Catarax Catarax changed the title GameIni: Force LLE Audio on Star Wars Rogue Squadron II: Rogue Leader GameIni: Force LLE Audio on Star Wars Rogue Squadron II & III Jun 22, 2016
@Catarax
Copy link
Contributor Author

Catarax commented Jun 22, 2016

Fix added for Rogue Squadron III.

@MayImilae
Copy link
Contributor

As we talked about this on IRC, the issue with this is that there is no way for a user to override this - LLE and HLE have to be chosen before the game is run, so there is no way to override this while the game is running. And the only way to override it is to edit the gameini and remove the feature, which is something we don't really want users doing!

So it might be a good idea to just wait for a proper fix, instead of covering it up like this.

@JMC47
Copy link
Contributor

JMC47 commented Jun 22, 2016

You can turn it off via the game properties page?

@Helios747
Copy link
Contributor

I'm iffy on the issue as well. I do not want to encourage users to "get extra speed" by opening things while running to change a setting. This is already enough of a problem with the graphics settings.

On the other hand, this is awful, holy crap! I just tested the game and BGM entirely kills it.

soooo.... meh meh meh meh meh mehhhhhhhhh.

Maybe if this was after 5.0 I'd be fine with it? I don't care what happens to perf then.

@Fallcrest
Copy link

@Helios747 Why don't we make this simple by having there be a checkbox that says "Use Default Game Settings" at the top of the settings menu so that it doesn't automatically switch to the other settings when you open up the menu?

@Helios747
Copy link
Contributor

Helios747 commented Jun 23, 2016

I don't think that is a bad idea, but it'll be bikeshed to hell.

Oh wait, I misunderstood what you meant.

I'd rather just fix the config system and rework the UI than do that.

@Fallcrest
Copy link

@Helios747 I agree that there probably is a better solution, but I think having a checkbox for that is a good idea. The current system of hidden default settings via the INIs and the fact that the INIs are overwritten when you open up the settings is extremely unintuitive for new users and even people that actually understand what is going on.

Because currently, even if you do override the default settings, there is no way to go back (unless there is... I don't know, like I said, it is not an intuitive system for anyone). A checkbox that could be toggled on and off would be very useful and visual. Maybe with some mouseover text that reads "Many games have been tested for a set of optimized settings, this box will enable those settings and ignore the manual settings."

Maybe the rest of the settings could be grayed out and not interactable unless the check box is off.

A final note, to increase user friendliness, there should be some place to easily see what the default settings are.

@Helios747
Copy link
Contributor

Helios747 commented Jun 23, 2016

If we didn't have a config rewrite in the works, I would consider this, but this idea is just a bandaid. A bandaid we don't really need anymore.

@phire
Copy link
Member

phire commented Jun 23, 2016

Are we really concerned that there will be no way to for the user to enable the option that Damages their hearing. That sounds like a feature to me.

@Helios747
Copy link
Contributor

phire, I'm sure you're very aware of some of the insane lengths our users will go to go fast.

@phire
Copy link
Member

phire commented Jun 23, 2016

Yes, and they are welcome to edit the config files.

@Fallcrest
Copy link

Fallcrest commented Jun 23, 2016

@Helios747 Fair enough. But the new config system is still a ways off, is it not? (Although, even something as minor as my patch idea wouldn't get into 5.0 at this point.)
Just curious, how does the new system address the problem at hand?

@JMC47
Copy link
Contributor

JMC47 commented Jun 23, 2016

I'm personally neutral toward this. I think having it emulate accurately, but slowly, by default is the slightly more sane option.

@Helios747
Copy link
Contributor

Helios747 commented Jun 23, 2016

True.

My issue is that for the insane users, they're 10x more likely to know that they can just open a menu and things magically go faster (I've seen one user claim this is because Dolphin had a memory leak) than know they can edit a text file. I'm not thrilled about encouraging this behavior. That said, I feel like just keeping this in the wiki isn't a bad solution considering the hard speed hit this will have on an already hard to emulate game.

haha nvm you can't change backends when running anyways

OTOH, current behavior is absolutely awful and I would equally hate for this to be default behavior.

This will absolutely destroy performance though.

@Fallcrest Depends on when @mathieui rebases it again and addresses a silly naming issue. But it's done. It addresses the problem at hand by not having every UI selected setting override GameINI whenever the user opens a menu. As well as cleaning up a lot of bandaids in code.

@Fallcrest
Copy link

Fallcrest commented Jun 23, 2016

@Helios747 What PR is the new configuration system? I can't find a single PR ever made by mathieui. There is a new configuration system PR by Sonicadvance1.

(Okay, yeah, I found it, sorry. It would not let me search by mathieui's name, for some reason. When I typed it into filter by author, nothing showed up...)

@Helios747
Copy link
Contributor

Did some testing since we have analytics now on a 4790k (Most popular CPU) and a 4700MQ (25th most popular CPU)

Tests done against the first mission at 1x IR

4790k:

HLE:
flying around: 200~ FPS
Blow something up: 170-180~ FPS

LLE:
flying around: 100~ FPS
Blow something up: 80 FPS

4700MQ (averaged 3 ghz):

HLE:
flying around: 120~ FPS
blow something up: 45-60 based on distance

LLE:
flying around: 90 FPS
blow something up: 40-50 FPS
Some cutscenes: 45 FPS

I'm not sure why LLE didn't hit my 4700MQ as hard. But yeah. This is something to consider. If trends continue after 5.0 and my CPU remains the most popular? This is a no-brainer and we should totally do this. If 5.0 brings in the flood of AMD trash CPUs, they may prefer to just turn off BGM. (which, honestly, we can just have them check HLE audio in game properties)

@JMC47
Copy link
Contributor

JMC47 commented Jun 23, 2016

For RS2, we could probably get back some of the performance with turning off EFB2RAM. It's not needed for the targeting computer any more. It's only needed for some special effects... none of which are game breaking. But, maybe it'd be best to leave that on for now.

@RisingFog RisingFog added this to the Dolphin Release 5.0 milestone Jun 23, 2016
@RisingFog
Copy link
Member

Reviewed 1 of 1 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@RisingFog RisingFog merged commit bc55510 into dolphin-emu:master Jun 23, 2016
@konpie
Copy link

konpie commented Jun 23, 2016

I think that should set this.
[DSP]
EnableJIT = True

@Helios747
Copy link
Contributor

To quote @lioncash

I like how this comes roaring into existence after we merge the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
8 participants