As I explained, weather engines, all weather engines, inject wind and temperature targets for FSX to follow. In OpusFSX case these targets are derived from the NOAA GRIB forecast data.

 

These targets are completely visible and easily accessible just be examining the various Opus text reports, on screen weather reports, and weather maps.

 

The on screen weather reports even show the flyer the exact wind and temp target injected into the sim. Nothing hidden, all visible and plain to see. You can clearly see in all cases whenever FSX goes adrift that it is FSX that has departed and ceased to follow its targets.

 

This is as plain as day and can be monitored continuously in your flight. You can even calculate the TAT yourself and see the result of the erroneous ambient temperature inside the sim. Once again this data is not controlled directly, only targets, which you can monitor and see in the reports, are injected for FSX to follow.

 

There has never been a case of garbage in. If there ever was then this data would be glaringly visible and noticeable, and would be corrected in a matter of hours. But in EVERY single case the injected Opus targets have been found to be 100% accurate.

 

Please read my previous post if you want the facts and please ignore idle and speculative comments by people who just do not know the facts.

 

Stephen

Sorry that is just rubbish. The data is derived from the downloaded GRIB global forecast data and adjusted to ensure it is 'sim friendly'.

 

Nothing is hidden in the OpusFSX weather engine, there is a VAST amount of information available at your finger tips in both reports, on screen weather reports, and now in the Live Weather Assistant and smaller Weather Maps. The on screen weather reports also SHOW you 'on screen' both the ambient wind and temperature targets along with the ambient temp and calculated TAT. The INFORMATION is there for you to see and see for yourself that it is 100% correct. Nothing is hidden.

 

So your statement is totally unsubstantiated and complete garbage itself.

 

Look at the data yourself. All the wind and temperature targets are there for you and everyone to see.

 

Look at the weather reports. Examine the Opus WeatherReport.txt file, its all there.

 

Stephen

 

First of all, I never addressed what your particular software does. I'm talking strictly about FSX behaviors.

 

FSX is simple. You send it some values, and it uses some assumptions (like standard lapse rate) for the rest of the data.

 

I already invited people to test for themselves. Maybe I need to elaborate?

 

--------------- 10000 ft = +10 °C

--------------- 5000 ft = +20 °C

--------------- ground level = +25 °C

 

OK, so we agree the spacing is 5000 ft between layers? OK. Some numerical analysis.

 

Between ground and 5000 ft level, we have a drop of 5 °C. FSX will average that out to 1 °C per 1000 ft.

 

Between 5000ft and 10000ft we have a drop of 10 °C. FSX will average that out to 2 °C per 1000 ft.

 

Above 10000 ft, as no further temperature layers exist, FSX will apply a standard lapse rate to the temperature to infinity.

 

You can test this in the sim yourself.

 

HOW FSX is programmed with those layers doesn't matter (and if you really want to get into it, I will drag out the publicly available FSX SDK on the matter).

 

The problem lies in the values being sent to the sim, not the sim itself. They are not targets (unless you have dynamic weather enabled, then all bets are off as who knows what FSX is doing to determine future weather). They are actual values that the sim will use at those specific altitudes, using linear interpolation between layers, and standard lapse rate above the final layer.

 

A subject for investigation is if you have a temperature inversion, e.g.:

 

----------------- 10000 ft = +10 °C

----------------- 5000 ft = +5 °C

----------------- ground level = 0 °C

 

Maybe FSX will do weird things.

 

EDIT: All those seeing strange behavior with TAT, ensure dynamic weather is DISABLED in FSX.

 

Best regards,

Robin.

 

 

is this where you guys recommend turning off weather?

 

No, even simpler:

 

Don't even start any other weather program, and at the Create a Flight screen, select the NGX, choose an airport, select the weather in FSX itself (select clear skies), select the time.  Report back.

You cannot achieve anything resssembling true winds and true forecasted temperetures aloft relying on the FSX weather or FSX calculations. Our simulated winds and temps are designed to match the FSX comfort zone in this case but again they are not intended to result in anything resembling the current RW upper atmospheric conditions. It is through the use of wind and temperature targets, in our recommended case, Sim Friendly upper targets, that RW upper winds and temperatures are achieved.

 

If Opus users follow my listed recommendations then the vast majority of system will be OK and the targets will be followed by the sim.

 

But all our data is visible and can be verified, the flight can even be monitored as you fly so that any deviation by FSX becomes very noticeable. This is a very rare occurrence and is usually eliminated using a variety of the above stabilisation and sim friendly options. The sim friendly option being very important to ensure FSX can follow the target temps and winds without too much trouble. There are certain temperature and wind gradients that FSX is just not happy with and cannot follow, these are eliminated using the sim friendly option. But once again these parameters cannot be controlled in real time, targets must be specified and FSX has to follow them, filling in using its own internal calculations.

 

Stephen

I can only comment on the FSX sim interface as supplied by the SDK (which I presume you are using).

 

I don't know what you mean by "sim friendly", but I can take forecast winds aloft and temperature data, program the sim via custom weather, and see that weather correctly.

 

Sure, FSX sucks when at 10000 ft winds are 270 at 20 kts, then at 15000 ft they shift to 360 at 5 kts, but that is only because of the literal way it applies data.

 

I thought half the point in external weather programs was to understand the limitations of FSX, and how to work around them to create both a more enjoyable and realistic experience.

 

It seems to me that they do no more than read some data and write to the sim, ignoring the sim limitations and drawbacks, and saying "nothing to do with us" when it goes wrong.

 

As for targets... FSX doesn't target anything (unless dynamic weather is enabled, then as I said, all bets are off). It only applies what is sent to it. If bad data is sent, you get bad data out of the sim (in this case, in the form of unrealistically high TAT), hence my comment of garbage in, garbage out.

 

The idea of updating weather at weather stations is good in theory, but as we know, in FSX this goes terribly wrong. I'd prefer the weather engine to write globally, care about where my aircraft is, and apply the weather I should be seeing at that point (computed within the weather engine itself and written to FSX frequently), instead of allowing FSX to do any processing of its own.

 

Best regards,

Robin.

FSX limitation ... That's why you set the sim friendly option in the Opus weather dialog which takes account of its limitations and makes sure the targeted upper wind and temperature values are achievable, which they are in 99.9% of all systems.

 

The weather engines provide targets for FSX to follow that's the only way to get FSX adhere to RW upper forecasted conditions. FSX weather generation is not used at all, the weather is injected into FSX by the engine. Targets are the only means through which an external engine can get FSX to match RW conditions.

 

There are no facilities to control this data directly. Even trying to do so via some other interface, even if updated 50 times a second, will just end up with FSX fighting against itself and can end up going crazy. Once the targets are lost then nothing much can be done, its best to just ensure the targets can be safely met.

 

When FSX drifts away from its targeted values, set by the external weather engine, then it is certainly not the case if garbage in, not at all. I think you are seriously misinformed if you think it has.

 

Stephen

Hey CT,

 

If you are using FSINN than that's probably causing it.

 

Choose "CAVOC" on the main control panel to try it.

 

If that solves it, you can switch the FSINN weather permanently of in the settings.

 

 

frigid January

 

Had the pleasure to sit off Oslo in January with snow all over the LPH I was on. :unsure: . :blush:

Thanks for the FSInn ... see picture below ... is this where you guys recommend turning off weather?

 

https://www.dropbox.com/s/m6hsitg4zcst0rz/FSUIPCOptionsAndSettings.jpg

 

Thanks,

 

C. T.

Think they are referring  to if  your flying  on vatsim  theres is  an option  where  you can turn of  fsin weather

 

If using fsinn, disable weather

 

https://www.dropbox.com/s/r387c4cwb981vxu/FSInnWeatherDisable.jpg ... sometimes it is the subtle voice that speaks the loudest.

 

I assume that the illustration above is the form in which the weather can be disabled? 

 

C. T.

Robin,

Stephen is right - I've seen the targets he's injecting into the sim and they're correct but the actual temp the sim generates from the targets is wrong. In station mode at least you can't actually force FSX to a particular SAT, you can only give it a target to shoot for - it's somewhere in that process of being given the target to trying to achieve it that FSX screws it up and it gets all high like this. Trust me, I'd say so if I thought it actually was Opus's fault (or whatever other weather engine) - I initially did think it was, but Stephen convinced me it wasn't. You can do it yourself by opening up the local weather window and watching the target vs. the actual. No one controls the actual except FSX.

https://www.dropbox.com/s/r387c4cwb981vxu/FSInnWeatherDisable.jpg ... sometimes it is the subtle voice that speaks the loudest.

 

I assume that the illustration above is the form in which the weather can be disabled? 

 

C. T.

 

Correct!

 

Works fine for me.

Happy flying!

https://www.dropbox.com/s/r387c4cwb981vxu/FSInnWeatherDisable.jpg ... sometimes it is the subtle voice that speaks the loudest.

 

I assume that the illustration above is the form in which the weather can be disabled? 

 

C. T.

That is way you can disable weather in FSInn (VATSIM client) if you use that software. If you do not, that's is not a way to disable weather, just use "clear skies" in FSX weather menu.

CT-

 

I fly the NGX with FsINN and AS2012 DWC..... No issues. Test offline with clear skies. Once you know that works test off line with AS2012 or Opus. IMHO REX doesnt do Wx nearly as well as those- BRILLIANT textures though. Then when you know that works, test online WITHOUT FsINN weather enabled. The odd time I have had a high TAT I have closed AS2012 waited a few minutes and restarted same... However, I run it on a secondary computer.

 

ALL THE NGX IS DOING is reacting as a 737 would (in the unlikely event of a 50+ TAT in the FLs). I'd be horrified if she flew/climbed well there, wouldn't you? She, unlike MOST FSX aircraft, requires a pilot to stay AHEAD of the airframe.

 

From your descent planning document, we know you are not averse to scientific methodologies (I'd just suggest starting all that planning a 100 odd miles before TOD).

FSX limitation ... That's why you set the sim friendly option in the Opus weather dialog which takes account of its limitations and makes sure the targeted upper wind and temperature values are achievable, which they are in 99.9% of all systems.

 

The weather engines provide targets for FSX to follow that's the only way to get FSX adhere to RW upper forecasted conditions. FSX weather generation is not used at all, the weather is injected into FSX by the engine. Targets are the only means through which an external engine can get FSX to match RW conditions.

 

There are no facilities to control this data directly. Even trying to do so via some other interface, even if updated 50 times a second, will just end up with FSX fighting against itself and can end up going crazy. Once the targets are lost then nothing much can be done, its best to just ensure the targets can be safely met.

 

When FSX drifts away from its targeted values, set by the external weather engine, then it is certainly not the case if garbage in, not at all. I think you are seriously misinformed if you think it has.

 

Stephen

 

This is what is so confusing - why does FSX drift? I have never seen FSX drift, but then I have DYNAMIC WEATHER disabled.

 

If you enable DYNAMIC WEATHER, then yes, FSX goes silly after a while, but I have NEVER seen it drift with it disabled.

 

Maybe you assume (or even set) dynamic weather to ON? Maybe there is a bug in FSX that enables it internally?

 

At this rate you're going to make me write a test application...

 

Best regards,

Robin.