Solutions
-
Opus Software's post in OpusFSI Weather update window popping up on top of everything. was marked as the answerI would configure OpusFSI not to load weather on start up so you can perform the first weather update manually. That way you can open spy, set your destination and cruise altitude (min 4000 feet needed for GRIB data .. which I would strongly advise you to include), click Update Weather in the OpusFSI Weather dialog, then monitor the weather download and generation.
Run the sim in windowed mode at first so you can see everything. You will see the Upper Atmosphere report displayed reporting GRIB progress. This can be displayed docked (transparent) or undocked(opaque).
If undocked the report text window can inadvertently get hidden behind the sim display. Popping into focus only when updated and the sim restoring focus to its main display shortly after. If this is so then dock the view so that it won't happen when in full screen mode.
You should Google your grainy when raining problem. Could be something to do with your rain textures or graphics etc.. Nothing to do with opus though.
Also make sure you have stepped through the GS Guide (very important).
I guess you've just had the sims menu text window displayed in undocked form and hidden behind the sims main display. It would then pop onto view during an update and disappear again after the main display is updated and takes back focus.
Please read our Recommended Practices as that helps to make the most out of the various weather related information and expected en route data.
Stephen :-)
-
Opus Software's post in Configuring OPUSFSI 4.65.6 beta and Prepar3d 3.3 Permission issues still was marked as the answerProblem solved after email exchange. Error due to incorrect folder path in OpusFSI configure.
Stephen :-)
-
Opus Software's post in Problem with network client was marked as the answerPlease follow the above instructions and can you show me your sharing and permissions (both sharing and security) for your server's C drive.
I need feedback to confirm you have followed the GS Guide and added the Everyone group. The error is very straight forward, the client is unable to access the files it need on your server. I will retest the client LWA geo maps here though and report back.
Stephen
P.S.
I have just this very minute connected up a laptop and configured it as a 'No Connection ...' type OpusFSI client and have all the LWA Geo map data no problem, its all displaying and updating just fine without any problems on my client system so it looks like a definite set up problem on your system.
Please follow the above instructions and can you show me your sharing and permissions (both sharing and security) for your Server's C drive, with the Everyone user group added with Full Control, no AV programs running etc.
Also step through the GS Guide for Networked PCs ... enabling File and Printer sharing.
Stephen :smile:
-
Opus Software's post in Static Weather Themes was marked as the answerIt has always been implemented. But the options are always greyed out when Live Weather is enabled. You can also use the Opus Addon menu which will automatically disable Live Weather when a static theme is selected. To use the dialog options you must manually disable Live Weather. Note though, that ALL static themes are very limited, they are never as detailed as any Opus Dynamic Weather Themes. You should always use the Import METARs From File option to create your own static weather using a single GLOB METAR rather than a very limited static theme.
Stephen :-)
The Import option, even when used with a single GLOB (Global) METAR, will result in creating an Opus Dynamic Weather Theme. The weather will be static or global but the theme will also contain the full range of all upper visibility, wind, and temperature layers. They will also use GRIB forecast data if required. On the other hand, Static themes generally are very incomplete or basic.
Stephen :-)
-
Opus Software's post in FSX Weather options was marked as the answerThe whole process is very simple to do if you need to do it.
For a start if you want to see what the current weather is at your departure (before loading the weather using Opus).
Then 'simply' go to the NOAA ADDS site and type in your departure ICAO code.
http://www.aviationweather.gov/adds/metars/java
You could even Google the weather, its very simple either way. Takes less than a minute to check and something all pilots should be able to do in a heartbeat.
But do not consider flying with the simulators RW weather or even static weather, that's like stepping back into the dark ages.
Stephen :-)
Personally I don't bother or worry about AI traffic using a different RW, never seems to be a problem. But for those that want to force the issue then any of the above techniques are extremely simple and fool proof. Always best to 'keep things simple', usually works without error or fuss.
Stephen :-)
Alternatively, you can wait and see if we can implement the option to load the weather before running the sim in OpusFSI then consult the Opus weather report or LWA weather map. The NOAA ADDS site is extremely simple though. Just Google NOAA METAR or NOAA ADDS and away you go.
Stephen :-)
-
Opus Software's post in Weather file for PFPX? was marked as the answerWe will implement that soon.
-
Opus Software's post in Hazy Reduced Surface Visibility was marked as the answerIn Opus the METARs rule, so you will get whatever reduced visibilities are reported in the METAR statements. Your specified Default Surface Visibility is only ever used when the METARs report no visibility restriction (normally with CAVOK, 10SM or 9999 statements).
So its not really a case of a solution, The weather engine is depicting real world conditions where it is most common for the visibility to be less than perfect.
You should use Recommended Practices and use the on screen weather reports and weather map to get some idea what the Met stations are reporting.
If you do not like the RW conditions (its very 'extremely' rare to fly in gin clear conditions) then you could try,
1. Upgrade to the latest release version.
2. Tick the Ignore Reduced Surface Visibility box.
3. Set the visibility distance to a low value (see below).
4. Increase the Default Surface Visibility to your desired setting.
The default reduced visibility limit is 6000m (do not ignore misty conditions), you could reduce this to 1000m (do not ignore foggy conditions) or even 0 (I don't like any reduced RW visibilities at all).
Its then up to you to set your desired level of surface visibility. Set 128km to effectively always fly in absolute gin clear skies.
I do not recommend any of these settings personally as they result ion totally unrealistic weather. You will not get these conditions in the RW.
Stephen
Try the above, if you have any problems just let me know and I will investigate further. Also if you are using P3D then please check out the Volumetric Fog warning topic as the P3D and OpusFSX setting must always match.
Stephen
-
Opus Software's post in Free movements outside the airplane was marked as the answerYes you use Live Camera Control which allows you to adjust the eye point in any camera view. But this is only possible in the Opus 'Custom' External Aircraft views so you will have to create some of those. The simulator does not allow the eye point to be adjusted by the camera software when in spot plane or tower view etc..
So first create some External Aircraft views using Live Camera, then use the standard hat switch panning and LCC to move around outside, You can also configure LCC Shortcuts and better still assign a dedicated 6-axis Gamepad Controller such as the Sony DualShock 2.
Stephen :smile:
-
Opus Software's post in NAVIGRAPH AND OPUS was marked as the answerThe opus data is intended for use only as default data for those who don't have any other source. So continue to update your specific planes, and in the Flight Plan Options dialog you can point to your <SIM>\PMDG\NAVDATA folder instead of the Opus data for the source of the Navigraph data.
Regards
Cheryl
-
Opus Software's post in OPUS weather loads for 2 secs, then returns to CAVOK? was marked as the answerIt cannot become unloaded so there must be another source of weather being loaded. Check your FSInn again as this is the usual culprit. Also check your FSX weather, and any other weather engine source. Opus will not inject any weather without displaying an update in the Spy message. Also the opus on screen local weather report will still be showing the Opus weather after the corruption. So it is definitely another source of weather being injected that is causing the problem. Do you have any weather related DLLs active still, another other weather engine active, any FSUIPC4 weather options enabled, FSX RW weather, and finally double check FSInn, or try it with FSInn disabled completely.
Stephen
FSInn could be re enabling its weather each time it is loaded if it cannot save your settings. So check the FSInn settings again, its usually the culprit.
Let us know what you find.
Stephen :-)
Googling ... It seems others have problems disabling FSInn weather.
Stephen
-
Opus Software's post in iFly 737 NG and Live Camera was marked as the answerMany thanks Gordon,
A recent beta and release removed aircraft that did not have a panel folder. My mistake I should check for any folder with 'panel' anywhere in its name. I will correct this problem and should be able to post a new beta tomorrow. Sorry for any inconvenience.
Don't bother renaming them unless you want to do it on a temp basis. But you will have to modify the relevant aircraft.cfg file as well (or the file that identifies the panel folder). I will post a beta with the fix ASAP.
Regards
Stephen :-)
-
Opus Software's post in Feature request - runway/ILS info was marked as the answerHi,
I will keep it in mind perhaps for a future OpusFSI upgrade, but we are very busy at the moment with other work (industrial software) so are unable to implement anything other than the current planned OpusFSX work.
Stephen :smile:
-
Opus Software's post in Flight Constantly Restarting when Network Client Active was marked as the answerThe drive name should be a single letter otherwise it won't work. You omitted the drive name on your example above so it should be something like \\mycomputername\c\opusfsx . Also the computer names should not contain any non-alphanumeric characters such as - since windows networking will not work correctly.
Remember to set both sharing and security permissions.
Let me know if you still have a problem.
Cheryl
-
Opus Software's post in quick question was marked as the answerIt has never been wrong to need fixing. All gusting winds are injected into the surface layers up to 4000 feet, these conditions will result in increased Opus turbulence when flying at lower elevations. Any other effects are down to the simulator as it controls the wind gusts, not the weather engine which just injects the gusting surface wind layer. So you should enable your FSX turbulence and thermal effects and then only expect any gusting effects when at the lowest elevations. I wouldn't expect to see any feedback in the displayed wind (shift Z info bar) though, they are just gusts after all so I'm not sure they would ever register on the info bar, just result in a few more turbulent bumps. The gusting data is injected though and certainly factors highly in the Opus turbulence strength and frequencies when low down.
Stephen
-
Opus Software's post in OpusFSX won't start. was marked as the answerI don't suppose it is minimised to the taskbar? We are working on a solution at the moment and will post a beta as soon as possible.
Cheryl
Try deleting the FSXSERVER.DAT file and see if this works.
Another idea is that perhaps Windows has moved the server form off the screen. One other person who had this problem rebooted their PC and it was OK after that.
-
Opus Software's post in Limited Operation on Reinstall was marked as the answerLic file unique to pc must reactivate using key file, details in faq
Stephen
-
Opus Software's post in Few questions about temps from a "weather-newb".. :) was marked as the answerI think you are making the common mistake of comparing the TAT with the Upper Temperatures (Ambient Temperatures).
What you should be looking at is the Ambient Temperature (also called the SAT or OAT).
The TAT (Total Air Temperature) is a CALCULATED value, derived from your current SAT (Ambient Temp in the sim) taking into account air quality and the square of your airspeed as a Mach number.
Its a simple calculation. Unless you are motionless, the TAT is always warmer than the SAT.
The TAT takes into account any compressional heating to the ambient air, heating that results in slowing the ambient air down to become static.
Your TATs seem perfectly fine and correct.
Stephen
-
Opus Software's post in wind shift :( was marked as the answerYou must try all the options mentioned in the Wind Shifts topic. Adjust Sim Friendly GRIB Data + Stabilised GRIB Data + Maximum Stabilisation etc.. Just turn on all the Stabilisation options. It looks like your FSX simply cannot cope with hardly any RW weather changes so needs all the help it can get. There is nothing else we can do apart from the stabilisation options provided since as you now know from reading our Wind Shifts topic, the problem lies inside the FSX code. The vast majority of systems have no problems after using the appropriate stabilisation and sim friendly options, normally the sim friendly option is all that is needed but a few systems need all the help they can get.
Just turn on all the options recommended for you to try. Nothing more can be done than that I'm afraid apart from resorting to completely stabilised or static weather.
Stephen
-
Opus Software's post in Excessive Gforce with PMDG 747 on VAFS5 was marked as the answerHi Christophe
You already have the correct settings. Please read the SimForums topic but there is nothing that you can do to stop the 'fleeting' erroneous data being calculated by FSX, its always done this when any weather changes are injected. But do read our FSX Wind Shifts sticky topic. You system is not really experiencing any problems though, your aircraft is not misbehaving, just the recording package is logging the 'known' momentary erroneous data produced by the internal FSX bugs, that is all.
Stephen :-)