+5% strength, -5% deviation, -5% duration per level *I haven’t personally attempted this yet, so anyone with experience may be able to weigh in here. Unfortunately, the Damaviks max out at 4000 m/s, so you probably won’t be able to outrun a fleet indefinitely. Once the fleet warp is initiated, you can warp away and the fleet will continue warping to your previous spot.Ī fast agile ship should be able to warp in at 100km, then turn around and burn away from the Trig fleet with a prop mod. To prevent your fleet from breaking your cloak use one these tactics:Īsk the commander to fleet warp onto you at rangeĪsk the commander to alert you when they initiate warp. It’s generally not difficult to keep that range on the Trigs if you warp in cloaked at range, but you’ll want to take care when warping into an asteroid belt or having the fleet warp onto you. (Triglavian NPCs have target lock ranges over 1000km, so even if you warp to 100km, the Trigs may target lock you before you get a regular cloak up.)Ĭloaks break if you get closer than 2000m of any object. Some options on doing this safely:Ĭov-Ops cloaks allow you to warp while cloaked. Unfortunately, this puts the prober alone, on-grid with the Triglavian fleet before the friendly fleet arrives. This has the advantage of getting the fleet directly to the signature without needing a nearby celestial or station In some cases probers will warp themselves to the signature, then the fleet will warp to the prober. You don’t want to warp a sniper squad at 0km. This puts a little more responsibility on the scanner. This has the advantage of warping the squad onto the signature, and doesn’t require a nearby celestial or station In this example, the planet has 4 moons and 2 stations in orbit, all of which fit in a 0.5 AU sized probe clustered So instead of starting with a wide probe size and narrowing down, we can start with the smallest size, and scan clusters of celestials one at a time. Unless they’re in warp, the npcs will be clustered around a celestial, station, or structure. Either bind the broadcast to a hotkey or keep your fleet window visible. Keep your ship or your active modules visible to keep an eye on cloak statusīe mindful to broadcast when being targeted. Approach or orbit the structure to make bumping you more difficultīe mindful of decloak distance. You can press the Up or Down Arrows, Home, End, and Page Up or Down keys to move up and down and access all the processes.If the signature’s signal drops to zero, then move to the other endpointīe mindful of people trying to bump you out of tether range. The status of the process can be one of the following: The COMMAND column is off-screen, to the right-it didn’t fit in the image above, but we’ll see it shortly. COMMAND: The command name or command line (name + options).TIME+: Total CPU time used by the task in hundredths of a second.%MEM: The share of physical memory used.%CPU: The share of CPU time used by the process since the last update.(See the list below for the values this field can take). SHR: Amount of shared memory used by the process.RES: Amount of resident memory used by the process.VIRT: Amount of virtual memory used by the process.The column headings in the process list are as follows: The latter includes memory that’s expected to be recoverable from caches. The fifth line shows the total amount (also in kibibytes) of swap memory, and how much is free, used, and available. The fourth line shows the total amount ( in kibibytes) of physical memory, and how much is free, used, and buffered or cached. st: Amount of time lost due to running virtual machines (“steal time”).si: Amount of time spent servicing software interrupts.hi: Amount of time spent servicing hardware interrupts.wa: Amount of time the CPU spends waiting for I/O to complete.ni: Amount of time spent executing processes with a manually set nice value.sy: Amount of time spent running system “kernel space” processes.us: Amount of time the CPU spends executing processes for people in “user space.”.The third line displays the following central processing unit (CPU) values: The second line shows the number of tasks and their states: running, stopped, sleeping, or zombie. The first line of numbers on the dashboard includes the time, how long your computer has been running, the number of people logged in, and what the load average has been for the past one, five, and 15 minutes. By default, top updates its display every three seconds-you’ll notice a slight flicker when it does. The default display contains two areas of information: the summary area (or dashboard), and the task area (or process list).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |