Sign in to follow this  
Geofa

Reality-XP NAVCOM Radios in Deb

Recommended Posts

I installed everything per Geofa's instuctions. Main install file, CAB from first Patch, Panel.cfg (XP version) from second Patch, copy and rename RealityXP_FlightLine.gau to RealityXP_FlightLine2.gau.In the main pilot's panel, clicking on the radio icon brings up the stack with the Reality XP boxes. However, the NAVCOMs do not accept any inputs or mouse-clicking changes. In order to change a frequency, I have to bring up the copilot's panel and use the stack on that panel (which works). However, back to the main panel and the pop-up radio stack, the freqs displayed are not the ones placed in the radios from the copilot's side.Has anyone else reported this? Is there a fix?Doug

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Doug-I'll take a look.What the problem is is the copilot view. I chose to include it and have "double instruments"-eg a radio stack on the main panel and one on the copilot. What I found was the default fs radios had no problem-but fs had a problem with two xp radios-and definately a problem with double gps's.I found the work around was to have two seperate instances of the xp running at the same time. Did you make a copy your reality xp flightline gauge-rename it to flightline2 and stick it in your gauge directory?This way you fool fs-the directions probably more clearly stated in the readme html file (directions) that come with the package-should be in your start menu under geof a.When reality xp releases the 1.1 version this step should not be necessary anymore.Again-a confusing issue for me as I am beta testing the 1.1 now. Let me know if that fixes the problem.Geofhttp://members.telocity.com/~geof43/geofanim2.gif

Share this post


Link to post
Share on other sites

Geof:I had already done the copy/rename thing for the flightline gauge (see my original message).Doug

Share this post


Link to post
Share on other sites

Doug,In the Window04 (for the Collective Stack), try renaming the gauges to FlightLine!NavCom_FL30(rather than FlightLine2!NavCom_FL30). Same for the Transponder (FlightLine!XPDR_FL70).I had the same problem as you, and this solution worked on my own setup. YMMVMike

Share this post


Link to post
Share on other sites

Mike and Geof:Yep, Mike's instructions worked as advertised. Thanks for your help. Doug

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this