Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Yes, I have maxed it to only get 144fps due to having a 144hz monitor
what you encounter can have multiple reasons.
if you are a client on someone elses game, it might be that the host-toaster is rather on the weak side and can't handle the job - or the host is busy with otherthings, or it's network connection is too busy/crapy.
is it happens to you when you are the host, or playing solo, then of course the above reasons might also be applyed to your machine, but this, you would normally not be unaware of and it wouldn't be occasionally spikes either. it could be though, that your rig is doing something in the background which clog your network or eat up you cpu/gpu time. this should not be happen (normally) but some silly updater that love to run in the background still do the homecalling/update routine even if the system is running something that uses most resources atm. and if it aren't legit applications, then it could alwasy be some nasty maleware that uses your computer for crypto mining, as a spam-bot or as part of a attack-botnet for things like ddos.
what i can sya without looking into your system, is that your specs are more than enough to run warframe at highest without any problems. but... you might want to test about running the game NOT from your kingston SSD. run your OS from it, which is good, and maybe (if you create a different partion for it o the SSD) your pagefile too, but i always refrained from running anything that will do a lot of file-tranfere due to pack/unpack operation from archieves (which is pretty much the way all modern games are build into these days). modern day SSDs should be working better with this and shouldn't get the drop of transfer rate like the first and 2nd generation had, but old habits die hard - and you can't never be sure too...
anyway, parting the operation system, the pagefile and the rest of the "working" programs from each other is a much better way to go (even though with SSDs you won't get the "fragmentation" problem anymore).
so, what you can do is checking your system for unwanted guest (which you should do regulary anyway), and do so from a clean system that you booted from a optical disc or an usb-stick (google around for further instruction if needed - ther are a lot).
you can then (if all is clear in your OS) start using analysis tools to log the behaviour of warframe and also of your own privat network and your uplink to the internet. a good working set of program which can do most of this you can get from microsoft/sysinternals link: https://technet.microsoft.com/en-us/sysinternals/bb842062.aspx
the programs process monitor (procmon), process explorer (procexp), tcpview and autoruns are the best starting point to work with - again, you can find a lot of "how-to-use" manuals in the net if needed.
even with windows own command shell you can find out a lot of things but it is a bit bothersome at times.
in the end, there is no clear answer to your question and you will need to do a good bit of detective work yourself to root out the problem.
happy hunting!
Thank you for your message! The issue was fixed by me using uncapped framerate and changing my monitor settings to 60hz (144hz kept on lagging and causing issues), also, the latest NVIDIA update is causing major issues for my 144hz monitor in general with flashing and stuff, it's defo not my monitor as I rolled it back and I never had an issue. So I'm just going to keep the current update at 60hz until I see it's been fixed (for me, at least). But thank you for your message, I appreciate it dude