Only way I can get temp indications to move is too RTO. I haven't seen them move off 0.0 under my normal use witch sometimes can be heavy at times to make a turnoff.

 

Only reason I'd RTO was to see if they moved and they did. But still can't imagine normal use reading 0.0? (guess this is FSX fault somehow)

 

However as to failures; I've had one so far after 200ish hours, ECC went out on a engine during a PHNL to KLAX flight not long after leaving HNL and hand flew all the way back to HNL.

I have a question somewhat related,

 

I have service based failures turned on for all models and paints, but what does this really mean? I treat my NGX well, fly it by the manuals, soft landings etc... But does this mean I will never have a failure? Because random failure's happen?

 

Perfect example, I was up in the Eclipse this morning and we had an unsafe gear light, the plane was just out of gear maint. This kind of stuff just happens!

 

So could someone explain the failure model?

^ My understanding is that it models failure probability on each individual system based on accumulated hours, accelerated from the real life probability to allow for the fact that sim planes are flown less than real airplanes.

Do a bunch of rejected takeoffs, using auto RTO brakes and NO reverse thrust. Wait about 10 minutes after doing e.g. 5 rejects. You should most certainly see a rise.

 

Best regards,

Robin.

Now do you need to save the panel state after landing to continue accumulating hours, or can you just exit FSX after landing and start it up tomorrow without losing the accumulated hours towards your next maintenance service?

 

By that, I mean if I land and save and exit, will I hit "Next service in 200 hours" at the same time as if I were to land and exit fsx without saving?

Do a bunch of rejected takeoffs, using auto RTO brakes and NO reverse thrust. Wait about 10 minutes after doing e.g. 5 rejects. You should most certainly see a rise.

 

Best regards,

Robin.

no need to wait 10 mins it rises for me when i stop at the end of the rwy when i do the rejected takeoff all i need is just 1 rejected takeoff and the temp rises to 4 imeddiately

Now do you need to save the panel state after landing to continue accumulating hours, or can you just exit FSX after landing and start it up tomorrow without losing the accumulated hours towards your next maintenance service?

 

By that, I mean if I land and save and exit, will I hit "Next service in 200 hours" at the same time as if I were to land and exit fsx without saving?

 

probably not the right thread, but i was wondering about this as well. i believe i read somewhere that loading C&D refills some fluids. if your default panel start is C&D, does that mean that things like fluids will always be full? i havent seen any drop in levels, but i AM seeing "hours til maintenance" drop. just kind of confused me....

 

as for the original topic:

 

i have seen the temps rise and had brake failures after RTO's, but i did notice that when using autobrake on landing, the temps always read "0". even if it is slightly cooler outside, there's alot of energy being put into the brakes on landing. i feel like there should be some sort of rise in temp.

Are you using the default panel states, or are you saving a new state each time you land?

 

As for myself, I use a slightly modified default panel state.

As for myself, I use a slightly modified default panel state.

 

Thanks. And do you get what you'd consider 'normal' brake temp indications after rollout (above zero from time to time)?

 

I guess half my problem is that I don't truly know what 'normal' is, so I don't have much to go on. I'm just assuming when I slow an aircraft from 130ish to about 15-20 in 5000', there's going to be some heat that shows up on the display (yes, I know it's unit-less).

And do you get what you'd consider 'normal' brake temp indications after rollout (above zero from time to time)?

 

I do not usually monitor brake temp after landing... most of the tails I fly dont even have the indicators. But I definitely get brake temp rises after long taxi with a lot of braking, and even more so after an RTO.

For what it's worth, the ticket I submitted came back with the fact that it's an unfortunate side effect of an FSX issue.

 

Thanks, Ryan, for the quick response. I'll RTFM the manual a little closer next time. Haha.