fghdgdfdfgfgf

@ Ricardo: You nailed it! The RNWY 27 approach is spot on beautiful. Thanks for the V2 update, Ken

I'm using the 212 EVO on my I5 4670 @ 4.7ghz on a 4.5 FSB using the Artic MX-4 thermal compound. Temps are in mid 60's C with the ambient room temp around 75 f. Nice cooler. Easy install. Cheap!l

For me it's the PMDG v4 product line (i own the 747 and the 737 base package) and the take it or leave it stance on dynamic lighting that has left a sour taste in my mouth.

I'lll take Cali against the world. The only things you won't see here are swamps and hurricanes. Wiki California. Then go get yourself Orbix Nor-Cal and So-Cal and be amazed.

Corrupt shader cache? .....Try jumping into the SFO tower using the view track/pan (toggle) switch and scan the area for stutters, to eliminate a scenery issue???

There is another .bgl file '''FTX_NCA_objects_CA_San_Francisco.bgl''' that can drop performance and cause a momentary pause while loading into memory around KSFO. There is no off switch via the FTX control panel so you'll have disable it manually. I don't think you'll miss anything with this BGL, I think it's associated with Aquatics Park and maybe the near by yacht club by Crissy Field. You can see the fps performance hit from the KSFO tower view looking out over Candlestick Park towards downtown.

Did you recently do the orbit light update? If so, go back and dbl check that orbx related sfo bgl's are turned off. The light update will write new bgls where existing have been disabled.

The short answer: get the 2400.

going from 1600c9 to 2400c10 is significant. you wont have any trouble seeing and appreciating the value in that upgrade.

Try pumping up the volts a few ticks.

I don't have a baseline. I just built my Haswell system for my V3 upgrade this past April and really didn't have it tuned til middle May ....and then V4 was released.......and then... Prior to all of the above mentioned excitement I was on a Sandybridge using Prepared V2.5. I will say this; my 2133c9 1.5v memory used with my Sandybridge (when overclocked) is as fast as my 3000c12. Oh, and yes, performance does scale with bandwidth and latency.

I'm reporting broken beacons since last update with V4. They're fine with V3.

For me the big "fix" would be to see the runway at night with the Dynamic Lighting switch OFF and the Landing-lights illuminate ground switch in the ON position. While I love the dynamic lighting with V4 I do not need it while I'm flying the 747. I can't help but think what it would be like if Light Bloom was required to see the model during daylight hours in FSX.

The only thing that sticks out as a real performance liability with your config is the ram speed. Might be hard to find these days, but try to get that to at lease 2133 c9. You might also get a lil bump in performance with a gtx1070 upgrade. I have a similar setup as yours and can run 3rd party airports, orbix stuff, Active sky 2016 and the PMDG 747 with no performance issues, save the dynamic lighting stuff. Oh, and that's on 8GB of ram.

Doesn't mean that PMDG and other developers don't have a problem, cuz in my mind they do..

Inspector doesn't differentiate V3 from V4. So if you launch V4 V3 inspector settings are in full affect, and visa-versa. You could rename one of the prepared.exe files and create a new Inspector app or just run the same setting for both V3 and V4. note: renaming the preared.exe file will lose some of your settings

V4. I cant help but see similarities with the HBO series Deadwood.

I did, and happy to report we're all good here! In fact, we are better than ever. :-) used Inspector alias settings: All default except- Mode: Enhanced the application setting Setting: Application controlled/off Transparency: 4x Sparse Grid Supersampling In sim setting: 8 sample mssa Thanks!

I'm on a gtx1070 that's being pushed by a 4.75 GHZ Haswell with 3000MHZ c12 memory. Dynamic lighting is not an option due to the tremendous stress it puts on my system. And Its not just the frame rate counter that gets pummeled its also the i/o that slows to a crawl. Furthermore, I'm not a ""all settings right" type of simmer, I can satisfy my V4 pleasure with far less than the 8 gigs of physical ram I have available for the program. Peace, Ken Carlin

Well that's not good news. Dumbing down my modest V4 system settings to accommodate the new 747 would be taking a step backwards with regard to the immersion qualities that I cannot compromise on -good thing I have V3.4, cuz I do love the aircraft. Now are we going to see that same lighting approach with the 737 and, is it the same for the 777? Thanks, Ken Carlin

I to am not seeing any lighting effects on the ground with V4 default and 3rd party airports - this is with the dynamic lighting switch set to off. I do see lighting on the ground with the default aircraft. While I do see ground lighting with the dynamic switch on, this is not an option as the performance hit is too great. Ken Carlin

For kicks a giggles ... My V4 report: 30 FPS!!! in the PMDG 747- in virtual cockpit Orbix NorCal -with the well known bgl object frame rate killers disabled via the scenery option control panel Flightbeam KSFO at rnwy 1L default time, weather, gates stuffed with AI -from well know model producers graphic and scenery settings that I will actually use -I'm still blown away by the visuals Meanwhile, back at Fsdreamteam's KLAX rnwy 6R ...wait for it ....30FPS. -without Orbix Socal sys specs i5 4670, gtx1070, 8 gigs ram. win7, 1920x1200

While I cant speak to having good performance with the Fsdreamteam KLAX and Orbix SoCal combination, because I don't, I can say I get 30 FPS with all gates stuffed with AI while sitting in the cockpit of the PMDG 747 or 737 at rnwy 1L with the Flightbeam KSFO - Orbix NorCal combination. -using Prepar3d V3.4 at 1900x1200

When loading the default scenario all views are stretched ( fish bowl effect) and in low resolution. I can clear this by loading a new aircraft, but the corrupt view returns when I switch from windowed to full screen. Thanks- Ken

Glad I asked. Thanks!