DAL1850

Found this: http://www.avsim.com/topic/455599-gns530-2d-popup-clickspot-issue-b55-solved/

Bueller? Bueller?

I was wondering if anyone had success integrating the Mindstar GNS into the RealAir Duke B60 or Twin Turbo? I've been able to integrate it visually, but the VC gauge cannot popup the 2D window via mouse click though I am fairly certain the 5th parameter idents are correct. My panel.cfg can be found here in the Mindstar support forum (but have not received a reply). http://www.avsim.com/topic/480804-gns530-in-duke-b60/

Upon closer inspection, it looks all mouse clicks are not forwarded to the VC gauge. Only the 2D gauge responds to mouse input. Has anyone had success integrating the 530 into this aircraft?

Hello and Happy New Year. I am experiencing a curious problem with the RealAir Duke B60 and the Mindstar GNS530. I currently have the RealAir panel configured (via their configurator) for the RealityXP 530 and have modified it to swap the RXP gauge for the Mindstar 530 (I have a dummy rxpGNS.dll in my gauges folder). This allows the gauge to properly display in the VC, however the hotspot does not seem to work properly. By contrast, if I configure the Duke for the default GNS 500 and make the same edits to the panel.cfg, the hotspot works correctly but the gauge does not display correctly in the VC. Below is my panel.cfg for the Duke (configured for RXP 500) w/ my Mindstar edits: // Panel Configuration file // RealAir Simulations Beechcraft Duke B60 2013 Update // Panel and Gauge Programming by Sean Moloney // Copyright (c) 2013 RealAir Simulations [Window Titles] Window00=Main Panel Window01=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE Window02=Blank [Window00] file=2D_Help.bmp size_mm=1024, 95 position=6 BACKGROUND_COLOR=0,0,0 visible=1 ident=MAIN_PANEL [VCockpit01] size_mm=1024,1024 pixel_size=1024,1024 texture=$RAS_Duke_CFG background_color=1,1,1 gauge01=Config!Options, 1020, 1023, 1, 1 gauge02=Config!RealView, 1021, 1023, 1, 1 gauge03=RASDuke!InitVars, 1022, 1023, 1, 1 gauge04=RASDuke!1hzCode, 1023, 1023, 1, 1 gauge05=RASDuke!2hzCode, 1024, 1023, 1, 1 gauge06=RASDuke!18hzCode, 1025, 1023, 1, 1 gauge07=Config!AdfDip, 1026, 1023, 1, 1 gauge08=RASDuke!NavCom1, 1, 2, 509, 61 gauge09=RASDuke!NavCom2, 1, 64, 509, 61 gauge10=RASDuke!ADF, 4, 127, 332, 49 gauge11=RASDuke!Xpndr, 7, 243, 305, 57 gauge12=RASDuke!Autopilot, 5, 177, 292, 62 gauge13=RASDuke!DME, 4, 305, 256, 46 gauge14=RASDuke!Annunciator, 886,131,137,262 gauge15=RASDuke!KA285_Annun, 512,2,337,108 // =============================================================================== // IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' BELOW CAN BE OVERWRITTEN // BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE // IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY // CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22' // =============================================================================== ;gauge19=rxpGNS!GNS530, 1, 660, 504, 364 gauge19=MPI_GNS!GNS530, 1, 660, 504, 364, 1:1:-1 gauge20=RASDuke!Blank, 0, 0, 1, 1 gauge21=RASDuke_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke B60 V2/Panel/Sound/RASDuke_Sound.ini gauge22=RASDuke!Sound_Manager, 1,1,3,3 gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1 [Color] Day=255,255,255 Night=225,117,89 Luminous=200,200,101 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=6144 [Window01] window_pos=0.739583,0.000000 window_size=0.260417,0.300000 visible=0 ident=15531 zorder=99 ;gauge00=rxpGNS!GNS530,0,0,100,100 gauge00=MPI_GNS!GNS530,0,0,100,100,1:2:15531 [Window02] size_mm=1,1 position=0 visible=0 ident=15600 BACKGROUND_COLOR=0,0,0 gauge00=RASDuke!Blank, 0, 0, 1, 1 Any ideas why my VC hotspot won't activate Window01 in this setup? Thank you for your help! J

After an initial investment of several hundred dollars into the MSE 2.0 series, I do not honestly see myself breaking open the piggy bank to get what I feel should have been delivered from the beginning. Granted, there are several states I'm very happy with in my collection which had quality 50cm source material to begin with, but several were delivered subpar and exhibted the already noted poor water masking and hackneyed blending between ultra-res and base MSE 2.0. I feel like these 4x releases - which seem like a rehash of the original source data - are being rushed to market again, just as MSE 2.0 was, in order to turn the cash crank once more in time for the 2015 holiday season. I would really appreciate longer release cycles and a more attentive eye to detail rather that cashing in on the output of a giant batch script. I've been drifting away from photoscenery a bit and towards FSGlobal, Vector, and Landclass and deploying the best of my MSE photoscenery in select areas where I fly most often. External load times and storage also make global 4x coverage somewhat prohibitive. J

Thanks, Kyle!

Just looking for continued assistance with issue: 20E-1CFFCA5B-0416It's been 10 days since I last received any correspondence from the support team. If anyone else is available from your staff to assist on this issue it would be much appreciated! Thank you,

I believe, in addition to Fail Op, you also need the Collins MCP selected and ISFD selected for Standby Instruments

Unfortunately, switching back to the Trike did not remedy the problem. The sim crashes immediately the moment I try to load the NGX again. It's definitely a one-and-done kinda deal. I will log a support ticket.

Thanks for the feedback. Strangely, I did not have this problem previously in FSX SP2 except if I tried to load a different PMDG aircraft over top another (like the 777 over the NGX - which is most definitely a no-no). Reloading a situation file in exactly the same NGX aircraft (for example, an autosave from FSUIPC) has not caused the simulation to CTD before until now. I will try going back to the trike between loads as you suggest and see if that helps.

I am running FSX-SE exclusively these days (no side-by-side FSX installation). I recently reinstalled the NGX SP1D and having a problem with a recurring crash whenever this aircraft is reloaded (after a crash, scenario reset, loading a new scenario, etc.) My startup aircraft is the Trike Ultralight so this should not be an issue. The problem only occurs after the NGX is loaded once, and then any subsequent reload of the NGX will cause a simulator crash as follows: Faulting application name: fsx.exe, version: 10.0.62613.0, time stamp: 0x551a6ac5 Faulting module name: PMDG_737NGX.dll, version: 1.0.0.0, time stamp: 0x54f7d429 Exception code: 0xc0000005 Fault offset: 0x001ef506 Faulting process id: 0x27f0 Faulting application start time: 0x01d09c81b37a11b9 Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\gauges\PMDG_737NGX.dll Report Id: 8d12496e-0875-11e5-8275-742f6865360b Faulting package full name: Faulting package-relative application ID: I thought I would post here to solicit ideas before formally submitting a service ticket. Thanks in advance. J

I have a button mapped on my flight yoke for this. Convenient on those missed approaches.

My mistake. It is in the DISPLAY section. Strangely, I have this set in both sections (not sure why), but Steve's instructions are to put it in DISPLAY so I would take that on good authority

Try this option in your GRAPHICS section (note the spelling) ForceVCShadowMap=1 ...in addition to... Force VC Walls, HD Shadows, and HD All Aircraft are checked in DXSceneryFixer Aircraft Casts Shadow on Itself checked in FSX Note, the cockpit shadow effects are a bit subtle in the NGX and most easily observed with a low sun angle.

ReShade will not inject for me. It spits back an error creating an sRGB compatible swap chain and chokes.

I didn't have any "spikes" to speak of. I did experience some issues with ground shadows at one of my third-party (Orbx) airports however that was causing some terrain unpleasantness, but the default airports seem OK.

Made the change you suggested. When I restarted DX10Fixer it prompted me to update my effects folder. I re-enabled ground shadows in fsx.cfg and I am happy to report I don't have any flickering! Now you have TWO success stories. This should be a featured part of the tool! The only downside at the moment is that ground shadows do not seem to inherit the shadow boost or contrast adjustment that aircraft shadows receive; the building shadows are very faint at times - most notably at low sun angles - while their aircraft counterparts are rather dark by comparison creating an odd effect. Any chance of resurrecting this code officially and promoting it to full glory? J

Does DX10 Fixer currently offer a solution for the violent flickering of ground scenery shadows that are cast onto other building surfaces? Everything I've seen so far in the forums has been with respect to aircraft/VC shadows. I am curious to know if the ground scenery shadows benefit from some tweak or adjustment in either the driver (nvidia) or DX10 Fixer? Thanks!

Oh cool! I had no idea they had snuck that in there. Neat!

Hello, I was just about reinstalling the latest versions of NGX and the T7 which include an updated Op Center. I noticed when I went to install liveries for the NGX, that the P-8A Poseidon was listed as a valid category in the Livery Downloader. This seemed a bit out of place. Perhaps this is known, but figure I'd report it just the same. Cheers,

I am trying to contact support regarding my recent purchase of the 777-300LR expansion. I submitted a ticket through the website a couple weeks ago but have yet to receive a response from PMDG. I'm hoping someone could follow up on my ticket and reply to it. Thank you, Jason Barlow

After installing FlyTampa OMDB 2.3, I observed some strange corruption of the default scenery tiles. Strangely, the problem persists now after uninstalling the product. Any ideas as to what may be causing this? J EDIT: This was caused by FTX Global landclass lookup BGL script (Scenery\BASE\Scenery\lclookup.bgl). Just had to disable FTX when flying in this region. Related thread: http://www.orbxsystems.com/forum/topic/83462-texture-morphing-issues/

Great info. Thanks!

This thread already answered one of my two questions regarding POS mode on the ND. In addition to ADIRU marker, there is another icon looks a bit like >()< and it floats out in front of the aircraft position indicator and bobbles around some. What is this indicator? I couldn't find a reference to it in the FCOM (or maybe I didn't know what to look for!)