Overcooling shortly after spawning despite warmed up engine start

[coconut]

Problem: engines overcool quickly despite warmed engine start-up

 

Description:

Multiplayer set-up, I have not tested in single player.

Mission is set up in october on the Moscow map, temperature between 0C and 10C, middle of the day.

Server has warmed-up engine start enabled. No automatic engine controls (i.e. expert mode).

Spawn with a twin engine (e.g. bf110, pe2, ju88...). Techchat notifies you the engines are overcooled soon after you spawn.

Start engines. It is not uncommon that at least one of the engines will stall unless one gives a bit of throttle. For people who are not used to control engines individually, it can be difficult to get both engines going.

 

Work-around:

Keep feet on brakes during the entire procedure.

Select engine 1, start engine, wait until it's started, give 20% throttle, set pitch to manual 50%, set throttle to 45%

Deselect engine 1, select engine 2, repeat steps above

Select both engines, wait until both engine temperatures reach 40C

 

This work-around is what I imagine a startup with cold engine would look like. I have no idea if the behaviour with warmed up engine is realistic or not, but from a player's point of view it does not make the process of starting up easier. I would expect this to be the reason why the option exists in the first place.

 

Attachments:

ColdStartupMission.zip Multiplayer mission showing the problem

 

EDIT: Please ignore, nothing wrong here.

Edited May 31, 2017 by coconut

[coconut]

There is something weird with my server or mission, and I can't see what it is. Basically, my server running my mission is always using cold start-up, even with hotEngine = true. But when running someone else's mission, it uses warm-up engine!

 

This is my sds file:

// Generated by dserver

// credentials

login = XXX
password = XXX

// server info

ranked = 0
allowMouseJoy = 1
ServerName = "Coconut dev new"


// connection settings

protection = XXX
maxClients = 85
maxClientPing = -1
ExternalIP = 0
ServerIP = ""
DownloadLimit = 1000
UploadLimit = 1000
DownloaderPort = 28102
TCPPort = 28002
UDPPort = 28002

// remote console settings

RconStart = 0
RconIP = ""
RconPort = 8991
RconLogin = ""
RconPassword = ""

// mission rotation data

ShutdownLoads = -1

[rotation]
random = false
   file = "moscowwb\moscowdynamicwarwinterclear"
   file = "AutoGenMission2"
[end]

// preset and advanced settings

preset = 0

// preset: server related

killNotification = 0
friendlyFireReturn = 0
finishMissionIfLanded = 0
lockPayloads = 0
lockSkins = 0
lockFuelLoads = 0
lockWeaponModes = 0
penaltyTimeout = 0
respawnTimeout = 0
coalitionChangeTimeout = 0
finishMissionTimeout = 0
missionEndTimeout = 0
idleKickTimeout = 0
tdmPointsPerRound = 500
tdmRoundTime = 3600
coalitionsBalancer = false

// preset: mission related

objectIcons = false
navigationIcons = false
aimingHelp = false
courseWeaponsAimingHelp = false
padlock = false
simpleDevices = false
allowSpectator = false

easyFlight = false
autoCoordination = false
autoThrottle = false
autoPilot = false
autoThrottleLimit = false
autoMix = false
autoRadiator = false

noMoment = false
noWind = false
noMisfire = false
noBreak = false
invulnerability = false
unlimitFuel = false
unlimitAmmo = false
engineNoStop = false
hotEngine = true

The first mission in the rotation is from the dynamic war finnish server (someone else's mission). The mission is set on Moscow during winter, temperature is -20C. When spawning in a Pe2, after starting the engine, the engine temperature gauges show 80C.

Rotate the map to use AutoGenMission2 (my mission), set on VLuki, temperature -3C. Spawn in Pe2, start engines, engine temp is below 40C and falling quickly.

 

I don't get what's going on, it's the same SDS file!

As far as I know, there are no settings in the mission that control this, other than maybe Parked vs Runway start. In both missions, spawning happens engines off, on the ground, which I think is what Parked gives you.

Edited May 30, 2017 by coconut

[Lusekofte]

I was testing a JU 88 in your server and had over cooling , since it is first time I flown JU 88 in multiplayer I thought I did something wrong

[[DBS]Tx_Tip]

I thought that you originally had Cold engine start when you started the Dynamic Testing using console commands. At least when we visited the server we always had to warm up the engines. Perhaps the console commands to start the mission is overriding the actual Airfield/Plane server settings within the missions now. 

 

I can't see anything going on in the mission above that would cause this. Will give the mission a go on the server and see if it overrides the settings.

I can say that this happened before when we downloaded a MP someone had put up. A practice mission which overrode our No Icon settings within the server. 

Edited May 30, 2017 by [DBS]Tx_Tip

[[DBS]Tx_Tip]

The above Mission overrode the our server setting of "Warmed up Engines".

Engines overcooled.

[coconut]

I have a theory, will check this evening. I might be using summer clouds, causing the engines to be warmed up for summer temps, i.e. not warmed up much or at all.

[coconut]

My theory was wrong, but got me on the right track. My generated missions differed from missions created with the editor in a number of ways. MultiplayerPlaneConfig entries were missing in Options{}, the season of the cloud config was wrong (set to summer, where it should have been winter). I fixed these but the problem remained.

 

It turned out it was the spawn type of the planes. It was set to 0 in my missions, which apparently meant "in the air". How that resulted in my planes spawning on the ground with the engines off is a mystery I will leave alone. It's now set to 2, which means "on parking" as it should be. With that fixed, my planes are now spawning warmed up and comfy.

 

TLDR: No problem, it was all me doing stupid things.