Game bug (Python overheating) cost's me to much...

I play base assault mission with this particular Python loadout:
http://coriolis.io/outfit/python/27...4.AwRj4z1Sg===.IwBj4yNUWI==?bn=Surface Terror

The problem is ... it starts to overheat without any reason. up to 250 and more degries.
I lost this ship about 10 times so it is about 100 millions, because 9 million is rebuy cost.
I am a good at combat and there is nothing in my loadout that can produce so much heating.
It just starts to happen and it is unstoppable ..
I am very very angry now... I lost so much money because of this ship bug!
This really, really sounds like you engaged silent running and didn't turn it off, the python has been nerfed but not in terms of heat, last I flew mine, granted that was pre horizon but horizon shouldn't have done anything to it last I checked.

That or you are using your shield cells way way too much since you don't have heatsinks.
 
Last edited:
This really, really sounds like you engaged silent running and didn't turn it off, the python has been nerfed but not in terms of heat, last I flew mine, granted that was pre horizon but horizon shouldn't have done anything to it last I checked.
SCBs were nerfed.
 
I have been loving my Python for many months, but there was one single time I did have something strange happen that could be what the op is describing.

I was on a planet surface, my heat was fine, but after I deployed hard points my heat shot up through the roof. Disengage weapons, all is fine & dandy, deploy hard points again, and again the heat flies out of control. It was a long time ago, and it hasent happened to me since, but there was that one planet (don't remember which one) I couldn't deploy my Pythons hard points without heat going from a normal 30 something, to YOUR GONNA DIE!!!!!!

... Just to be clear, that's just deploying hard points, not firing them

I had a very similar issue in my random Ground Assault Cobra Mk III. I was just pootling along, looking for POIs, in a straight line, at normal cruising speed (300~).

Then my heat shot up to around 140% for no reason.
Wasn't silent running cos my shields were still up, wasn't charging FSD(FSD only takes the heat up to 60% anyway), didn't even have hardpoints deployed. Wasn't being fired on.

Can't think what else it may have been. But it's never happened since.
I fixed it by just logging off. When I logged back in my temperature was nominal again.
 
Last edited:
IF it keeps happening, fire off heat sinks and retract weapons. See if that helps.


YOU could also try rebooting the ship (automated repair sequence).

Anything to buy you time whilst you work out what the fudge is going on.
 
CMDR, you fry your ship. 2 (!) class 6 cells without heat sinks is suicide.

Fire one heat sink 2 seconds before (!) you fire 2 class 6 shield cells for NOT roasting your modules.

This bug is on osi layer 8, unfortunately.
 
SCBs were nerfed.
Personally I don't think of it as a nerf, they just now have a consequence to them, and they were extended in duration and output too so no, not a nerf, also edited it in a moment after, since I gathered OP knew this but yeah might not.
 
Personally I don't think of it as a nerf, they just now have a consequence to them, and they were extended in duration and output too so no, not a nerf, also edited it in a moment after, since I gathered OP knew this but yeah might not.
Yes, "nerf" is a bad word. Balance? Sounds better.
I've just said that SCBs "nerf" caused this "overheating bug" in Python, not Python "nerf".
 
Silly me, I was freezing when deploying scanner with a weapon trigger. Thought it was a bug, checked multiple times, stared at the screen... It was happening again and again.... I use key combination to enable heat sinks and do not use fire buttons for them.

I was trying different loadouts and assigned heat sinks (dont know how and when) to a weapon group trigger, BUT Ive had so many things on a weapons tab, that the heat sinks were at the bottom of the weapon tab screen. That was making them invisible because I simply forgot one thing - that slider on the right side of the weapons tab you have to scroll to check all Utility mounts. :eek:
 
Last edited:
Yes, "nerf" is a bad word. Balance? Sounds better.
I've just said that SCBs "nerf" caused this "overheating bug" in Python, not Python "nerf".
I don't believe python's ability to handle heat has ever been touched?, its always been a bit sensitive to it, which kinda makes sense with a bulky ship like that? it was only pitch and shield that was touched?
 
The powerplant has nothing to do with generating heat,
in fact the only factors regulating heat are heat efficiency and how capacity of your pp you are using.
A rated pps all have a-rated heat dissipation,
but if you have more MWatts at your disposal and only use 80% of it with hardpoints deployed,
you will see a difference in heat in idling and firing.

So bigger is better heat wise.

i'm sorry, but this isn't true.

for a test result see here: https://forums.frontier.co.uk/showthread.php?t=192282

see powerplant size&class chart.

... beside the various builds of explorers.

you can check it out by yourself! (it would make more sense if it was your way, but it isn't)
 
The only time I have come close to losing my Python from overheating was when I got too close (too impatient) scooping and hit the shield boost instead of heat sink (DUH!).

No idea why yours should go over 250 but not a general Python issue afaik. Maybe record it next time so we can see what is happening?
 
Missiles can generate some heat along with that beam laser. You will also run hotter in atmosphere period.

Python has never really dealt with heat well.
 
Two SCBs... size-6. There you go. Disable the one which you don't absolutely need as they'll *both* activate when you poke the SCB keybind (or voice-bind, etc). Heat goes through the roof and beyond.
 
Last edited:
No, SCBs were buffed. They only generate more heat.
And as OP stated, they have nothing to do with this thread.
I see you too hurry again. Read from 1st page.
JdCO.png


About SCBs i've said too
Yes, "nerf" is a bad word. Balance? Sounds better.
I've just said that SCBs "nerf" caused this "overheating bug" in Python, not Python "nerf".
Two SCBs... size-6. There you go. Disable the one which you don't absolutely need as they'll *both* activate when you poke the SCB keybind (or voice-bind, etc). Heat goes through the roof and beyond.
even one 6A SCB will cause Python to overheat.
 
Last edited:
Back
Top Bottom