ss_lemonade
Member
Does this still work with Final Fantasy XIII? I can't seem to get the game to launch anymore when gedosato is active. I would use DSR if I could but it doesn't look like nvidia has added support yet for mobile gpus (on a laptop)
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
GeDoSaTo - Downsampling from Infinity and Beyond!
- Thread starter Alo81
- Start date
Tried installing GeDoSaTo on my new laptop but I keep on getting this when I launch it even after I've disabled secure boot:
Tried redoing everything from a clean install. (also I do have the pre-requisites installed.)
Anyone have any idea of whats going wrong? Windows 10 if that's important.
Same exact error here. I just reinstalled Windows 10 Pro 64. My old installation was a legacy BIOS and it worked fine but my new one is UEFI. System Information reads Secure Boot State: Unsupported (I have a P67 motherboard, I believe it's one of the earlier UEFI implementations. Couldn't find anything about Secure Boot in the menus).
The program is installed to the root of my C drive. Prior to installing, I ran the Visual Studio 2015 file linked on Durante's blog. Also tried the .NET file but the installer says I already have it installed.
Any ideas?
edit: And now it's working. Not sure what I did. Maybe installing some prerequisites for some other games I'm installing fixed the problem?
BossDarkseid
Member
Does anyone know if it's possible for some workaround if your UEFI Secure BOot is locked via BIOS and unchangeable on Win 10? Only really want this for Ds2 atm with texture override etc but i just checked BIOS and it's not changeable 
Or am i just shit outta luck?
Or am i just shit outta luck?
Did you test out any of the mouse compatibility fixes close to the end of GeDoSaTo.ini?
Thanks, I looked up those settings and found that I did have to modify these.
Code:
modifyGetCursorPos true
modifySetCursorPos trueGlad it worked out.
Posting some PSHash for the hudless screenshot function I've accumulated just for reference and people who don't want to look for them (like me...), hope someone can find them useful! and I'm too lazy to test them since I don't play my games as much I'd like to lol, so some may not work, also thanks to my profile folder being a mess with a bunch of different backups , had to dig for some of them... it's why I didn't upload them to github
Edit: Removed some of the ones I uploaded to github since I tested those or they're more recent games I've played that should work. :V
, had to dig for some of them... it's why I didn't upload them to githubEdit: Removed some of the ones I uploaded to github since I tested those or they're more recent games I've played that should work. :V
TomcatTheLion
Member
Does anyone know if it's possible for some workaround if your UEFI Secure BOot is locked via BIOS and unchangeable on Win 10? Only really want this for Ds2 atm with texture override etc but i just checked BIOS and it's not changeable
Or am i just shit outta luck?
Been having a similar problem as well. Never had the issue on my previous rig since it was still running Windows 7.
StarCreator
Member
Posting some PSHash for the hudless screenshot function I've accumulated just for reference and people who don't want to look for them (like me...), hope someone can find them useful! and I'm too lazy to test them since I don't play my games as much I'd like to lol, so some may not work, also thanks to my profile folder being a mess with a bunch of different backups
Don't you need executable name for these to work?
yeah it's easy to find that exe filename yourself tho and just add them to user whitelist and create a profile, I didn't think to add that info on the list
Posting some PSHash for the hudless screenshot function I've accumulated just for reference and people who don't want to look for them (like me...), hope someone can find them useful! and I'm too lazy to test them since I don't play my games as much I'd like to lol, so some may not work, also thanks to my profile folder being a mess with a bunch of different backups
Cool, I'll link this post in the OP.
Great work, you (or someone else really) should make a pull request for those so that they don't get lost.Posting some PSHash for the hudless screenshot function I've accumulated just for reference and people who don't want to look for them (like me...), hope someone can find them useful! and I'm too lazy to test them since I don't play my games as much I'd like to lol, so some may not work, also thanks to my profile folder being a mess with a bunch of different backups
Paracelsus
Member
Any idea what could be causing this?
http://abload.de/img/screenshot_2016-01-08zdq2b.png
Forlane|Rei version (rather, forlane dll replacing the latest version's since it gives the error.txt), all it takes to explode like that is for rivatuner to be open with custom D3D activated, I don't even need to turn osd on. Close rivatuner, works fine. No OSD no matter the sw though (except fraps which works but overlaps on itself as soon as I upscale).
http://abload.de/img/screenshot_2016-01-08zdq2b.png
Forlane|Rei version (rather, forlane dll replacing the latest version's since it gives the error.txt), all it takes to explode like that is for rivatuner to be open with custom D3D activated, I don't even need to turn osd on. Close rivatuner, works fine. No OSD no matter the sw though (except fraps which works but overlaps on itself as soon as I upscale).
Boulotaur2024
Member
Wanted to post a small how-to since I just felt the urge to play Splinter Cell Chaos Theory in 4K with some downsampling in the mix and realized AMD VSR wasn't cutting it (apparently Nvidia DSR doesn't work either with this game) :
* Yes this works on Windows 10
- Launch and configure the game to its max settings (Shader model 3.0, Tone Mapping...) then quit the game.
- Navigate to C:\ProgramData\Ubisoft\Tom Clancy's Splinter Cell Chaos Theory and modify SplinterCell3.ini
Code:[WinDrv.WindowsClient] WindowedViewportX=640 WindowedViewportY=480 [B]FullscreenViewportX=3360 FullscreenViewportY=2100[/B] - Now make the file SplinterCell3.ini Read-only !
- Download and install GeDoSaTo.
- Activate the game in the whitelist.txt file :
Code:# GeDoSaTo Whitelist # One application name per line (application name = file name of the .exe without the .exe) # Wildcards supported (* = any sequence of characters, ? = any single character) # Format: # Exe File Name (or pattern) || Readable Name (optional) [B]SPLINTERCELL3[/B] - Edit GeDoSaTo.ini so that the rendering resolution matches the one you've just modified in the above step :
Code:# The actual rendering resolutions you want to use, # and how many Hz you want the game to think they work at. # format: renderResolution [width]x[height]@[hz] [B]renderResolution 3360x2100@60[/B] - Now some additional parameters to make the game compatible with GeDoSaTo :
Code:# Forces borderless windowed fullscreen mode instead of fullscreen mode # options: "true" (= force borderless windowed FS) and "false" (= unchanged) [B]forceBorderlessFullscreen true[/B]Code:# Adjust the reported client rect when downsampling [B]modifyGetClientRect false[/B] - Now you can launch GeDoSaToTool.exe and enjoy running the game with the best IQ available !
* Yes this works on Windows 10
DaciaJC
Gold Member
Does anybody have an idea why GeDoSaTo would cause Dark Souls II to crash upon startup? Recently installed Windows 10 x64 and I can install GeDoSaTo without issue, but upon starting DS2, I get a "Program has stopped working" error after a few seconds. Seemed to only happen when I had texture overriding enabled, but now it crashes as long as the program is activated.
robgrab
Member
Posting some PSHash for the hudless screenshot function I've accumulated just for reference and people who don't want to look for them (like me...), hope someone can find them useful! and I'm too lazy to test them since I don't play my games as much I'd like to lol, so some may not work, also thanks to my profile folder being a mess with a bunch of different backups
Nice list. HERE is one I found a long time ago for Flashback 2013 although I'm not sure if it was rolled into GeDoSaTo since I haven't used it in a few years since NVIDIA introduced DSR.
http://www.neogaf.com/forum/showpost.php?p=131924954&postcount=2914
Not sure if you ever fixed it but I was having the same problem as well. Fixed it by uninstalling GeDoSaTo and reinstalling it in a folder that has no spaces in it. It wasn't working in program files so I installed it in my games folder and now it works.
lightchris
Member
The latest update seems to have broken something with Valkyria Chronicles for me. The brightness in realtime cutscenes as well as gameplay is constantly changing slightly about once per second.
The problem is gone when GeDoSaTo is deactivated, so it has to be related somehow.
Can anyone confirm, or offer an earlier version for download so I can check myself if the behaviour really changed? (I accidentally reran the GeDoSaTo updater so my own local backup files of the earlier version were overwritten)
edit:
I focused so much on that annoying flickering that I didn't notice the whole 2D background is missing in the images above.
(the difference visible when cycling through the images)
The problem is gone when GeDoSaTo is deactivated, so it has to be related somehow.
Can anyone confirm, or offer an earlier version for download so I can check myself if the behaviour really changed? (I accidentally reran the GeDoSaTo updater so my own local backup files of the earlier version were overwritten)
edit:
I focused so much on that annoying flickering that I didn't notice the whole 2D background is missing in the images above.
The latest update seems to have broken something with Valkyria Chronicles for me. The brightness in realtime cutscenes as well as gameplay is constantly changing slightly about once per second.
(the difference visible when cycling through the images)
The problem is gone when GeDoSaTo is deactivated, so it has to be related somehow.
Can anyone confirm, or offer an earlier version for download so I can check myself if the behaviour really changed? (I accidentally reran the GeDoSaTo updater so my own local backup files of the earlier version were overwritten)
edit:
I focused so much on that annoying flickering that I didn't notice the whole 2D background is missing in the images above.
Just installed Valkyria Chronicles for the first time today and ran it with GeDoSaTo (latest version). I tried downsampling from 4K and 1440p down to 1080p. Unfortunately, I'm having the same problem as you; Whenever I have GeDoSaTo running I get the weird lighting glitch as well as textures missing in the character portraits during dialogue. During the prologue mission however not only is the water texture missing but the tree models/textures start freaking out in weird ways, sometimes straight-up disappearing at certain camera angles (I'll get some screenshots up soon). I've been looking for solutions but haven't found anything.
Edit: Here's what I was describing:
The latest update seems to have broken something with Valkyria Chronicles for me. The brightness in realtime cutscenes as well as gameplay is constantly changing slightly about once per second.
(the difference visible when cycling through the images)
The problem is gone when GeDoSaTo is deactivated, so it has to be related somehow.
Can anyone confirm, or offer an earlier version for download so I can check myself if the behaviour really changed? (I accidentally reran the GeDoSaTo updater so my own local backup files of the earlier version were overwritten)
edit:
I focused so much on that annoying flickering that I didn't notice the whole 2D background is missing in the images above.
You should both try going to edit config, finding Valkyria's config file, and removing the PSHash for the game if it exists, then reporting back your results.
Thanks for the reply. I just tried this but unfortunately got the same results as before.
Regarding Dragons Dogma, the game crashes at start up with GeDoSato enabled. It seems like I have to delete config.ini whenever I want to boot up the game. Then GeDoSaTo works fine when changing the settings from the game's option menu.
Does anyone know what I am doing wrong since I have to delete config.ini every time I want to boot up the game?
EDIT: by config.ini I mean the game's config.ini in Appdata\local\Capcom\dragons dogma
Does anyone know what I am doing wrong since I have to delete config.ini every time I want to boot up the game?
EDIT: by config.ini I mean the game's config.ini in Appdata\local\Capcom\dragons dogma
Hmm, I did some changes to state management recently that might have broken VC. I'll investigate.
That's strange, I can't reproduce that issue.
lightchris
Member
Yes, that fixed it.
Should I report issues directly to Github next time I believe something might be wrong?
..and I just noticed the binaries are also on Github, so next time I could check there if I wanted to compare the behaviour of the current revision to an older one.
Should I report issues directly to Github next time I believe something might be wrong?
..and I just noticed the binaries are also on Github, so next time I could check there if I wanted to compare the behaviour of the current revision to an older one.
TomcatTheLion
Member
Dio Brando
Banned
yeah, i'm having the same problem.
Running perfectly now. Thanks!
Cannon Goose
Member
How do I enable AO in Dragon's Dogma?
You need to change this line in the main gedosato ini file.
pluginOverride none --> pluginOverride GenericDepthPlugin
Cool!
Also multiple PSHashes is a big plus on some titles where I found UI elements are still visible in certain scenes.
So for an AOHash just track the shaders and find a suitable hash as your entry point(s) then right?
Dictator93
Member
Very cool, and will definitely clean up some AO injection problems
Sadly, the update broke the DD AO hash in some dungeons. Will need to find another new one.
This is my config for DDAO:
(I also use a custom/tweaked postprocessing shader)
I think HBAO looks rather bad and doesn't have good large-scale coverage. I use SAO.
This is my config for DDAO:
Code:
forceBorderlessFullscreen true
postProcessingType asmodean
enablePostprocessing true
addProcessingPass deband.fx
pluginOverride GenericDepthPlugin
ssaoType SAO
ssaoStrength 3
ssaoScale 2(I also use a custom/tweaked postprocessing shader)
I was using the same except gaussian instead of sharp and losing ~30FPS. Not sure if that's normal but I can't really justify such a huge drop.
Cannon Goose
Member
"30 frames" or "40 frames" isn't a very useful metric, since it depends on your initial framerate, but high-quality artifact-free injected AO is not cheap. Especially in DX9. In a simple game like DD it wouldn't be too unusual to spend almost as much GPU time on AO as you do rendering the frame.
Of course there are a billion parameters you can tweak to get a different performance/quality tradeoff, the default is heavily on the quality side of the equation.
Of course there are a billion parameters you can tweak to get a different performance/quality tradeoff, the default is heavily on the quality side of the equation.
KainXVIII
Member
Also AO is visible above some stats screens or when you buying something (like one shopkeeper in quarry)
That's the same issue. (Unless it happens outside of dungeons). Finding the right hash for the new version will fix both bleed through fog in dungeons as well as the UI bleed-through.
Edit:
Oh, and what I forgot to mention is that the current setup only works reliably if your character has visible (that is, not hidden by a helmet) hair.
(Because when the game draws hair it's a very good marker for when it would be the best time to apply AO. It's after all the other geometry but before all the fog/smoke/particle/light overlays)
I forgot to mention that frame dumping now makes it much easier to identify target shaders, since it dumps at every shader change and lists the shader hash in the filename. This is particularly important if you need more than 1 shader -- you can now also directly test these by reloading settings while the game is running as long as "TrackShaders" is enabled. However, this also means that you need to be careful about which resolution you do a framedump at -- you don't want 20 GB+ of data per dump
Most of the changes don't really matter to DS2 -- e.g. this particular way of fixing the fog rendering wouldn't work for it because it does things differently. However, you should be able to use SAO and its improvements in DS2.
I forgot to mention that frame dumping now makes it much easier to identify target shaders, since it dumps at every shader change and lists the shader hash in the filename. This is particularly important if you need more than 1 shader -- you can now also directly test these by reloading settings while the game is running as long as "TrackShaders" is enabled. However, this also means that you need to be careful about which resolution you do a framedump at -- you don't want 20 GB+ of data per dump
Most of the changes don't really matter to DS2 -- e.g. this particular way of fixing the fog rendering wouldn't work for it because it does things differently. However, you should be able to use SAO and its improvements in DS2.
Oh, so it's different. I think I'll load it up and look at it myself, always curious about these things.
And yeah, I was surprised at the amount of dump frames and wondered if that was new as well in this version.
I forgot to mention that frame dumping now makes it much easier to identify target shaders, since it dumps at every shader change and lists the shader hash in the filename. This is particularly important if you need more than 1 shader -- you can now also directly test these by reloading settings while the game is running as long as "TrackShaders" is enabled. However, this also means that you need to be careful about which resolution you do a framedump at -- you don't want 20 GB+ of data per dump
Oh shit. This is the real game changer.