Frontier Developments... Fix the titan core bug. please?

Dear Frontier,

As you are woefully aware, the 18.01 patch did nothing, but bring more issues to the table. It is even easier to bug the core now and have vents lockup where they dont open.

Discoveries include, but not limited to:
  • more success with 1 person bombing all 8 vents.
  • more success with everybody port forwarding.
  • STUN connections are more reliable to avoid locking the titan
  • In a larger group setting, controlling WHEN people enter the Titan Instance so as to have them hold off from dropping out of supercrusie during a bombing run and thermal core attack.
  • In a larger group setting, controlling WHEN people click the Okay button after death to avoid them leaving the instance.
  • Play by Regions (US, South America, Europe) has more success.
  • Play in instances where Ship Launched Fighters are not utilized
  • Play in instances where there are less than 20 players.

The failures of the development team to fix this induce a lot of wasted time on your Customers, in retail, customers tend not to be repeat customers if the business is wasting their time. Also, when will combat be BUFFED (do not nerf sampling) so that its is feasible to be on par with sampling.

I implore the readers of this thread to positively criticize Frontier Developments and their handling of the game's state and addressing of bugs that are not even on the bug tracker.
 
Hi FDev

Please fix this, I've wasted to much time this evening getting to the titan multiple times just to find it's bugged so have to rinse and repeat. I haven't once managed to succesfully find a working instance.

Really can't expression how frustrating it is.
 
Sadly I've never yet been able to engage in Titan gameplay because every single time I've gone there as an open-only pilot it's been bugged. Every. Single. Time.

I may have to do it in Solo just to enjoy the content. The gameplay looks fun, I just can't partake in it coz it's bugged to all hell.
 
Also this issue is well known to Frontier and the CM put out a post about it. In that post they funnel us towards the ever dreaded issue tracker and ask us to add our experience there. It can also be voted on here if you think that does anything.

 
Also this issue is well known to Frontier and the CM put out a post about it. In that post they funnel us towards the ever dreaded issue tracker and ask us to add our experience there. It can also be voted on here if you think that does anything.


12-Am-I-a-horse-flowchart.jpg
 
Sadly I've never yet been able to engage in Titan gameplay because every single time I've gone there as an open-only pilot it's been bugged. Every. Single. Time.
Which is super weird because i've done around 100 sorties in open only, both in wings and with a full complement of multicrew with zero issues.
-while i can ofc sympathise, having such a broad fan of experiences makes it quite apparent it is not a bug that will be easy to fix.

If the on foot CZs are anything to go by, the initiator should run a good pc with very solid net.
 
Which is super weird because i've done around 100 sorties in open only, both in wings and with a full complement of multicrew with zero issues.
-while i can ofc sympathise, having such a broad fan of experiences makes it quite apparent it is not a bug that will be easy to fix.

If the on foot CZs are anything to go by, the initiator should run a good pc with very solid net.

bro...
 
Feel free to look up the terms, I'm not going to explain them. Type of connection (mobile/broadband/satellite ect) matter more so than the toaster you're playing on. Larger instances will see toasters catching fire.

FDEV utilize amazon web services for their servers. Which use STUN and TURN to accomplish the intended peer-2-peer network. People that dont connect STUN end up getting routed through TURN which is EXTREMELY INEFFICIENT for instancing properly with other commanders and often results in severely diminished instance stability for all clients connected to the peer-2-peer server.

This is why port forwarding is critical in larger instances and with instances involving multiple geographic regions.
In the Xeno Strike Force, we host events that occupy different regions and we ask all our pilots to ensure they do port forwarding. There are times where that doesn't help, however, its easily detectable by reading the netLog file and we try to help our community members resolve TURN connections into STUN connections.

Regardless, the netcode does start degrading approximately around the 20 clients connected part, so we limit our events to that number. Hence our "strike team" structure.
 
Back
Top Bottom