Nope; it's a hack. Until we find a proper fix, it should be broken by default. That'd be like saying we could flatten zfreeze to fix Mario Tennis, or stop rendering it to fix Rogue Squadron, so those things should be added. By adding hacks like that, you remove part of the incentive of fixing the issue.
True, I suppose, but then why have game specific settings and not take advantage of it? Perfect emulation wouldn't need game specific configurations in the end. So I don't see why we shouldn't take advantage of what has already been implemented (other than that it can introduce laziness towards fixing the underlying issues, okay, so my idea isn't that great).
I can't seem to get this game to look very clear in HD.
Here's my setup:
Dolphin 5.0-2286 x64
Windows 10 Pro x64
AMD Phenom II x6 1100T
NVIDIA GT 750 TI
16 GB RAM
I have the internal resolution set to 3x (1080p), but not matter what settings I tweak, the game still looks really pixelated. Any ideas? I've already tried OpenGL (my usual), Direct3D 11, and Vulcan.
Here are my full GFX settings:
Code:
[Hardware]
VSync = True
Adapter = 0
[Settings]
AspectRatio = 3
Crop = False
wideScreenHack = False
UseXFB = True
UseRealXFB = True
SafeTextureCacheColorSamples = 128
ShowFPS = False
LogRenderTimeToFile = False
OverlayStats = False
OverlayProjStats = False
DumpTextures = False
HiresTextures = True
ConvertHiresTextures = False
CacheHiresTextures = True
DumpEFBTarget = False
FreeLook = False
UseFFV1 = False
EnablePixelLighting = True
FastDepthCalc = True
MSAA = 2
SSAA = False
EFBScale = 6
TexFmtOverlayEnable = False
TexFmtOverlayCenter = False
Wireframe = False
DisableFog = False
EnableShaderDebugging = False
BorderlessFullscreen = True
SWZComploc = True
SWZFreeze = True
SWDumpObjects = False
SWDumpTevStages = False
SWDumpTevTexFetches = False
SWDrawStart = 0
SWDrawEnd = 100000
ShowNetPlayPing = False
ShowNetPlayMessages = False
EnableValidationLayer = False
BackendMultithreading = True
CommandBufferExecuteInterval = 100
DumpFramesAsImages = False
InternalResolutionFrameDumps = False
[Enhancements]
ForceFiltering = True
MaxAnisotropy = 2
PostProcessingShader =
ForceTrueColor = True
[Stereoscopy]
StereoMode = 0
StereoDepth = 20
StereoConvergencePercentage = 100
StereoSwapEyes = False
[Hacks]
EFBAccessEnable = True
BBoxEnable = False
ForceProgressive = True
EFBToTextureEnable = True
EFBScaledCopy = True
EFBEmulateFormatChanges = False
Attached is a screenshot of how pixelated it is when attempting to run at 1080p.
EDIT: Figured it out. Having External Frame Buffer set to "real" makes it look really pixelated while setting it to "virtual" or "off" clears it right up. I'll have to see if I get the green transition issue now with it on virtual EFB.
Hi All.
Can i get a hand to get Eternal Darkness to run?
It crashes at the moment the gameplay is supposed to start, right after the intro.
https://youtu.be/TsvCIGgDfZI?list=PLbHnvetEKQG__v2_uNIXamTv356JGVnyk&t=183
I have the following settings on (besides default settings)
[Core]
CPUThread = False
[Video_Settings]
EnablePixelLighting = True
my system is an Nvidia shield TV
thanks
(04-17-2017, 05:39 PM)cathair Wrote: [ -> ]my system is an Nvidia shield TV
It doesn't work on it yet. You can get a little further using that single core option and then nothing will be drawn...but the music keeps looping.
I've been playing this game for a while on Dolphin 5.0 and everything was just fine until I had to summon a creature. I cast the summon Trapper spell and within a few seconds of moving it, I lose control of it. I know the button to return to the character is the start button so I tried disabling that button in Dolphin but it didn't help. I've tried different controllers and that hasn't helped. Any tips? I'm only trying to get the optional purple rune right now but I know summoning is going to be necessary in future puzzles.
EDIT: wow I'm dumb. I finished this game four times over the years and never noticed that summoning creatures and controlling them drains sanity. I was just at 0 sanity and needed a recovery spell lol
I am doubtful that the "Transparency Issues" really exist - at least not for all users. I never turned on Per-Pixel Lighting, tried both OpenGL and Direct3D, several versions (recent Dev builds, 5.0, 4.0.2, 3.5), and never saw any transparency problems with the hanging vines. Can anyone confirm or deny? If nobody can reproduce it, that entry should be removed from the Wiki page.
Hi! Newbie here. Using Dolphin 5.0, and later 5.0-69something, on Windows 10, ran into a couple of issues. One is just the general "action replay Z+? codes are unstable" thing. But the other is, with or without any such codes, entering some rooms produces a spam of "invalid instruction at PC ..." type errors.
I don't know enough about Dolphin to know what to look for here. I can go get the more detailed errors with exact numbers, but given that other people have completed the game, apparently, presumably they're not getting weird crashes immediately on trying to enter certain rooms in the mansion.
Interestingly, which rooms seems to vary over time; there was a room that used to do that, but after doing some other things, it stopped doing it. This was fine until I got to a point where, so far as I can tell, I just plain can't continue the game without going into one of the bugged locations.
Doesn't seem to be tied to sanity mechanics or anything.
(A friend suggests (1) make sure dual-core is off, (2) try latest Dolphin 4.x build.)
Just as an update: 4.0.2 (the latest 4.x I can find) seems to work. It slows down quite a lot sometimes, but does run the game without crashing.
I spoke too soon. We got to the end of Chapter 10, and there's a point where there should probably be a cutscene.
Dolphin 4.0.2: "Backpatch: Currently only supporting reads." [dies]
Dolphin 4.0-9058: Errors about invalid read at various PCs. [dies.]
Dolphin 5.0-7038: Nothing, just silently hangs. FPS meter continues to update, the game's just hung on a black screen.
I have tried with and without dual core disabled, etcetera, and can't seem to find any combination that works better. Based on some comments seen elsewhere, have tried stuff like changing the DSP emulation, changing CPU emulation mode, and so on, none of which changed anything except making it slower.