• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › General Discussion v
« Previous 1 ... 134 135 136 137 138 ... 369 Next »

Conduit full speed on old build
View New Posts | View Today's Posts

Pages (3): « Previous 1 2 3 Next »
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Conduit full speed on old build
03-03-2014, 08:26 PM
#11
MayImilae Offline
Chronically Distracted
**********
Administrators
Posts: 4,616
Threads: 120
Joined: Mar 2011
Try some old builds, like 4.0.2 and 3.5. If it works on an old build, try to find the build where it was broken. That is remarkably helpful for the developers.
[Image: RPvlSEt.png]
AMD Threadripper Pro 5975WX PBO+200 | Asrock WRX80 Creator | NVIDIA GeForce RTX 4090 FE | 64GB DDR4-3600 Octo-Channel | Windows 11 22H2 | (details)
MacBook Pro 14in | M1 Max (32 GPU Cores) | 64GB LPDDR5 6400 | macOS 12
Find
Reply
03-04-2014, 12:59 AM (This post was last modified: 03-28-2014, 09:45 PM by davew_uk.)
#12
davew_uk Offline
Junior Member
**
Posts: 17
Threads: 0
Joined: Apr 2013
Quote:Try some old builds

The config file I posted works for both 3.5.x and 4.x - they have the same problem with the frame rate limiter. Interestingly enough the vbeam hack *doesn't* work in 3.5 however and so I can't get full speed in splitscreen mode, and not even half speed in singleplayer. That might be a CPU limitation, or maybe they changed how the vbeam hack works, I don't know.

EDIT: I've updated my settings several times, see my last post in this thread for the final version with all game modes working at acceptable speeds
Find
Reply
03-28-2014, 09:42 PM
#13
davew_uk Offline
Junior Member
**
Posts: 17
Threads: 0
Joined: Apr 2013
Sorry to flog this dead horse a bit more. I've reported the bugs I found as requested: http://code.google.com/p/dolphin-emu/issues/detail?id=7132&thanks=7132&ts=1396006717

..and I also managed to fix the single player!
In addition to the INI file settings posted, Idle Skipping needs to be OFF and VBeam needs to be on. Both can be added to the INI file.

Code:
[Core]
gfxbackend = Direct3D
SkipIdle = False
VBeam = True
[EmuState]
EmulationStateId = 4
[Video_Hacks]
EFBAccessEnable = False
EFBCopyEnable = True
EFBToTextureEnable = False
EFBCopyCacheEnable = True
EFBEmulateFormatChanges = False
UseXFB = False
DlistCachingEnable = True
[Video_Settings]
SafeTextureCacheColorSamples = 128
EFBScale = 7
FastDepthCalc = True
EnablePixelLighting = False
DisableFog = False
[Wii]
DisableWiimoteSpeaker = 1

That's my final version, I'm done with this and moving on. It does slow down on certain multiplayer maps and when there's a lot going on in single player - but that's my weak processor rather than any bug I think.
Find
Reply
09-21-2014, 05:52 AM
#14
davew_uk Offline
Junior Member
**
Posts: 17
Threads: 0
Joined: Apr 2013
Tried this in the latest revisions just to see how the emulator has moved on.

In 4.0-3247, it runs absolutely great - I just needed to turn off Idle Skipping and set EFB->RAM and the game runs at a solid 100% speed even on my ancient PC. However the sound is absolutely terrible - garbled, glitchy, incorrect pitch, you name it. It has to be played with the sound off quite frankly unless you like listening to digital distortion. Nothing I have tried seems to be able to fix this.

In almost any build *after* 4.0-3247 however it crashes when entering gameplay. The menus are fine, however.
Find
Reply
09-21-2014, 06:00 AM
#15
DJBarry004 Offline
Don't even bother...
*******
Posts: 2,456
Threads: 33
Joined: Sep 2013
If the sound is "garbled" then it´s not running at 100% speed...
Rig 1: Windows 10 Home | AMD A6-1450 @ 600/1000/1400 MHz | AMD Radeon HD Graphics 8250 | 4GB RAM | HP Pavilion TouchSmart 11.

Rig 2: Windows 10 Pro | Intel Core i7-2640M @ 780/2800/3500 MHz | Intel HD 3000 Mobile | 8GB RAM | Dell Latitude 6320.
Find
Reply
09-21-2014, 06:20 AM
#16
davew_uk Offline
Junior Member
**
Posts: 17
Threads: 0
Joined: Apr 2013
I can assure you that it is.
Find
Reply
09-21-2014, 07:11 AM
#17
Shonumi Offline
Linux User/Tester
**********
Administrators
Posts: 6,513
Threads: 55
Joined: Dec 2011
It's not entirely impossible that an audio regression popped up. Verify that everything is in order (game runs fullspeed, screenshot it just in case) and pass it along to the Issues page on Google Code. If the audio is being distorted, perhaps it can be fixed soon.
Website Find
Reply
09-21-2014, 07:12 AM
#18
drhycodan Offline
Senior Member
****
Posts: 740
Threads: 160
Joined: Apr 2013
It crashes during gameplay in the newest revisions? Can someone else confirm this?
Find
Reply
09-21-2014, 06:12 PM (This post was last modified: 09-21-2014, 06:14 PM by davew_uk.)
#19
davew_uk Offline
Junior Member
**
Posts: 17
Threads: 0
Joined: Apr 2013
I haven't narrowed down the *exact* revision that causes the issue yet but I might have a go today.

I already reported a bug for this game's strange timing issues. It seems that they use some measure of the time it takes a frame to be rendered to determine the frame rate - if your computer is fast enough it'll try and render at 60fps, which then in turn slows down the emulation (but the game thinks it is still running fullspeed!).

If you artificially slow down the rendering (setting vsync every other frame, increasing the IR/AA, EFB->RAM instead of texture etc.) then it drops to a max of 30fps. The audio, however, seems to have some weird timing issue also. With the old audio frame limiter, once you had the game running fast enough you could engage the audio frame rate limiter in any build up to 2233 (though classic controller was broken from 1961 onwards and not fixed till after) and get a steady 75% speed with rock solid audio. I played the game for a long time like this before switching back to my old faithful 3.5-1124 (last build before async audio removed) where I can get anything from 75%-100% speed with rock solid audio.

So to get this game to run properly I have to do one of two things that Dolphin developers hate. Either use vbeam/audio frame rate limiter OR async audio. The good news is that going forward, with the newer builds, the performance is so much dramatically better that it can be run completely hack-free. The bad news is that the emulation of this particular game is still broken in terms of the sound and only works up to somewhere around 4.0-3247.
Find
Reply
09-21-2014, 06:52 PM
#20
davew_uk Offline
Junior Member
**
Posts: 17
Threads: 0
Joined: Apr 2013
OK, I narrowed down the exact revision that causes Conduit 2 not to work any more - it is 4.0-3254
Find
Reply
« Next Oldest | Next Newest »
Pages (3): « Previous 1 2 3 Next »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 2 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode