[1.3.0] Kerbal Engineer Redux 1.1.3.0 (2017-05-28)

[Padishar]

Not sure if this is the right place to ask, but will 1.0.2 KER works on 1.0.4? I didn't dare to try to prevent certain "kraken" happening.

Yes, 1.0.16.6 should work as well in KSP 1.0.4 as it does in KSP 1.0.2 (slightly better in fact, as there were a couple of bugs fixed in 1.0.3 that directly affect KER, like the latitude display showing north for small south values).

[Guest]

It doesn´t work for me . It says "Unsupported KSP version. Please update for 1.0.2. [Close]" Any way to prevent this? Because it seems to work for you guys apparently.

EDIT: Nevermind, after redownloading it worked ingame nevertheless.

[Padishar]

That message shouldn't stop it functioning as normal. It just tells you that the version of KER you have was not built explicitly for KSP 1.0.4.

[SquaredSpekz]

It doesn´t work for me . It says "Unsupported KSP version. Please update for 1.0.2. [Close]" Any way to prevent this? Because it seems to work for you guys apparently.

EDIT: Nevermind, after redownloading it worked ingame nevertheless.

That is a plugin looking at a file where it says 1.0.2 and says its wrong. does not mean its not going to work.

[Jananton]

I just looked here to see if there's a simple solution to get rid of that message, but it seems there isn't. So we just have to wait I suppose.

Fwiw the plugin itself works fine.

Greets,

Jan

[Eleven]

I just looked here to see if there's a simple solution to get rid of that message, but it seems there isn't. So we just have to wait I suppose.

Fwiw the plugin itself works fine.

Greets,

Jan

I guess that depends on what you mean by 'simple'...if you just delete the MiniAVC.dlll and it's html cfg file, you stop getting that warning

[MartGonzo]

I don't think it's fully working in 1.0.4 as it was telling me that a rocket had a TWR of 1.4 but it wouldn't get off the pad, could be something to do with KW Rocketry though as most of the parts were from that mod.

[Padishar]

Were you in "Atmospheric" mode? Engines generate considerably less thrust at sea level...

[MartGonzo]

Were you in "Atmospheric" mode? Engines generate considerably less thrust at sea level...

I'm 99% percent sure I wasn't but I can't check right now.

I'll give it another look tomorrow and try various engines to try and understand what's going on and report back.

[Padishar]

You are misunderstanding. The build engineer in the VAB defaults to showing figures for vacuum where all rocket engines give more thrust than they do at sea level. This causes the reported TWR to be higher than it will be when on the pad. Clicking the "Atmospheric" button switches it to display figures for sea level and also gives you a slider to adjust the altitude used for the simulation (and one for the speed of the vessel as well, though this only affects jet engines).

[Jananton]

I guess that depends on what you mean by 'simple'...if you just delete the MiniAVC.dlll and it's html cfg file, you stop getting that warning

Hmm, did take a look, but wouldn't changing the *.version file be easier. ;-)

Meanwhile I do like to see when an update is available, so I better leave it, can't be too long.

Thanks for providing a solution though. ;-)

Greets,

Jan

[Eleven]

Hmm, did take a look, but wouldn't changing the *.version file be easier. ;-)

Meanwhile I do like to see when an update is available, so I better leave it, can't be too long.

Thanks for providing a solution though. ;-)

Greets,

Jan

Changing the version number in the text file doesn't work in the case of a mod that uses AVC. You have to deal with AVC, not just the version number. Now if a mod doesn't use AVC, then yea, just changing the version number and resaving the text file will make the popups go away

[MartGonzo]

You are misunderstanding. The build engineer in the VAB defaults to showing figures for vacuum where all rocket engines give more thrust than they do at sea level. This causes the reported TWR to be higher than it will be when on the pad. Clicking the "Atmospheric" button switches it to display figures for sea level and also gives you a slider to adjust the altitude used for the simulation (and one for the speed of the vessel as well, though this only affects jet engines).

oh ok, was that changed at some point?

I seem to remember it defaulted to showing TWR at sea level.

[davidpsummers]

That message shouldn't stop it functioning as normal. It just tells you that the version of KER you have was not built explicitly for KSP 1.0.4.

I just started using KSP 1.0.4. I'm getting the message to use KER 1.0.2 also. I take it I should ignore it and use KER 1.0.16?

[Padishar]

oh ok, was that changed at some point?

I seem to remember it defaulted to showing TWR at sea level.

It has always defaulted to showing vacuum figures but, pre-1.0 the changing Isp with pressure caused the fuel flow rate to change and the thrust to remain constant but this was changed in 1.0 so that the fuel flow rate stays constant and the thrust varies.

Davidpsummers, yes, just ignore the warning for now.

[cybutek]

Version 1.0.17.0 is now available! - Get it here!

Added: 'Mach Number' readout under the 'Surface' category and included it on the default surface HUD.

Added: Stock sections in the Flight Engineer can now become HUDs.

Added 'Thermal' readouts category including:

Internal Flux

Convection Flux

Radiation Flux

Critical Part Name

Critical Part Temperature

Critical Part Skin Temperature

Critical Part Thermal Percentage of Max Temperature

Hottest Part Name

Hottest Part Temperature

Hottest Part Skin Temperature

Coldest Part Name

Coldest Part Temperature

Coldest Part Skin Temperature

Changed: Mach on the Build Engineer now accurate to 2 decimal places.

Changed: Max mach in the Build Engineer defaults to 1.00 even when no jet engines are present.

Changed: Increased eccentricity readout to 5 decimal places.

Changed: Implemented Sarbian's object pooling.

Changed: The default selected body is now assigned via 'Planitarium.Home'.

Changed: HUDs to clamp fully inside the screen instead of allowing them to run off the edge by a certain amount.

Fixed: Physically insignificant part mass is now associated with the parent part.

Fixed: Longitude and Latitude readouts now use a KER formatter instead of Squad's incorrect implementation.

Fixed: Possible null reference in the Rendezvous Processor.

Fixed: Fairing mass issues introduced with regards to simulation changes.

Fixed: Use of per-propellant fuel flow mode override.

Fixed: Burn times calculated for jet engines.

Fixed: Thrust issues introduced with Sarbian's simulation alterations.

Fixed: Issue where HUDs positioned close to the top/bottom of the screen could be pushed out of position.

[Red Iron Crown]

Excellent! I've been hoping for more thermal data and a Mach readout, thanks for the update. Great work as always!

[Harry Rhodan]

Added: 'Mach Number' readout under the 'Surface' category and included it on the default surface HUD.

Nice work. Have you thought about adding a dynamic pressure readout too? But I guess that's a lot less trivial.

[Jananton]

Nice, updating now, thanks.

I really do hate incompatibility messages.

Greets

Jan

[Nansuchao]

Congratulations for the new release, it's awesome!

Wonderful job!

[bloatedpenguin]

I just wanted to run this by you in case it isn't an intended feature. The readout in the VAB doesn't take into account the weight of objects attached by decouplers or stack separators.

http://imgur.com/a/k3Sml#0

[Red Iron Crown]

I just wanted to run this by you in case it isn't an intended feature. The readout in the VAB doesn't take into account the weight of objects attached by decouplers or stack separators.

http://imgur.com/a/k3Sml#0

You have the decoupler and engine in the same stage. The mass showing in the overlay at bottom left is correct, the simulation is reading your staging as jettisoning the payload simultaneously with igniting the engine. You can see more info if you click "Show All Stages" to see non-propulsive stages and their masses.

Edit to add: One of the pics shows separate staging, I think the simulation is assuming the "dead" mass of the rover will be dropped immediately (KER doesn't have a way to designate what is payload other than by looking at root part).

Edited June 25, 2015 by Red Iron Crown

[bloatedpenguin]

One of the pics shows separate staging, I think the simulation is assuming the "dead" mass of the rover will be dropped immediately (KER doesn't have a way to designate what is payload other than by looking at root part).

Right. I forgot to switch the staging on the 1.25m decoupler, but it's the same anyway if it is switched. And you're right, I tested it by rebuilding it beginning with the rover body as the root part and it took the mass into account.

[A_name]

Why is KER not appearing on CKAN?

[Goddess Bhavani]

Thanks for the 1.0.4 update! I have refrained from playing 1.0.4 until Kerbal Engineer got an update, that's how crucial it is to me