No evidence of reentry heating of any kind

[stratvox]

I came home to a new version of KSP today. Yay!

However, while I can see that there are aero effects, I'm not seeing any atmospheric effects (i.e. no mach effects, and no re-entry flames) and AFAICT there is no reentry heating happening at all. I did a clean install to check it wasn't some sort of mod issue, and even with a clean install and firing a rocket straight up past the orbit of Minmus and right back down again it didn't heat up and didn't blow up until it hit the ocean going app 2 km/s.

This cannot be right.

I'm running the 64 bit executable under ubuntu linux. Special points: I have an NVIDIA optimus card and am using bumblebee to switch to the card and load the game. This seems to be working as designed; attempting to load the game without bumblebee results in a non-functioning game, whereas the only issue I seem to be having when I use bumblebee is that re-entry is MIA.

I am willing to do such things as load debug builds etc etc. I'm not a dev, but I am a sysop in a development house and am quite happy to mess around and ship logs back and forth etc.

Oh, and FWIW I've been running the 64 bit executable from day 1 with basically zero problems.

...and I just tested using the 32 bit executable, and the issue is still there.

Here's Jeb about to pancake into the ocean: https://goo.gl/photos/TbHW1MhHV2qc6Hso8

[stratvox]

Here's the stuff:

BuildID.txt

----8<----

build id = 00859

2015-06-22_13-02-29

Branch: master

---->8----

Computer is a Samsung laptop with an nVidia 710m.

It has run the game without problems so far.

Game acquired via Steam.

[Daveroski]

I'm running under Linux Mint - Nvidia 980

Got all the effects that you are lacking.

I built a space plane. got to orbit, brought it back down on a very shallow decent ap@72 pe@1000

got heat, flames, temp gauges, mach effects, cooling gauges. stable flight, slightly front heavy. got to 2000m at <200ms. Used pitch-up to decelerate, pitch-down to cool off.

Before decent I sent fuel up front to make the front heavier and keep my CoL behind my CoM.

Of course it all went nuts as soon as I made a course adjustment to line up with the runway, Nose flew upwards, despite being nose heavy went into reverse and I tail-spun into the ground.

New install. No mods.

Back to the drawing board I suppose.

[KerbalEssences]

Have you checked the options menue whether the Aerodynamic effects are enabled? (Aerodynamic FX -> High) Might be set to low on default now for lower end graphics cards. Reentry heat can be also be set between 0% - 100% when starting a new game in the difficulty settings.

Edited June 23, 2015 by KerbalEssences

[stratvox]

Have you checked the options menue whether the Aerodynamic effects are enabled? (Aerodynamic FX -> High) Might be set to low on default now for lower end graphics cards. Reentry heat can be also be set between 0% - 100% when starting a new game in the difficulty settings.

Yes I did. And I started new games as well and checked to make sure that re-entry heating was enabled.

I have in fact completely deleted the install and installed afresh to make sure there were no extraneous issues. The problem remains.

Did you get yours from Steam?

Cheers,

Jack

- - - Updated - - -

And as an aside... I looked in the new save game file and here is the difficulty section:

----8<----

DIFFICULTY

{

AutoHireCrews = False

MissingCrewsRespawn = True

BypassEntryPurchaseAfterResearch = True

AllowStockVessels = True

IndestructibleFacilities = False

ResourceAbundance = 1

ReentryHeatScale = 1

}

---->8----

- - - Updated - - -

I have another post up as well, I figure I might as well mention it here; the Warp to Ap/Peri/Maneuver/SOI arrows are missing.

I'm hoping a dev will see this and can maybe give some insight as to what's going on here.

Thanks very much for the suggestions; while I'd already checked those it's always nice to see people taking a shot at figuring out what's wrong with this one.

Cheers,

Jack

[chrt]

Also affected by this.

[stratvox]

That's... pretty common in this game

Nice to know it's working for you. I'd love to figure out why it's not working for me. If you're in an unshielded capsule and you're still going over 2km/s 1800 m above the ocean, well, you should've died a few kms up from where you are. When it first hit the atmosphere it was going a LOT faster than that, so the aero is definitely working; it's both the heating and the actual effects (mach effects and re-entry heating effects) that are missing in this one.

I just took another shot at getting a craft to burn up on re-entry.

Here's the orbit I set up: https://goo.gl/photos/pRVcZnRtcyXW85LY9

It didn't burn up on a completely uncontrolled re-entry. This is pretty absurd.

It also kind of looks like the aero model is off... with chutes deployed and SAS turned off the craft is inclined to to the direction of travel about 25 degrees or so from where I would expect it to be.

Cheers

- - - Updated - - -

Also affected by this.

Nice to know I'm not the only one.

Linux? Steam? What video card do you have?

Cheers,

Jack

[chrt]

Ubuntu 14.04, non-steam version of KSP, Geforce 670 GTX with proprietary drivers.

[sal_vager]

Most of the variables for the heating are in the Physics.cfg so try renaming it, that will force KSP to make a new one when next started.

[stratvox]

Ubuntu 14.04, non-steam version of KSP, Geforce 670 GTX with proprietary drivers.

Ubuntu 14.04, 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M]

Using the proprietary drivers and OpenGL from the x-edgers PPA... absolute bleeding edge. Everything worked fine until this update came along.

The thing is... not only are the effects gone (as in I don't see them) but there's no reheating happening on reentry.

As more evidence, here's a ship running at 1742 m/s at 5800 M with temp overlay enabled. No mach fx, no heat fx, and the only part of the ship that appears to be heating up is the engine which is running flat out.

https://goo.gl/photos/K9iqSwVufgj2Qp7U9

I'm hoping we'll hear something soon, I want to get back to my career game. If I could figure out a way I'd install 1.0.2.3 again but I can't see any way to recover that version after Steam auto-updated my game.

Cheers.

- - - Updated - - -

Most of the variables for the heating are in the Physics.cfg so try renaming it, that will force KSP to make a new one when next started.

Oh, that's been done; I grabbed my saves folder, deleted the local content in Steam, deleted the entire "Kerbal Space Program" folder, and reinstalled it and am doing my testing on an utterly stock install. Hasn't made any difference.

I'll take a shot at it when I get home on the off-chance, but I don't hold out a lot of hope here...

- - - Updated - - -

I'd like to add thank you to everyone that's looking at this, I very much appreciate any and all suggestions coming my way!

Cheers!

[chrt]

Well, this is strange. I'm only able to reproduce this when starting KSP from a desktop shortcut ( exec=/opt/KSP/KSP.x86_64 ). If I actually go into the folder and launch it, it works fine.

Edited June 23, 2015 by chrt

[stratvox]

Well, this is strange. I'm only able to reproduce this when starting KSP from a desktop shortcut ( exec=/opt/KSP/KSP.x86_64 ). If I actually go into the folder and launch it, it works fine.

Now that sounds interesting! I'll have to try that when I get home and see if that makes a difference or not.

Working directory issues... perhaps they dropped a var representing the working directory when it comes to loading the models etc for that stuff.

[sal_vager]

I think that's come up before, but I forget why, I think the guy was failing to cd to the KSP folder before running the game.

Shortcuts really need to cd to the folder, then start KSP.

[stratvox]

I think that's come up before, but I forget why, I think the guy was failing to cd to the KSP folder before running the game.

Shortcuts really need to cd to the folder, then start KSP.

Okay, home now, and here's what I've found. Starting from the actual directory in 1.0.3 didn't work (as in "primusrun ./KSP.x86_64" from a terminal). I then updated it to 1.0.4. From my gnome launcher, still no goodness, but... running it from the Kerbal Space Program directory in the terminal brings it all back: aero fx, re-entry heating, the works.

Squad might want to look at what broke that in these latest updates (because it always worked fine using my launcher before) but at minimum I've got a workaround that'll deliver the game. I'm going to craft up a quick shell script and point my launcher at that and I'll be off to the races.

Thank you everyone for your help!

Cheers,

Jack

[sal_vager]

Primusrun didn't cause any issues then?

I have a script for my Steam install because I can't be bothered to open the game folder, it's not complex.

#!/bin/bash
cd "/home/user/.local/share/Steam/SteamApps/common/Kerbal Space Program/"
LC_ALL=C ./KSP.x86_64

[stratvox]

No, primusrun has never caused any issues afaict. In fact, without it the game is useless because the intel card in this machine doesn't support some absolutely necessary video features... resulting in their being NO LAND!

That's pretty much what I wrote, minus the LC_ALL=C statement. I assume that's to set the charset to C? I have a ~/bin folder that's in my path, I'll stick it in there.

Thanks again for your help. Hope you have a great night!

[sal_vager]

No land usually happens because the Unity engine anti-aliasing is broken on Linux, and has to be disabled, multisampled or fast-approximate AA can be forced by most drivers though