Eternal
-
Posts
276 -
Joined
-
Last visited
Posts posted by Eternal
-
-
This is a long time running problem for the past few years now, I'm personally not sure why or how it happens but the fix is pretty simple. You'll have to download Display Driver Uninstaller (DDU) to uninstall your gpu driver and get a proper fresh install of your graphics driver. There's plenty of guides online to figure out how to use the tool if at any point you get stuck but it's fairly straight forward, downloads are available from guru3d and wagnardsoft but I'll post the link to guru3d as it's more accessible https://www.guru3d.com/download/display-driver-uninstaller-download/
I will say I usually notice the problem more with people using AMD gpus but doing that fresh install of your driver should completely fix this for you.
As another side note, directx10 support ended a number of years ago now, so yeah it's definitely a strange bug
-
4 hours ago, Avrael_Asgard said:
But your chat stays the same? Are you on 2k or 4k? I cant imagine only me having this problem if other people notice the loading screen weirdness too. Well at least that tells me its probably not on my end... which means i cant do anything about it. c':
Oh no, the chat does get moved for me as well about half way up the side. I'm on 3440x1440 on 1 monitor.
-
Just want to add to this real quick, I switched back to dx11 just to test it out and got another one of these crashes, this time I actually have log files. Unfortunately they don't show much of anything. Happened from alt tabbing in borderless windowed mode sitting in orbiter
Event viewer shows a generic nvidia driver crash, similar to it being "not detected" because the driver crashed
And here the EE log shows about the same but it makes me think it is a dxgi swapchain issue
Spoiler2388.929 Gfx [Warning]: D3DAssert: Dx11GpuStats::CreateQuery(D3D11_QUERY_TIMESTAMP_DISJOINT) returned 0x887A0005 (The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.)
2388.933 Gfx [Warning]: D3DAssert: Dx11GpuStats::CreateQuery(D3D11_QUERY_TIMESTAMP) returned 0x887A0005 (The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.)
2388.933 Gfx [Warning]: D3DAssert: Dx11GpuStats::CreateQuery(D3D11_QUERY_TIMESTAMP_DISJOINT) returned 0x887A0005 (The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.)
2388.933 Gfx [Warning]: D3DAssert: Dx11GpuStats::CreateQuery(D3D11_QUERY_TIMESTAMP) returned 0x887A0005 (The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.)
2388.933 Gfx [Error]: Dx11TextureMgr::Present() failed, hr = 0x887A0005
2388.933 Gfx [Error]: Present failed; device removed: DXGI_ERROR_DEVICE_HUNG
2388.946 Gfx [Warning]: ResetDriver called on: Dx11Driver
2388.947 Gfx [Info]: Dx11 Driver FailureSo I'm going out on a whim here and saying this is likely an issue with using Optimized Flip Model Presentation in the dxgi swapchain for dx11. Again using these exact same settings I haven't had a single crash inside of dx12.
-
6 hours ago, Avrael_Asgard said:
Update, i can now say that the chat places in the middle, most times, on at least 2 occasions: Right after i log in, and in loading screens. And just now i noticed it concious for the first time, cause i just rawdogged the loading screen without looking at my other monitor, like i normally do. The tip-text in the top left started glitching a bit and switching from bigger to smaller font constantly really fast, like changing from 2k to 4k resolution and back, like it couldnt decide what to use. Which would fit my problem perfectly.
Still no idea why it happens to me and seemingly noone else, or what to do about it. I now just know that its at least partially caused by the game itself.
I actually was thinking about this just yesterday since you had me noticing it more often now, yeah it seems like the entire window size actually resizes within loading screens into a small corner at the top left. You can see it happen in real time if you're hung up on a loading screen because of a slow (console) host. The only thing I can think of is how warframe handles scaling or it may be a strategy to boost loading times when the game hasn't readied the mission yet? Mostly conjecture coming from me but I would be curious to find a solution to this as well, seems to happen more frequently inside of dx11 for some reason
-
You're seeing the animation and resource updating as you "feed" the helminth, but you're not FINALIZING the feed. If you don't press the "Feed" button at the bottom right after you're done selecting your resources it's not actually consuming the resources and giving helminth resources. I make the same mistake sometimes where I'll just press back on my mouse and it hasn't actually consumed anything, just make sure you press the button in the future 👍
-
1
-
-
8 hours ago, RLanzinger said:
To @Eternal,
DX11 is not faulty, it is a bit more limited.
- DX11 use one CPU, more ram but DX12 can use multiples CPU and dedicate more to the GPU.
- DX11 Linear GPU tasks (lightning/texture) per frame where DX12 can use multiples tasks for different features.
- ...
With higher resolutions and higher FPS/setting, DX12 which is newer can handle more than IF you gpu support it.
On the counter part DX12 can have some problems : "The reason for FPS drop and stuttering is that the game engine tries to use all the CPU cores at once, and if your PC doesn’t have enough power, it will drop frames " that means some players had to change their power source for a bigger one OR use more power supply wire (yeah some Dumbo did only use one Y power wire for a rtx4090 🤦♂️).
Not saying dx11 is inherently faulty, it’s just that the issue exists only while using dx11. There’s always gonna be some api specific bugs, especially with a game like warframe that has more than 1 available to use. Unfortunately it is difficult for them to track it down, they don’t have any crash reports of this, the game just brings you to the faulty hardware page when it happens.
Also, dx12 stutters from shader compilation, not from using all your cores at once or anything. Once your shader cache has been built up the stuttering goes away. Games don’t have asynchronous shader compilation yet so the main render thread has to abruptly stop to wait for a new shader to be rendered.
-
6 hours ago, RLanzinger said:
To @Alex_Nos and ee,
There could be multiple reasons so First try to ensure what IS the problem...
- Make shortcut "C:\Windows\System32\perfmon.exe /rel" name it Performance Monitor reliability. This give you program/windows crashes details since ONE MONTH.
- You can use ProcDump too
- (optional for advanced geek) : You can also use ProcDump if warframe crash but not your OS,
- Get the logs in launcher after a crash,
- Submit a ticket with all those files above
There can be multiple reasons, so far I did see :
- XMR ram or Intel Overclock not working correctly
- Video Driver's (To Update or before-last update)
- Game Update fail : Verify+Optimize twice can solve,
- Problem with DX11, ok with DX12... -_-;
- DUST, yeah the I must clean my graphic card and ram (that was mine)
- Windows "Game mode" was ON.
- Frequent Alt-tabbing with Fullscreen make crashes => Borderless Screen (got this one too)
- ...
I think it’s all but confirmed that it’s an issue solely in dx11 mode. I’ve even seen it affecting people inside of Linux using dxvk proton. I’ve been using dx12 again for the past month now and I haven’t had a single crash again where it was happening at least once every couple days before. New system, no mem issues, bios and drivers are up to date, totally stable on my 7800x3d and rtx4090
-
1 hour ago, PaarthurnaxDovah said:
Have a second monitor so that's a no-go as my cursor would go off the screen
Warframe actually does have mouse constraint, the only time it doesn't is when you free the cursor in a chat window. So why not give it a shot?
-
Have you tried starting the game in windowed fullscreen then? If the problem goes away by switching to windowed fullscreen then you could just use windowed fullscreen. Turning on optimized flip model presentation eliminates any latency and essentially just makes it better than exclusive fullscreen in every way. If it still does it even after switching then I’d start looking elsewhere
-
Interesting to see oodle already has documentation on this specifically, I still think that was one of the best updates they did for this game 😁 Updating the bios and turning off Enhanced Multicore Performance should be all you really need to do though, latest bios version has added the stock turbo power limits in by default, turning off Enhanced Multicore Performance just makes sure it's not bumping your core ratios past x55 and having the bios automatically adjusting your voltage further for the higher speeds. If you still have crashing that's when you'd want to turn to tweaking in XTU and limiting clock speeds etc but your 13900k would have to be pretty worn out for that to be the case
You can find the latest bios version F11f for your motherboard here, I'm sure you know how to but if you don't there's plenty of guides out there on how to flash your bios https://www.gigabyte.com/Motherboard/Z790-AERO-G-rev-10/support#support-dl-bios
-
Common problem with 13th and 14th gen intel cpus on z790 chipset motherboards. Go into your bios and disable “Enhanced Multicore Performance”. I’m assuming you’re on dx11 as well, when it’s loading you’ll notice it maxes out a core momentarily, likely spiking your cpus voltage for single core turbo speed and subsequently crashing. So you could try and see if dx12 will help with that as well as it evens out the workload across more threads.
I would also suggest looking to see if gigabyte has a new bios version for you as well. The intel power crashing issue is more of a recent find, you’ll see articles about it everywhere though.
You can read more into it here if you’re interested https://www.techspot.com/review/2836-intel-cpu-crash-baseline-spec/#:~:text=About a month ago%2C we,systems to avoid stability problems.
Good luck, hopefully that does the trick for you
-
1
-
-
I think you’re on the right track there, I would guess the same thing. I think this is just an issue in general with windows scaling in full screen applications. I’d start by making sure you’re not using full screen mode in warframe, you need to use borderless fullscreen, then turn on optimized flip model presentation in the settings as well. Specifically with exclusive fullscreen when alt tabbing, windows will “rescale” on the fly and occasionally it will set the bounding box to be a lower resolution ie your other screen. Same reason with older games when you increase the resolution the mouse won’t move to the edges anymore, it will just stop like the mouse hits a smaller window.
Good luck
-
Per the wiki
Refraining from Mercy killing a lich candidate will remove their weapon from the pool of potential lich weapons until each has been refused, but only if the mission is completed. Weapons rejected from aborted missions will remain in the current cycle.
Best way is Cassini Saturn Capture, you have to make sure they DESPAWN before you extract and you can't quit the mission early. If you don't do both of those you aren't using the mercy system
Good luck
-
dx12 works much better in general in warframe, I run protonge with dx12 and never had any real issues
-
Unequipping and re-equipping the warframe will solve the issue
-
This might sound silly but have you tried unchecking the fullscreen button in the game launcher before attempting to start the game? Also are you trying to use dx11 or dx12 through dxvk or vkd3d respectively?
-
You actually are infected with a cyst, the first 24 hours after infection you just won't see it. I think with the ephemera on it just assumes it to be at full size (7 days). Which is why you don't see it on your warframe but you do on the silhouettes.
-
Glad it worked for you 🙂
I have a sneaking suspicion it might be related to something with dx11 that's relevant even on windows. Few other people (including myself) are having crashing issues on dx11 since Dante update. I had swapped because of the visual issues I was having on dx12 were annoying me but after switching apis it started having hard crashes pointing me to a page about faulty hardware etc. But switching back to dx12 has proved to be very stable, just not in regards to the flickering issues on lighting and ui (not sure if that is present in linux).
But GE releases have always worked much better for me on warframe with my steam deck in general, cheers.
-
2
-
-
Thought I'd post this here real quick but the temporal prime ephemera isn't taking custom colors atm, the energy colors work but the orbs are stuck at default colors
-
1
-
-
Just bought PA, new ephemera doesn't take colors, they're stuck at the default, energy colors do work however
-
I've seen playstation user threads requesting gyro for a long time in warframe, I do like the option of having gyro, it's nice on switch. You could make a feedback thread of some sort though, I think that's really the best you're gonna be hoping for unless some other 3rd party tool or steam input gets updated to have both working.
-
3 hours ago, The_Mustachio said:
This is funny. I've come back to the game after a year hiatus. My game crashes every 10-20 mins now using DX11. Before my break, I had ~10 crashes going all the way back to 2015 across 2 different PCs.
Using DX12 has fixed the crashes, but now I get the menu flickers. Better than crashing I guess ¯\_(ツ)_/¯
Using a RTX 4080 with AMD 7900X on Windows 10 (posting for posterity)
Yeah I thought recently I'd start using dx11 again myself since I got tired of the visual glitches in dx12, I could live with the slower load times but man I started having a couple "hardware" crashes in warframe a bit too frequently that I never get with dx12. Back on dx12 again for the past couple weeks, I suppose I'll be living with the flickering too lol
I've got a 7800x3d and an rtx 4090, still wondering if cards older than 2000 series are affected, I have a friend with a gtx 1080 that swears he doesn't have this problem but it reamins to be seen if he actually doesn't or hasn't noticed it.
Some kind of update on this would be really nice, its been a long time issue
-
You should try using protonGE. I haven't tried out Proton 9 bleeding edge yet but you can get Glorious Eggrolls Proton8-32 release that includes most of the stable release fixes with updated dxvk and vkd3d commits. I've personally been using dx12 mode with glorious eggroll proton versions and its worked far better than proton experimental or proton 8.0-2 in warframe, never crashed anywhere. You can get the release here to try out or what I recommend is using ProtonUP-QT to just install it for you from a simple drop down list, you can find it in the steamdecks arch store https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton8-32
-
2
-
-
Adaptive triggers only work in native mode, maybe that will change in a future steam input update that can passthrough the adaptive trigger api data but until then you're faced with that choice unfortunately. Personally I'd go for the adaptive trigger support 🙂
Zenistar Disc Range Mods Don't Work.
in PC Bugs
Posted
They did change how range mods work with melee 3.0 so it’s now a static +x meters from each mod. Just keep in mind that only primed reach, spring loaded blade and riven stats can affect the disc range. So I guess depending on the riven it’s likely a max of about 10.5 to 11m? But yeah zenistar has been hurting real bad for a long time now, it’s sad tbh