Valorant

Valorant Dev Tracker




04 Sep

Comment

Originally posted by HOTMILFDAD

I stand corrected. Thank you for the insight :)

Question for you, though: is it typical for game studios to actually sit on maps/characters/lore for [x] amount months after release? Or is more customary for devs to focus on having a certain amount of content for launch and then worry about stuff further down the line?

There can be some amount of that, for sure, but fully ready stuff for months after release isn’t super common. What tends to be more common is content that’s fairly gameplay locked, but needs a lot more work for other disciplines to clear before shipping (like art, QA, engineering, localization, etc)

It obviously differs a lot for games as a service compared to boxed product games, too!

Comment

Originally posted by HOTMILFDAD

It’s just game development. Nothing crazy.

Developers usually have years worth of content they sit on and can plan small teases.

We're actually not sitting on it, game dev just takes a lot longer than people think it does.


03 Sep


02 Sep

Comment

Originally posted by meme_poacher

The ping used to be 70ms to Kenya now its 240ms, it's literally the only server the whole of africa can play on

I just got word today that there is an outage on the direct path between Kenya and Bahrain that started around August 23. Our partner in the region is waiting on repair details but it sounds like a submarine cable fault so may take a few weeks to repair.

Comment

Originally posted by Frozoken

would this be for telstra users only or all perth users? thanks for taking your time to respond to so many people

Initially just Telstra so that we can prove the concept but the intention will be to capture as many players from WA as we can at this point. Every step of this will require the cooperation of ISPs since it'll be new interconnects and we're building in a location where they all have common presence to try and avoid any air gaps.


01 Sep

Comment

Originally posted by --Shin--

Does this mean there will be a server in Perth?

No there wont be a server in Perth. There will be network equipment to try and capture your traffic locally and send it over to our other equipment in Sydney on the shortest path we can find.

Comment

Originally posted by RiotKorensky

If you can get these stats (need to enable them in the menu) from a practice/custom game on Sydney-1 it'll help

https://imgur.com/a/OErOSKM

Disclaimer: i do not work day to day on the Valorant client side of things and have very little knowledge of some of the other trace/debug/log options that may exist in it. I will make some time to talk with folks on that team to see if we have a better way of extracting this data also for specific cases.

Comment

Originally posted by Equivalent_Ad505

I’ll try and do it tonight. What settings do you want me to record besides ping?

If you can get these stats (need to enable them in the menu) from a practice/custom game on Sydney-1 it'll help

https://imgur.com/a/OErOSKM

Comment

Originally posted by meme_poacher

Anything on the bahrain server, or adding african servers?

What's your issue with Bahrain sorry? It should be up and working as normal to my knowledge.

Comment

Originally posted by TheZedMan610

It's not horrible per se, but when I'm trying to compete with the east coast players who average 25 ping, anything is better. I'm with Telstra, and I play in Perth, if that helps.

Telstra solution is in the works but is realistically probably going to take us a few weeks to get implemented (we will have some paperwork to sign once the details are ironed out, people will need to do some work on both sides, equipment will need to arrive in Perth from the COVID capital of Australia etc).

Comment

Originally posted by DontGetGotGooG

i just did tracert and i get 52 ping, and in game its 66 ping, is it visual glitch ? might be in stats not working properly

1 <1 ms <1 ms <1 ms 192.168.2.1

2 1 ms 1 ms <1 ms 192.168.1.1

3 38 ms 7 ms 5 ms Loopback1.bng01-sbb-1william-per.au.superloop.com [203.132.88.1]

4 6 ms 6 ms 6 ms bundle-ether13-100.bdr01-ipt-1william-per.au.superloop.net.co [27.122.123.71]

5 51 ms 52 ms 51 ms hundredgige0-0-1-3.bdr01-ipt-4millros-per.au.superloop.net.co [103.200.13.135]

6 52 ms 52 ms 52 ms hundredgige0-0-1-2-126.bdr01-ipt-4edenpar-syd.au.superloop.net.co [103.200.13.152]

7 52 ms 52 ms 52 ms as6507.sydney.megaport.com [103.26.69.85]

8 * * * Request timed out.

Superloop use Indigo Central (the submarine one) to get from Perth to Sydney and the network round-trip there is about 46.8ms for that segment.

The in-game ping will be adding the client render-time to the number so it's always going to be higher than the network number. I need to chat with some of the folks on the development side who are a little more in the weeds on the specifics here but the article here talks a bit about it: https://technology.riotgames.com/news/peeking-valorants-netcode -- a higher framerate will help bring this number down in-game but the network ping you see when you're running thos...

Read more
Comment

Originally posted by DontGetGotGooG

i live in western Australia.... (sydney 2) i got 51 ping in game, and (sydney 1) 67 ping in game please explain how the servers are in the same location,then why such a huge ping difference.

i have fibre to premise 250 down 40 up.

what a piss weak response ....... ''If it isn’t then we can take a look at your ISP and how they’re routing to us''

there is only 1 way to route, 1 under sea cable from sydney to perth, on the valorant competitive reddit there is plenty of people complaining if its this wide spread how is it our ISP's

for a game was marketed as having no peakers advantage.... no ping advantage this is a joke. playing on 67 ping vs 0 to 40 ping players in eastern states its unplayable there is no hit reg

There are three major terrestrial routes from Perth to Sydney and one undersea cable. The submarine one is not the fastest. There are also many more than one ways to route packets over the Internet, even inside Australia.

Comment

Originally posted by tqstin

yeah playing on anything higher thab like 30 ping is aids for le

Still can't help you if you don't run a traceroute and post the results.

Comment

Originally posted by Daisy_1

Aussie Broadband - Canberra

1 <1 ms <1 ms <1 ms ARCHER_VR600 [192.168.1.1]

2 88 ms 87 ms 84 ms 100.96.128.1

3 * * * Request timed out.

4 75 ms 79 ms 87 ms 180.150.0.235

5 87 ms 73 ms 74 ms be10-3999.core1.nextdc-s1.syd.aussiebb.net [180.150.2.96]

6 88 ms 88 ms 79 ms be1.core2.nextdc-s1.syd.aussiebb.net [180.150.1.117]

7 87 ms 77 ms 70 ms as6507.syd.edgeix.net.au [202.77.88.10]

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.Trace complete.

88ms to hop 2 - you should really call your ISP and talk to them about this..

Comment

Originally posted by rpkarma

Okay me again, so my in-game ping right now is 57ms and my traceroute shows this:

``` Tracing route to 43.229.65.1 over a maximum of 30 hops

1 4 ms <1 ms <1 ms RT-AX86U-ED58 [192.168.50.1] 2 13 ms 14 ms 12 ms lo40.lns03.brisngn.qld.vocus.network [203.134.103.92] 3 12 ms 11 ms 27 ms ae2-14.per01.brisngn.qld.vocus.network [203.134.98.130] 4 13 ms 23 ms 12 ms ae6.per03.brisngn.qld.vocus.network [203.134.12.160] 5 12 ms 12 ms 12 ms be106-99.bdr01.bne08.qld.vocus.network [114.31.195.82] 6 29 ms 30 ms 30 ms be202.lsr01.bris.qld.vocus.network [103.1.77.192] 7 32 ms 30 ms 30 ms be801.lsr01.brdg.nsw.vocus.network [103.1.76.137] 8 29 ms 31 ms 29 ms be221.cor02.syd04.nsw.vocus.network [103.1.77.9] 9 29 ms 29 ms 30 ms be100.bdr04.syd03.nsw.vocus.network [114.31.192.45] 10 30 ms 29 ms 30 ms 218.100.53.59 11 * * * Request timed out. ```

...

Hop 3 shows inconsistent response times (and 4) so congestion likely starting before that. Can you download something like ping plotter or similar and run a longer trace over time during peak to try and get a better sampling window? I suspect it'll give a stronger indicator. These issues would also have been present on Sydney-2 since they're close to the access end of the route so we're dealing with a lot of cognitive bias :(

Comment

Originally posted by Frozoken

iinet(NBN), perth

2 1 ms 1 ms 1 ms 203-219-198-201.tpgi.com.au [203.219.198.201]

3 49 ms 48 ms 49 ms 203.29.134-193.tpgi.com.au [203.29.134.193]

4 50 ms 54 ms 54 ms syd-tpg-wat-crt2-ge-3-1.static.tpgi.com.au [203.26.22.125]

5 49 ms 49 ms 49 ms 203.29.134-18.tpgi.com.au [203.29.134.18]

6 50 ms 50 ms 50 ms 203-219-106-254.tpgi.com.au [203.219.106.254]

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

This looks pretty good - you should be on the same sort of performance that you had before...

Comment

Originally posted by Equivalent_Ad505

so im not the only one? the ping flunctuation is also insanely fast, when i watch my netword rtt it fluctuates atleast 2-3 times a second between 65-115 ping over and over again.

Any chance you can capture a video of this or what the network stats are like in the practice range? Which ISP are you using? Can you capture a traceroute as well (instructions somewhere in the thread). This data will help us get the places that were not at parity performance wise with Sydney-1. We have a good idea what the problems are but need to reach out to our contacts in the ISP community for assistance in correcting it.