vrdubin6

I think the biggest thing for me is finally being able to fly into larger cities. This is where I'm seeing the biggest performance gain. In the past any decent sized city would just crush my framerates and make it a stuttering mess. I have sliders slightly higher than v4 and was just able to shoot a dusk approach into KLAX with ENVTEX/ENVSHADE/ORBX and hold a very smooth 40-50FPS. This is a night and day difference from any experience I've ever had. For me this opens up so many new areas that I've always avoided flying to.

I've seen this tweak before but as I understand it a larger number for day threshold should turn the lights on earlier in the evening. I just tested values between 40000-55000 and the lights turn on at the exact same time. I must be doing something wrong.

One issue I ran into was the "disable and restore" option in ENVDIR only reverted the ENVTEX settings and not the ENVSHADE effects. I had to manually get it back to the default shaders which was a bit irritating. Stock: ENVSHADE: Stock: ENVSHADE: I upped the HDR brightness on the V35 shot a bit per ENVSHADE recommended settings, so the shots are a bit more comparable. The Duke shot is with the exact same scenario and settings. The thing I like most about having ENVSHADE is it gets rid of the fluctuating brightness when you look up/down with the default HDR settings of P3D. I was really impressed with the shaders of v5 out of the box but I think I'll be sticking with ENVSHADE for now.

Anyone else having issues with bloom not making much of a difference in v5? I've fiddled with my HDR settings quite a bit and found a nice balance of brightness/saturation but I've found bloom doesn't really have much effect until I get way up around 3 and then it's obviously very blown out and comically overdone.

I echo your thoughts. I've had the dreaded invisible wall on final a couple times but other than that I've been very pleased. The performance is night and day and I've had a few great flights over the last few days. I had a nice long flight in the Turbine Duke today and descending into KBOI I was able to maintain 60FPS and it was silky smooth. This is an area in Orbx CRM I fly into regularly and I always hover around 45-50FPS. This was with higher settings for autogen buildings and autogen draw distance than I used in v4. For $60 I'm one happy camper.

I lied, I think I like ENVSHDE better than vanilla v5. I also like that ENVSHADE doesn't change brightness when panning up/down. Here is a comparison in the exact same scenario. Only difference is the ENVSHADE screenshot was zoomed out to 0.7 I think. Default v5 ENVSHADE

I installed it and honestly I'll probably stick with the default v5 shaders. ENVSHADE was a must in v4 but I didn't notice a drastic difference in v5 and I feel like it looks great as is. I can post some before/after comparison shots later this evening.

I'm running a 980ti and I've yet to have my VRAM usage go over ~4.1GB. This is with ENVTEX, ORBX regions/LC/Base and add-on planes.

If you look at any system monitor you will see that at idle with nothing running Windows will use a fair amount of VRAM. P3D is showing how much there is available to use.

I'm loving it so far. I only have 6GB of vram but I haven't seen it go over 4.1 out of 5.1 available. My only issue is I had the dreaded invisible wall of death while flying the RNAV 34R into KRNO today. Just past the FAF and bam I'm slammed into the ground. It was just a short flight to test stability as well as the RXP GTN750 so I got a little chuckle instead of being word not allowed off after a long haul.

You’re a lifesaver. Worked perfectly.

Seemed to be a driver issue. I rolled back to 445.75 and with a full overcast layer I'm holding 60FPS. I'm a happy camper again.

Thanks for the tip. Antialiasing transparency was off but I may try a different driver. I updated my driver yesterday and I'm almost positive I wasn't seeing this kind of performance impact when I first installed v5.

I am not using enhanced atmosphere. Clear skies and I'm getting a solid 60FPS but the addition of a very sparse layer of clouds and it is dropping me to 20FPS. Turning off cloud shadows doesn't change a thing. I haven't seen any one else complaining about this so I'm thinking I have a isolated issue with my system.

ENVTEX and ENVSHADE from Toga Projects are cheap and very simple shader/texture programs that are commonly used.

Yes, aside from ENVTEX/ENVSHADE and using clear skies since I'm not using Active Sky in V5 yet. Comparing between the two, with TrueSky off, in the same region I always fly in ORBX CRM area and the difference is impressive. I also loaded up a quick flight at KRNT with the same exact scenario and settings in both sims. v4.5 - Bouncing around 40FPS v5 - Holding 60FPS

I'm running a 6600k with a 980ti and the increase in performance is huge.

Once I can get a shader to fix the colors/saturation as well as some replacement water textures I'll be one happy camper. The performance increase is well worth the price in my opinion.

I got through to the downloads page and it's clipping along at ~5MB/s. Should be done in an hour or so.

I think I've come up with a fix I can live with. I used the [GTN_750_1.NO_BEZEL] trick to adjust the brightness of only the VC gauge and not the pop up. With the following setup the gauges load at 100% brightness but if I just open the pop up windows really quick and then close them it adjusts the VC gauges to the correct brightness. I have no problem doing this at the beginning of flights as it's much less annoying than going into the setup each time and adjusting the brightness slider. Let me know if there is a better fix but this will hold me over 🙂 New .ini settings [GTN_750_1] ; is the master device if true. MasterDevice = true ; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2 NavDbType = 1 VoicePref = MALE ; connects to: 'PFC_GTN' or any '#PID' (#D067 for PFC_GTN) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 LinkVor = true UseSimGpsCmds = true ReduceRate = true Rheostat.Buttons = 100 [GTN_750_1.DEFAULT] ; show screen only gauge if true. nobezel = false ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; enable default 'hand' cursor over the touch screen (2D only). usealtcursor = false ; enable touch beyond screen bounds if true (2D only), clip if false (GTN native). extendtouch = true ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225) (requires SHIFT+left mouse button). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 [GTN_750_2] ; is the master device if true. MasterDevice = false ; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2 NavDbType = 1 VoicePref = MALE ; connects to: 'PFC_GTN' or any '#PID' (#D067 for PFC_GTN) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 Rheostat.Buttons = 100 ReduceRate = true [GTN_750_2.DEFAULT] ; show screen only gauge if true. nobezel = false ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; enable default 'hand' cursor over the touch screen (2D only). usealtcursor = false ; enable touch beyond screen bounds if true (2D only), clip if false (GTN native). extendtouch = true ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225) (requires SHIFT+left mouse button). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 [GTN_750_1.NO_BEZEL] ; offset brightness (-100 to +100) brightness.screen = -40 [GTN_750_2.NO_BEZEL] ; offset brightness (-100 to +100) brightness.screen = -40

So it looks like I lied. I fired up the RealAir Legacy and it looks like it's the secondary GTN that doesn't maintain the brightness setting. Here is a screenshot when I fire up the Legacy. I go to the settings for the bottom GTN and it has a brightness setting in the 60s just like the top GTN but is obviously displaying 100% brightness. Panel.cfg

Thanks for the speedy reply! I will grab it this evening when I get home.

The issue I'm having is in all the aircraft where I have 2 GTN 750s. I set the screen brightness to 70 on both but when reloading the aircraft only the secondary 750 keeps the brightness setting. The main 750 will be at full brightness but when going to the settings for that window it will still show the setting of 70% or whatever I had it set for. So each time I load up any aircraft with 2 750s I will have to go to the settings menu for the main unit and adjust the screen brightness 1% either direction and then apply in order to get it where I would like. I'm assuming it's a simple setting I'm overlooking but any help would be greatly appreciated. Thanks in advance!

Edit - tttocs already answered while I was typing.

I've also had zero issues since they made the switch to ORBX. I've been using it on a daily basis and also transferred my purchases over to the ORBX website without a hitch.