Please make the rain realistic. Right now it’s purely cosmetic

Hi there!

Both in FS20 and FS24, I’ve always had the impression that rain is purely cosmetic and has absolutely no impact on the aircraft’s physics, and if it does, it’s clear that it’s not properly modeled. After a flight I did yesterday, this became even more evident, so this morning I decided to run a few tests.

I used the A330-300RR for this, since it’s the default aircraft that is supposedly the most realistic and best suited for this kind of task. That way, I get cleaner results and no one can argue that the issue comes from a third-party add-on.

For the tests, I used runway 07C at EDDF and conducted several runs in both dry and wet conditions. I kept the same weather conditions for both, with no wind, the only difference being the presence of rain.

To get the most accurate results possible, I conducted both tests in exactly the same way: brakes at the same temperature for both runs, fuel and payload loaded from SimBrief to get the exact same weight, applied TOGA thrust with the parking brake set until stabilized, then released it. I used 160 knots groundspeed in both cases for testing. Once reaching 160 knots, I cut the throttles to idle so that the RTO would activate, and kept the reverses stowed. I ran several tests, and I selected the two best ones to post here, as sometimes the rain wasn’t present over the braking area (I’ll discuss this later).

Dry test:

Wet test:

As you can see, in both tests the aircraft stops almost at the exact same spot, which is completely unrealistic. You might say: “In the wet test, the aircraft stops a bit further,” and yes, according to Google Maps, the distance is 56 meters longer.

But I have an explanation for this:

It’s virtually impossible to make the RTO trigger at the exact same moment in every test. However, by capturing the frame where the RTO activates in both tests, you can see that in the wet test it kicks in slightly later, which matches the slight increase in stopping distance.

Therefore, if the RTO had triggered at exactly the same time, the aircraft would have stopped at virtually the same spot in both tests. And even so, 56 meters of extra distance is ridiculously low under these conditions and nowhere near realistic.

I don’t fly the A330, so I don’t have access to its OPT (if there’s any A330 pilot around who’d like to share real-world figures, it would be very welcome), but let’s compare this with how a 737-800 would behave according to its OPT. I loaded the same runway with the same weather, zero wind, and no reversers, and generated a few examples under different runway conditions (Blue line for reference):





As you can see, the figures from the OPT are very different from what we’re seeing in the simulator. And that’s for a 737. For an A330, the stopping distances should be significantly longer because it’s much larger and has much greater inertia.

The conclusion is that rain and wet surfaces in MSFS are purely cosmetic, just eye candy. Pretty, but with no real simulation behind it. Another thing I believe should be implemented is proper water evaporating behavior. Right now, there’s no simulation at all for it. It’s just: raining = wet runway, not raining = dry runway. The change is instant, the moment it stops raining, the runway immediately dries up. No puddles, no gradual drying, nothing. It’s an instant switch from wet to dry, which honestly completely breaks immersion. In overall, this is an area I’ve confirmed is done better by other simulators.

My request to the development team is to implement this properly, with a real simulation behind it, and not just eye candy. I can’t understand how the team spent so much time refining tire friction, and yet wet surfaces, which would make the most of it, aren’t even simulated.

Thanks for attending my TED Talk.

10 Likes

While you might be onto something, comparing to real life performance figures will not proof anything. On a wet runway a 15% penalty is used, nomatter if the runway is just a little bit wet or covered with water up to 3 mm in depth. On a grooved runway, the wet and dry performance would likely be very similar in practise.

Also runway condition codes are to be used for landing, not take-off as they only consider the friction coefficient and not the drag component (acceleration to V1 would be affected by the contaminant drag, the accelerate stop by the friction). Take-off performance should be based on type and depth of contaminant. Furthermore wet runway (up to 3 mm) would be code 5, the other screenshots are irrelevant in this discussion.

So do understand that comparing to real world figures might not be the correct way forward. These are factors which might under certain conditions be conservative and even in real life performance would likely not match 1 to 1.

Also know that on some aircraft types, thrust reverser(s) might be included in calculations for runways other than dry, there are a lot of regulations around this, but some manufacturers did go through the hurdles to get this approved. So comparing dry to wet performance figures won’t give an accurate picture as one is with while another is without reverse.

Edit: I also notice that the all engine operating distance is always the same in your performance calculations (which makes sense, as I said, runway condition codes don’t factor in the contaminant drag), I don’t understand what is influencing the one engine inoperative go distance, it should remain the same as well. Only the ASD should be different all other factors being the same. I don’t know the source but it does not seem reliable.

Hey!

The source is the OPT of the 738 given by the company. I can’t remember now if the 15% is already applied in the OPT, but in this case it’s irrelevant, whether you add or remove that 15%, the number will change, but not the overall result. The OPT already takes everything you mentioned into account; in fact, the screenshots were taken calculating for takeoff with reversers INOP, not for landing. It doesn’t make sense to test this with landings. Testing it with an RTO is the proper way to do it, because it ensures the start conditions stay exactly the same the whole time.

Running this same test in another simulator using the Challenger 650 gives 535 actual meters of dry stopping distance and 876 meters in wet conditions. That’s a 341 meter difference, which, if you notice, is consistent with the difference shown by the OPT when comparing with poor conditions, even if it’s a different aircraft. (By the way, the second test is nowhere near Condition 5, I completely disagree with you on that)

Anyway, the OPT screenshots are simply illustrative, to get an approximate idea of the variations in each case. But sticking to the main point: in this exact situation, under the conditions shown in the simulator, aborting the takeoff at 160 knots (well above V2 if I had input the actual performance) with no reverses, would have likely made the A330 overrun the runway, there’s no way it would have stopped at exactly the same point. If an small Challenger eats up 341 meters of extra runway, I don’t even want to imagine what would happen to an A330. It would have gone off the runway 100% guaranteed.

It’s quite clear that there is no simulation whatsoever of wet surfaces in MSFS, nor of the friction associated with them (And if there is any, it needs a lot of tuning because it’s nowhere near the real values). But feel free to make your own testing and post the results here, the more info, the better.

I don’t agree because runway condition codes shouldn’t be used for take-off :smiley:. That is not the actual Boeing OPT used in real life is it? It can’t be. The runway in your video could be just wet, even in heavy rain, it is usually not more than 3 mm of water which makes it RWYCC 5 (for landing), more than 3 mm becomes RWYCC 2, which I have only seen a handfull of times.

Anyway, in real life it would likely not make an enormous difference, depending on whether the runway is grooved or not, depth of contaminant etc. I agree there should be a difference on a wet runway, but not to the extend of your challenger. In your figures the wet ASD compared to dry ASD is about 5% more, I think something like that would be accurate. Runways contaminated with snow, standing water, slush or even ice is a different story all together. I never tried but does snow have any effect?

Making thrust reversers inop is a good method to prevent these from spoiling any figures, I’m not sure about A330 or 737, some types use 1 thrust reverser in calculations for ASD and idle reverse for landing on runways other than dry. Still, comparing performance calculations with actual performance is a bit like comparing apples to oranges. These performance factors are generally quite conservative.

While this would be a welcome addition let’s worry first about getting actual thunderstorms with lightning back into live weather and tall CB cloud tops before we worry about this part.

4 Likes

But that’s irrelevant, and yes, it’s the real OPT.

As I said, the OPT screenshots are simply there to give some perspective. It’s a pointless discussion: a runway with standing water, snow etc is exactly the same for takeoff as it is for landing, it doesn’t change.

Regarding your question, I don’t know if you’ve watched the video of the wet test, but it meets the conditions you mention, you can even see the snow which is why I’m telling you there’s no way it’s a condition 5. It’s condition 3 at the very least.

The point here, and the whole point of the discussion, is that the aircraft, in all the tests I’ve done, stops at exactly the same spot regardless of the runway conditions. Which is obviously wrong and shows that there are no real numbers running in the background.

2 Likes

Nope this is incorrect. Runway condition codes only factor the runway friction which affects the braking, it ignores the contaminant drag. Therefore RWYCC cannot be used for take-off. For take-off the acceleration is affected by the drag of the contaminant, therefore it takes a longer distance to accelerate to V1 which you ignore when using RWYCCs.

I just googled for the Boeing OPT and it does not use RWYCCs for take-off (at least from what I can find).

There should be a difference I agree with that. But before Asobo does anything over the top like with the aircraft icing effect. Lets establish how much it should differ. There isn’t an accurate way to determine the runway conditions in MSFS, what I saw in your video is a wet runway? It could be snowing but the surface is wet?

Wet runway should be in the order of 5/10% more distance required. Not 50/60% more as in your challenger example.

1 Like

Yeah, but you’re not taking one thing into account, we are talking about a rejected takeoff here, which is why we’re not measuring the runway I use for takeoff, but the one I use for braking. Therefore, it is correct, because once you brake, it’s applicable. But you make a very good point, because if the figures also don’t affect the drag generated by that contaminant during takeoff, it’s another piece of evidence that nothing is being simulated.

The conditions are with the maximum level of precipitation allowed by the simulator, with snow and at zero degrees C in both comparisons, which could perfectly form ice patches in real conditions. How the runway looks is up to how Asobo creates the representation. In the other simulator, I loaded exactly the same conditions to test it.

2 Likes

Yes, the distance from brake release to 160 kts should already be longer, followed by a longer braking distance. So it should work double, not only affect the accelerate stop.

Yeah, they don’t visually model it correctly in that case. Runways are usually chemically treated so having a wet runway in the winter in snowy conditions, especially around 0C is not unrealistic. Ice patches should be a no go for take-off.

I don’t think there is an accurate way of knowing the runway conditions unfortunately in MSFS, would be nice to have a runway condition report in ATIS.

1 Like

It would be nice if someone from the development team could come here and enlighten us with data from the simulator. But it’s clear that something is off here. In fact, I spoke some time ago with one of the developers of the A350 about the BTV Contam, and he mentioned that although they had included it, there was no way to make it realistic because the friction values in MSFS didn’t match those of the real world at all. And these tests prove it.

4 Likes

Lighting in storms is already in, at least i had them few weeks ago …didnt see any proper lighting just flashes and sound…