#Can't clip
9 messages · Page 1 of 1 (latest)
Seeing the same here.
The issue is caused by the ? in the name. Nvidia automatically puts the game name in the recording file name. (So a recording created through Nvidia recording/instant replay would look like RV There Yet? 2025.12.30 - 19.22.10.03.DVR.mp4 for example.
Since the name of the game is RV There Yet?, this causes it to fail to save the file as Windows does not allow the ? character in file names.
Nvidia should be removing this character from the game name (like how they remove the trademark or copywrite symbols from other game names, so this is more of an issue on the Nvidia side.
Previously the game was called Ride before the nvidia driver profiles updated to use the actual game name, and thats when this issue started.
I have the same issue! I can’t record anything in game with the Nvidia overlay.
For your point about the question mark, I believe Nvidia automatically strips it
The issue is actually that Nvidia is not stripping the question mark for some reason (but yeah it’s supposed to).
I’ve been able to fix the issue on my end using Nvidia Profile Inspector with these steps:
-
In NVPI, search for and select the “RV There Yet?” profile
-
In the top menu bar, choose the option to export the current profile and save it as a .nip file somewhere. You’ll have to edit the file name to remove the question mark as well to save it.
-
Then use the option in the menu bar to delete the profile and then close NVPI
-
Open the exported profile in a text editor and change the name near the top from “RV There Yet?” To “RV There Yet” and save.
-
Open NVPI again, and choose the import profile option in the menu bar and select the edited .nip profile
After doing that recording has worked fine through the overlay
Wow wow wow, you are goated for this
Thank you so much
Nvidia still fixed nothing though, ty for solution, worked on me
Thank you so much! It worked.
Still hurts that I've lost clips of some of the best gaming session with my buddies that I captured last week
I had the same issue. Thank you so much for the solution! Now it is working perfectly for me too. 😃