Pr1nce
-
Posts
104 -
Joined
-
Last visited
Posts posted by Pr1nce
-
-
Phew! I thought I'm the only one. I have the exact same problem as well. I can see my fps dips every 1- 2 seconds or so from 60 to 50 ish. Weird thing is, I tried playing around with my RAM clock speed from 3200 to 3400 Mhz and it seems to temporarily alleviate the problem. That is... until I open another application like a browser or Discord and BAM! it happens again.
-
I had an issue with FPS as well and finally fixed it after some experimenting here and there. Not sure if the issue is similar to anybody else on this thread, but I was having fluctuating fps as soon as I load WF. My fps would be 60 (don't have a 144hz monitor) and it dips to 35-ish every 2 seconds or so. My system specs are (it's a new rig that I just put together about 3 weeks ago):
CPU: i7-8700K @3.70Ghz (non-OC to have stability and baseline reading)
RAM: Corsair Vengeance 32GB
GPU: Geforce GTX 1080 ti
OS: Windows 10
I tried setting graphic configs to low, vsync on and off, verified cache, uninstall/reinstall WF and GPU driver, etc. Nothing works. I finally decided to take a look at my bios settings instead and realized my RAM frequency is defaulted to a mere 2133Mhz and realized silly me. So I just bump that up 3200Mhz which what my corsair vengeance sticks are rated for. Load up the game, and voila. Everything is smooth as butter now. I hope this information helps a bit to give a different perspective to investigate your issue.
-
17 hours ago, kai661xbox said:
I think it's the particles. Turn them off and go from there. Turn the quality to low.
Tried that.. still the same and also tried switching everything to low.
I tried installing it on my mid-tier gaming laptop
CPU: i7-7700 HQ @2.8Ghz
RAM: G.Skill Ripjaws 16 GB
GPU: Geforce GTX 1050 ti
OS: Windows 10
Set it at max graphic settings and it ran smooth as butter with native resolution although capped at 60 FPS. Still it never fluctuate at all after playing on it for an hour or so. Can't determine whether it's the CPU/GPU compatibility with the engine or... WF just works better if your rig isn't that advance for the engine to fully utilize your hardware.
-
CPU: i7-8700K @3.70Ghz
RAM: Corsair Vengeance 32GB
GPU: Geforce GTX 1080 ti
OS: Windows 10
Having similar symptoms as the rest over here are facing. FPS would constantly fluctuate between 60 - 40 in game. Tried clean GPU uninstall/reinstall, redownload the game, turning off Physx. Nada. This happened after Sacrifice update.
I run much more demanding games without a hitch. Not sure what's going on with this update.
-
FINALLY! I found the solution to the problem!
I know I late but I just found out about it.
Ok. This is assuming that you are sure that there is no strict NAT issue on your side and the necessary Warframe ports are opened to you.
For me, the issue is related to the MTU settings.
Try to double check your MTU within your router settings (mostly around the WAN settings). If your MTU has too low of a value, it will cause the problem that you all are (might be) facing now. Usually, the default MTU value is at 1440. You can try tweaking your MTU to get the optimal speed for your bandwidth by using the command below in Windows Command prompt:
ping [replace with any website address] -f -l 1490
If you see results such as "Packet needs to be fragmented but DF set.”, reduce the value by increments of +/-10 (eg. 1490, 1472, 1462, 1440, etc) and keep repeating the pinging process till you achieve a successful ping response without the "fragmented but DF set" in the results.
After that, you add 28 to the value that you have utilized for the successful ping response. This 28 is to allocate for the packet size IP/ICMP header. So your optimal MTU settings would be something like this:
1412+28 = 1440
Take that value and configure it to your router and hopefully it would solve your issues as well.
-
FINALLY! I found the solution to the problem!
I know I late but I just found out about it.
Ok. This is assuming that you are sure that there is no strict NAT issue on your side and the necessary Warframe ports are opened to you.
For me, the issue is related to the MTU settings.
Try to double check your MTU within your router settings (mostly around the WAN settings). If your MTU has too low of a value, it will cause the problem that you all are (might be) facing now. Usually, the default MTU value is at 1440. You can try tweaking your MTU to get the optimal speed for your bandwidth by using the command below in Windows Command prompt:
ping [replace with any website address] -f -l 1490
If you see results such as "Packet needs to be fragmented but DF set.”, reduce the value by increments of +/-10 (eg. 1490, 1472, 1462, 1440, etc) and keep repeating the pinging process till you achieve a successful ping response without the "fragmented but DF set" in the results.
After that, you add 28 to the value that you have utilized for the successful ping response. This 28 is to allocate for the packet size IP/ICMP header. So your optimal MTU settings would be something like this:
1412+28 = 1440
Take that value and configure it to your router and hopefully it would solve your issues as well.
-
FINALLY! I found the solution to the problem!
I know I late but I just found out about it.
Ok. This is assuming that you are sure that there is no strict NAT issue on your side and the necessary Warframe ports are opened to you.
For me, the issue is related to the MTU settings.
Try to double check your MTU within your router settings (mostly around the WAN settings). If your MTU has too low of a value, it will cause the problem that you all are (might be) facing now. Usually, the default MTU value is at 1440. You can try tweaking your MTU to get the optimal speed for your bandwidth by using the command below in Windows Command prompt:
ping [replace with any website address] -f -l 1490
If you see results such as "Packet needs to be fragmented but DF set.”, reduce the value by increments of +/-10 (eg. 1490, 1472, 1462, 1440, etc) and keep repeating the pinging process till you achieve a successful ping response without the "fragmented but DF set" in the results.
After that, you add 28 to the value that you have utilized for the successful ping response. This 28 is to allocate for the packet size IP/ICMP header. So your optimal MTU settings would be something like this:
1412+28 = 1440
Take that value and configure it to your router and hopefully it would solve your issues as well.
-
When equipping Burston Prime with a an alternate skin which apparently uses the new Burston model, it seems that there is some model clipping issues. The left hand seems to be grabbing the rifle like the old Burston/Burston Prime model. Tested with various frames and it is the same problem for all of it.
-
Ok. so I'm not sure if I have encountered bug (pretty sure I did), but seems like I have some missing XP.
So I'm quite certain that I have all the frames, companions, weapons (from events and beta as well) in game as well as completing every inch of the solar map as well.
The ones that I have yet to get my hands on are the Zenith (login reward) and Jat Kusar (latest tenno reinforcement) and I am still 8,644 XP away from MR 24. Despite not having those 2 weapons, I'm pretty sure I don't need to have those 2 weapons to get there. I'm not sure what else I am missing (ideas anyone?)
Or I am just one of those unlucky ones that have gotten the missing affinity bug.
-
Just finished a mission and while I was minding my own business...
"Hey kiddo."
Seriously, get off my ship and stop freeloading
-
18 hours ago, [DE]Megan said:
Octavia’s Anthem: Hotfix 20.3.1
Oberon Changes & Fixes:Smite:
As a part of this revisit, Smite has remained largely the same in execution but different in stats. After a review yesterday's deployment, we are further tweaking stats to have better initial impact and scaling.
- Increased Smite's projectile damage from 20% of the target's max Health + Shield to 35%.
- Added base damage to Smite and its projectiles. With the damage of Smite scaled into its projectiles, this will give Smite more punch when facing lower level enemies.
Renewal:
Oberon’s ability to keep himself and his teammates alive is a large part of his overall role. Feedback brought forth further tweaks with the intention to solidify this role.
- Removed Heal Time from Renewal. Renewal now functions more conventionally as a toggle which drains 2 Energy per second while active + 3 Energy per second per target actively being healed. *Please note that Trinity's Energy Vampire will not give Oberon Energy while Renewal is active.
- Added the "is active" ability icon animation to Renewal.
- Fixed Renewal bleedout buff being removed when entering bleedout.
*We are aware of a UI bug where the Arsenal stats for Renewal show that Energy per target is not affected by Efficiency/Duration Mods. A fix will come at a later date- we wanted to get this out ASAP!
Hallowed Ground:
- Fixed Hallowed Ground being impossible to see with low particle quality setting. *Please note we are still working on Hallowed Ground FX improvements overall.
- Fixed a script error with Hallowed Eruption Augment upon deactivating while another Oberon has Hallowed Ground active, resulting in the FX to remain forever.
- Fixed Hallowed Ground & Hallowed Eruption Augment not hurting ragdolled enemies.
Broberon seems like DE's illegitimate child, ya know.. the one who always gets the short end of the stick. The one who always stares at the rest of his siblings as they get ice cream while he doesn't.
Psst.. Hey there! He still sucks!
-
Drop locations please?
-
50 minutes ago, DopingMD said:
its bugged for sure but you can manually type the invite :) by /invite and type players name!
I think the gravity of the situation is a bit more serious (or at least mine). Rather than being able to invite people, I can't even see the other player even though the other party has successfully joined the session. This applies to relays as well.
-
30 minutes ago, EnterTheShikari said:
This bug is still affecting my trades.
Missing out on things because people aren't in clans. This needs fixing.Think I'm gonna put off playing WF (again) until this gets fixed. Really frustrating to see them put out new skins and stuff while game breaking things like this are not being looked into even though proper support tickets have been raised.
-
I got support to escalate this issue (hopefully) and by some prayers, hopefully they would take a look at it and fix it soon.
Btw, I can more or less confirm this is not a port restriction issue as I have tested out with a DMZ configuration on my router and of course, still nothing.
-
Just got a response from support and as expected, not the answer I was hoping for.
Guess I shouldn't have expected that much from support other than copy-paste solutions on port-forwarding. *sigh*
Looks like we are on our for now.
I'll keep testing stuff out to get a workaround this problem myself I guess.
-
I am having this problem too ever since updating to U20.
It's a problem with them relays / dojo servers. They must have changed some server setting of theirs in U20. I tested this out by using my mobile data plan instead and launched WF. Everything worked well but when I switched back to my home's Internet connection, the same issue happened.
So I narrowed it down to their firewall rules or config that DE needs to set in their servers.
-
3 hours ago, MikeUzumaki said:
Yes, I just tried to join the dojo with another friend who I 100% traded with just before U20, ever since I haven't been able to see people in non-mission instances.
Yeap. Same problem here as well. It seems that they changed some config where relays/dojos are at currently when they update to U20. I tried using a mobile hotspot connection from my phone everything works well. But when I switch back to my home's net connection, same problem.
There are some threads around with people having the same issue, but judging by how many people were affected, looks like we are the selected few.
I created a ticket to support, still waiting for a response. Maybe you could do the same to expedite whatever bug fix they need to do.
-
15 hours ago, MikeUzumaki said:
So, I've been trying to trade with a friend of mine, we are in the same clan, however no matter what we did I would never be in the same instance as him in the dojo, so then we tried going to a relay, however once again, I would never be in the same instance as him. We can always play missions together just fine so I have no idea what caused this? Then I realized it wasnt just my friend, it was anyone. Whenever he would go to a relay it would be densely populated but on my end it would be completely empty.
I would really appreciate some advice as this is completely game breaking, being unable to interact with any other tenno outside of missions is frustrating.
Just checking, did this happen to you after U20?
-
I am currently having this issue. It seems that this issue affects just a handful of people. Not sure how long it will take to get this fix as it is not as "popular" as other bugs. Try creating a support ticket to push the issue forward. That is what I did.
-
Still having problems with dojo and relays. Still can't do any trading since U20.
Please fix.
-
13 hours ago, thecarrera said:
Yeah, just a wild shot :) I know it helped me during some chat errors I encountered. But it does sound like your problem is client based.
Hope they can solve your problem soon!
Much appreciated for the assistance.
I believe it is more towards the servers that hosts relay/dojos. Might be some config or settings that needs to be looked at. Prior to update 20, no problems at all whether it is dojo or relays. I tried messing around with my firewall settings but still no improvements
I have seen a couple of threads with people having the same problems but judging by its popularity, it seems to affect selected few. Hopefully this can be fixed soon.
-
1 minute ago, thecarrera said:
Try verifying integrity of game cache.
Comparing all your files with the current build. Might be something damaged in your files. If not and it's a client based error, then I guess making a ticket and wait for help is your best shot.
I practically uninstalled - reinstalled. Problem still there. Just shot a ticket to support.
-
Yeap. Having the same problem as well. It affects both dojo and relays. Can see activity in chat, but can't see a single soul in relays/dojo.
Increased graphical stuttering during playtime. Need help! - Unresolved
in PC Bugs
Posted
Hi UlgrimUnpleasant,
I've been following your post as I am having a similar issue. Earlier this year, I built a new system with:
I've been doing some testing myself and got some temporary success in alleviating the problem. Just wondering if you could just help in testing out something if you don't mind. Btw, is your RAM overclocked or at stock speed?