My GPU is only using one PCI-E lane... and I have no idea how to fix it or if it's even fixable.

[ӕolus]

So if you run another game it works at 2.0 x16?

Well, what I meant was that I'm not experiencing any other debilitating frame rate issues in any other games.

Out of curiosity, I just ran Battlefront with GPU-Z running to see if my GPU was working at 2.0 x16.

Nope. It still reads PCIe x16 2.0 @ x1 2.0

So I don't think this issue is limited to Planet Coaster. I'm just not experience similar issues with other games.

are you Running the render test when taking the screenshots??? cuz it wont say its highest speeds unless a graphic load is applied...just making sure..its happened before in the past with others asking same question

Sorry. In the last screen I posted, the render test was not running. I'll post another screen in a moment while running the render test.

 

[ӕolus]

 

[jboydgolfer]

i think someone else will need to help You, im unable to even understand what the issue is, best of luck with this , and i hope your next thread is under better circumstances .... Welcome to TPU.

 

[ӕolus]

I think earthdog is on to something here. If it works in other games, then it is not detecting this as a game needing full power.

You need to manually force it.

open the nvidia control panel

Go to 'Manage 3D Settings'

'Program Settings' tab

Find the .exe for the game having issues

Find the Feature 'Power Management Mode'

Set it to 'Prefer Maximum Performance'

Apply

Fixed.

Thanks for the suggestion. I tried it, but unfortunately Planet Coaster is still running at 10-20 fps.

 

[EarthDog]

Sorry for not sorting through the other threads you linked..

..but have you tried using CCleaner or DDU to wipe drivers clean then install the latest version ?

 

[Aenra]

Beyond me too; the first GPUz pic you posted here showed something going wrong at least, i mean something to focus at
The second one eliminates it, lol

Since however you actually -do- experience this elsewhere too as you just mentioned, i'd really take it off in your shoes, have a good look (flashlight if necessary), then resit it.

 

[ZenZimZaliben]

Well then now it is time to narrow it down. If you have a spare PCIE video card..install it and see what it says. If it fails then its the motherboard...IF works then it is the 1060.

 

[Vya Domus]

For my board if I change the CPU base clock it will switch to PCIe 2.0 1x and stay there regardless of any other PCIe related setting in the BIOS. So I suspect as well this is something to do with the BIOS , I haven't looked through all the comments but I suppose you did try to load default settings ?

 

[ӕolus]

Sorry for not sorting through the other threads you linked..

..but have you tried using CCleaner or DDU to wipe drivers clean then install the latest version ?

Yes, I tried that.

Beyond me too; the first GPUz pic you posted here showed something going wrong at least, i mean something to focus at
The second one eliminates it, lol

Since however you actually -do- experience this elsewhere too as you just mentioned, i'd really take it off in your shoes, have a good look (flashlight if necessary), then resit it.

I resat it again as you asked. I was as careful and deliberate as I could muster... but GPU-Z still says "PCIe x16 2.0 @ x1 2.0"

Out of curiosity, what does "take it off in your shoes" mean? I'm in my slippers, so perhaps I made a catastrophic mistake.

 

[ӕolus]

For my board if I change the CPU base clock it will switch to PCIe 2.0 1x and stay there regardless of any other PCIe related setting in the BIOS. So I suspect as well this is something to do with the BIOS , I haven't looked through all the comments but I suppose you did try to load default settings ?

I have indeed tried this. I loaded the default settings in UEFI and unfortunately it had no effect.

 

[Ferrum Master]

Could you take pictures of your GPU pcie slot parts. Both sides... I have a feeling about missing parts.

 

[Vya Domus]

I have indeed tried this. I loaded the default settings in UEFI and unfortunately it had no effect.

At this point to me the only thing left to blame is the motherboard slot, it wouldn't be the first time I have heard of partially broken PCIe slots causing similar issues. If you are willing to do it maybe try an OS reinstall , all kinds of weird issues I have seen being fixed by this , including some that I have encountered which I could not figure out for the life of me.

 

[INSTG8R]

I'm gonna take a left here and ask have you installed the latest chipset drivers for your Motherboard?

 

[xorbe]

What are the gpu clocks while the offending game is running? Post screen cap of MSI AB chart.

spool up your CPU: Control Panel -> power -> max perf -> cpu min 100%

spool up your GPU: nv cp -> 3d settings -> prefer max perf (not just one *.exe)

If both of those maintain top clocks, and MSI AB chart looks good, then something is tweaked in your PC setup, malware, etc.

 

[Jetster]

Whats your heaven 4.0 score at max settings 1080

Or is it just the one game?

 

[jaggerwild]

Try a different PCI-E Slot.

 

[Jetster]

If its just the one game then it must be coding right?

 

[dorsetknob]

Try a different PCI-E Slot.

OP only has one PCIx16 Slot and one PCIx1 Slot

1 x PCIe 2.0 x16, 1 x PCIe 2.0 x1
so kind of pointless trying other Slot

 

[ӕolus]

Well then now it is time to narrow it down. If you have a spare PCIE video card..install it and see what it says. If it fails then its the motherboard...IF works then it is the 1060.

I just reinstalled my old Sapphire Radeon R9 270and ran a render test. It reads:

Out of curiosity, I booted up Planet Coaster with my old graphics card installed. And guess what?

The game runs perfectly.

So doesn't that rule out the possibility that the motherboard is the issue?

And wouldn't this also rule out that my PCI-E lanes are the issue, here? I'm getting the same @ x1 2.0 reading with my Radeon R9 270 as I got with my GTX 1060, and the game works fine.

Is it possible I'm getting a misreading from GPU-Z, and I'm actually running at x16 2.0? I've read elsewhere that GPU-Z has given people inaccurate readings on this exact topic.

 

[revin]

I'd do a fresh install just to eliminate any other issue before the dreaded thought of a bad card

 

[ӕolus]

If its just the one game then it must be coding right?

Honestly, that's what I've suspected from the very beginning. That the game itself is just poorly optimized.

But don't bring that up with Frontier devs because they'll flip out and basically tell you you're an idiot.

I'm gonna take a left here and ask have you installed the latest chipset drivers for your Motherboard?

Yes, all my mobo drivers are up-to-date.

I'd do a fresh install just to eliminate any other issue before the dreaded thought of a bad card

A fresh install of what? The game? Because I've tried that, like, 10 times.

The GPU? I've resat the thing maybe a dozen times now.

 

[revin]

@aeolus could you go ahead and fill out your system spec's it's too hard to back track to find them Thanks

Windows

A fresh install of what? The game? Because I've tried that, like, 10 times.

The GPU? I've resat the thing maybe a dozen times now.

 

[EarthDog]

Please dont triple post.. add to your posts with the edit function... mods will get ya!

 

[ӕolus]

@aeolus could you go ahead and fill out your system spec's it's too hard to back track to find them Thanks

Windows

I've actually done that already. I was originally running Planet Coaster (and encountering this PCIe issue) on Windows 7.

Someone suggested upgrading to Windows 10 because it was possible the game would run better.

So I shelled out the cash and I did a clean install of Win10. But it didn't affect either the game's performance or the PCIe issue.

 

[ZenZimZaliben]

I've actually done that already. I was originally running Planet Coaster (and encountering this PCIe issue) on Windows 7.

Someone suggested upgrading to Windows 10 because it was possible the game would run better.

So I shelled out the cash and I did a clean install of Win10. But it didn't affect either the game's performance or the PCIe issue.

So the issue is with the code. The developers and support will not admit it. Pretty clear they didn't optimize it