Jump to content
Temporary sub-forum for Update 30: Call of the Tempestarii ×

Recommended Posts

On 12/10/2016 at 6:51 AM, Neo_182 said:

 

 

@[DE]Glen Can we get confirmation what the issue above with Neo is what we're looking for? 

Just a passing observation; a lot of people with issues seem to be running GTX 1000 series GPU's in tandem with skylake CPU's, where others with GTX 1000 gpu's are paring them with Haswell CPU's. Don't know if there is a correlation, but in Neo's case above, i'm not aware of there being much, or any, PhysX particles on Jupiter (but im likely wrong). It may help narrow down what to look for. It's seemingly hit or miss atm, even for 1000 series owners.

Additionally, is it specific to Nekros? I see a lot of people running nekros, but i don't know if this is just because the video in the op also had a nekros and people are merely trying to replicate like for like.

Link to post
Share on other sites
59 minutes ago, MillbrookWest said:

@[DE]Glen Can we get confirmation what the issue above with Neo is what we're looking for? 

Just a passing observation; a lot of people with issues seem to be running GTX 1000 series GPU's in tandem with skylake CPU's, where others with GTX 1000 gpu's are paring them with Haswell CPU's. Don't know if there is a correlation, but in Neo's case above, i'm not aware of there being much, or any, PhysX particles on Jupiter (but im likely wrong). It may help narrow down what to look for. It's seemingly hit or miss atm, even for 1000 series owners.

Additionally, is it specific to Nekros? I see a lot of people running nekros, but i don't know if this is just because the video in the op also had a nekros and people are merely trying to replicate like for like.

900 series cards also have seen this issue so it is also related to them, I have seen skylakes with the issue and not, same goes for the haswells.
Its more like a fluke and not sometimes its hard to say for glen at least what it is even at this point I think.

Chao, The Roaring Lion

Link to post
Share on other sites
1 hour ago, Neo_182 said:

I needed neural sensors and decided to do the testing there and try narrowing what the problem may be by eliminating overlays and programs as i continued thru the week.

What was the trigger on the Corpus Jupiter tileset though? I know Infested use PhysX in abundance, i'm not too sure what Corpus unit uses any PhysX. Or indeed, if physX is even used at all. It obfuscates the matter a bit if we're looking for problems with physX but the problem lies elsewhere. Unless the video was highlighting an overlay being the problem?

I can't really say too much about the issue. I apparently don't suffer from it, and can only go off of what people are describing and what's been posted in videos.

For example, in your video, up until ~39 mins, you are rocking 130-140fps, however, after a certain SotD summon (not spawn) around 39:15 your framerate tanks to 120-130 almost immediately, and never comes about recovering. Watching at half speed, there is seemingly no evidence of any physx particles.

Just looking for a bit of clarification. 

Link to post
Share on other sites
50 minutes ago, MillbrookWest said:

What was the trigger on the Corpus Jupiter tileset though? I know Infested use PhysX in abundance, i'm not too sure what Corpus unit uses any PhysX. Or indeed, if physX is even used at all. It obfuscates the matter a bit if we're looking for problems with physX but the problem lies elsewhere. Unless the video was highlighting an overlay being the problem?

They're definitely rare on Jupiter with Nekros but there are a few -- some of the Moas' sparks are. When re-running with more PhysX-FX heavy scenes (Infested vs Vauban) Neo was able to repro much more quickly.

Link to post
Share on other sites
2 minutes ago, [DE]Glen said:

They're definitely rare on Jupiter with Nekros but there are a few -- some of the Moas' sparks are. When re-running with more PhysX-FX heavy scenes (Infested vs Vauban) Neo was able to repro much more quickly.

Awesome, will try running missions with a Vauban to see if non-1000 series GPU's are in anyway affected, or if anything come to light that may be relevant. @TheRoaringLionsays he's seen it with 970's, hopefully can cause an effect on my end. 

Link to post
Share on other sites

not exactly the GPU you asked for, but on a few occasions vs infested and on 1 occasion against corpus while i was using mag I had huge performance drops on a GT940m

dropped from 70 - 80fps to 15 - 18fps this happened when I had used mag's second ability on a group of chargers and a frost used snow globe at the same time this stayed until

when i returned to the liset however. I had lower frame rates from what i normally had when standing near the nav panel.

the problem fixed it self when i restarted the game though.

not sure if i completely missed the point of this thread though.

specs: GT940M 2gb

           windows 10 64bit (updated with all MS updates to date)

           background programs: steam, origin, nvidia geforce experience, intel rapid storage, SCM( quick launch functions)

          driver ver: 376.19 (started on previous version 369.)

         I also have every set to max setting and most options like physX on 

I don't have this recorded though :/

Link to post
Share on other sites

@Romiith was kind enough to send me a series of dumps from his testing but sadly they didn't turn up a smoking gun.

If you are one of the unlucky few that can reproduce it maybe peek at NVSMI and see what else is running maybe there's a clue in the process list there?

C:\Program Files\NVIDIA Corporation\NVSMI>nvidia-smi.exe

Mon Dec 12 11:19:03 2016
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.70                 Driver Version: 375.70                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name            TCC/WDDM | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 980 Ti WDDM  | 0000:01:00.0      On |                  N/A |
|  0%   44C    P8    25W / 275W |    382MiB /  6144MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 980 Ti WDDM  | 0000:02:00.0     Off |                  N/A |
|  0%   44C    P8    23W / 275W |     96MiB /  6144MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      3952  C+G   C:\Windows\system32\Dwm.exe                  N/A      |
|    0      6340  C+G   ...Visual Studio 14.0\Common7\IDE\devenv.exe N/A      |
|    0      7164  C+G   ...x86)\Google\Chrome\Application\chrome.exe N/A      |
+-----------------------------------------------------------------------------+

Sorry for mangled formatting -- preformatted text isn't supported in this forum software yet.
 

Link to post
Share on other sites

Normally I'm good with glitches and other related shenanigans, but this one is throwing me for a loop.  Nvidia 860 here.

 

I ran the test Saturday afternoon and could not reproduce the bug, then I tried it again by launching Warframe from Steam and DID reproduce the bug.

Thinking that this was weird but could be a possible cause, I tried again three hours later (again from Steam).  Could not reproduce the bug.  Launched without Steam.  Reproduced the bug.

Understandably confused, I tried again last night after doing a raid (it was normal LoR if that somehow makes a shred of difference) from a non-steam launch.  Reproduced the bug, and my frame time was 10ms higher than the last two times I had reproduced the bug.

 

Each time I ran this test, the only other programs I had open were 8 chrome tabs and MS Excel (it was a decently large spreadsheet full of Warframe-related data, so I thought it would be appropriate to leave it open).

According to a constantly-running subroutine I have up that takes a consistent 1.3% of my computer's processing power, my CPU usage spiked from 33% to 81% for approximately two uninterrupted seconds that roughly corresponded to the post-mission loading screen after finishing Apollodorus.

No idea if any of this nonsense will help, since it's confusing me to no end, but hey, data data data.

Link to post
Share on other sites

trying to reproduce it even though I'm not affected. I've got a GTX 1080 and a GTX 970m to test with.

Note to all those who are effected. Just a question, but are you experiencing any oddities with performance in any of your other games? Similar drops in performance over time? Or is it just warframe.

Link to post
Share on other sites
7 minutes ago, OfficerBeepsky said:

trying to reproduce it even though I'm not affected. I've got a GTX 1080 and a GTX 970m to test with.

Note to all those who are effected. Just a question, but are you experiencing any oddities with performance in any of your other games? Similar drops in performance over time? Or is it just warframe.

I do. whenever Share is enabled (Geforce experience 3.0 or higher) Tom Calncy's Division will crash due to input switching (pressing a controller button and then keyboard) and from my test so far it also causes the current issue with warframe. (for me at least) I ran 2 hieracon runs, first 2400 cryotic with share on and it slowed down to 24-30 fps while the second game (3200 crytic, share disabled) was a stable 60 fps with the exact same groups (2 vauban, 2 frost).

I haven't been able to do any more tests since they take up lots of time but I suggest you try doing them with share on/off. It may not be a 100% reproducable bug from what I read but it has given me some hope at finding it.

I'm keeping my share on for now to see if it happens again though I will most likely not be doing long runs again. By the way, yes the fps stayed low in the liset too.

All this on latest drivers and software with a 1080 (see my previous post for exact specs)

Link to post
Share on other sites
On 10.12.2016 at 11:31 PM, Lerzu said:
Spoiler

 

  1. GPU: GTX 1050 Ti
  2. OS: Windows 10 64-Bit
  3. Nvidia Driver Version (376.09)
  4. FT Before: ~4ms
  5. FT After about 20 minutes of sitting: ~21ms and still rising
  6. Programs Running: Steam, GOG Galaxy, GeForce Experience, Firefox, Waterfox, MSI Afterburner

After countless unsuccessful tries, I decided to install GFE and use the same settings as shown in those screenshots and the bug finally happened. With Instant Replay on, my performance keeps getting worse even while sitting at the starting point, looking at the floor. After walking around the Orbiter and being amazed by how much my framerate stutters, I noticed that scenes where the GPU video engine had to work harder to encode the video, the lower my GPU power dropped. Then turning to look at something that's easy to encode made the power rise again, but it never went back to full power. Even after turning off the background recording it still keeps getting worse, though maybe not as fast. Starting the game with Instant Replay already off keeps everything working perfectly so the overlay from GFE shouldn't cause any issues.

The weird part is that this has happened to me before without GFE. I often have a video playing on the second screen and that uses the GPU video engine so maybe hardware accelerated videos are at fault? I'll look at some 4k and 8k videos to see what happens.

Welp, nothing happened with those videos.

 

  

A small update to that. I got the latest driver (376.19) and Win10 also decided to update right after and I haven't been able to reproduce the bug since, no matter how much extra I try to throw at my GPU. But since 1050 Ti is a low-mid tier card it might not be possible to get the bug, the one with GFE recording in the background causing GPU to lose power probably had nothing to do with Warframe and was fixed with 376.19... or the Win10 update fixed something relating to power management.

Edited by Lerzu
Link to post
Share on other sites

I find it curious that Windows Update fixed it for Lerzu and that Neo_182 is having problems reproducing it now. Maybe the rest of you that are having problems can run Windows Update manually and see what happens?

Link to post
Share on other sites
6 hours ago, Lerzu said:

A small update to that. I got the latest driver (376.19) and Win10 also decided to update right after and I haven't been able to reproduce the bug since, no matter how much extra I try to throw at my GPU. But since 1050 Ti is a low-mid tier card it might not be possible to get the bug, the one with GFE recording in the background causing GPU to lose power probably had nothing to do with Warframe and was fixed with 376.19... or the Win10 update fixed something relating to power management.

Well it's not background recording. It's the Share overlay (which includes the recording feature) that is causing it for me. Turning share off completely fixed it for me (so far, haven't played a lot since then yet). I did get the issue on driver 376.19 but windows 10 has not attempted to update yet for me. I'll keep playing with share enabled after the update happens and hope it will be fixed that way.

Link to post
Share on other sites

Perhaps everyone should run a System File Checker:

Open an Admin rights Command Prompt or PowerShell and run: sfc /scannow. If there are errors that can't be repaired run:  dism /online /cleanup-image /restorehealth and verify again with sfc /scannow.

...Win update might also have removed some form of malicious software.

Edited by cx-dave
Link to post
Share on other sites

Hi Hi! I know you guys were aiming for mostly high end cards but I thought as a good way to help with finding out if it IS Windows 10 related or not might be to offer my often volitile rig's output. I've frequently had graphical issues after both Nvidia updates and Windows 10 updates, but within the last 2 weeks no out of the blue driver issues or bad preformance. You probs dun wanna know how many clean reinstalls I've had to do for my graphics card drivers after updates.

  1. GPU Model: Geforce GT 740m
  2. Operating System: Windows 10 Home 64 bit, most recent update
  3. Nvidia Driver Version: 376.09
  4. Frame Time Before: 16.6/16.7ms (it skips between the two constaintantly)
  5. Frame Time After: 16.6/16.7ms (it skips between the two constaintantly)
  6. Programs Running: Steam (with overlay), Firefox, Kaspersky Anti-Virus and that's about it. I've long since kicked GeForce Experience off my rig for causing a LOT of issues, likewise with things like the Xbox app and its associated capture software.
  7. Borderless Fullscreen is enabled.

Welp, ran for 40 mins on Apollodorus with the majority of settings on (including Physx) and with vsync off. Behaviour of my card was not abnormal at all, so I hope this can at least count towards the possiblility of 'If it was Windows 10, the update fixed it'. Welcome to the life of 'did that Win10 update break something or not?'

Link to post
Share on other sites
10 hours ago, Neo_182 said:

That's what seemingly was causing issues on my end. Has the recent windows updates fixed it for you too or are you still able to get the game to a bad state?

No, my game has been running flawlessly for pretty much as long as I can remember. If you refer back to my original post, the test results conclude that my frame time did not change at all (AKA I was not able to reproduce the problem.) I just posted the results since Glen stated in the OP that you should post your results even if you are unable to reproduce the bug, in order to get an idea of how frequently the bug occurs.

Link to post
Share on other sites

Win10 and Nvidia had new updates, I got them both and my performance is dropping again. I haven't actually used GFE for a few days now as I was hoping to catch the bug I've had before without GFE, I got nothing. Now with GFE installed again (and recording) the frame-times are getting pretty long. Before I uninstalled GFE the recording was working fine and not decreasing my performance but now it is doing it again? It's so weird. Might as well post my system info again.

OS: Windows 10 Pro x64 (1607, 14393.576)
CPU: i5-3570k OC'd to 4300MHz
GPU: 1050 Ti 4GB of VRAM
Driver: 376.33
RAM: 16GB
Game settings: Borderless Fullscreen at 1080p, all settings maxed but AA and AO are off.
Frame Time before: 5ms
Frame Time after: 29ms
Handles and Commit size have remained the same during this.
Background programs: Logitech Gaming Software, GeForce Experience, Steam, Task Manager, Resource Monitor. Only after the frame-times had started increasing did I open Firefox for this thread.
Not 100% sure what my starting frame time was as I got the Christmas decorations and moved to the back room for the test but it's usually around 5-6ms.

Here are all the programs that are currently using the GPU:

Spoiler

 

| NVIDIA-SMI 376.33                 Driver Version: 376.33                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name            TCC/WDDM | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 105... WDDM  | 0000:01:00.0      On |                  N/A |
| 30%   42C    P0    39W /  75W |   1498MiB /  4096MiB |     22%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0        76  C+G   Insufficient Permissions                     N/A      |
|    0      1136  C+G   C:\Program Files\Mozilla Firefox\firefox.exe N/A      |
|    0      4152  C+G   ...ost_cw5n1h2txyewy\ShellExperienceHost.exe N/A      |
|    0      4248  C+G   ...indows.Cortana_cw5n1h2txyewy\SearchUI.exe N/A      |
|    0      5084  C+G   ...teamapps\common\Warframe\Warframe.x64.exe N/A      |
|    0      7088  C+G   ...VIDIA GeForce Experience\NVIDIA Share.exe N/A      |
+-----------------------------------------------------------------------------+

 

You can see from that how the GPU is not being used properly. I used procdump on Warframe in case that is still needed.

Link to post
Share on other sites

just to confirm:

Still having the issue with the latest windows 10 update. Also updated drivers today but it did not help sadly.

1 Hieracon run to 1600 cryotic and frame time is already down to ~24ms (from ~16 with V-sync on).

As stated before I am running a GTX 1080, i5 3570K, 16GB of DDR3, driver version 376.33 and geforce experience version 3.2.0.96.

Nvidia Share enabled. Haven't had the issue yet with it disabled.

Link to post
Share on other sites
1 hour ago, [DE]Glen said:

Ok -- not my problem then! I would invite you to discuss this with an Nvidia support forum then.

 

Sorry for asking but English is not my native language. With this do you mean the issue (for me personally) is separate from your thread here and I should contact Nvidia or are you saying it's not up to you to fix it and we are talking about the same issue (the gradual performance loss over time)

Link to post
Share on other sites
4 hours ago, Neo_182 said:

Doesn't sound like the issue they are chasing unfortunately.
If the Nvidia overlay causes problems Glen suggests you discuss it in the Nvidia forums.

Thanks for the reply. I was pretty sure it was the same issue since it shows the same symptoms as described in the post. After a certain amount of time the frametime starts dropping noticeably and stays there, even in the liset. So if it is related somehow I suggest you guys keep it in mind just in case. It's an Nvidia related issue after all and it wouldn't surprise me if this had something to do with it.

Anyway I'll unfollow the thread from this point onward since I've been told to contact Nvidia instead, so if you decide to reply please quote me so I can see it.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.
×
×
  • Create New...