Posts Tagged ‘ scanning ’

Proposal: Directional Scanner Changes

Apocrypha 1.0 and the updates that followed overhauled the probing system, simplifying it and making it more accessible to probers. But the improvements neglected the directional scanner, only one tab to the right from probing system. Here are some definitions to help distinguish the directional scanner and the probing system.

Definitions

The directional scanner is a tool that allows you to perform an instantaneous scan of all nearby objects in space. It allows you to manually adjust the scan range from 0 to 2,147,483,647 km (14.413 AU) and scan angle from 5 to 360 degrees.

The probing system is an interface that enables you to control up to 8 scan probes that can be manually moved anywhere within a system. There are various types of probes, but they generally can have their scan range adjusted from 0.25 AU to 64 AU (1024 AU for Deep Space Scanner Probes). Each probe is essentially a 360 degree directional scanner with a self-adjusting scan range within the max scan range you set. Thus they return the distance but not direction from certain space objects (ships, drones, cosmic anomalies, sites, etc.) within that scan range. The accuracy of the distance estimate varies depending on how many probes returned the result, what scan range they are at, and their position relative to the object (Eve does the trigonometry for you).

Of these two systems, the directional scanner has remained nearly the same as before Apocrypha, the only significant change being a nerf limiting scans to every 2 seconds. The current directional scanner today suffers from several significant problems.

Flaws in the Directional Scanner

1. Nonexistent Integration. This is the largest flaw of the status quo’s directional system – it completely lacks unity with the HUD and overview. Unlike with probes, where results are shown on the system map (essentially a very zoomed out HUD – the tactical overlay still shows up), the directional exists only in its little window.

A. Scan Range. Scan range is measured in kilometers while nearly everything else in Eve is measured in astronomical units (AU). It is true that the overview shows range in kilometers for close range objects, but no one uses the directional to see objects that are visible on the grid. Additionally, the overview itself switches to displaying AU for faraway objects.

B. Scan Angle. There is no visible indication of how large of an area the scan angle covers.

C. Identification. There are no scan IDs distinguishing objects. The only identification on objects are their names.

2. Overcomplicated Operation. It only takes a few minutes to understand the directional’s use, for the concept is fairly simple. But actually using all of its features is quite difficult, especially with the new 2-second scan time.

A. Scan Range. Even those who are quite accomplished with the directional rarely ever use the scan range feature; it is simply set to the maximum.

B. Scan Angle. Lining up a belt or planet in the center of the screen while scanning at 5 or 15 degrees is very painful and requires you to reposition and zoom your HUD.

3. Unrealistic Functionality. It is true that the Eve universe conflicts in some ways with the physical universe as we know it. For example, ships in Eve rapidly decelerate despite the absurdly large number of forward thrusters and complete absence of rearward thrusters. But unlike those (largely) aesthetic concerns, the directional scanner is purely illogical.

A. Ship Type. Reading the exact ship types (Impairor) from 2,147,483,647 km is implausible, particularly when not even probes can give this information until you have near-100% signal strength.

B. Ship Names. Viewing ship names (HowCanYouReadMyNameFrom14AU’s Impairor) from impossibly large distances is even more ridiculous. It has no equivalent in Eve – not even the probing system can determine this. This incredible knowledge cannot be attributed to databases in a system’s stargazes – if that were the case, we should also be able to see who the pilot is.

Clearly, the status quo’s directional system is broken and needs amending. There is no valid reason why the directional should be as separated, confusing, and senseless as it presently is. Here are some proposed changes.

Proposals

The current directional system should be fused with the probing system and HUD via the following methods:

1. Probing Integration. The old directional scanner’s tab should be completely removed, its results instead appearing in the same window as the probe system. This is because the directional’s operation currently is identical to that of probing: both involve pressing a ‘Scan’ button and returning results in a list. The new scanner interface would function in the following manner:

A. No Scan Button. The usual ‘Scan’ button for probing would be unchanged, but the directional scanner would be automatically activated every few seconds, thus requiring no scan button. This would eliminate the need to spam the scan button. The time taken for every scan of directional would be affected by the scan angle. For example, full 360 degree scans would take 30 seconds, while 5 degree scans would take half a second.

B. Object Type. In the results list, a ‘Type’ column would indicate whether the result is a site, cosmic anomaly, ship, drone, etc., just as it does in the current probe window. However, unlike the current probe window, objects without 100% signal strength would not be filtered (so a ‘Ship’ result with 9.32% signal strength would still be shown in the Ships filter). The filter would use saved overview settings, eliminating the need to create filters separately and allowing more freedom in choosing what results are shown. All current probe and directional result types (cosmic anomalies, scan probes, etc.) would be added to the overview’s filter settings to facilitate this change.

C. Distance. Appearing together with probe results, the distance to scanned objects would be measured in AU. As with the current probing system, the accuracy of this range estimate would depend on both the object’s signature radius and your scan angle (see 1D). As range is automatically calculated, the current mechanic of allowing the user to choose maximum scan range would be removed. Maximum scanner range would still be 14 AU (but not 2,147,483,647 km).

D. Scan Angle. The scan angle would be set via a drop down list on the scanner interface (not the current slider, which is difficult to control at small angles), and would directly affect scan speed (see 1A) and the accuracy of range estimates (see 1C).

E. Signal Strength. This would be unchanged from the current probe system.

F. Identification. Objects found through directional would display scan IDs, just like probed objects.

G. System Map. To complete the integration with the probing system, directional scan results would appear on the system map just like probe results – large red spheres indicating estimated location. The results would be marked similarly because probes are essentially directional scanners that change scan range instead of scan angle. Not only is this change imperative for a full splicing of the directional and probe systems to occur, but it would also make the directional useful in probing, as you could thereby gain a general estimate of the location of nearby objects.

Here’s what the proposed scanning system would look like (apologies for my poor photoshop skills):

2. HUD Integration. The system map is fundamentally a HUD that is zoomed out enough to view distances in AUs instead of kilometers. For this reason, the improvements to the system map would also carry over to the HUD.

A. Scan Angle. When the angle is set to below 360 degrees, a light blue cone (identical in color and texture to the current probes’ scan spheres) would be displayed on both the system map and HUD indicating the angle and direction of the scanner. The direction of the scan angle cone would be set by alt+clicking in space (custom shortcuts allowed) or right-clicking in space and selecting “Set Scanner Direction”.

B. Scan Results. When a scan result is clicked or highlighted in the scanning interface, the appropriate bracket for it would temporarily appear in the HUD. For example, if you were at a planet and clicked on a scan result at the planet’s asteroid belt, a red bubble would momentarily appear on the belt. This HUD feature would work with any result in the scanning window, with the appropriate marker (green dot, yellow dot, red dot, or red bubble) appearing in space.

Conclusion

As explained earlier, the current directional scanner has severe defects. This should not be the case. It is hard to imagine that, in an age where warping, jumping, and interstellar spaceships are possible, capsuleers do not even have an automatic scanner. Even in the twenty-first century, submarines’ sonar and aircrafts’ radar systems automatically give objects’ range and direction. With the proposed scanner interface and HUD changes, the directional system would simultaneously become easier to use, more realistic, and more robust.

Advertisements

Piloting Savviness

PDF version here: Piloting Savviness

Although I’ve only been flying through lowsec wrecking mayhem (well, as much as my little Rifter will allow) for one week, I’ve been very surprised by the lack of pilot skill many people I’ve faced demonstrate. Against people with about my amount of skill points (4.5 mil), I’ve been doing quite well.

I started off in a PVP autocannon Punisher fit, as many guides have suggested. With it, I “won” 4 fight against Rifters, even those with more expensive T2 modules. I had two 1v1s with a Rifter, who managed to get away both times because I lost a point. I then got this kill, which I was quite happy about. Shortly afterwards, I fought another Rifter, who again got away. This was because, even with an afterburner, my Punisher could not keep within 8km (scrambler range) of Rifters fitted with an afterburner and web (plus a Rifter’s base speed alone is faster than a Punisher). So I switched to a Rifter.

I’ve been using the Rifter (fitted similarly to wensley’s suggestions in his excellent Rifter Guide) since then. And so far I’ve had quite a bit of success for a carebear who was so afraid of lowsec that I never ventured out of highsec for the first two months of my life.

Which makes me wonder sometimes: why am I doing so well against ships that theoretically should kill my Rifter? Part of it definitely is fitting. For example, this Stabber, which was shield and armor tanking. But another part is piloting. It’s true that you learn the best from experience. But pirating doesn’t have to purely be a school of hard knocks.

I think it’s definitely true when people say that winning a fight is more about pilot ability than skillpoints or ships. Tactial errors can and will get you killed. Of course, pilot ability can’t save you all the time, particularly from blobs. But it does play a huge part. So how do you get this piloting ability? How do you acquire Piloting Savviness level 5?

1. Know your ship. This is a given. You can practice on NPCs and corpmates.

  • Find the best orbit range that lets you get hits without being hit. Don’t just orbit at 500 or whatever Eve says your turret’s/launcher’s optimal is (for missiles, find your max range – EFT helps with this). Find your guns’ tracking speed, and turn on “Radial Velocity” in the overview. Make sure you can hit a target (e.g. turn off afterburner if necessary to lower your transversal).
  • Find the tightest orbit range at which you can maintain near-maximum ship speed (different from transversal – this is useful for fighting missile ships).
  • Find out whether you should orbit at all (this point may be a bit controversial among the Eve community). If your ship does more DPS or has a tougher tank but has poorer tracking (e.g. cruiser vs frigate), you may want to simply “keep at range” (e.g. in a Punisher vs Rifter fight, you may want to negate the Rifter’s tracking speed bonuses by simply approaching and keeping at range.)
  • Find out how long it takes you to close distances if you spiral in (and as all the guides say, do NOT simply click ‘Approach’ unless you can tank all the damage you are going to get).
  • Know what to do if your opponent has “tricks” like a neut or smartbomb (e.g. get out of smartbomb range if their turrets do less damage).
  • Get familiar with the damage types and optimal ranges of your ammo (e.g. I often use Fusion S instead of EMP S because of the damage type and slightly longer optimal).
  • Practice monitoring cap and keeping a point (e.g. if your opponent starts running, do not simply keep orbiting. If you can kill him, pursue it by clicking “approach”. If he does more DPS and is trying to kite you (make you follow so that your transversal goes down), refuse to fight on his terms.)
  • Know how to pulse your cap-draining modules (e.g. pulse your armor rep so that cap stays near the max cap recharge point of 34% – no more (don’t overconserve it – by using cap well, you will be able to “use” more cap in the long run. so turn on that armor rep/shield booster as soon as you start taking enough damage for one cycle to rep) and no less (in 1v1s against tough opponents, every bit of cap counts. don’t let it drain)).
  • Use your ship’s strengths/bonuses (e.g. if you are in a Rifter and fighting a Punisher, you may want to pulse your afterburner to take advantage of your tracking speed bonus).
  • Know how to respond to drones. Know which ones will hurt you and which ones won’t. Have a corp mate set drones on you (you can either ignore them and shoot the ‘mother ship’ or you can try to destroy them).
  • Know how to use drones. Know what damage types they do. Know their speed. Know their resistances. Set keyboard shortcuts for telling drones to attack/come back. Know how effective pulling in and putting out drones is (if you have a large drone bay and your opponent is having a hard time taking out your drones, you may just want to leave them out and just send another one out as necessary).
  • Know your align speed (EFT helps with this). Know how fast you warp. You should be able to guesstimate how many seconds it takes to arrive at different objects.

2. Know other ships (both targets and threats). Obviously, this is another huge factor in PVP. Know which ones to run from and which ones to fight. Don’t just go, “Oh hey, there’s a ship my size. Attack!”

  • Know the ships’ bonuses and make them worthless (e.g. when in a Punisher and facing a Rifter, don’t do your usual orbit-tightly-and-shoot technique. They have bonuses for tracking; you don’t. I’m not saying not to orbit at all, I’m saying to just orbit loosely enough that their bonus means nothing for them).
  • Know the other ships’ resistances (and change ammo as appropriate; also know which type of shield/armor tanking they do, and use ammo against that).
  • Know the other ships’ fits. Use EFT and Battleclinic. See which fits are rated well. Look at them and get an idea of what type of fits to expect (e.g. I’ve made at least one EFT fit for every ship of every race from frigates up to battlecruisers). This takes time, but it’s a one-time effort. And be pleasantly surprised if their fit is lacking.
  • Know the other ships’ speeds and optimal orbit distances (if they have short range guns, try orbiting farther away. For example, if you are in an interceptor and are fighting a Rifter, you should almost always try to stay farther than 10km away. That way they cannot web you, cannot turn off your MWD, cannot run out of disruptor range, and cannot hit you. Of course, if you’re in a Taranis or other blaster boat, you may have to come closer).
  • Know the other ships’ tracking speeds. Use the DPS charts in EFT to figure out what distance and speed you should orbit at.
  • Plan accordingly, and know your responses to actions. And before going into any fights, know what the opponent may try to do. Once again, be pleasantly surprised if their pilot skills are poor.

3. Know your surroundings. Make use of the system map. It’s not there just for probing.

  • Know its size and location of objects. Know where clusters of “juicy” belts and planets are.
  • Know where stations are, and know what agents are in the station that newbies may use.
  • Know how much gates and stations can protect you (if you’re blinky red, not at all; when I don’t have a GCC, I hang around stations so that I can dock to get out of danger).
  • Know your system’s occupants. Know who is usually there. You may want to set “permanent” residents red so that you are wary of them.
  • Know nearby systems. Know how many people are usually in them. Know why they are popular.
  • Make bookmarks. Don’t be lazy. Don’t wait until you have a GCC and a cloud of angry/opportunistic capsuleers chasing you to make a safe. Make a couple deep safes. Make enough so that you can hop from one to another every few minutes to thwart probers. Make bookmarks outside gates, belts, and stations. Eve isn’t simply a 2D game. If you have a battleship or other long-range ship, you can even hop from one bookmark to another and pummel your opponent while he vainly attempts to close in on you (just make sure not to get scrammed). Fight on your own terms.
  • Know how to use directional. Figure out a good scanning strategy. Set up an overview setting called “Scanning” that lists only ships.
  • Watch local. It will take up extra space, but keep it in a separate window from your other channels. THIS IS CRUCIAL (when I first started, I didn’t do this because I wanted to see more than just a mass of windows. That quickly changed when I got blobbed without realizing that the local count had shot up). Watch local for large gangs. Watch for GCCs that indicate recent battles.

4. Know your opponent. In smaller systems, know EVERY single pilot in local. You are never alone – local is your best friend.

  • Before warping in on anyone, try to find out as much as you can about them. See their bio, what type of person they are. Big-time “I keel you” pirates are often brash and overconfident and often have support. Look at their corporation history and alliances. Check their standings – see if they missioned a lot. If they have medals, check those out too (and salivating over medals that you wish you had doesn’t really hurt either). If some player (noob!) has certificates, check those out. For players older than Apocrypha (around March 2009), check their race. Players less than a year or two old are more likely to have trained largely toward ships of their starting race.
  • Set dangerous corps/militias red. This will help you easily see blobs.

5. Know your computer. Eve may be like a whole world in itself, but you do happen to live in another world.

  • Move your windows around. Those that you don’t use much, make clear and pin them down. Know exactly where on the screen things like targets, the overview, modules, chat, drone bay lists, fleet windows, etc. are. And make sure all pertinent information is clearly visible. Don’t try to save room by stacking windows; when PVPing, you often forget to check stats that are not immediately visible. The only windows I stack are overview and the fleet list (when you’re fighting, you almost never check your fleet list; all important people should be on your watch list).
  • Declutter your overview. Learn how the overview works. Customize them to your liking (Manasi offers some practical advice here). You should never have to search through a long list for your target. You might even end up shooting your teammate.
  • Configure graphics. Yes, textures and all are pretty to look at. Your wreck isn’t. Set settings as low as necessary (and as low as you can bear – I play on a laptop with a 13″ screen).
  • Configure your ship controls. Group weapons. Hide passive modules and empty slots. Move offensive modules (turrets/launchers, nosferatus, energy destabilizers, tracking disruptors, smartbombs, ecm, etc.) to the top row. Move defensive/nonoffensive modules (afterburner, armor repair, shield booster, etc.) to the middle row. Move resistance modules (damage control, active hardeners) to the bottom row – you rarely ever need to turn these on or off. Memorize their location and keep them in the same place every time, regardless of ship, to avoid confusion.
  • Use custom keyboard shortcuts. Make sure they’re intuitive and easy to reach. (e.g. I have ctrl+1, 2, 3, etc. for the top row, ctrl+q, w, e, etc. for middle row, and no shortcuts for the bottom row. Telling drones to attack is ctrl+9, and recalling drones is ctrl+0).

The lists above are just a starting point towards succeeding in Eve, toward acquiring Piloting Savviness level 1. You need to go further. As you train skills and gain experience, hone your techniques. Fly smart. Fly deadly.