Large Port - Must be used in conjunction with a Heavy Storm Radar Extender or the built-in one on a Trident Type M.
Name: Long-Range Ion Field Detector
Mass: 10000kg
Grid: 4
Licenses: -/-/-/-/-

When equipped, is able to detect all ion storms within a system and marks them blue on the Nav map. Also further increases radar range within an ion storm to 4000m.

*strokes chin* yes

+1
yeah, baby!

I disagree with having it system-wide. Give it a three- or four-sector radius instead.

+1 Pizzasgood

-1 to system-wide, neither Trident builtin.
+1 to limited range, 3 sector radius covers some 24 sectors, quite enough.

We can have a AWACS version of Trident with full sensor suite(cargo, addon, storm), group extender, and this ER storm radar. Maybe even sporting a 25/50KM radar, practically covering all sector... but not for every model.

He didn't mean it would be built into the trident. He meant that the storm radar that is already built into a trident would satisfy this addon's requirement for having a storm radar.

-1. Just cause you have a trident doesn't grant you the right to add some extra crap to be able to have notification of storms in the area. Learn to plot around it, like everyone else.

Uh, it's not just for the trident. You could put this on any other ship with two l-ports too and act as a storm scout for your group.

Besides, people who *really* want to avoid storms already do so with NavComp and making ridiculous extra jumps all over the system.

Also, this would take up the trident's only captain-operable port. So a trident using it would not be able to carry nukes to drop on you.

One application this would have besides avoiding storms is more easily finding storms, to get the XP multiplier while botting.

XP multiplier is valid in off mission botting as well?

I don't know actually.

No the XP modifier is only for hive skirmish missions. There's other uses for ion storms though.

enlighten me please. I thought they only got in the way

They can be a good way to hide or lose pursuers. I imagine storms could also be a good way to mine covertly, since it would be a lot harder for pirates to tell that you're there.

Actually Navcomp does a pretty good job now at plotting around a system, especially if you take the time to play with setting the system metadata. The defaults were quickly put together and can lead to weird solutions when avoidance data density gets high; I'd always expected that people would research the best metadata sets for the comparator logic and make it sellable. I've got my copy pretty customized on the metadata side. With caching turned on, NC can plot fairly reasonable paths across multiple systems in just a few seconds. It's not perfect, and I admit that. Current version is 1.6.5, so I really should update the writeup in the forum. The new version includes things like: autoplotting of loaded paths, and autoreloads for doing things like combat in a particular sector or bombing runs.

Yeah, NavComp is great for avoiding storms. I don't want to avoid storms, I want to find them.

Duh...
If NavComp is good for avoiding storms since it shows where they are... also show where you can go to get 'ionized'...

Despite not all storms will show allways show up, but a few well planned diagonal jumps will cover a whole system. Add both and you already can have coverage, if you're not lazy...

What I'd love with storms would be a way to mathematically predict them. If they were a big blob that covered multiple sectors but "moved" across the system, it would be very possible. Presently, the things are just random speed bumps. That was one reason I had to accept the "all or nothing" approach to storms in NC; once a storm is recorded in a sector, that sector is marked as to be avoided no matter what.

Whether we have some new toy that allows us to find storms more effectively or not, the fact they are still randomly occurring is really the problem here.