Scattykat

Like I said in my previous post, updating graphics drivers worked a treat for me:

On 2 occasions with the RTM version, I experienced the pause type behaviour. Since SP1, this happened at least once every flight, random times, different routes. I have a Radeon HD7700 running at 1.1GHz. Today I updated my graphic's driver from the latest official 14-4 version, which was released in April 2014 - to the latest14-7 beta version, released around a fortnight ago. Both are available here: http://support.amd.com/en-us/download/desktop?os=Windows%207%20-%2064#amd-catalyst-packages . VAS has dropped significantly from around 2.7Gb to 2.36Gb (windowed mode - I use 2 monitors). My frame rates are marginally better but running around 26fps in VC view. Because of the improvements, I tried running in DX10 mode but this was useless (tearing with polygons appearing & disappearing) and so have gone back to DX9. So far, touch wood, not one single pause with the sim feeling more stable and smoother fps. Hope this helps those with AMD Radeon cards. All the best,

Here you go ... I think PMDG speeded the clip up though http://youtu.be/gVZr3WbMQ6w

Heck! No one has said it yet .... so I will. Please include your name in your post as per PMDG forum rules. Thank you! I use Simbrief for flight & fuel planning and it seems pretty good, especially with the NGX. And for rule of thumb calculations, I go with 8000 Kg/hr of flight.

This happened to me yesterday flying the NGX from EGKK-LPFR whilst inputting the arrival details. First I selected the runway, then the STAR. No probs there. It was only after choosing altitudes along the arrival path (there were 2 altitude options on each waypoint of the STAR) that the VERT PATH FULL annunciation appeared. VNAV disengaged and that was when I started going through the manuals in order to find out what to do but to no avail. Like the OP, googleing came up with the same result - not really helpful. So I tried resetting the FMC by inputting the company route again (I have all my routes stored and thus use Co Route option). The original route came up from the start at EGKK to the last waypoint before the STAR. The FMC then asked for the next waypoint enroute (can't remember the exact wording) but this seemed a logical step to bring lateral aspect of the route up to current location. At this point, the FMC appeared to recalculate the required VNAV path and then the whole sim froze. A bit annoying really as I was already 2 hours into the flight. Flight plan was: SAM UN621 MARUK UM195 LORKU UN866 QPR UM30 LOTEE DCT BATAX DCT BABEX DCT ALAGU Airac at time was 1405rev1 I hope this info offers some insight as to what actually went wrong. Best wishes,

Ooops .... I guess I should have foreseen some folk don't possess a sense of humour / irony ... from wikipedia Of course it's all very serious stuff, this release date business Wouldn't want to spook the market or jig the stock price, would we? :ph34r: Best wishes.

... doth protest too much, methinks :ph34r2:

Will the SP1 version have the ability to integrate with the up and coming VATSIM client SWIFT thus allowing ACARS / CPDLC / ATSAW via FMS / MFD? See: http://forums.vatsim.net/viewtopic.php?p=449633&sid=9221716c72673070b03ebeb17d8a56a0#p449633 Best wishes,

Do you have all the .NET framework versions installed on your machine? All my OOMs ceased once this was done. Now my VAS with PMDG 777 runs around 2.5 - 3.2 and in the NGX it's around 1.8 - 2.5 max. See post: http://forum.avsim.net/topic/408493-couple-win7-64-questions-on-net-framework-and-visual-c/?p=2675687

I know ... but it's like sitting in your newly painted living room, or watching that brand new kettle or being a kid strapped in the back of a car .... and asking those obvious questions ... You can't help it But you do.

I have to say this whole escapade featuring WX radar has been an excellent distraction from the question when will SP1 be released and a huge bonus for HiFi - On reading the news PMDG are going to simulate weather radar and, taking into account winds aloft data can be imported into the 777 FMC RTE DATA, I felt the best option for my flying experience was to buy ASN. So I did And it has been fantastic! Meanwhile, after the initial furore concerning how PMDG could be so inconsiderate as to post an April fool joke about WX radar and the like, everyone is oohing and aahing about the next best thing in flight simulation ...... raindrops on radar and the mystical datalink which Capatin Randazzo has yet to explain ;oP A huge flightsim breakthrough, no doubt. However, we are not any closer to knowing when Service Pack 1 for 777-200 will be released, save for the fact it will be released with the 300ER version. We know the beta testers have a version to work with and that there are issues with the FBW modelling. We have no idea when those issues will be resolved... In other words, pretty much the same status as: Feb: http://forum.avsim.net/topic/435001-14feb14-pmdg-777-200lrf-sp1-300er-update/ March: http://forum.avsim.net/topic/436852-14mar14-forum-return-to-service-important-read-all/ April: http://forum.avsim.net/topic/438427-01apr14-pmdg-777-200lrf-feature-preview-wx-radar/ I love my T7 and I fly her with all the current bugs. I can't stick her in a hangar coz she's born to fly. However, just knowing there are fixes to all these bugs in this thread: http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread-read-before-posting/ , is quite frustrating, because every month, just around the 14th day, we are told things along the line of, 'not to worry ... we're nearly there ... just a few things to sort out and we'll be in beta' ... and so it goes. Just, it would be good to know how close we are to SP1, rather than being given a tantalising tease every month or so, and then capitalize on Apr 1st just to keep all interested. Best wishes -

Bits I like: B) Don't like, -_- only coz this means delay .... the QC bit is essential and let's hope any issues are quickly resolved: Like: and And the best bit .... :lol: Now that I like Tessa Hauke

Yes, that was the link I used to check for the installed .NET framework versions - my PC was only a couple of months old at the time and I think I had to download all the versions from 3 back to 1. But it made a difference immediately and after that it was a matter of fine tuning. I use DX9 - DX10 didn't sit well and I noticed a big framerate drop rather than OOM All the best, Tessa Hauke

Aside from reducing the memory intensive settings like water (Low x2) & AI (AI=0 for vatsim), the most important factor for me in preventing OOMs was to make sure I had all the .NET framework versions going right back to 1.0 - apparently they are not backward inclusive. I still have the scenery settings to almost max. I cant remember the last time I had an OOM and as I write, I'm flying a PMDG 777-200 and my virtual memory is running at 2,525,396 K - I'm using UK 2000 EGKK scenery set to high res. Will be arriving in CYOM using freeware scenery and I expect my virtual memory to increase to about 2,980,000 K - 3,150,000 K, which is ample enough spare. Hope this helps, Tessa Hauke