Optimization issue... [Fixed, kill LCore.exe!]

[Chang]

https://dl.dropboxusercontent.com/u/2340974/MetroLL_optimization.png

CPU: i7 3770k @ 4.5GHz
GPU: 2x GTX 570 in SLI with 320.14 drivers

Very High settings. Vsync off. SSAA off, Physx on, Tess Normal

25FPS with around 30-35% being used on each card INDOORS.

edit:

WTF! I've been stumped with my 30fps and it freaking turns out to be an issue with Logitech Gaming Software (LCore.exe)... Closed it and my FPS triples... WTF! Now what to do... I don't want to be using my G19 and G700 without LGS...

Might just be some weird issue with using LGS and an SLI configuration that is somehow conflicting with MetroLL and wouldn't affect those with a single card.

edit:

Looks like it might be something that 4A needs to fix. http://forums.logitech.com/t5/G-Series-Gaming-Keyboards/Lcore-exe-Causing-Issue-In-Metro-Last-Light/m-p/1032485/highlight/true#M29368

Anyone know how to contact 4A?

[-=]Bradza[=-]

oh man turn off v syc ingame its crap. when its on it drops to 30-60 fps. v syc off 60-75 fps :D

[-=]Bradza[=-]

oh and i take back my last commet on sli it does help fps when your not locked by v syc

[Dungeoncrawler69]

Something that might help low to mid range gpu users:

change the ’r_api #’ value that is located in the %APPDATA%\Local\4A Games\Metro LL\(numbers)\user.cfg file. In order to run the game under DX9, PC gamers will have to change it to a 0 value. For DX10 they’ll have to change it to 1 and for DX11 to 2. It’s ironic but with this workaround - and despite the company’s claims about the game’s DX11-only renderer offering a better overall performance - PC gamers can run Metro: Last Light in DX9. Not only that, but DX9 comes with a huge performance boost, meaning that this option will be ideal for all those with low-end DX10 GPUs.

[deadbc77]

3770k@ 4.5ghz with GTX Titan max settings 25 to 35fps. 1080p res...with v-sync off,and lastest beta drivers.

[KenpoJuJitsu3]

โพสต์ดั้งเดิมโดย Freyar:

Logitech won't push an update to fix this issue, since they've essentially abandoned software support for their G-series stuff (which they no longer develop in the first place.) Sadly, the ball is in the Metro dev's court.

โพสต์ดั้งเดิมโดย Freyar:

โพสต์ดั้งเดิมโดย GW2|CD|Craziplaya.2103:

Uh, no they have not abandoned LGS, it was just updated a few weeks ago.

My software reports no update available.

http://www.logitech.com/en-us/support/g13-advanced-gameboard?osid=14&bit=32

Title: Logitech Gaming Software
Software Version: 8.46
Post Date: 27-APR-2013
Platform: Windows 7
File Size: 55 Mb

Unless it was abandoned very recently they are still updating LGS.

[Freyar]

So does the newest version of LCORE fix this problem? Or is it still conflicting?

Pardon me while I eat my hat. I'm not particularly happy with the direction Logitech has gone, and frankly, I'm surprised they pushed an update in the first place.

[Chang]

โพสต์ดั้งเดิมโดย Freyar:

So does the newest version of LCORE fix this problem? Or is it still conflicting?

Pardon me while I eat my hat. I'm not particularly happy with the direction Logitech has gone, and frankly, I'm surprised they pushed an update in the first place.

Nope, I was already using the latest LGS when I had this issue with metroLL

[Cheechako]

Killing LCore had no impact on my performance. It could be a combination of LCore and the specific HW.

I own a G105 keyboard (no fancy display) and an F310 controller, although I did not have the controller plugged in at all while playing MLL. Rocket Fish mouse and simple headhones plugged into the on-board headphone jack - so no other Logitech components.

[Dungeoncrawler69]

I posted this problem at the logitech support forums. Anywho the newest version of the software is 8.46. I'm running version 7.0 on another computer and it doesn't have the frame-lock issues so it might be version specific? The version before 8.46 suffers the issue also. However it might be tied-in with a particular gpu hardware configuration? Here is the thread link at logitech.

http://forums.logitech.com/t5/G-Series-Gaming-Keyboards/Lcore-exe-Causing-Issue-In-Metro-Last-Light/td-p/1031483

edit - srry, my other pc I referenced with no issues is running a g15 keyboard, not the newer g19.

[Chang]

Looks like it might be something that 4A needs to fix. http://forums.logitech.com/t5/G-Series-Gaming-Keyboards/Lcore-exe-Causing-Issue-In-Metro-Last-Light/m-p/1032485/highlight/true#M29368

[MIK]

This helped me quite a bit. now im running maxed (without ssaa) at 60-75 fps on my 580 sc

[Flyingbox]

โพสต์ดั้งเดิมโดย -=Bradza=-:

oh and i take back my last commet on sli it does help fps when your not locked by v syc

... You seem to not know what VSync does or why it exists. It FORCES a lock to 60fps to stop screen tearing. Only use it if you see tearing that really bothers you. If not then don't turn it on. If you don't know what it does then don't turn it on. It's NOT a "high performance" graphic option--It's aesthetic.
VSync is only necessary if you can keep a constant 90+ FPS when the feature is disabled as that is when bothersome tearing is seen.