Rivatuner osd not display in league of legends: Reddit — Dive into anything

Reddit — Dive into anything

Reddit and its partners use cookies and similar technologies to provide you with a better experience.

By accepting all cookies, you agree to our use of cookies to deliver and maintain our services and site, improve the quality of Reddit, personalize Reddit content and advertising, and measure the effectiveness of advertising.

By rejecting non-essential cookies, Reddit may still use certain cookies to ensure the proper functionality of our platform.

For more information, please see our
Cookie Notice
and our
Privacy Policy.

Get the Reddit app

Scan this QR code to download the app now

Or check it out in the app stores

Go to pcmasterrace

r/pcmasterrace

Welcome to the official subreddit of the PC Master Race / PCMR!
All PC related content is welcome, including build help, tech support, and any doubt one might have about PC ownership.
You don’t necessarily need a PC to be a member of the PCMR. You just have to love PCs. It’s not about the hardware in your rig, but the software in your heart!
Join us in celebrating and promoting tech, knowledge, and the best gaming and working platform. The PC.

Members

Online

•

HarDingus

MSI OSD Is NOT Showing No Matter What I Do. Any Suggestions?

So MSI/RTSS’s OSD legit doesn’t work at ALL for me… well the «show own statistics» option in RTSS does but that’s merely a framerate counter I think. I did EVERYTHING correctly, downloaded and redownloaded Afterburner/RTSS countless times, rebooted several times as well, spent hours searching and NOTHING works. I thought it was a Steam problem at first but it turns out it doesn’t work in any of my other games either. This is extremely infuriating as I see all these tutorials where people literally have it work with no problems whatsoever, sometimes not even putting hotkeys in for the OSD and it works just fine for them… I don’t understand why it won’t work for me. I don’t know if it’s my GPU but that doesn’t make any sense as it works swimmingly well with everything or just bad luck with software/compatibility issues. Is there anything I might be missing or does the MSI OSD just not work with some systems (which also makes zero sense as I have an MSI GPU) and if so is there any other OSDs I can use that aren’t MSI? Any help is greatly appreciated.

Archived post. New comments cannot be posted and votes cannot be cast.

Precision X/Afterburner don’t show OSD and/or FPS on certain games

JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.

I can’t seem to get either program to display the OSD on certain games (BF3, Crysis 2, etc.), whereas it works on others (Source Engine, Aion, etc.) The G15 LCD always displays the information though, but on games where the OSD won’t display, it doesn’t show FPS either. This used to work back on my HD6990 though.

Also, Fraps displays FPS fine. But I’d like to just use Afterburner and keep it simple. I also like being able to determine if a game is using DX9/10/11 again. Any ideas on how to resolve this?

Save

1 — 20 of 22 Posts

Have you tried uninstalling and re-installing?

Save

Yes, I’ve tried a fresh install of both drivers and Afterburner and/or Precision X.

See less

Save

The OSD doesn’t work on 64bit apps. Is what you’re running 64bit?

Nevermind. I see that it should work with your list.

Save

Bring up the Rivatuner settings and make sure that the OSD location is not out of the viewing area for the games you are having problems with.

Save

It’s on the default position so it shouldn’t have any problems. Nobody else is having trouble having the OSD display on Crysis 2?

Save

Are you using any type of shader based enhancements (injectFXAA, SMAA, etc.) and the latest MSI:AB (2.2.4) ?
If so, you must create a new profile for that game in RTSS (big + sign, and select the game executable) and check Enable compatibility with modified Direct3D runtime libraries.

See less

Save

Go into the onscreen display settings and try changing the Display rendering mode to Vector 2D.

Save

Quote:

Originally Posted by EVGA-JacobF

Go into the onscreen display settings and try changing the Display rendering mode to Vector 2D.

Click to expand…

I am having the same issue as OP. But, I am running 64bit applications (BF3, FC3, etc..)

Did anybody try the suggestion above? I tried everything else I could find and the only thing I can get to work is Fraps. One would think that by now 64bit applications should be pretty well universally supported by overclocking software.

Save

Well, the OSD in Rivatuner doesn’t support 64bit apps yet so FRAPS is the only way for now.

Save

So is everyone just using 32bit applications in their 64bit operating systems to get the OSDs to work?

Save

Since when do you think that BF3 or FC3 is a 64bit app???

They are all 32bit LOL

And NO, we aren’t using 32bit applications on our 64 bit OS’s just to get a working OSD.

Only a few games are with 64bit executables and there’s no real demand for AB or PrecisionX to make their OSD to work with them.

See less

Save

Quote:

Originally Posted by Sebi

Since when do you think that BF3 or FC3 is a 64bit app???

They are all 32bit LOL

And NO, we aren’t using 32bit applications on our 64 bit OS’s just to get a working OSD.

Only a few games are with 64bit executables and there’s no real demand for AB or PrecisionX to make their OSD to work with them.

Click to expand…

Thanks for the witty comebacks hotshot

God forbid you guys take it easy on a clear newbie. Where else am I suppose to ask these questions? Maybe Jeeves would know perhaps?!?

So, why then is either OSD not working in either game? I have followed all the applicable instructions I could find

See less

Save

Quote:

Originally Posted by Mreim76

So, why then is either OSD not working in either game? I have followed all the applicable instructions I could find

Click to expand. ..

I had this trouble once with Crysis 2 — what my workaround was at the time was to switch the display from full screen to windowed in the game setup options after launching it, and then immediately back to full screen before starting a game. It just wouldn’t launch on its own with OSD enabled for some reason.

Save

Reactions:
1

Quote:

Originally Posted by stahlhart

I had this trouble once with Crysis 2 — what my workaround was at the time was to switch the display from full screen to windowed in the game setup options after launching it, and then immediately back to full screen before starting a game. It just wouldn’t launch on its own with OSD enabled for some reason.

Click to expand…

Interesting, I will give that a shot when I get home tonight.

Reply

Save

Like

@ Mreim76
Hey, chill man, I was a bit sarcastic after seeing your post (#11) and looking at your avatar. I apologize for that.
It’s funny in some way, I thought that you’re staring at your monitor in the same manner like «that guy» in the pic.

Back to topic:
AfterBurner (or PrecisionX) has problems to show the OSD whit any kind of overlay. Are you using any?
But there are quite a few options to overcome that. It happened to me too in a few games, when I used some type of post process against aliasing (injectFXAA, Danoc’s inject FXAA, SweetFX, etc.)

First, did you configured your MSI:AB like this?
http://imageshack.us/photo/my-images/24/osdh.jpg/

Second, MSI On-Screen Display server is running in the taskbar?

I suggest to uninstall MSI:AB, delete all remaining data from that, restart your puter and reinstall (latest Afterburner 2.3.1)
Start from scratch and tell us what are your settings and with which game. I assume with BF3 and FC3…

If we are unable to help you, you’d better not ask the Jeeves… you should ask Unwinder, but please be polite and do a search before that.
I’ve done that and it didn’t came up anything relevant.
There aren’t known issues with the OSD, the problems reported by the users are usually, guess what: user errors.

Take care and report back.

See less

See more

2

Reply

Save

Like

Reactions:
1

I tried both of your ideas and still nothing. I am using «Very High» settings on both as my 670’s can’t quite support Surround on Ultra at all times. I have added every possible .exe I could find that was related to both BF3 and FC3. I have even tried both Precision X and AB individually as well as simultaneous with various settings on and off. Can you see why I am frustrated?

I was being sarcastic about Jeeves

Edit: No overlays either

See less

See more

1

Reply

Save

Like

In order to have OSD, the RTSS.exe process must be running — that process is dependent on Windows Event Viewer service. If that service is inactive, then you have a problem.
Please check (Ctrl+Alt+Del -> Task Manager) if you have the eventlog under the Services tab!

Here is my RTSS config for BF3:
http://imageshack.us/photo/my-images/688/rtss.jpg/

See less

See more

1

Reply

Save

Like

RTSS.exe a running process and my RTSS config looks exactly the same. What else could it be?!?!

Reply

Save

Like

Well, I’m reaching for **** now, but there’s a checkbox for enabling compatibility with modified DirectX runtime libraries in the OSD. You click on the wrench button to access it.

Reply

Save

Like

1 — 20 of 22 Posts

This is an older thread, you may not receive a response, and could
be reviving an old thread. Please consider creating a new thread.

Engine Error in Apex Legends. Fixing the Error — Guides

In this article we will try to fix the Engine Error in Apex Legends.

Apex Legends PC players are reporting crashes during a match. Often, the failure is displayed with an Engine Error (DXGI, CreateTexture2D, or CreateShaderResourceView) error message. This manual will discuss how to resolve these errors.

Engine Error 0x887A0006 — DXGI_ERROR_DEVICE_HUNG
Application device failed due to malformed commands sent by the application.

Engine Error CreateTexture2D
Failed to create texture _rt_updateddepth #0 #1 with HRESULT 0x8007000e: width: 1024 height: 1024 mips: 1 copy: 1 im gFormat: 0x29 flags: 0x1080000

Engine Error
CreateShaderResourceView in Gfx_TextureAsset_ResizeAndCopy failed in (no debug name) with HRESULT 0x887a0005.

Method #1 to fix Engine Error

Origin may install the game itself incorrectly and a simple reinstallation of the game helps the user. To do this:

Open Origin on your PC.

Click Game Library on the left panel, then select Apex Legends.

On the Apex Legends screen, click on the gear icon, these are settings. It is located right below the play button.

Select restore from the list of options in settings.

Please wait while the restore process is completed. Once this is done, it is advisable, but not required, to restart the computer.

Try to play a match in Apex Legends. The crash issue should be resolved after restoring the game via Origin.

Method #2 to fix Engine Error

One user of the English EA forum solved the problem by disabling overlay, other applications and downgrading the Nvidia Graphics driver to version 417.71.

Overlay is software that displays an overlay on top of other windows. For example, displays FPS, CPU temperature, Origin in game, Asus GPU Tweak II, MSI Afterburner, Aura for ASUS, RivaTuner OSD, RivaTuner statistics. If you have any of these, try disabling them before launching Apex Legends.

If your computer has Nvidia Graphics Driver 418.81 installed, try downgrading it to version 417.71.

Link to the official NVidia website.

You can also try temporarily disabling voice communication programs: Skype, Discord, etc., and if the game still freezes, then go to the task manager and disable everything that can consume a lot of RAM.

After you disable overlay and install the Nvidia Graphics 417.71 driver, restart your computer and try playing a match in Apex Legends. The Engine Error should resolve itself.

Other methods

If the above options did not help, it would also be useful:

Lower the graphics settings in the game.

Set the display mode to Windowed or Windowed Borderless from the in-game graphics settings menu.

Run Apex Legends troubleshooting compatibility test. Right-click on the desktop shortcut of the game and select troubleshoot compatibility issues from the context menu.