Nvidia Replay Turning Off

[Keri Gamrath]

sofirst of all everytime i enter a game nvidia instant replay turns off and i havent found a way to fix it

second the name of the enemies seems to be a dark red and not yellow as i set them to be

are there fixes for these issues ?

I just want to chime in and add that my GeForce Experience also stopped working recently. I have over 150 GB free on my recording drive and it works just fine in other games. Oddly enough, at least in my case, it can record while in the Overwatch menus, but the moment I load into any game, such the training grounds, both Instant Replay and the option to record video directly turns off in GFE.

Battle for Olympus update heavily affected NVIDIA users: Average PC Latency spikes to 80ms with Alt+R. (Borderless Windowed or Full Screen). The only thing helps: Turning ON/OFF V-Sync and Reduce Buffering ON, but sometimes changing the video settings leads to another bug. Also have some movement lags without FPS loss, Borderless Windowed is unplayable without V-Sync now.

Guys I think I found the solution!

All u have to do is starting overwatch from geforce experience, so close the game, open geforce experience and press play on overwatch from there, it worked for me!

I thought it was only me heh.

I was so sad when I did something spectacular in-game and that I couldn't save the replay afterwards. I noticed, as you guys already mentioned, turning shadowplay off and on again fixes it.

And I always keep forgetting to restart shadowplay each time I start Battlefield

Basically the problem is what @DeggTSK said and it is the EA APP that is messing everything up and not BF2042.

Somehow Shadowplay sees it as a videogame and tries to record the EA APP instead of games like BF2042.

I've been having this issue for a couple of months, where when I try to save an instant replay, it will just say instant replay: off, even tho it is on, and im using the save keybinds? I poked around on google and to my suprise there were numerous people reporting the same bug, on this forum, reddit etc. Even one user said he had reported this bug 10 times and the issue was still never resolved.

Maybe I can help, I had this same issue and I fixed it by doing a reset in the software. It doesn't uninstall anything, it just resets all your settings if you're willing to do that. After that I set my record settings like this. If you have any questions just ask!

I had tried all these solution just not working , Recording Desktop not even recording a sec and Instant Reply says off even it's enabled , changed all settings , 60 FPS and 30 FPS , enable Virtual Res, and disable it , all these not working and still have the same issue

any updates to Fix it ?

Hey i had this same problem, if you want Instant Replay to work or any other Relive feature you MUST reset the keybinds/shortcuts. After the first Radeon adrenalin update custom keybinds became inactive.

A couple years later... But I found the core reason! If you've tried disabling desktop recording, and changing the audio channel, and still get the "Instant replay off" message, it's because of DRM! Specifically HDPC which blocks recording if you have copyrighted material streaming, like Netflix open. It doesn't even matter if it's playing, even if it's in the background it will block AMD/nvidia etc from recording anything! The GPU manufacturers are apparently legally required to obligate to the standard. (It would be nice if the error messaged indicated this though...)

Made an account just to comment on this.

This was my issue lol had Prime video streaming NFL on the other monitor. Got a slick throwing knife kill in cod and wanted to clip it and Instant Replay was on in settings but would say off when I would try to make clips.

Closed the football game tab and went onto another site to watch it and now I can make clips again.

Didn't have to update, restart, reset, or toggle any settings.

Thanks!

While I know for a fact this can be an issue I think it might be getting false flagged at times which is incredibly frustrating as I'll know when I do it by accident, promptly go close everything then try again to record but still be met with "instant replay: Off" even though it most certainly is not. It leads me to believe that it is either incorrectly at time detecting things or there is another issue going on. Our inability to determine which is rather problematic. I considering this is now been many years it will likely never change which is even more frustrating.

this didnt answer much. does turning on instant replay just enable the action to be able to replay? Or does that actually start the instant replay? if that actually starts it, by selecting turn on, does that record the last 5 minutes? or does it start recording from that point on? you make it sound like it starts recroding from the second you turn on to the second you turn off. but thats just recording, not a replay. im more confused reading this article than i was before.

When debugging or profiling, it is important to narrow your investigation to the path that provides the most impactful and actionable data for you to make conclusions and solve problems. Nsight Graphics provides a number of tools to fit each of these workflow scenarios.

If you have determined that you are CPU bound, you will want to use a CPU profiling tool to discover how you can eliminate inefficiencies to issue work faster to the GPU. You may also want to look into the overhead of the API constructs you are using and determine if there are more lighter weight constructs that can offer the same effect at less cost. The Frame Debugger tool is an excellent resource while you are making these adjustments to your engine.

To analyze an application, Nsight Graphics requires the launching of applications through its launching facilities. The sections below describe creating a project, launching the application, and connecting to it so that you can perform your analysis.

Upon starting Nsight Graphics, you are presented with the option to create a project. If you are using Nsight Graphics for the first time, skip project creation by selecting continue under Start Activity.

Once selected, you will be presented with a target-specific dialog that allows you to configure the application to launch. Browse and select the activity you wish to run and then proceed to the target-specific instructions below to configure the application to analyze.

The target-specific sections below describe how to launch and connect on each specific platform. While the process may be different on different targets, there are many commonalities between all systems. In particular, once a process is launched, the Nsight host must attach to that process in order to analyze it. This logical separation of launch and attach facilities allows for complex use cases including remote targets, launching though command lines, reattaching to previous sessions, etc. The Nsight host does simplify many common cases, however, by supporting user-controlled automatic connection to processes that were just launched. The sections below cover these uses cases and more, in turn.

Nsight Graphics supports automatic attach to processes of interest. It accomplishes this by identifying the processes in a process hierarchy that perform graphics work, signaling that these are of interest.

In the example image above, VRFunhouse.exe is a child process of the UE4Game.exe launcher. Selecting VRFunhouse.exe and clicking Attach would allow you to analyze the primary application.

Remote debugging is supported on Nsight Graphics on Windows through use of the Nsight Remote Monitor. This is a process that runs on a target machine to allow connections to be started on that machine.

Once the monitor is launched on the remote machine, you need to add the remote monitor as a connection in Nsight Graphics. By default, launches will be done on the localhost machine. To add another machine, click the + button.

Any number of connections may be added; connections can be removed by clicking - on the selected connection. The connections may be switched between any of the added connections before launch or attach. Connections are globally persisted and may be applied to any project once they are added.

Nsight Graphics offers a command line interface (CLI) to facilitate launching on applications for which the environment setup can be complex to transfer to the host application. Currently it also provides a non-interactive way to Generate C++ Capture from a Command Line or Generate GPU Trace Capture from a Command Line).

There are also activity-specific options beyond the general options above. For examples on launching with a specific activity, as well as referencing these activity specific options, see the follow sections:

To get started, make sure you close out all browser windows. This is necessary due to the method that Nsight Graphics uses for injecting code into your application. Specifically, Chrome will tend to launch a child process from one of the other, already running processes. If that initial process is not injected, then the child process will not be either, even if you launched it from the Nsight Graphics Connection dialog. So, close out any browser windows and use Task Manager to ensure that no Google Chrome processes (or other browser processes) remain.

Optional: This flag will cause a dialog to display on launch of the graphics process, to help find the process you want to debug. Note that Nsight Graphics can typically find the process without resorting to manual intervention.

To mitigate this problem, Nsight Graphics attempts to detect processes that are known to interfere and to offer the user an opportunity (dialog shown below) to terminate the processes before launch, thereby allowing a launch without interference.

After a process is connected, it is ready to be analyzed. For many activities, a default set of windows will come up that offer an impactful set of tools for analysis that pertains to the activity. You can also add additional windows to the application by selecting a view from the menu bar. See the User Interface Reference for a detailed discussion of each view and tool window.

3a8082e126