Have any of you Cdrs ever explored in a Python?

[Cdr Voorheez]

I have been running a few figures through Coriolis this morning over a nice cup of tea and noticed that you can squeeze a bit more range out of a Python than you can out of a Cobra. Now I own both of these beauties: one for trade one for exploring, and was wondering:

Have any Cdrs here ever explored in a Python?
Am I best just sticking with the Cobra to explore and the Python to trade/BH?

My tidy brain is thinking 'keep it all in one ship'. The Python can do all roles admirably but is it too much a risk?

Advice please, my builds are attached for your analysis. The Python build is speculative and is just Coriolis data at the minute. Cobra build exists.

COBRA: http://coriolis.io/outfit/cobra_mk_...8242f2i.AwRjNco5KA==.Aw1-kA==?bn=Kon-Tiki III

PYTHON: http://coriolis.io/outfit/python/03...h2f.AwRjNcq5Nsg=.Aw18eQ==?bn=Proteus Explorer



All advice appreciated.

 

[PanicButton]

Again with the docking computer

NPC interdiction seem to be the flavor of 1.4, so we might have to rethink the exploration builds. I would say best thrusters and power distributors may be in order for faster ships. Maybe weapons and stronger shields for bigger ships.

I just found out that we have the nebula CG in two weeks, so I have to postpone my next voyage (again)

That's a lot of cargo space on your explorer python, seems like a waste for all those high class slots, but I'm no expert.

 

[goemon]

here is another python explorer: https://forums.frontier.co.uk/showthread.php?t=164901
___

interesting build -

concerning the cobra, i still think you will want to fit a cargo rack. what do you do if you find a unknown artifact by chance --- or something they add while you are out exploring?

the python: i'm fascinated, that the python get's more jumprange than the cobra. never thought about it as an explorer.

i would suggest the following: either put thrusters or the d-class shield one class more (if you keep the docking computer, take the shield). the python is slow by itself, and it has a massive hitbox, so you should make sure that you can stand at least an npc-attack when returning from a trip.
for above reasons i would put a d-class collector limpet controller with 0,5 T weight, and take 3 limpets with you, because with 5D thrusters the python might "fly" like a brick (actually i never tried, but i know the python with 7D - no fun...)

___

i personally have parked 2 of my 3 exploring vessels on the edge of space, if i want to do a trip i take my python or cobra there and set off. so i'm totally not the "one ship"-cmdr - but each his own!

 

[Eisen]

What I would find interesting is, if the explorer-build-Python also has heat-issues while scooping. My battle-Python always heats up very quickly while scooping.
The jump range is great for the Python, never thought, that you can squeeze that much range out of it. But another con may be the fuel consumption.
Maybe you just give her a go for a small journey and report back here. I'm looking forward for your findings.

 

[goemon]

What I would find interesting is, if the explorer-build-Python also has heat-issues while scooping. My battle-Python always heats up very quickly while scooping.
The jump range is great for the Python, never thought, that you can squeeze that much range out of it. But another con may be the fuel consumption.
Maybe you just give her a go for a small journey and report back here. I'm looking forward for your findings.

hm. no heat issues on my multipurpose python. have a 4a fuelscoop there, and run it with a powerplant one class lower.
__

on fuel consumption: the 5A fsd takes 5 tons of fuel max, so reducing the standard to 16 t and adding an additional 4 T should give you full 4 jumps, with a few ly more plotted jumprange... did this on my Asp. if you are ready to watch your fuel constantly, 4 jumps are enough... but it's not "comfortable" (also depends on your exploring style - if you are used to top up every jump, maybe that's a good outfit for you).

 

[Edelgard von Rhein]

I've taken my Python out to the Eta Carina Nebula complex, with what was then my regular armed trader loadout (jump range just over 21LY and a 6C scoop). The reason I did that was because I wanted to feel safe upon my return to the bubble (I had had a narrow escape returning from the Crab Nebula in my Asp on my previous expedition). It turned out that the UA affair kicked off as I was on my way out and I felt secure enough to pop into a few WSS/USS (I was not confident enough to try SSS back then). Feeling safe is important for me - I get jittery once I've been away for long. With a Python, many human pirates will leave you alone but the ones that are prepared to take you on can be trouble, whereas the Cobra has speed as its safety net. I would feel safe in either, to be fair.
Lately I've been running a more lightweight armed trading loadout for my Python that can just about manage 23LY jumps whilst also being able to fight (though not against other Commanders). I might take it out on another expedition once Horizons arrives and there will be the extra demands placed on internal bays for SRVs etc. but it's my go-to all-purpose ship for tasks in and near the bubble until then. If you want to be able to fight in a Python, you can put an A-rated shield on it and add a mix of lasers and projectile weapons and still get away with a downsized Power Plant. If you want to run, an A-rated shield will protect you for long enough to hyperspace to safety, without needing boosters or a SCB, so long as you're not facing a wing of Commanders in Clippers and Vultures. I suppose it depends just what jump range you want to get and what you want to do when you're out there (looking for interesting wrecks or other content that might be waiting to be found). A couple of heat sinks or a chaff launcher on your proposed build would add some extra safety without impacting much on jump range but it's your call to how you intend to respond if you find a filled/hollow triangle on your scanner. I like the handling of the Python, both in normal space and supercruise, and was happy to spend about two and a half weeks on my voyage but if you've not flown one before, try it out and see for yourself whether it suits you.

 

[Eisen]

I am feeling quite safe in my ASP. I can always high-wake out if I get into a situation and only another Explorer ASP or Explorer-Conda can follow me .

 

[CMDR_TheBS]

I've taken my Python out to the Eta Carina Nebula complex, with what was then my regular armed trader loadout (jump range just over 21LY and a 6C scoop). The reason I did that was because I wanted to feel safe upon my return to the bubble (I had had a narrow escape returning from the Crab Nebula in my Asp on my previous expedition).

Sorry to bump and old thread, but for those of you who have been out to the Crab Nebula ... what was the minimum jump range you needed to make it from one galactic arm band to the other? Would 20-23ly not be sufficient? I'm not worried about long jumps to reduce time, but whether or not a Python (that isn't totally stripped down) could make it?

 

[Henkka77]

There was at least 7 Pythons at the Distant Worlds expedition so i dont see any reason why it wouldnt be as suitable for Crab Nebula expedition.
Im returning from DWE atm with jump range of 26Ly and had zero problems, although I needed jumponium to reach the Beagle Point.
She's a fine exploration vessel and can highly recommend her for exploration.

 

[Kaybe]

Hmmm ...

I'm not overly enthused about the idea a Python as an explorer, personally. I do own and love the Python, but while it's jump range is 'good enough' for exploration, that combined with it's abysmal supercruise pitch rate make it kinda 'meh' for that purpose in my books.

 

[Henkka77]

I wouldnt say abysmal. She's a slowish pitcher but with exploration thats hardly an issue.

 

[Traveller_GG]

Hmmm ...

I'm not overly enthused about the idea a Python as an explorer, personally. I do own and love the Python, but while it's jump range is 'good enough' for exploration, that combined with it's abysmal supercruise pitch rate make it kinda 'meh' for that purpose in my books.

Gawd.... don't ever buy an Anaconda then

 

[Ziggy Stardust]

Hmmm ...

I'm not overly enthused about the idea a Python as an explorer, personally. I do own and love the Python, but while it's jump range is 'good enough' for exploration, that combined with it's abysmal supercruise pitch rate make it kinda 'meh' for that purpose in my books.

Looks good in screenies though.

Gawd.... don't ever buy an Anaconda then

After two days grabbing that cow by the scruff if it's neck to get it turned towards the next waypoint, skimming the star scooping, I did notice the difference between it and my precious T-6.

 

[Edelgard von Rhein]

Sorry to bump and old thread, but for those of you who have been out to the Crab Nebula ... what was the minimum jump range you needed to make it from one galactic arm band to the other? Would 20-23ly not be sufficient? I'm not worried about long jumps to reduce time, but whether or not a Python (that isn't totally stripped down) could make it?

The Crab Nebula is reached by a bridge of stars that requires a jump range around 25.5LY to get in, so with a level 1 jumponium boost a 21LY Python would hopefully make it (I forget the exact value of the longest jump I made but a combination of a low-fuel jump and jumponium should be enough). I have only been out there in my Asp, so I don't know if crossing the arms would be problematic with a 21LY range, though. Stay close to the Galactic Plane when making the crossing - the star density can also sometimes be slightly higher just below the Galactic Plane, although there are more unscoopables in this region, so be careful.

 

[dognosh]

With Engineers, the Python has become a viable Explorer(better pitch rate, but good luck RNGing it at the engineer !!!)

 

[Kaybe]

Alas, it can have better 'normal space' pitch rate. To my knowledge, there are no engineering mods that affect supercruise flight models.

 

[Kuroshio]

Never felt more comfortable exploring than in my Python during Distant Worlds. The maneuverability is good enough to allow minimum turn around times (being aligned with target while charging so you can still check the system map and abort when there's something shiny).

Still waiting for the official numbers, but the Python success rates during DW were quite high. They are tough old ladies - not fast, but they'll get you where want to be.

(Edit: Also, googling the news "python thai toilet" shows that they are both used to turning up in unexpected places and ... persistent.)