Dolphin 5.0 will surely blow people away, but only those who have been using 4.0.2 until now. If you're using the latest development builds, then you're pretty much already using 5.0 (except for a few issues that still need fixing).
You mean Ishiiruka? What, you haven't tried it, yet? I told you to, you know
It's just another branch of Dolphin. It just has a few features which some people love but some devs don't want them in Dolphin proper because of several reasons.
Especially the Async Shader Cache Generation is a great feature, though, because it gets rid of that annoying stuttering in games.
Just go and try it out... darlin'.
https://forums.dolphin-emu.org/Thread-unofficial-ishiiruka-dolphin-custom-version
Is there any way to play this and/or RE:make in widescreen without it being stretched? Using force 16:9 and/or having the widescreen hack enabled stretches the image horizontally. Thanks in advance!
(12-19-2015, 08:56 AM)D34DL1N3R Wrote: [ -> ]Is there any way to play this and/or RE:make in widescreen without it being stretched? Using force 16:9 and/or having the widescreen hack enabled stretches the image horizontally. Thanks in advance!
Anyone?
I haven't the slightest clue why Dolphin is doing this.. I'm using Revision 4.0-8877 x64. I get a weird thing pop up when I sometimes enter or exit a door (it's usually save rooms oddly enough) It's a gfx fifo error (random hex number stuff here) along with anther thing that pops up after I click ok.. The last part talks about illegal operations.. I can't exactly remember what it was doing and It hasn't done it since for whatever reason I have no idea. I just remember playing this game on the gamecube version as I have both and it did the same thing but towards the end of the game it actually crashed at the elevator inside the lab after the tyrant battle. I'm running dolphin on a i7-4700MQ, 16 gb ram, and my gpu is an nvidia Geforce GT 740m. I know my laptop doesn't have the best specs but It handles dolphin (and other emulators) pretty well no matter the game..
Sometimes with pcsx2 I have to tweak settings but that's only been with one game (shadow of the colossus). I'm really just trying to figure out if this is happening to anyone else here? I mean I haven't had it crash yet except on the gamecube version and I couldn't replicate that or any of this really.. I guess I'm just trying to figure out what could be causing this.. I'm a software developer in college so coding emulators really interests me because I really like code. That being said I'm an emulator noob and have really limited experience with all areas of programming be it oop, procedural or some mix of the two and I have no idea how an emulator works on the opposite end of the end user, I am gonna be starting school again soon though so I'm gonna learn all I can.. This is really interesting to me, but I have no idea what any of the crap that goes wrong and prompts me with is saying aside from the Hex numbers referring to memory space or whatever. I kinda want an explanation as to why it's popping up with a FIFO error in the first place.. I know FIFO (if I remember right) stands for first in first out? A term involved in data structures (I can't remember exactly which one.. Queues maybe? I don't remember ;-; I'm so rusty with coding it's ridiculous I can't wait to start school again so I feel the motivation to study and practice more.) So I'm just curious here what that is relating to.. But I guess FIFO might have to do with something else in this case cause it doesn't really make sense.. At least my mind is drawing a blank atm.. I'm pretty fried right now so... Also Yeah Is this GFX FIFO thing popping up for anyone else for this game? I found several other posts on here about it but it was all really old.. Most of the FIFO stuff I've seen was for mario galaxy.
I'm going to try and see if I can replicate it.. I doubt I'll be able to cause it usually happens when I DON'T want it to. (Dolphin hates me or something) Nevertheless, I'll try and replicate it and get a screencap for you guys... No promises though..
Okay so.. I managed to replicate it and I got some screencaps for you guys to look at.. Don't know what help it would be.. I went ahead and downloaded and installed the non developmental release of dolphin and it runs too slow for me to play for some reason... That's weird as hell to me why the stable release 4.0.2 is less stable with this game than the developmental build I'm currently using (4.0-8877 x64) but I guess it makes sense with the way dolphin is laid out in terms of developmental releases being every day and stable releases being every few years. Anyway any help or suggestions would be awesome or even just a reason why it's doing this would be great... I'm gonna say it's safe to assume that if it's doing this with this version too (as I said before I have both the gamecube and wii versions) that when I get to the elevator before the lab after the tyrant battle it's gonna crash. I'll keep playing and see but I have a feeling it's likely.. I also screencapped my settings on the version I use consistantly for you guys (4.0-8877-x64.. I don't use the "stable" 4.0.2 one I downloaded I only installed it for the sake of testing to see if the game worked better and didn't reproduce the issue I am having).
[
attachment=14361]
[
attachment=14362]
[
attachment=14363]
[
attachment=14364]
[
attachment=14365]
[
attachment=14366]
Okay so... Update... I got past the part I was talking about without the game crashing... It seems I found a viable workaround for the time being.. State saves in this game are a no go as upon loading one the vps drops considerably rendering the game unplayabe (no one likes feeling like their character is moving in slow mo am I right?) Using the normal way you save through typewriters in game I have found that after the aforementioned problems happen (upon entering or exiting any door) immediately find a save point and use it .. Following that close out of dolphin completely and relaunch as normal.. I'm not sure if this is actually working or rather that maybe the crash doesn't happen with the wii version.. I have no clue.. I can say for certain, however, that it DOES do the same thing the gamecube one did to me, at least as far as the GFX FIFO crap, so at this point my little "band-aid" fix is what I'm going to do until I have completed this game once again (I'm trying to relive my childhood LOL!) I no longer have a wii OR a gamecube so emulators are all I have to play my games ;-; Oh well I'm too broke to afford 2 new consoles even if they're older.. Nonetheless, I'd still appreciate someone talking to me and telling me a bit about what's causing this.. I'd appreciate a fix but that isn't necessary as much as I really just want to know what is doing this.. Any help appreciated C: (on a side note.. The term "band-aid" fix is something I learned about in programming classes.. LOL! Everyone who's a decent programmer should know "band-aid" fixes are not to be used if they are avoidable as they don't really FIX anything.. I just deemed this a situation where, although I'm not coding or anything similar, it was okay to use the term because I'm just trying to play the game to completion and not fix the issue)
Gosh I hope I'm not necroposting here. I don't wanna make a new thread and have it removed because it's an issue for another area..
How often does this happen? I had a quick go to see if I could reproduce your problem and add some confirmation, but I haven't been able to get any crashes yet. That said, I'm playing the PAL version, so that might make the results not directly comparable.
If it's random crashes we may have something interesting coming down the pipeline.
(02-10-2016, 11:30 AM)Silanda Wrote: [ -> ]How often does this happen? I had a quick go to see if I could reproduce your problem and add some confirmation, but I haven't been able to get any crashes yet. That said, I'm playing the PAL version, so that might make the results not directly comparable.
I'd say it happened pretty frequently... Maybe an hour or two in each time it's hard to say.