bradrcfii

I am a lttile embarrased I have not been able to solve this as I thought my FSUIPC skills have evolved futher than my current problem. My brakes will not disengage after applying the brakes and then releasing. Additionally, the parking brake will not disengage when pushing the brakes to their full limit. I need to use Control "." to release the parking brake. I am using FSUIPC for calibration. The rudders are fine. I have checked the brake reverse boxes in the calibration screen. What did I miss?

I am having problems with rudders and brakes. I followed the directions carefully including the reverse button. All worked well for a year but I implemented the Joy names feature very recently. The following is what I have in my INI file. Any problems here? [JoyNames] AutoAssignLetters=Yes R=CH PRO PEDALS USB T=CH THROTTLE QUADRANT T.GUID={598567D0-FA35-11DF-8004-444553540000} 1=CH THROTTLE QUADRANT 1.GUID={598567D0-FA35-11DF-8004-444553540000} Y=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> 2=Saitek Pro Flight Yoke 2.GUID={598567D0-FA35-11DF-8005-444553540000} A=Saitek Pro Flight Yoke A.GUID={598567D0-FA35-11DF-8005-444553540000} 0=CH PRO PEDALS USB 0.GUID={598567D0-FA35-11DF-8003-444553540000} As always, thanks in advance for your help. EDIT: PROBLEM SOLVED

Looks like a re-install is not necessary.

Answer from an ASE developer. It's been a long time but from my memory, FSUIPC configures these files on installation based on the existing configuration. Depending on the way you configure SimConnect, FSUIPC and other add-ons including ASE may fail to operate. Installing FSUIPC again would solve such issues and thus recommended to avoid connectivity problems. It's entirely possible to set things up without re-installing FSUIPC, you just need to correctly configure the server xml file. As a suggestion, you could back up your FSUIPC files to replace after re-installing if it becomes necessary.

Thanks Pete. The ASE doc is strange in regards to re-installing. I will ask in the ASE forums.

I have built my new machine and moved the fsuipc.ini file from the existing machine to preserve my hardware configurations, keystroke mapping, etc. According the the ASE installtion guide concerning simconnect, I am to reinstall FSUIPC after installing the simconnet ini and xml files. If I reinstall FSUIPC according the the ASE document on the top of page 54, will I preserve the current fsuipc.ini file? Thanks,

Great catch! I did look at lettering but not sure if I followed thru. I will have a look and implement lettering if not already.

Thank You for the answer I hoped for.

I am building a new machine and am hoping I can transfer my FSUIPC settings over to a new load of FSX. Possible?

PM sent. Thank you

Thanks Steve, I followed the install directions and the speed, altitude and heading controls work fine. The MCPPro buttons do not work including heading FLCH, etc. Also the range control on the EFIS are inop. I can set baro and minimums but no range and map controls. What should I look at? Additionally, how do I disable usb2 supports. Thanks again?

As usual Pete, you helped solve another problem. It was a time sync fucntion in FSCopilot. I did not think to look there becuase I was not running FSinn but I guess copilot is always running. Thanks, as always,

I changed those settings to zero and or off. Still no luck.

I am aware of the EFB problem and it was one of the programs I eliminated when trying to isolate this problem. Is there anything in FSUIPC that causes a time change and or FSX reload? Thanks,

This problem has returned. No matter what time I enter into FSX, FSX will reload to a time 4 hours earlier. I have disabled every application but FSUIPC but I see nothing in FSUIPC that would cause this. Additionally, I tried deleting the fsx.cfg file for a new rebuild. This did not solve the issue as well. I am trying to avoid a re-load of FSX as it looks like a weekend project. Any ideas? Thanks,

I guess not. It's windows. I think Apple got it right with their OS choice.

Well darn. Let the computer sit for a few hours, fired it back up and now all is well. You might be right, a nervouse breakdown that a nap cured. Wish I knew what was going on. Thanks,

No matter what time I select int he Time and Season window in FSX, it will load the time I select and immediatly reload to a time in the middle of the night. My PC clocks are correct. I am running FSUIPC 4.719. I am posting here because I had this problem before and reinstalled FSUIPC and the problem was solved. I did replace the dll but problem persists. Any ideas?

I see. Thanks.

ORBX response asking about the event stream when hitting the Heading button. "Unfortunately the fsx autopilot system does not mimic well the functions of the stec55x. A fair bit of coding trickery was employed to get it to function close to correctly. A byproduct of this is the event streaming you noticed. Regardless there is no performance hit or other problems associated with it. As for setting up hardware to work with it your best bet is to dissable it and use a simpler AP because it will usualy cause conflicts" I am not sure what he means in his statement about disabling and using simpler hardware. Integrating some of the MCPPro functions has been easy via FSUIPC.

Thank you. The constant steam of FD events starts when I hit the Heading Button. Does not look right to me either. On this AP, you must engage a lateral mode before a pitch mode can be enabled. I first hit the heading button that started the event stream and then VS.

I logged the event(s) when I hit the VS button on the AP. The log shows many events for the button push so not sure what to do. Thanks, 534531 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534593 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534640 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534671 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 0 (0x00000000) AP_VS_VAR_SET_ENGLISH 534671 *** EVENT: Cntrl= 66124 (0x0001024c), Param= -100 (0xffffff9c) AP_ALT_VAR_SET_ENGLISH 534671 *** EVENT: Cntrl= 66103 (0x00010237), Param= 1 (0x00000001) AP_PANEL_ALTITUDE_ON 534671 *** EVENT: Cntrl= 66102 (0x00010236), Param= 1 (0x00000001) AP_VS_SET 534703 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534765 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534812 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534875 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534937 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 534984 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535046 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535109 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535156 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535218 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535250 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535312 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535359 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535421 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535484 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535531 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535593 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR 535656 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

Make sure the yoke sensitivity is low within Ifly and that you have a good yoke dead zone.

Thanks for the suggestions. I will enable logging. The Lancair autopilot is a little less functional in that there is no altitude selection, can't set an altitude. You push the ALT button when you are at the altitude you want to be. Kind of old style. A Cessna T210 I flew in the early 80's operated the same way.

I am setting up a GoFLight MCPPro for some of the Autopilot functions for the ORBX Lancair. I was able to use sucessfully FSUIPC for Heading, Altitude Hold, Approach and Nav. However, I have not been able to integrate the VS function. It is an on/off type switch on the AP panel. You first engage VS, then dial in the rate. I am not sure if I should use CS Hold, VS On Off,. VS set etc. functions found in the FS drop down list. I believe I tried them all and non worked. Any idea's or is this an Orbx problem. Thanks, PS I am running 4.70b.