Jump to content

Iihcap

PC Member
  • Posts

    43
  • Joined

  • Last visited

Posts posted by Iihcap

  1. Magnum mustache makes me think of P.I's, and P.I's like muscle cars. And muscle cars were popular for going FAST. And you know who else goes fast and themed after a car?

    Time for the fastest Vehicle on legs, now with a daring mustache fit for a cop drama! He's even got a Chrome finish and Crash safety pads for those high speed chases!

    GAUSS P.I: He's gonna capture his target, and probably run into every single wall doing it!

    0GKDKE2.png

    • Like 1
  2. Recently it seems trying to use a sigil on an operator causes the sigil to flicker and fade in a spastic pattern while moving or simply animating. This happens primarily in captura, but also occurs in planet navigation as well as the plains.
    Captura Example

    This also occurs to warframes, but at a far more rare chance. I tried seeing if there was a graphical setting causing it, but I couldn't find one.

  3. I don't have the greatest PC. I'm not crashing, but I'm pretty damn close to it each time as the game utterly consumes my RAM and framerate to render the plains.

    v7v1tCX.png

     

    Loading into Cetus puts my RAM at about 88-90%, less that at a fraction if I manage to find an Empty instance that is actually 'Empty' and not lying to me. It drops naturally in transition, but when I get to the plains? Ho' boy. First my RAM shoots back up to 90%, lots of suttering. Then the doors open, and my framerate drops to 2 and RAM goes up as high as 98% of my 6 GB rendering the whole damn map.

    On the plus side, if I weather it it'll eventually simmer down to 95-90% and my frames maintain a reasonable 20-22 FPS. This is with most of the 'fancy'  features off, 75/100 resolution scale with the mainstay functions at medium. I like DE using awful PC's to test quality, but I think the blindspot they have is their testing PC's have actual graphics cards, rather than an integrated card that can easily eat more than intended.

  4. So I'm not sure what's causing it, but lately the game has been crashing my drivers. In fact before U16 it was happening, seemingly at random in places like the Void, usually when I die. Hard for me to tell what causes it. I stopped caring by then because I stopped playing over aggravation over the support staff that isn't related to this issue. Once patchnotes said that they fixed the issues, and when U17 came out I decided to come back to it. While I didn't seem to have a driver crash for a few hours, eventually it did it again in the middle of a Tyl Regor fight.

     

    I am running the game on DX9, 32-bit. Here are my Specs.

     

    Operating System
        Windows 7 Home Premium 64-bit SP1
    CPU
        Intel Core i5 2450M @ 2.50GHz
        Sandy Bridge 32nm Technology
    RAM
        6.00GB Dual-Channel DDR3 @ 664MHz (9-9-9-24)
    Motherboard
        Dell Inc. 0YH79Y (CPU)
    Graphics
        Generic PnP Monitor (1600x900@60Hz)
        Intel HD Graphics 3000 (Dell)
    Storage
        465GB Seagate ST9500325AS (SATA)
    Optical Drives
        TSSTcorp DVD+-RW SN-208BB
    Audio
        Realtek High Definition Audio

     

    And to be clear, I get damn good FPS on the game. Warframe has always excelled at being able to run on older computers, aside from the Tyr regor fight, but it has yet to be optimized I believe. That will likely be put into order later. When the drivers crashed the game displayed nothing but a white screen, so I had to force close it. I do not think that would make a crash log for me to send in. I could play for hours at a time before U15 or so, and now here in U17 it happened right around approx 87 minutes.

     

    Update (7:53 AM August 1st): I was able to play for three hours straight today with no Driver crash, but at the same time I did not go to the Tyl regor fight throughout the whole three hours. So the crash might actually be an optimization issue with the new level.

  5. try running it in 32bit mode, and with dx9, lower resolution, and set all detail levels to low/off

    (change to 32bit/dx9 via the launcher)

     

    also make sure you drivers are updated

     

    intel IGP's arnt really good for much when it comes to gaming, so expect crashes/bugs/glitches

     

    only thing to suggest aside from that is get a better pc with a good GPU in it, then you wont suffer this kinda issue at all

     

    if ur unable to get a new pc, then search the forums to see if others have found workarounds/solutions to the same issues

     

    best of luck

     

    I have my drivers updated, I'm already running at a smaller windowed resolution with a lot of the beefier options off. And I'm complaining ABOUT DX9's causing driver crashes. If you read that you wouldn't have mentioned it.

     

    I already get 32-55 FPS standard, unless big firefights bring it to about 19-23. When the driver crash happens there is literally no change in resources whatsoever. So far I've seen either a transmission or a death screen set it off.

  6. This has been recently showing up since the DX10 Loading bug (Which I'm pretty sure still isnt fixed) Where suddenly, though thankfully rarely; when I die in missions I occasionally have a chance of suffering a driver crash. My screen blacks out, then whites out, then returns to normal. Warframe is a white screen, what was once my browser is also a white screen; and I am forced to close both.

     

    I'm not too sure what triggers this, but so far both times it's been when I died and faced the revive screen. There's no change in resources used or anything when it happens, it just...happens.

     

    http://i.imgur.com/XGTdgmY.png

  7. But what else?

     

    That only accounts for ~2,31Gb out of 6GB, which is about 39% of your memory usage.

     

    In all the numbers you've shown, Warframe barely passes 40% memory usage.

     

    Warframe and Firefox are not the only things running. There must be other things adding up.  Have you clicked "show processes from all users"?  have you added up all the other processes when you have 90%+ memory usage?

     

    I have a feeling we are both missing numbers here. In order of memory used (When warframe is up) Its Warframe, followed by firefox, then steam, then csrss/dwm/explorer, and a bunch of minor functions like svchost and the like, which take up only atleast 1-10K each. Merely starting up warframe moves me to 55-60% usage at the login screen. So it might be putting out more than thought.

  8. Run the game windowed (if needed) so you can keep track of things and see what else is using a lot of RAM.

    I have been. Only way I figured this out.

     

    Warframe is top contender at (Currently because 32-bit version of the game takes up less) 1,889,172 K followed by Firefox, which uses 435,900K. Closing firefox hardly makes a dent in the usage. More so it seems traveling back to my Liset after visiting a mission or hub causes memory usage to not purge entirely all the time. It keeps just...swelling.

     

     

    Also keep in mind we still have the memory leak. This causes WF to use up more and more memory the longer you play.

     

    Basically this.

  9. 27% usage of 6GB of physical memory would be 1.62GB, that's with WF closed so let's assume that's a baseline.  So let's assume 4.38GB in ready availability (i.e. not pushing into superfetch space).

     

    Your screenshots show, at the most, 2.4GB used by Warframe, which would add 40%, adding up to 67%.

     

    ... and even if we go outside of the percentages, just looking at the raw numbers, it's obvious that there's something other than Warframe.64.exe.  So find out what else is using up so much RAM.  Does it show up in the processes list?  You can click the headers to sort by the columns.

     

    The only other big contender for memory usage is Firefox, but the 27% is achieved when I close the game /while/ firefox is open.

  10. Let me elaborate further, since I have the statistics from the Hubs (Which by the way got a bugged trader, fyi)

     

    This was when I first started up warframe, currently in the Liset at 74% Memory usage: http://i.imgur.com/eO7Y9Xe.png

     

    This was when I entered the pluto hub, one of the lesser filled hubs to avoid getting whammied instantly. It raised to about 85% in a few seconds: http://i.imgur.com/HRHgH9T.png

     

    Fifteen minutes later, 92% Usage. Spiked at one point to 97% but lowered back down to 90% after: http://i.imgur.com/XJCtRXa.png

     

    Finally the crowning moment, waiting for the trader to arrive and never receiving it. Sitting around at 93-95% usage: http://i.imgur.com/dqeHqVF.png http://i.imgur.com/yfcHl3w.png

     

    Dissapointed by the no-show trader, I left. The game froze on me, cause apparently it couldn't trim out all that data I swelled up so I had to end the process manually while my PC was freezing up. Even after it closed the footprint it left left me stuttering for a few more minutes.

     

    Once closed, I was at 27% Usage: http://i.imgur.com/0oYQ4dP.png

  11. Uh, where are you getting these numbers?  You should be looking at Warframe.64.exe in the "Processes" list to see the actual amount of memory thast Warframe is using, not a combined total of everything else on your computer.

     

    I didn't think it was worth mentioning, but Warframe by itself takes up about 2.7m to 3m Kb in usage.

     

    When the game is closed (From the 80% usage I get on liset) my overall usage drops to 32%

  12. I couldn't help but notice prior to this content update that Warframe now takes up an unusual amount of memory.

     

    I have about 6 GB, and by standard warframe would put me to 68-72% usage, 75% at most in missions. Now since this update, I get about 77 to near 80% Usage in my Liset, up to about 85% at most in missions. And in Hubs? A staggering 94-96% usage (Though I think thats cause there might be a memory leak.) In fact I already had a driver crash in a mission earlier today.

     

    I'm not quite sure how to make a comparison of something like this, but it's certainly something I've began to notice.

     

    EDIT: Turns out this process usage amounts are linked to the 64-bit version of the game. 32-bit gives me weird stutters, but rarely goes above 80% usage, even in Hubs.

  13. It seems ever since the Mesa update, I'm unable to connect to atleast a large majority of players games. I only manage anything if the game is hosted by me, or if I happen to get lucky about it. People I used to be able to connect to now just give me a "Connection to the host has been lost" when joining. I get about halfway through the load bar before it busts, and I realize what happens.

     

    Can we fix this? More so, we can we fix this before the next 5 revisions?

  14. Same problem. I'm on SSD and a fairly powerful CPU, and it takes longer sitting in black screen before the animated load screen loads now that loading screen lasts.

     

    Went from about 5 sec load times to about 20-30.

     

     

    Running x64. Could this have something to do with memory usage optimizations for low end systems on x86?

    Quite possibly, I'm running x64 but it does this on 32 or 64 bit process. More so I play 32 because 64 doesn't hook the steam overlay properly.

  15. It seems upon launch of U15, the loading bug from U14 has come back in thicker force.

     

    Back in U14, Loadscreen hell was an apparent bug fixed with "Fixed bug related to FPS issues at the Load screen."

     

    This has returned. In U14 The loadscreen issues revolved around the game suddenly taking nearly 5 minutes to load anything if you have a lower-than-average system specs. Despite the fact that I maintained 30-40 FPS in the load screen, it was apparently 'tied to FPS' and fixed.

     

    Now it's back in U15, and somehow worse. FPS will drop to 3-5 at the start making things take 4x as long before it goes up to 30 again and loads fine. Around U15.0.5, it got worse when they tried to fix it. The loading not only lagged at start, but for a longer period and also bled out a bit of the FPS drop to the start of the mission. Now we are here, and still no fix for this Colossal issue that's persisted for far too long. I'd hate to miss out on the Hubs when they release with this issue still biting at my heels.

     

    U15.1.0 has somewhat fixed the issue. The load time is less, but still pretty bad; and more so it has now another instance of it toward the end of the load screen. I'd take a video but I cannot with this FPS drop threatening to crash the game if I do.

     

    I'll likely update this topic as hotfixes go by. (Or post, should circumstances arise)

     

    a. Which element(s) of the game are affected: All loading screens, from missions to Dojo to Liset to the starting load to Login screen.

    b. How the bug affects these elements: Triples loading times, from their previous 5-30 seconds to 50-90 seconds.

     

    EDIT 1(Nov 6th 12:01 AM): It tuns out the loading issues are linked to P2P2S connections. When I host a game and only have one party member, the lag lasts for about 5-8 seconds before it starts loading normally. More-so, when someone joins in-progress the whole game gets the same FPS drop as the loading screen showed for about 5-8 seconds again. Something might be unoptimized in the way netcode is handled.

     

    EDIT 2(Nov 20th 6:14 PM): Well we officially headbutted a corner. Clearing DL cache's isn't exactly a fix to the problem DE, in fact it causes system freezes for a lot of users including myself. You wanna know what happened the last time I cleared the cache? My comp froze up atleast 6 different times, Physical memory was pushed to 87% (And I have 6 gigs on a x64 system) and for some reason my computer control panel opened. And now you just made it happen automatically.

     

    I'm fairly certain its P2P connections now, as load speeds are extremely fast without anyone joining, but frame-rate drops from the load screen (That cause the loading issues) happen whenever someone joins that game. For the love of god if you folks read this, please look into this.

     

    EDIT 3:(Nov 27th 4:24 PM) Well it seems fixed. Mostly. Apparently the 'streaming optimization' for the game is basically just shoving all the loading in at the start of the load bar, so the game freezes up for 10-15 seconds instead of slowly being given out over time while your FPS gets mauled. Either way doesn't fix the loading bugs, but at this point I've probably just about given up. Now if only we could make that PC-slowing Optimization process no longer a thing!

×
×
  • Create New...