The forum

Hello, I have the same error using a geforce 970.

Every approx 5 seconds i get:

fixme:wbemprox:client_security_Release 0x7d18ad6c
fixme:win:EnumDisplayDevicesW ((null),0,0x4e5dfd8,0x00000000), stub!
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:wbemprox:client_security_SetBlanket 0x7d18ad6c, 0x4a94e88, 10, 0, (null), 3, 3, (nil), 0x00000000

almost the same as bouki.

Intel® Core™ i7-2600K

GeForce GTX 970/PCIe/SSE2

Manjaro Linux 64-bit

running nvidia 346.59 driver 

fixme's are not errors though

Tango, are you noticing a stuttering with the fixme messages as well or just the messages?  A quick drop in framerate that bounces back up?

yup, very brief fps-drop and lag. And it seems to be synchronous to the fixme messages. 

I have not been able to test to see if the error occurs in other games, but it is at least very obvious (and anoying) in LoL. 

err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.

This error is interesting, not sure what it means, but its Nvidia related.

    /* Recent (304.64, possibly earlier) versions of the nvidia driver only
     * report a DFP's native mode through RandR 1.2 / 1.3. Standard DMT modes
     * are only listed through RandR 1.0 / 1.1. This is completely useless,
     * but NVIDIA considers this a feature, so it's unlikely to change. The
     * best we can do is to fall back to RandR 1.0 and encourage users to
     * consider more cooperative driver vendors when we detect such a
     * configuration. */
    if (only_one_resolution && XQueryExtension( gdi_display, "NV-CONTROL", &i, &j, &ret ))
    {
        ERR_(winediag)("Broken NVIDIA RandR detected, falling back to RandR 1.0. "
                       "Please consider using the Nouveau driver instead.\n");

 

totally unrelated to the problem though

Thanks Petch

Its always a guessing game for me when it comes to League of Legends.

So I clicked Configure->Wine tab->Configure Wine.  Then on the graphics tab, check the box that says "emulate virtual desktop" and enter your full screen resolution (in my case, 2560x1440).

Then when I start the game I run "fullscreen" in LoL under 2560x1440.  Running fullscreen under this "emulated" desktop seems to remove the stutter.

 

The downside is of course lower FPS overall because of the higher resolution (for me) but the game is smoother for sure.

 

Can any one else confirm this workaround?

 

Thanks,
Aaron

I use virtual desktop for every single game in Wine.  So this is a good solution.  As for high resolution... you could run it lower at 1920x1080 and probably get better frame rates.

are you still getting the stutter every 5 seconds?

Unfortunetly this does not seem to fix it for me. Are there any other changes from the default POL installation you have made bouki?

 

/TANGO

I managed to fix this by setting the following in Display Settings:

• GLSL Support : disabled
• Direct Draw Renderer : gdi
• Video Memory size : 4096 (Should match the gfx card size)
• Offscreen rendering mode : fbo
• Render target mode lock : disabled
• Multisampling : disabled
• Strick Draw Ordering : default

FPS is still much lower than what i would like from a gfx card such as mine, but the lag is gone and the game is playable. :)

Did you set these all at once or did you try them one at a time?
I'm asking because maybe one of them actually made a difference.

I've never disabled Multisample before or Render target mode lock.

You may want to investigate so we know exactly which one did the trick

Same issue, setting a virtual resolution does not work for me and gdi raises a DirectX error and I can't launch the game (client works fine). The error below is raised every 5 seconds and causes a noticable stutter in otherwise awesome performance. I really want to get this working, I am so close. I have tried multple versions of Wine and Play On Linux (POL) none have fixed the issue. Any ideas?

​fixme:wbemprox:client_security_Release 0x7d73e9f0
fixme:win:EnumDisplayDevicesW ((null),0,0x9e2dfc8,0x00000000), stub!
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:wbemprox:client_security_SetBlanket 0x7d73e9f0, 0x4f048d80, 10, 0, (null), 3, 3, (nil), 0x00000000

Try switching some of the display settings in PlayOnLinux Configure like TANGO did... He seemed to find a solution there...

• GLSL Support : disabled or default
• Direct Draw Renderer : gdi or opengl
• Video Memory size : 4096 (Should match the gfx card size)
• Offscreen rendering mode : fbo
• Render target mode lock : disabled or default
• Multisampling : disabled or default
• Strick Draw Ordering : default or disabled

I finally managed to play a little around with the settings.

Changing the Direct Draw Renderer to opengl returned the stuttering/lag for me. 

While i dont have the lag, i still have fps drops, occational missing effects and rubberband-lags. But the game is much more playable without the stuttering. :)

I'm also getting this exact problem.

Changing the DirectDrawRenderer to gdi makes the game crash, and the other options don't affect anything. Also tried using the emulated desktop to no avail.

Are you all getting these errors?

xrandr12_init_modes Broken NVIDIA RandR detected

I found this post and the person who replied suggested disabling the IncludeImplicitMetaModes option

There is a chance this is related to Nvidia drivers, Wine and screen resolution.

 

Are you all getting these errors?

xrandr12_init_modes Broken NVIDIA RandR detected

I found this post and the person who replied suggested disabling the IncludeImplicitMetaModes option

There is a chance this is related to Nvidia drivers, Wine and screen resolution.

 

Quote from booman

 How do I create a debug log? I have the impression that that's happening to me too. I'm using the 346.59 driver from the official repos on Ubuntu 15.04.

I'll switch the drivers to an older version and report back.

Edited by curti21

when you launch any game, click "Debug" instead of "Run"

This will produce a window that outputs all of the err: fixme: and crash information