Ron,

Unfortunately the RC4 window disappeared again on a flight today, and even using the Ctrl-x toggle the AdvWindow would not display again, so I did not know what frequency I needed to tune. RC4 also never contacted me again. There must still be a clash somewhere.

 

Is it possible to set an alternative toggle button for AdvDisplay, and if so what values could one use? How can one find the values to use for different keys?

 

Also, when an airport is uncontrolled and no ATIS is available, is there a specific frequency that one must tune? I was only able to get initial response from RC4, before loosing the AdvDisplay, by checking "Tune on contact", which I normally leave unchecked?

 

Thanks again for any advice you could give.

 

Cheers,

Stuart

First there is the key mapping within RC itself. Check that as the defaults do not appear as in the manual.

 

The rest of the key mappings are in fsuipc itself. Some are available on the tabs of fsuipc in dropdowns. Bring up your FSX many bar, click on modules, then click on fsuipc. Others have to be edited in to the proper section of fsuipc.ini.

 

The users guide and advanced users guide have the key codes for the keyboard as well as listing the functions available. For RC registered fsuipc  only some functions are available. If you register fsuipc (user paid) all are available.

 

You need to find out what was different between the flight that worked and what did not work. Was the aircraft changed? Other add-on installed? Different airport? New flight plan? Longer plan?

 

Again use for the first test RC and FSX with a default aircraft and scenery.

 

Also, when did the hang-up occur in your flight.  Was it right away on getting weather or clearance?

 

Creating a log on a repeatable error may be the shortest route. Start debug before loading your plan. In addition to the pinned topic when the hangup occurs, alt-tab to see if you can bring up RC itself. If so, then hit the quit button to save the debug log. Then go into your rcv4 folder and rename rcv4.log to something-meaningful.log so it will not be overwritten.

 

You can also in Win go into via the Control Panel and select Admin Tools. The select the long event log. Do this right away after an error so you can find anything before it fills with many normal things.

 

I also suggest you fill out your system and FS data in your AVSIM profile. Do not do that in your tag as that is against AVSIM rules. This way anyone can click on these description linked under your avatar (see my ancient setup) so if it is an add-on or system resource problem we might catch it.

Thanks Ron.

I have since found in the thread for a post that I made on the fsuipc forum, http://forum.simflight.com/topic/76828-rc4-not-responding-to-commands-help/?p=467748 that it seems others are experiencing the same issue, and am now wondering if the issue is with the later version of fsuipc.

 

Thinking of trying the earlier version again, if I still have it, before spending lots of time investigating other causes.

 

Cheers,

Stuart

Thanks Ron.

I have since found in the thread for a post that I made on the fsuipc forum, http://forum.simflight.com/topic/76828-rc4-not-responding-to-commands-help/?p=467748 that it seems others are experiencing the same issue, and am now wondering if the issue is with the later version of fsuipc.

 

Thinking of trying the earlier version again, if I still have it, before spending lots of time investigating other causes.

 

Cheers,

Stuart

 

Why not try the fix I posted for you in the thread you added to in my Forum? I posted it last night, and am just waiting to see if it helps before making a formal release.

 

Pete

Go to MCE. Open Tab ATC and uncheck Auto-hide ATC window checkbox. This should solve your problem