bbuckley

To close this out... I finally went with the FV12 panel and dash that has 2 13.3 displays. Then on the side I added a 3rd 13.3 display. On the main 2 displays I put the primary flight instruments and in some cases even the main standby flight instrunments. I use the 3rd display for panels and switches and indicators and in the case of the Honda Jet, I even added the 2 GTCs. It all worked out perfect for me using Air Manager and PopoutMgr.

I'm considering a FVPro6UDM panel with dual encoder and dual 15.6" touchscreens. I like this option since the touch screens (with Air Manager) can be reconfigured to a number of different aircraft as opposed to a dedicated G1000 (or other) solution. Does anyone have experience with Flight Velocity and their touchscreen panels w/Air Manager and are you happy with it? Are the 15.6" touch screens overkill? Are there a lot of panels/instruments available for Air Manager and is it easy or a headache to configure? Thanks!

I use the FSUIPC7 .bat that can be created when installed. Then I use the FSUIPC7.ini [Programs] section to start the additional add on I want (SPAD, NavigraphSimLink etc). Works great!

Just FYI, I use the FSUIPC7 feature to put a shortcut on my desktop that I use to start MSFS. Works great. And in my FSUIPC7.ini I use the "Programs" feature to start other addons like SPAD.neXt and ForeFlightRelay. [Programs] Run1=CLOSE,"E:\XX - MSFS2020\My_MSFS_Stuff\Miller.MSFS..ForeFlightRelay\Miller.Msfs.ForeFlightRelay.exe" Run2="E:\SPAD.neXt\SPAD.neXt\SPAD.neXt.exe"

I just installed this afternoon and it was perfect. BTW, thanks @Bina !

Thanks stans, but more flights show this wasn't the answer. I'm out of airspeed, altitude and ideas, all at the same time...

After much continued troubleshooting, I discovered that the "blocky trees" were not happening when I flew the Carenado Phenom 100 but did happen almost all the time with the Carenado PA28 Archer. No idea why that airplane seems more intense on processing, but I figured it must be a CPU overload issue. So I changed my Affinity Mask from 116 (01110100) to 252 (11111100) to use all the LPs above 0 & 1 since I have a BAT file that starts ASN, PE Client, and FSXFlight with Affinity 3 (00000011). After a quick test flight in the Archer everything was perfect! Does this make sense to anyone? Thanks, Bruce

Hey Bill! It has become an obsession with me.. My FSX DX9 setup works beautifully except for this nagging problem, and a related issue at KCRQ, and occasionally when I switch on the panel lights in my Carenado Archer the gauges have a black box around them. Each of these problems gets fixed by pausing for a moment, switching to windowed mode, then back to full screen. In that reloading process everything comes back the way it should. So, I'm convinced that I have some kind of issue of balance between the CPU and GPU where in these intense HD scenarios, initially some texture transparencies don't get processed right. But I don't know enough about how FSX does the processing to know what to change. I don't think the scenery itself is bad, or that I have a conflicting scenery, although it could be but I've tried disabling everything and turning back on one at a time. The problem in doing that is that I also have ASN and PilotEdge running so to replicate the problem takes quite a setup and flying into the airport from outside the area, so it takes a long time. I'll figure it out someday.. Thanks for your continued help! Appreciated. Bruce

This is now the most annoying and disappointing problem I’ve had with an FSX add on. LatinVFR seems unable to help at all. I’ve tried disabling MegaSceneryEarth sceneries, I’ve tried re-downloading and re-installing KSNA, I've tried re-ordering scenery priorities, I’ve tried turning down the resolution of my REX4TD textures, and nothing seems to work. I have a pretty powerful system (specs below). Steve W -- I went to codelegend.com and made sure my fsx.cfg and NVIDIA Inspector profile was set up as you outline for DX9. I had high hopes that turning off Transparency AA (supersampling and multisampling) and setting the AA setting to 3x3s would do it, but no luck. I also changed Bufferpools to USEPOOLS=1 and POOLSIZE=2048. I have jpg screenshots but I can't upload them in this forum I guess. Any thoughts appreciated! I follow your posts and advice closely. Always educational. ​Thanks, Bruce I think I figured out the screenshot upload.

Sorry, was out of town a few days.. They are trying to help but so far it has them stumped. I am trying to recreate similar circumstances at KSAN another LVFR add on that I haven't had any issues at. I'm also going to try KSNA with the MegaSceneryEarth California South disabled. Since I have MSE LAX TCA Ultra Res also maybe the 3 sets of scenery is just overwhelming or conflicting. MSE California South, MSE LAX UltraRes, then LVFR KSNA. Should be able to report back by tomorrow. Thanks for the help!

Thanks. I uninstalled and reinstallled KSNA. Checked for any potentially conflicting AFCAD files manually. I'll check out SimpleAirportScanner. I turned off an airport scenery option to have photoscenery and landclass around airport since I also have MegaScenery LAX / SAN and Southern California sceneries. I have the airports at a higher priority in the scenery cfg. On a short flight tonight the "block trees" at KSNA were still there. The trees on approach outside the airport area were fine. This was before I uninstalled / reinstalled however so I'll try again tomorrow. I'm also going to post in LatinVFR support forum. Are these trees likely "Autogen"? I've tried the bufferpool section in & out and no difference I can notice on this issue. Thanks, Bruce

My system (see specs in sig) has generally been performing beautifully. The only issue I have has been nagging me for months. When arriving at either LatinVFR KSNA or SIM720 Palomar KCRQ I get blocks of scenery. At KSNA it's always blocks instead of trees or the tall grasses. I've tried turning down settings and reducing Autogen all to no avail. Can some fsx.cfg guru look at the relevant sections of my settings below and give me some advice? I have a pic but can't seem to post it here. Greatly appreciated!!! Bruce [GRAPHICS] SHADER_CACHE_PRIMED_10=1693500672 SHADER_CACHE_PRIMED=1693500672 TEXTURE_MAX_LOAD=4096 NUM_LIGHTS=8 AIRCRAFT_SHADOWS=1 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=1 AC_SELF_SHADOW=0 EFFECTS_QUALITY=2 ForceFullScreenVSync=1 ForceWindowedVSync=1 GROUND_SHADOWS=0 HIGHMEMFIX=1 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 See_Self=1 Text_Scroll=1 D3D10=0 //[bufferPools] //UsePools=1 //PoolSize=10485760 //RejectThreshold=126976 [Display] BLOOM_EFFECTS=0 TEXTURE_BANDWIDTH_MULT=120 UPPER_FRAMERATE_LIMIT=0 WideViewAspect=True [Main] FIBER_FRAME_TIME_FRACTION=0.2 [sCENERY] LENSFLARE=0 DAWN_DUSK_SMOOTHING=1 IMAGE_COMPLEXITY=4 [TERRAIN] LOD_RADIUS=6.500000 MESH_COMPLEXITY=100 MESH_RESOLUTION=25 TEXTURE_RESOLUTION=28 AUTOGEN_DENSITY=4 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=500 // Default 4500 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=400 // Default 800 DETAIL_TEXTURE=1 WATER_EFFECTS=4 [JOBSCHEDULER] AffinityMask=116

OK just to close this out as a reference for others... The issue was the PC sleep function. For some reason after I completely shut down the PC and power supply for a week, on return I fired up, and the PC wasn't correctly going to sleep after an hour. The display was turning off after 30 mins as I had set but the PC wasn't in sleep mode. Even with all the USB Power Management boxes unchecked, when my PC goes to sleep mode, the USB controllers (all attached to a powered 2.0 hub) all turn off. They come alive on wake and I've not had any issues with FSX recognition.

(Specs in sig) I have everything set up with all USB power management controls in device manager set to not allow PC to shut down device but up until this week when the PC would go to sleep mode the yoke (and rudders and a joystick for that matter) would all turn off. They would wake when the PC woke. This week I came back from a week away and before leaving I had turned the PC off and even shutdown the power supply. After firing it back up on return, the yoke (and other controls) stay on all the time. I don't know what happened or how to return it to the prior state. My concern is the darn bright green glow in that room all night and burning out the panel. Anyone have any ideas or suggestions? Thanks!

Glad it's all worked out.