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

tried running it #1

Open
a-villain opened this issue Feb 9, 2023 · 10 comments
Open

tried running it #1

a-villain opened this issue Feb 9, 2023 · 10 comments

Comments

@a-villain
Copy link

i tried running it and nothing happened, gshade folders and files are still there.

@MirisWisdom
Copy link
Owner

MirisWisdom commented Feb 9, 2023

Hey friend, thanks for giving it a shot and reporting the issue!

Just a few questions:

  • Did it create a backup ZIP on your desktop? What files do you see in it?

  • Do you still see the GShade folder in C:\Program Files? If you do, could you try running the thingy as an administrator?

Cheers,

Miris

@a-villain
Copy link
Author

no back up zip folder and yes the gshade folder is still in program files

@MirisWisdom
Copy link
Owner

Interesting, hmm... can you open up a Command Line/PowerShell window and manually run the program from it? Easiest way would be to:

  1. Windows + R, then type in cmd; then
  2. Type in the "C:\Path\To\gshade-nuke.exe"

And then send me a screenshot of what you see in the window -- curious if errors appear before the program actually does its thing!

@a-villain
Copy link
Author

ok so, realized i needed all the assets downloaded and not just the exe, my bad, but now this is the error i'm recieving

image

MirisWisdom added a commit that referenced this issue Feb 13, 2023
This commit integrates a few procedures for figuring out the paths for
the XIV game directory, and the GShade installation directory.

Issue #1 on GitHub will benefit from this update.

-----------------------------------------------------------------------

XIV
---

1.  Attempt to retrieve value from the GShade registry key.
2.  Attempt to check the default non-Steam installation path.
3.  Attempt to check the current working directory.

GSHADE
------

1.  Attempt to retrieve value from the GShade registry key.
2.  Attempt to check the default Program Files installation path.

-----------------------------------------------------------------------

Signed-off-by: Emilian Roman <git@miris.design>
@MirisWisdom
Copy link
Owner

Hey friend, cheers for capturing the error. I've released an update which will hopefully handle that scenario better. To keep things safe, place gshade-nuke in your XIV game folder before running it.

The error happened because you've ran the official GShade uninstaller before, which deleted some stuff that GShade Nuke needs.

Many thanks for taking your time to test this out -- it helps tremendously!

PS: If by assets you're referring to the .sig file, that one's simply to verify the download :P

@d3aths
Copy link

d3aths commented Mar 16, 2023

same thing here. i put the nuke in the game's directory, with all these files
image

(ive just updated the game after not playing for a year so i think a that d3d file is missing but all g)

running it via command like you instructed on this post gets this info
image

get this log created after trying to run it that simply says

at Miris.GShade.Nuke.Program.Localise()
at Miris.GShade.Nuke.Program.Main(String[] args)

@MirisWisdom
Copy link
Owner

Thank you for reporting the quirk -- I'll try to figure out what could possibly cause that and release an update as soon as possible. Welcome back to XIV!

@MirisWisdom
Copy link
Owner

@d3aths, could you try the latest version? It probably won't fix the error; however, it should show more information in the log file.

@d3aths
Copy link

d3aths commented Mar 17, 2023

ive already manually migrated the gshade stuff to reshade as of last night sorry, so can't try it out again. But i suspect it might have been giving me errors because i used a portable version of gshade, rather than the main installer, so my file structure etc would have been different since the program itself was never "installed" on my pc, only the configs and presets etc.

@MirisWisdom
Copy link
Owner

That makes perfect sense -- the thing checks for some system files which the portable version likely wouldn't include; will be improving the resilience for it.

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

No branches or pull requests

3 participants