2.2 is a Disappontment for PYTHON Commanders

Yea I can't believe they can land on a medium pad, given how large they are. It's like every Python comes with a Bag of Holding.

Actually, the reasoning behind this, is it doesn't have the required launch hatch underneath the ship. This isn't a design flaw, it was intentional.
 
As a Python pilot, I disagree with most but agree on one thing:

we CANT get cabin for passengers

I don't want passengers in my Python, my Python doesn't do sightseeing.
I don't want my cabin filled with the bad breath of passengers.
I don't want the grubby passengers to mess up the interior of my ship.
I don't want to get pirated for all that delicious airline food.
I don't want passengers iPhones interfering with my navigational equipment.

we CANT transport ANYONE

I don't want to. They can catch a Taxi instead. One of those Haulers with a yellow paint Job, with a good jump range. Not in a Python.
If I DID transport someone, chances are my style of piloting would cause them to vomit. Now who wants to clean that up? Or pay to have it cleaned?

we CANT get fighter port

Somewhat disappointed with this, I WANTED the ability to fit a fighter bay, just so I could send out the hired crew member to help out with the Pew-Pew.
I am led to believe the Python is too small to hold a fighter bay... Yeah, sure thing, I'll roll with that for now. I wasn't going to trust a hired crew member with my Python anyway.
(While taking out a SLF for a spin.) I can live with this for now.

what the f... they think the damn second pilot seat on my right is for?

Now this! this actually DOES grind my gears. Either throw out the second seat and center my pilots seat, or pop a hired crew member in the second seat and make him useful.
 
Yea I can't believe they can land on a medium pad, given how large they are. It's like every Python comes with a Bag of Holding.

Where they can or can't land is irrelevant to the internal size dimensions. If the Keelback, which is smaller, can carry a fighter bay, then the logic for why a Python is incapable of doing so, escapes me. After all, it can carry more cargo.

https://youtube.com/watch?v=t2uaRHFmBT4
 
Last edited:
Well,

we CANT get cabin for passengers
we CANT transport ANYONE
we CANT get fighter port
so all the fancy new stuff is NOT for python pilots which is ridicolous because what the f... they think the damn second pilot seat on my right is for? i cannot even take ONE damn passenger with?! SO WHY THE FRICKIN SECOND PILOT SEAT?!?!?!?!?!?!?!?

Also why no damn cabins? FD argued that the pythin is "already a multipurpose ship". YES IT IS!!! and exactly THATS WHY it does not make ANY sense at all why i cannot customize my MULTIPURPOSE SHIP as I WANT. I could live with not gettin the fighter bay. screw that. but why the damn not the cabins?

next thing i didnt understand so far: where can i setup my avatar?! i didnt find it anywhere. so?

right now, the whole "BIG" update are just some changed sounds, some new small details in the UI, a new menu i didnt ask for and some functions which are not that hard to implement - from a python pilots POV.

i cant get passenger missions
i cant hire crew members. well i can, but its absolutely pointless since i cannot not assign them since i dont have a fighter port. in "reality" i COULD assign a crew member to MY or the second seat which then would assist with my ship while im on the ground with the srv. but hey, thats not possible! so what the point anyway....

yes im damn disappointed. 9gb update for some little little sound and menu changes and that i cannot transfer my ship.... almost a year for that....

*slowclap*

did
3 passenger mission yesterday...

I could hire a crew (didn't do).

Guess your download is corrupted
 
Where they can or can't land is irrelevant to the internal size dimensions. If the Keelback, which is smaller, can carry a fighter bay, then the logic for why a Python is incapable of doing so, escapes me. After all, it can carry more cargo.

https://youtube.com/watch?v=t2uaRHFmBT4

Not that argument again....

From a beta discussion:

Size has absolutely nothing to do with it, it's down to the functionality of the design based on its intended role. Which is why you'll see the Federal Gunship in the list of fighter bay compatible ships alongside the likes of the Anaconda and Corvette.

Admittedly why they seem to have singled out the Gunship, when fighter compatibility in the basic Dropship would have made just as much sense purely from the design intention of the ship is anyone's guess. In my eyes, it should have been both the Dropship and the Gunship variants that could support fighter bays, and then leaving the Assault Ship as the only non-fighter variant in the series for the trade off of best individual combat performance.


On the subject of "Why the Keelback but not the T-x?". Again look at it from the perspective of the ships intended role when being designed.

The Keelback design is outright stated to be a more combat orientated solution as far as trade vessels are concerned, sacrificing efficiency as a trade ship in return for additional protection. Whereas the T-x series of designs are dedicated purely toward being dedicated trade vessels.... so in keeping with the design philosophies behind each series of ships, it makes sense that the Keelback would have part of its design included to support a fighter bay at the loss of trade potential, whilst most T-x series of designs don't make those sacrifices.

If it helps, think of it as that these features have always been the case and that the fighter bay space in the design has always been used for such (But just hidden, because the mechanics weren't implemented). And now we're actually seeing the implications of why the various ships have a difference in module capacity and the like.

What the Keelback never had in additional hardpoint/module capacity is because it was utilised for room to field a fighter bay.

What the T-x series of ships used for that additional hardpoint/module capacity, means they didn't have any spare room for a fighter bay.

Customisation of interior space so you can use parts of a ship for connective storage, a refinery or electronic scanners is one thing. Remaking the very shape and composition of the hull is another.

Same thing applies to the Python.
 
Wow, update is out less than a day and we already have whiners coming out to complain. So sad.

How can I put this... before 2.2 I was about to drop a very real £500 on a new graphics card for my gaming rig so I can enjoy E: D better. Between the lower perf of 2.2 and several major problems with game mechanics (i.e. running around doing missions for 15k cr when the ship re-buy is 8 M cr) then yes, people are going to get upset!

I still don't understand why people think Sothis was some kind of hack - everyone had access to it, everyone knew about it, so it wasn't "unbalanced".

What is completely unbalanced, is how you can no longer fly a ship of any value, because it would take so long to just make the credits for the re-buy that the whole thing becomes pointless.

Example: I had a combat fitted Anaconda, re-buy 15 M cr. I'm in a res for an hour and kill 12 ships. I get 150k.

I go to a high res - I take on one ship - an Anaconda - and kill him. 100k. BUT!!! It did 390k damage to my ship!

So now, I spent over 2 hours to make sod-all in the way of credits, and then end up making a loss.

The regular missions are currently borked - in "fixing" Sothis, they totally broke mission rewards, so you spend HOURS making 50k.

If this is "balanced", people have a very screw-up idea of what "balanced" really means. It's supposed to be fun. Before 2.2, it was. Now? Now it is broken.
 
It's a Python. What would I need a small fighter for if I had that ship?

Because it's not exactly agile and now mines are apparently useless. The former might change if you tangle with engineers, but I don't know anybody who wants the grind associated with that.

As for that quote, Tikigod, the contradiction in regards to the Federal ships points out how ridiculous this is. :) remember, the fighter bays are modular. They don't require spcific types of ships (and if they did, the Python is just as multi-role as anything else). Any ship can pretty much serve in any role, some are just more agile or faster than others, that's all (even hull and shield strength can be modified). The only value which should come into play is internal storage, nothing else - the thing is simply carrying a flight-capable vehicle. No different, in principle, to SRV carriage.

It's basically Frontier deciding the Python would magically become too powerful or whatever. Not allowing the Python to use a fighter bay makes no more logical sense than drones getting 'consumed' when they return back to you. I'll hand-wave it for that reason, but I'm not going to pretend it would stand up to scrutiny.
 
How can I put this... before 2.2 I was about to drop a very real £500 on a new graphics card for my gaming rig so I can enjoy E: D better. Between the lower perf of 2.2 and several major problems with game mechanics (i.e. running around doing missions for 15k cr when the ship re-buy is 8 M cr) then yes, people are going to get upset!

I still don't understand why people think Sothis was some kind of hack - everyone had access to it, everyone knew about it, so it wasn't "unbalanced".

What is completely unbalanced, is how you can no longer fly a ship of any value, because it would take so long to just make the credits for the re-buy that the whole thing becomes pointless.

Example: I had a combat fitted Anaconda, re-buy 15 M cr. I'm in a res for an hour and kill 12 ships. I get 150k.

I go to a high res - I take on one ship - an Anaconda - and kill him. 100k. BUT!!! It did 390k damage to my ship!

So now, I spent over 2 hours to make sod-all in the way of credits, and then end up making a loss.

The regular missions are currently borked - in "fixing" Sothis, they totally broke mission rewards, so you spend HOURS making 50k.

If this is "balanced", people have a very screw-up idea of what "balanced" really means. It's supposed to be fun. Before 2.2, it was. Now? Now it is broken.

Does no one know about the millions to be made at obsidian orbital?
 
Sounds like confusion over the luxury module, leading to an assumptions around outfitting.

Lux cabin is Beluga, Orca only, every other module (first, business, economy) can be fitted to any ship that can support at least a class 3 module.

Also fighters are only available for certain ships due to basic logic constraints around the hangar and fighter size; hence the class 5, class 6 module size. This pretty much means only certain ships may carry one (or two).
 
Last edited:
You all do know that all the ships said, in their description, if they could launch fighters, since the game came out... right?

Why are people complaining now? Did you not read? Did you think it might magically change because you really wanted it to?

So sick of the modern gamer and their sense of entitlement. The game maker doesn't want the python to have fighters. Deal with it. Go buy a better ship. I used to love my python, but now I love my cutter, my corvette and my beluga.

Just move on. They're not going to change their vision for their game because you cried on the forums.
 
Last edited:
I think the criteria for a ship getting a fighter bay should be that it has poor maneuverability and it also has a class 5 module slot, and the Python ticks both of those boxes.

Python just got even more unattractive I'll agree, shame because it's a beautifully designed ship. I'd love to be using one in endgame, and you'd think that something that costs 60 or so million with stock parts would be a bit more viable.

I know the Python is a multi-role ship also, and I'm not really sure if this is a good argument against it getting a fighter bay (since the Conda has one) I certainly think the Python would simply become more usable for those who are in love with the ship. It definitely wouldn't overpower it.
 
How can I put this... before 2.2 I was about to drop a very real £500 on a new graphics card for my gaming rig so I can enjoy E: D better. Between the lower perf of 2.2 and several major problems with game mechanics (i.e. running around doing missions for 15k cr when the ship re-buy is 8 M cr) then yes, people are going to get upset!

I still don't understand why people think Sothis was some kind of hack - everyone had access to it, everyone knew about it, so it wasn't "unbalanced".

What is completely unbalanced, is how you can no longer fly a ship of any value, because it would take so long to just make the credits for the re-buy that the whole thing becomes pointless.

Example: I had a combat fitted Anaconda, re-buy 15 M cr. I'm in a res for an hour and kill 12 ships. I get 150k.

I go to a high res - I take on one ship - an Anaconda - and kill him. 100k. BUT!!! It did 390k damage to my ship!

So now, I spent over 2 hours to make sod-all in the way of credits, and then end up making a loss.

The regular missions are currently borked - in "fixing" Sothis, they totally broke mission rewards, so you spend HOURS making 50k.

If this is "balanced", people have a very screw-up idea of what "balanced" really means. It's supposed to be fun. Before 2.2, it was. Now? Now it is broken.

Looks like your biggest issue are mission payouts. Sometimes it takes a few days after a major update until things settle down. I suggest to play for one week and gather feedback. If the issue still persists make a poll :)
 
I think the criteria for a ship getting a fighter bay should be that it has poor maneuverability and it also has a class 5 module slot, and the Python ticks both of those boxes.

Python just got even more unattractive I'll agree, shame because it's a beautifully designed ship. I'd love to be using one in endgame, and you'd think that something that costs 60 or so million with stock parts would be a bit more viable.

I know the Python is a multi-role ship also, and I'm not really sure if this is a good argument against it getting a fighter bay (since the Conda has one) I certainly think the Python would simply become more usable for those who are in love with the ship. It definitely wouldn't overpower it.

Maneuverability can't be the only criteria. The Python has serious fire power, and very good hard points. Not to forget the whopping big c7 Distributor. If you carried your argument just a step further the FDS, and Clipper should be on your list. I have a mission runner Python. It is tough as nails for this work. It doesn't have to be a down right fighter as well. Some ships were created with the SLF's in consideration. To me adding the ability to a ship not planned for them, should incur a cost to balance things out.
 
I think the criteria for a ship getting a fighter bay should be that it has poor maneuverability and it also has a class 5 module slot, and the Python ticks both of those boxes.

Python just got even more unattractive I'll agree, shame because it's a beautifully designed ship. I'd love to be using one in endgame, and you'd think that something that costs 60 or so million with stock parts would be a bit more viable.

I know the Python is a multi-role ship also, and I'm not really sure if this is a good argument against it getting a fighter bay (since the Conda has one) I certainly think the Python would simply become more usable for those who are in love with the ship. It definitely wouldn't overpower it.

The Python is unattractive? It's one of the best ships in the game.

I think the issue with SLF is that the Python isn't tall enough.
 
Maneuverability can't be the only criteria. The Python has serious fire power, and very good hard points. Not to forget the whopping big c7 Distributor. If you carried your argument just a step further the FDS, and Clipper should be on your list. I have a mission runner Python. It is tough as nails for this work. It doesn't have to be a down right fighter as well. Some ships were created with the SLF's in consideration. To me adding the ability to a ship not planned for them, should incur a cost to balance things out.

The Pythons firepower doesn't really mean much since it has a lot of problems getting anything in front of its guns. And I knew the multi-role argument would come up, but dont forget that the Python IS a naval ship and its a pretty terrible fighter, so it should perform a little better than it does. If you compare it to other multirole ships, the Python is probably the worst performing in terms of combat. (pound for pound)

IMO FDS doesn't qualify, because while it has poor "on paper" maneuverability, it's actually very easy to use in combat because of the built in drift. The thing basically uses automatic FAOFF and it's pretty fun to use in combat, not frustrating like the Python.

Clipper is also just too maneuverable. The only time you'll ever see that things broadside is if you're not in combat with it.
 
Last edited:
I am led to believe the Python is too small to hold a fighter bay... Yeah, sure thing, I'll roll with that for now. I wasn't going to trust a hired crew member with my Python anyway.

Now this! this actually DOES grind my gears. Either throw out the second seat and center my pilots seat, or pop a hired crew member in the second seat and make him useful.

Well, no, the Keelback can fit a fighter bay so one could probably be fit in to the Python as well, it was just never designed for it.

Multicrew is part of the next update, presumably that will include NPC crews.

Why are people complaining now? Did you not read? Did you think it might magically change because you really wanted it to?

To be completely fair, descriptions also said the Anaconda could launch a Sidewinder and that the Corvette could launch two fighters, descriptions and indicated capabilities are clearly open for change.

If there's any ship that deserves having fighter bay capability added I'd say it's the Type 7, Python is fine without (though I certainly wouldn't mind a small manoeuvrability boost).
 
Back
Top Bottom