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

No fx #2

Open
Ir1s07 opened this issue Jun 23, 2023 · 5 comments
Open

No fx #2

Ir1s07 opened this issue Jun 23, 2023 · 5 comments

Comments

@Ir1s07
Copy link

Ir1s07 commented Jun 23, 2023

no matter what i do there isnt any fx. ive tried reinstalling multiple times with no avail.
image

@byxor
Copy link
Owner

byxor commented Jun 23, 2023

I wonder if you have other conflicting files in your THUG Pro directory. e.g. files from an older version of Reshade.

If you get the time, could you run thedir command in your THUG Pro folder and paste the output here? Just want to see if you have extra unwanted files.

You can open Powershell quickly from explorer with File -> Open Windows Powershell:
image

@byxor
Copy link
Owner

byxor commented Aug 1, 2023

Multiple people are encountering this issue now. Not sure if it's a local setup issue or if it's broken now for a lot of people. I don't use it anymore so I haven't noticed any issues. Don't see why mine would stop working unless I updated Windows or DirectX in some way

@odiplol
Copy link

odiplol commented Aug 1, 2023

Yeah with this issue for me, i run windows 10 ltsc, and when i tried installing thug pro it wouldnt recognise my directx, i installed a different version with tons of tools and stuff and then it finally worked, maybe it has something to do with this version of directx.

@odiplol
Copy link

odiplol commented Oct 27, 2023

Guys, I found a SOLUTION!!! if you go to settings in the reshade menu, and select add effect directory path, select the effects folder in "reshade-shaders" and then press refresh in the reshade home menu.

@byxor
Copy link
Owner

byxor commented May 3, 2024

Only seeing this now, nice catch. I should probably mention this in the README, unless there's a way I can fix it directly

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