jdb2
-
Posts
10 -
Joined
-
Last visited
jdb2's Achievements
Newbie (1/14)
0
Reputation
-
My bad. Semi real-time? It's only "real-time" in that you can make real-time forecast projections from the data given the current GFS weather data on a second to hour basis until the next update comes around, although it should be said, you'd need a pretty powerful computer to do the forecast modelling. Regards, jdb2
-
The NOAA plugin is not based on METARs, although it can be set to transition to them below a set altitude. It's actually based off of a real-time 0.5x0.5 degree global forecast model that is updated every 6 hours. Specifically the NOAA GFS which is part of the NOAA NOMADS NCEP Ensemble GRIB Data Info : http://nomads.ncep.noaa.gov/cgi-bin/filter_gfs_hd.pl . Regards, jdb2
-
Yes, it was already set to that. ( I also have PowerMizer turned off in the registry ) jdb2
-
The environment variable seems to have completely fixed the problem! Now the pauses are very infrequent and when they do occur they last only a few seconds ( and that's on maxed out settings! ). SkyMAXX Pro v1.2 is awesome! I know I need to upgrade my GPU but I'm waiting until March/April 2014 when Nvidia releases the desktop consumer Maxwell cards ( 800 series -- the 800M series is already confirmed for a February launch. ). Just one more question : How does the environment variable affect rendering quality? Thanks for all your support! Regards, jdb2
-
Note that these backtraces where generated while SkyMAXX was hung at "apply" in its configuration window. Also, I can reliably generate the OpenGL crash from the configuration window particularly if if max the settings out. This behavior differs from 1.1 where it would usually just take a long time. Regards, jdb2
-
I use WinDbg x64 and attached to X-Plane while SkyMAXX was hung/paused and generated a two backtraces. See the attached file : Regards, jdb2 xpdebug.txt
-
Ever since the 1.1 update of SkyMAXX Pro I've been experiencing several problems that make it unusable for me. The first problem is that it pauses and locks up the main X-Plane flight loop every 5 seconds to 5 minutes and each "pause" ( lock-up ) can last from seconds to many minutes to an indeterminate amount of time. Here I mean that the mouse cursor changes to Window's little animated circular busy indicator and X-Plane stops responding. The second problem is that these pauses will often crash X-Plane with the following error : ---------------------------NVIDIA OpenGL Driver---------------------------The NVIDIA OpenGL driver lost connection with the displaydriver and is unable to continue. The application must close.Error code: 2Would you like to visit http://www.nvidia.com/page/support.html for help?---------------------------Yes No --------------------------- The third problem is that the above two problems manifest themselves whenever I make changes to the SkyMAXX Pro configuration within X-plane. After hitting apply, it can take *forever* before X-plane is responsive again. Also even after waiting all that time, when I close the plugin configuration window, it will take *forever* again, with X-plane basically locked-up, until the window finally closes. I'm using the latest SkyMAXX Pro 1.2 update and my system configuration is X-Plane 10.25 64-bit, Intel Core i7 3970X Extreme Edition CPU, 64GB of DDR3-2133 9-11-11-31, EVGA GTX 580 Superclocked Graphics Card, 2x 256GB OCZ Vectors in RAID-0 and an Areca ARC-1882-IX-12 SAS 2.0 / SATA III / 6.0 Gbps hardware RAID card ( with 4GB of ECC cache and BBU ) which controls my 12TB 6x 2TB WD Black RAID-0 array where X-plane is stored. Thank you, jdb2 EDIT : I'm using Windows 7 Ultimate x64 The relevant log files are attached : Log.txt GizmoLog.txt
-
WOW!!! That did the trick! Thanks a lot! jdb2
-
I'm using real weather. I have the overcast texture quality set to the max. jdb2
-
I have a serious problem with SkyMaxx Pro. When I'm at about 10000ft and above the cloud tops all lot of the time they will all look like white blobs / ice-cream / melted-marshmallows. Here's an example : Does anyone know what the problem is here? Thanks, jdb2