ferzal
-
Posts
10 -
Joined
-
Last visited
Posts posted by ferzal
-
-
I jizzed my pants
+1
-
You people...first, the original Brakk owners are complaining about have their 100 event runs feel worthless. Now when DE decides to compensate by making it rarer, everyone throws a tantrum because they didn't get their easy mode button. Seriously though, having the G3 drop all the parts in one run is a freaking joke so I'mma congratulate DE for fixing that. It's impossible to please everyone so why don't you guys just grow some balls?
But it IS easy mode button. It's just easy mode * 1000 * bored to death. There's nothing remotely challenging about it other than the ability to withstand the sheer, astounding boredom of it. That's not an achievement I applaud. That's like holding the world record for time spent watching paint dry.
-
All these "fixes" are kicks in the rear. This isn't a hotfix it's a hot mess.
Just a tip: games are supposed to be fun. That jat kittag anim... now that was fun.
But the fun police were alerted. As too were the RNG enforcers who've now made the game seem like a chore. I just don't even want to think about the G3 that I haven't been able to encounter yet after hours and hours. This hotmess sucked the life out of me a bit as far as logging in goes. When the prospect of playing a game feels like housechores perhaps it's time for me to think about another game. Sad but true.
-
Thanks for the response! My router is a Technicolor TG582n (the non-USB DANT-T version). Warframe started off saying it had a strict NAT (got that sorted), then reported a Firewall problem (also sorted). So it seems Warframe doesn't like this router, for whatever reason.
These routers can be a little troublesome apparently. I'm not sure it is the router if you have sorted everything else out. The best way to check would be to turn the firewall feature off entirely for a test or enabling DMZ mode (by selecting apply public IP address to device and selecting the PC you're using). This will open your PC up completely to the net but it's ok just for the shortest possible period to test the voice. Do that quickly and disconnect and restore the router settings as you have it now. If you're still having issues then it's probably some hardware/driver setting specific to your audio device or sound chipset combined with the game in which case you can look at other sections of support or this forum.
If that solves it then there's probably not much you can do because you don't want to run like that and there's no way to make any other changes with that router. It doesn't randomise outgoing source ports so it's not the issue I was having.
-
Could you say how you did this? I used port forwarding to get rid of the firewall message, but my mic doesn't appear to work in game (I can hear others, if they speak, and can use team speak ok). I'm thinking Warframe is struggling with my router and/or firewall, but just not reporting it.
It would depend on your router and it may not be possible with an out-of-the-box device which is why the fix should be done by DE. Your router may not scramble outgoing ports if you're not getting the firewall message - though the fact that you had to forward the ports isn't a good sign either. The people I play with have all had troubles with in-game voice (most games implement it poorly so this is not unique to DE) and we just use other programs like Ventrilo or Skype so I haven't had a chance to look at it. It may not be related.
I don't really want to start a support thread for each router for a problem that DE should fix themselves but if you can report your router model I might be able to quickly find whether it scrambles outgoing ports and if there's a way to setup a static rule for it.
-
Well I had to find the answer myself. Turns out this game doesn't like the source port (not destination) being scrambled by firewalls. There are a lot of reasons why this is a nice little security measure and we could go into how UPnP is pretty insecure as well but whether or not you think this is a good idea some firewalls do this by default which is the problem.
So far I've only run into one application of any kind that this breaks: warframe. And only sometimes... I still can't make any sense as to why this fixes the problem but it does.
I made a special OUTGOING rule to make the warframe default ports static and I no longer get the firewall message and can now connect to people I couldn't connect to before. Why this is a problem only sometimes I don't know.. but there's the clue to fixing it DE. Shouldn't be that hard. Or is there a valid reason why your code (sometimes) looks at the source port?
-
Life support is definitely ticking down faster? I thought I was imagining it. We wondered why we were having trouble making it past 20 minutes sometimes. I thought it was more likely a lack of enemies as we did seem to have lower killcounts so not enough packs dropping but it also seemed that by the time we made it to the first LS drop we would be at 60% at best.
There have been a couple of times we simply couldn't go past 10 minutes as we'd slaughtered everything, hit every drop and still hit zero.
-
I thought I'd get used to the UI pretty quickly but I'm not. I'm still struggling to grab the info I need at a glance whereas I had no problems previously.
I play warframe with a controller from the couch (yes it makes it harder but soooo much more fun) and the UI is not doing it. The difference in the status of the little dots under the reticule are not as apparent at that distance. The "power selected" dot does not contrast enough for me to see quickly enough at that distance. Give it a little contrast please, like power not selected is dark (or give us the option).
Also the mini-map is absolutely screwed at the moment. Objectives are really hard to find sometimes as they fly off screen and can't be seen at all. I have to turn around to swing the map back on screen so I can see what I want. Also the icons are so samey that it's confusing at a glance. Bring back the old console icon (or something else green and square or.. just different!!). I thought it was great to see fellow tenno icons change until I discovered that all grineer and corpus allies also had the same icons meaning you still have no clue who's who in invasion. Use a little colour difference for icons on the minimap - extraction point in survival should not be the same colour even if it does flash. Likewise the lifesupport drop icons, even if they don't show on the minimap, ought to be a different shape and colour. The symbol is easy enough to distinguish after a second or so but that's too long.
And let me add my voice to the throng, pointlessly given that all feedback was utterly ignored prior to implementation: FIX SNOWGLOBE. With the pathetic health quota it has, the point at where the skill is actually needed is now the point that it's utterly useless. Easiest fix to globe-camping if that's a problem (for some reason) make it two-way. Projectiles cannot go in nor out. Otherwise you may as well just remove the skill entirely. At this stage higher level defence is off the cards for us controller-wielding oldies. You've kinda kicked the fun outta the game there.
-
I'm reasonably new to warframe. I find it amazing reading this thread that this bug has persisted so long with zero official response.
I get the "strict nat" message using PFsense. The UPnP in this game is messed up somehow. I have forwarded the ports and turned off UPnP ingame and have problems with some players. I've tried it with UPnP (which pfSense obvious supports) with exactly the same results even though I can see pfSense respond properly (3960 reports open and listening as "client" and 3962 as "server").
I have one friend I can connect to every single time (as client or host) and another I can never connect to.
They're both using UPnP. There's nothing to differentiate why I can connect to one and not the other. I have never had a problem like this with any other game or application and I've played a lot of P2P hosted games (living in Australia that's par for the course) and have a 100/8 connection.
I think everyone would like this fixed so is there any indication what could cause this problem? Why does the game report pfSense as a strict Nat when UPnP is enabled? Do I need to inspect every packet here to figure out what's going on or can we get some info?
This is the point of a beta I thought - to solve these issues. Doubly so if you're already taking cash for the game (which I've gladly added to by the way).
Pc Event: Tethra's Doom
in Livestreams
Posted
It was too easy but no thanks to that idea. It was too easy to be fun so I wouldn't want to run that again. If it was a challenge to get 500 then it might be fun to keep having a go until you got it. But it's not so I'm done with that.
There's enough grinding against the RNG gods to farm the new prime stuff.