i dont have dlss or dlaa option #2173
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2173
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hookshot version
2.1.0
What kind of problem
Graphics (missing, black or wrong-coloured things, lighting, flicker)
What happened
I don't have the option to enable DLSS or DLAA, even though I have an RTX 3080 Ti graphics card.
Where in the game
game sating
How often
Every time
Graphics card and driver version
RTX 3080ti
CPU, RAM and operating system
i5 14400f 32 g ram
Changes from the defaults
No response
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
I don't have the option to enable DLSS or DLAA, even though I have an RTX 3080 Ti graphics card.
Screenshots or video
No response
Before you send it
Same for me! Non TI RTX 3080. It's also a little bit useless that it can only be enabled in the builder (which is never used again by anyone after the first build) but not in the updater.
Manually launching the phyton script mentioned in the readme does download the SDK but not copy it to the game folder and the instructions don't make it clear which folder is meant by "game folder\ngx" because copying the nvngx_dlss.dll to the "game folder\ngx" does absolutely nothing so "game folder" must be something else BUT the actual game folder. Moving it to the "bin" sub folder doesn't do anything either.
The option is just simply not available.
This is a problem. How can we solve it? Any - [ ] help?
I have RTX5070, same problem.
Changes in .ini file also do nothing.
I don't understand why this has to be such a procedure in the first place. The code for DLSS support (the menu options and the call to the nvngx_dlss.dll) should be compiled into the game regardless of the presence of the NGX SDK and adding it to the game should be nothing more but copying the DLL beside the main executable like it is with literally ANY other game/recomp.
For me (4070 ti) I initially neglected to select DLSS in the builder. Attempting it after the fact didn't work, but deleting the build and rebuilding from scratch fixed the issue.
Delete everything, reinstall the port from scratch, and tell me what you see.
Delete everything and reinstall the port, then let me know what you see; I’m at work right now, so I can’t perform the deletion and reinstallation myself
Do you suggest deleting the port and reinstalling it?
I for sure won't delete everything. It takes way too long to recompile and i'm slowly getting sick from staring at that screen over and over again. It's a developer issue and nothing any of us has to fix. The code to support DLSS after dropping the DLL into a folder that actually makes sense has to be built in from the get-go.
You can take a copy of the save file and place it in any emulator or platform you like; that’s what I always do.
It worked for me. DLSS is working beautifully. Obviously it’s going to take time to rebuild but it seems like it’s the only workaround for the time being.
The only issue I’m having now is HDR not working but that’s a separate issue.
You need to compile the game with the DLSS or FSR4 ticked in Hookshot Builder.
any link for that or how i do it
It's in the Releases page HookshotBuilder.exe
Builder took me like 2 minutes to add DLSS, just point it to romfs and exefs in your current installation and you're done so no need to delete anything. just don't fuck with the files adding dll files and editing ini none of that is needed.
sorry what do you mean point it to romfs and exefs
Thanks for the report. Reports of the same problem are now collected in #2511, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2511 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.