Some of you guys try to not act like forum velcro hooks. Try to understand, in common, what somebody just posted or tries to say. Because somebody can be focused on other things online and can’t notice word by word, their order and punctuation for the entire context in details.
About Cloak/MWD Trick
Again. As @Beast_of_Revelations posted, he had a problem because could not warp due to wrong actions and he got a message “can’t cloak while warping”. I understood that as a general Cloak/Warp trick and not just Gate Cloak/Warp trick, just because I used it and I’m using it in other situations, about which I’ll notice below. The Cloak/Warp trick is a much more generic game mechanic than Gate Cloak/Warp trick. If to be more accurate, it can be used:
- in space at Safe Spots while Probed by Combat Scanners;
- in Ore Belts or Combat Sites, if somebody just lands in suddenly at a distance (your ship just shouldn’t be locked by rats in this situation);
- while hacking Data/Relic sites or scooping resources from POCOS (but your ship must be at range above 2500m if I’m not wrong). It’s harder to use Cloak/MWD there. BTW, these are very popular locations where you can get tackled by different Covert frigates and T3 Cruisers. Some guys tried to lock my Epithal with a Loki at POCO unsuccessfully few times.
- it can be used while undocking from a Station, if your default ship speed is high (aka most Frigate class ships) which will allow to Cloak at a range before the Timer will expire. You’ll remove that Location Change Timer/Station Undock Invulnerability Timer by activating any module or by changing direction or by locking somebody. If your ship is at range above 2500m from the Station or other objects, you can Cloak your ship and MWD in other direction.
- it can be used at Gates as already was explained a lot. To remove the Jump Cloak Timer you have to align or warp your ship. To use the Cloak/MWD trick in this case, you have to align, then Cloak, then MWD. Just don’t MWD then Cloak! Because you’ll boost your Signature and will make a tackler to lock your ship even faster.
All previous scenarios are true for the standard Cloaking devices and for the standard ships. With Covert Cloaking devices you must do the same things in the same order and conditions, but you can warp while Cloaked if not in a Bubble of course. To escape from a Bubble Gate camp, both ships with a standard Cloaking device and ships with a Covert Cloaking device must Align, Cloak and MWD/AB in a random direction to avoid any attempts to decloak your ship by foes.
About Travelceptors vs Instalockers
I can’t say nothing about navigational particularities of Capital, Freighter and Black-Ops ships yet, but I can say a lot about navigational particularities of other ships. The generic concepts and formulas are good and works well in the most situations, but there are some exceptions when they works a bit differently when the net is overloaded, when the server is overloaded and when, maybe, CCP is doing some unofficial testing things on Tranquility.
Server Ticks are normalized to 1 sec. Therefore, all computations which happens between each tick are summarized and compared between each other. The results are concluded at the end of each tick and the responses are sent back to the user clients in a broadcast mode.
The Travelceptors (aka insta warping ships) are called ships with Aling Time <= 2 sec. They have a warp time (Align Time in UI) calculated by the formula:
Align Time = (ln(2)*Inertia Modifier * Mass)/500000 sec;
The Instalockers are widespread and are able to lock and point targets with an align-time under 3 seconds. Which is just about every ship except Travelceptors and capsules. But with overloaded Sensor Boosters, Remote Sensor Boosters, Command Burst effect an Insta-locker can be easily turned into Ultra-locker, which can lock in under 2 sec. Locking time can be calculated by the formula:
Targeting Time = 40000/(Scan Resolution*arcsinh(Signature Radius)^2) sec;
On EUNI site is enough generic information about this thing. But, in my opinion, the best guide about Travelceptors vs Instalockers is posted on:
INSTA-LOCK : IN FULL Guide
There is a plethora of data about how Travelceptors can avoid Insta-lockers, about how the Ultra-lockers can tackle Travelceptors and about how Travelceptors can avoid Ultra-locker’s gate camps. As that guide is concluding, to avoid a perfect Ultra-locking gang you need a Travelceptor with a T2 or better cloaking device and Faction Inertia Stabilizers. The idea is to use the Cloak/MWD trick on a Travelceptor. This method is vulnerable when Travelceptor’s client has much higher ping (net issues) than Ultra-locker client. And this is the case when the lower Align Time comes handy. We can’t reduce our ship mass with in game devices (except HICs), but we can reduce our ship Inertia by increasing its speed or/and Signature Radius. Lower Align Time or lower Inertia also means that our ship will get to 0.75*Vmax speed faster, based on the below formula, or will burn back to the Gate faster, before will get tackled by the entire gang fleet.
I - Ship’s inertia modifier, in s/kg
M - Ship’s mass in kg
This is what I tried to type very short in my first post: There are different modes for Cloak/MWD trick; You can get tackled even in a insta-warping ship (aka Travelceptor) based on my experience even.
Below is another handy diagram explaining the Travelceptor win condition and Instalocker win condition. On both, on the previous site as on the diagram below, the authors took into consideration only ping, player reaction, targeting and aligning and server ticks only. Their model is based on a concept that the server just performs all computation actions instantly. But what will happen if the server has its own latency on Queueing client requests, processing their data on different threads, arranging and comparing them. What will happen, if in a Travelceptor Win condition scenario, the data from both 2s-Travelceptor and Instalocker will be delayed by 100ms due to overloaded processes on a Server node? What will happen if a 2s-Travelceptor will not reach 75% max speed before Tick2? As we can see, the Instalocker can lock the target before the Tick2 even with internal server delays.
What is a Server? Server has a Collecting Inputs module (where he has to distribute each client request from a queue between physical servers and virtual servers on each physical server). A virtual server is supposed to be a “node” in EVE.
Summary
The work of each “node” can be displayed like this:
Where TCP Server works in his main 1sec Tick thread while Worker1/2/3 are different sub-threads (which works on max speed, and will return data after some cycling delays) which computing things like Align Time, Locking, Attack, Dock commands.
P.S. Therefore, I prefer my first post just because this one is too overloaded.
