Jump to content

Kamachi

PC Member
 View Profile  See their activity

  • Posts

    498

  • Joined

  • Last visited

 Content Type 

Posts posted by Kamachi

    In-game FPS Cap not working Windows 10 May 2020 Update

    in PC Bugs

    Posted · Edited by -Alleluia-

    2 minutes ago, [DE]Linkski said:

    Hi again,

    After some extensive testing with the Windows 10 May 2020 update, we believe we've found a solution to this problem, and we have just updated Warframe with an improved frame-rate limiter that should result in much more consistent numbers moving forward. It has been added with Hotfix 28.0.5, so you should see better results the next time you launch the game.

    More info on this hotfix can be found here.

    -----------------

    • Optimizations:
    • Implemented a new version of the frame-rate limiter to fix problems introduced with Windows 10 Build 2004 as noted here. The new limiter should be compatible with all versions of Windows and should provide an even more consistent framerate when your system can run at the max.

    I can confirm it's working as intended following the hotfix and I have updated the original post to reflect that this has indeed been addressed.
    My thanks to the team for the fairly quick turnaround in finding a resolution. 👍

    • Like 1

    In-game FPS Cap not working Windows 10 May 2020 Update

    in PC Bugs

    Posted

    On 2020-06-11 at 8:03 PM, [DE]Linkski said:

    Hi everyone,

    Just an update: I can confirm that we have been able to reproduce this issue, and it does appear to be related to Windows 10 version 2004. Unfortunately, we do not yet have a solution, but I can assure you that we are in the process of tracking down the culprit now.

    We'll try to get this fixed in a timely manner. Sorry for the inconvenience!

    Thanks for the heads up 👍

    Update 28: The Deadlock Protocol

    in PC Update Notes

    Posted

    2 hours ago, LordAsmolicious said:

    One unmentioned change found, to the Commodore Prime operator outfit, its colour scheme has been turned entirely black, with the colour options only affecting a few small parts on the outfit itself now. this has broken my fashion frame, but just quickly reportin it! 

    Indeed, they've turned one of the best Operator suits into pure garbage. 🤦‍♂️

    • Like 1

    The Deadlock Protocol: RELEASING JUNE 11!

    in PSAs and Announcements

    Posted

    What really boggles my mind is that it was only a few weeks ago during a stream with Megan that Rebecca was going on about how DE need to do better especially in terms of communication after the various disasters such as Railjack and Kuva Liches. 

    Fast forward a few weeks from then and DE have reverted back to their old bad habits.

    I'm also getting sick to death of people making excuses for DE, their lack of communication and continual delays far predate the usual excuses players throw out on DE's behalf. 

    As others have mentioned a very simple post on the forums from a member of staff keeping the playerbase up to date on a rough ETA would be much welcomed by a large proportion of the playerbase, it would legitimately take them seconds, mere seconds. 

    • Like 10

    The compromise to make Riven Mods less random

    in General

    Posted · Edited by -Alleluia-

    23 minutes ago, ArchSyker said:

    Hello there,

    the topic of Riven Mods has probably been talked to death, but i have an idea that doesn't change the way Rivens are currently handled, while adding means to make them more viable by reducing the randomness with a trade off.

    My idea involves the much wanted "stat locking", but with a twist. The twist is that once you lock a stat (even after unlocking it again) the riven mod becomes untradable. Meaning that that riven will stay on your account, unless sold/transmuted/etc. I wouldn't even mind if locking a stat costs a high amount like 50k kuva and/or doubles the rerolling cost per locked stat.

    Also with locking a stat I mean the "name" of the stat" not the number and some wishful thinking, it would be nice that the more kuva you pump into that riven the closer the stats get to the maximum possible value (similar to valence transfusion).

    That way an compromise is achieved, because player now have 2 choice:

    1. either they roll rivens like they can now, meaning going full random and potentially getting that "got tier roll" and make big plat or
    2. the option i propose, where a player has a semi-progressive way to getting his dream riven -which that person can do for his own use- with more work than luck

    This would be perfect and a sensible compromise.
    People who enjoy the heavy RNG of rivens (If those people even exist) would be able to continue to roll and sell/buy as they can now.
    Whereas people who would prefer to work and put in the time and effort to attain a specific set of stats on a riven would be rewarded after a hefty investment of both time and kuva. Honestly the only real losers would be the so called "Riven Mafia" and I'm fine with that personally as they are a tiny minority of the playerbase. 

    Unfortunately I cannot see DE ever implementing such a common sense solution because Rivens are basically indirect loot boxes that provides an incentive for people to purchase platinum. 

    • Like 1

    cloud walker sleep

    in Warframes

    Posted

    Let's be real, the only reason they made Wukong fun was to sell his Prime Access and now that that's finished with he'll be forgotten about. Such a shame as he was such a joy to play and still is albeit less so than before. 

    In-game FPS Cap not working Windows 10 May 2020 Update

    in PC Bugs

    Posted · Edited by -Alleluia-

    21 minutes ago, Contiguous said:

    Bump, because after updating to windows 10 2004 (may update) i started experiencing the same issue. I usually have 165hz on a gsync monitor. Now it is capped at 60~65fps for no reason. Nothing I did could fix it. 

    And warframe is the only game where I experience this issue. I also play Forza Horizon 4 where I got a major increase in FPS (80~100 to 120-140). Where did things go wrong?

    Thing I've tried: Changing compatibility settings, double checking nVidia control panel settings. Checking game mode whether there's a difference while disabled (none). Reinstalling my nVidia drivers. 

    I don't know what else to do frankly, besides rolling back. I find it silly however to do a rollback to the previous version while it is in fact one of the most stable updates Microsoft has pushed so far, looking back at their previous updates this past half year that just broke the OS. I hope this gets attention soon.

    It must be the Windows 10 2004 update causing this issue then, as it was the only thing changed on my PC from one day to the next. I didn't even force the latest Windows 10 update, it was brought to my attention via the usual windows update. 

    Edit: The workaround I've found is to set the FPS in-game to Unlimited and then limit your FPS with MSI Afterburner or whatever tool of your choice, not an ideal solution but it somewhat works. 

    In-game FPS Cap not working Windows 10 May 2020 Update

    in PC Bugs

    Posted · Edited by -Alleluia-

    Since updating Windows 10 to version 2004 the in-game fps cap is not working as intended and will limit my fps to a lower value than what is selected, for example if I select 120 FPS as the cap the FPS will be limited to 65.
    The fps cap only works correctly when v-sync is enabled which isn't ideal as many players such as myself prefer to use g-sync or freesync as opposed to v-sync.

    Things I've tried that have NOT worked.
    Reinstalling Warframe
    Reinstalling Steam
    Clearing the Appdata Folder
    Reseting all in-game settings to default
    Updating/Reinstalling my graphics card drivers (AMD)
    Disabling Game Mode within Windows 10
    Disabling Full Screen Optimisations within Windows 10
    Disabling Variable Refresh Rate Option via Windows 10 Graphics Options

    Workaround;
    Setting the in-game FPS Cap to unlimited and then capping your FPS with a third party tool or your Graphics Card's manufacturers software.

    Edit: This issue has been fixed as of the 17th of June 2020 deploying with hotfix 25.0.08
    My thanks to DE for the speedy resolution of this issue.

     

    • Like 3
×
×
  • Create New...