PDA

View Full Version : Eaglesoft Citation X v2.0 problems...



747jet
August 31st, 2017, 02:34
I owned the V1 of the X about 10 years ago for fs9. I remember that I liked this bird very much, especially its power and performance.

So I decided to buy v2 for fsx steam, as I read they updated it since summer last year. To be clear I knew that model, textures etc. are not the newest and best looking things for fsx. I have about 4 Carenado planes, although their system deepth is not the deepest, I like the good looking textures and cockpits. My computer is about 5 years old, but I do not have big proplems, running it with good fps. If Carenado would offer a Citation X, you might guess where I would have bought it...
Anyway some days ago I bought the Eaglesoft Citation X V2 and was very looking forward to it.... Until I did my first flights:

1. Problem: The throttle levers are stuck. ( I do not use a registered version of fsuipc) The plane reacts on throttle movements and I can fly but visually the levers in the cockpit are stuck! Here is a part of the manual:

"FADEC is Full Authority Digital Engine Control system. All the pilot need do is place the throttles in the detent position for the phase for Takeoff, Climb, Cruise, Etc. FADEC is annunciated on the EICAS Gauge above the N1 tapes.
Single\Dual Throttle Controller Setup and Configuration There are three requirements for proper FADEC\Throttle Operation with your Citation X 2.0. 1. Registered Version of FSUIPC installed. 2. Personal User edit of ESDG_CitationX.ini file as outlined below. 3. Personal User edit of Calibration\Controller Configurations in one of the following… 4. FSUIPC Controller Configuration 5. Flight Simulator Controller Configuration 6. Third Party [CH, Saitek, Etc.] Controller Configuration.

ESDG_CitationX.ini File Edit

Dual Throttle Yoke or Joystick: To enable Dual Throttle Controllers you must modify an entry in the ESDG_CitationX.ini file. The ESDG_CitationX.ini file can be found in the following locations: Windows XP: "C:\Documents and Settings\\Application Data\ESDG\CitationX" Windows Vista: "C:\Users\USERNAME\AppData\Roaming\ESDG\CitationX"
Open the ESDG_CitationX.ini file in notepad and locate the entry "Throttles". If you have a Single Throttle Controller, the value should be set to 1, if you have Dual Throttle Controller it should be set to 2. Higher values are not supported for this aircraft.
Example: ESDG_CitationX.ini file for Dual Throttle Setup [FADEC] LeftFadec=2 RightFadec=2 Throttles=2
Special Controllers: If you wish to disable Throttle Controller in order to use Keyboard Throttle Control the value should be set to 0 If you use an Xbox 360 Type Controller the use of FS Controller Configuration is advised. Some users report good results using special FSUIPC and Go Flight Module Calibrations\Configurations as outlined below. Note: Go Flight tips are user offered and are not official support from Eaglesoft Development Group."

[U]2. Problem: When I switch the autopilot to "ALT", the nose is going up and down all the time like the plane is drunk. No matter which speed or alt I go, even with weather settings off. I know this prolem from other planes but I could fix it with "flusifix" on all the aircrafts. On the Citation, it does not work.

3.Problem: Those guys of you who are familiar with fs9 might know the "no messages to transmit to anyone" problem. After take off the atc stucks, and after about 10 minutes it just says: no messages to transmit to anyone. Well I thought this was a fs9 problem, it now happened the first time after about 1000 hours in fsx and only with the Eaglesoft X.

Eagle Soft support is...I really don´t know if they have any support! I cannot register at their forum and I do not get any answer to my email.
I still would be happy if I could use the Citation. It is not only a question of money I spent for this thing. As I slowly get used to it, that about 1 of 5 FS addons are not working as they should. No matter how many reviews you read or in how many forums you search. There will appear problems, which are impossible to forecast.

Any solutions would be appreciated! :wavey:

Martin

747jet
August 31st, 2017, 02:41
Sorry for my bad English, I made some spelling mistakes. I cannot edit my posts, don't know why....
Sorry guys :banghead:

Penzoil3
August 31st, 2017, 14:49
From the support forum-

N400QW wrote:Ed Wilsons Multi Throttle Tutorial moved here:

WarpD wrote:If you set up throttles in FSX, here's how to do it.

Start FSX, go to the 'SETTINGS' screen. Select 'Controls...' from 'Other settings'. Once the 'SETTINGS - CONTROLS' dialog opens, click on the 'CONTROL AXES' tab to get a list of simulator events that can be assigned to a controller axis.
In the 'Controller type:' dropdown list, select your controller with the throttle(s). To set up dual throttle control you need to locate 'Engine 1 throttle axis' and double click on it's line to bring up the 'CONTROL ASSIGNMENT' dialog.
Once it's up, move your desired throttle axis on your controller so that FSX sees it and it will display the axis name in the dialog. Click 'OK'. Repeat the steps for 'Engine 2 throttle axis'.
Once those are assigned, it should look like this:

http://i107.photobucket.com/albums/m316/warpdrive/Axis%20Assignment%202.jpg (http://s107.photobucket.com/user/warpdrive/media/Axis%20Assignment%202.jpg.html)

Now click on the 'CALIBRATION' tab. You need to ensure your Sensitivity is at 127 for all joystick inputs and your null zones are 0. Nothing else works correctly... honest.
Once that's done... click 'OK' and you should exit FSX at that point to ensure it saves your joystick settings.
If you have only one throttle controller, then reverse it so the assignment is in 'Throttle axis' and both 'Engine 1 throttle axis' and 'Engine 2 throttle axis' are unassigned.

If you prefer FSUIPC to assign your joystick... fine... I was able to get that to work as well. First ensure you have NO ASSIGNMENTS for the throttles in FSX itself. Then load a flight and open the FSUIPC dialog from the menu.
Click on the 'Axis Assignment' tab. Click the 'Rescan' button and then move the axis for engine 1. You should see values show in the 'Joy#' and 'Axis#' windows.
In the bottom left area of the dialog select 'Send to FS as normal axis' then click the checkbox next to the first dropdown list below that. Select 'Axis Throttle1 Set'.
It should look something like this:

http://i107.photobucket.com/albums/m316/warpdrive/Axis%20Assignment%20FSUIPC.jpg (http://s107.photobucket.com/user/warpdrive/media/Axis%20Assignment%20FSUIPC.jpg.html)

Now click the 'Rescan' button and move the controller axis for engine 2. You should once again see values show up in the 'Joy#' and 'Axis#' windows.
In the bottom left area of the dialog select 'Send to FS as normal axis' then clock the checkbox next to the first dropdown list below that. Select 'Axis Throttle2 Set'.
It should look something like this:

http://i107.photobucket.com/albums/m316/warpdrive/Axis%20Assignment%20FSUIPC%202.jpg (http://s107.photobucket.com/user/warpdrive/media/Axis%20Assignment%20FSUIPC%202.jpg.html)

Now click 'OK' to close the FSUIPC dialog.

These are the steps I used... and my throttles worked correctly. If you follow these steps and your throttles don't function... please open your ESDG_CitationX.ini file and locate a line that has 'LEFT_THROTTLE'.
If the line is there, ensure it has a value after the = sign... if it is not there... let me know. There should also be one for 'RIGHT_THROTTLE' as well.
WarpD wrote:If you are missing those lines... add this to your ESDG_CitationX.ini file located in C:\ProgramData\ESDG\CitationX.

Code: Select all (http://www.eaglesoftdg.com/forum/viewtopic.php?f=7&t=1484#)
[KEYBOARD]
SETUP=1
L_RIC_CRS_INC=0x18100
L_RIC_CRS_DEC=0x18101
L_RIC_CRS_SYNC=0x18102
L_RIC_HDG_INC=0x18103
L_RIC_HDG_DEC=0x18104
L_RIC_HDG_SYNC=0x18105
R_RIC_CRS_INC=0x18106
R_RIC_CRS_DEC=0x18107
R_RIC_CRS_SYNC=0x18108
R_RIC_ALT_INC=0x18109
R_RIC_ALT_DEC=0x1810A
R_RIC_HDG_INC=0x1810B
R_RIC_HDG_DEC=0x1810C
R_RIC_HDG_SYNC=0x1810D
FGC_HDG=0x1810E
FGC_NAV=0x1810F
FGC_APP=0x18110
FGC_BC=0x18111
FGC_ALT=0x18112
FGC_VNAV=0x18113
FGC_STBY=0x18114
FGC_FLC=0x18115
FGC_VS=0x18116
FGC_NOSE_DN=0x18117
FGC_NOSE_UP=0x18118
L_SC_NAV=0x18119
L_SC_FMS=0x1811A
L_SC_BRG_1_INC=0x1811B
L_SC_BRG_1_DEC=0x1811C
L_SC_BRG_2_INC=0x1811D
L_SC_BRG_2_DEC=0x1811E
L_SC_PREV=0x1811F
R_SC_NAV=0x18120
R_SC_FMS=0x18121
R_SC_BRG_1_INC=0x18122
R_SC_BRG_1_DEC=0x18123
R_SC_BRG_2_INC=0x18124
R_SC_BRG_2_DEC=0x18125
R_SC_PREV=0x18126
L_DC_PFD_HSI=0x18127
L_DC_PFD_WX=0x18128
L_DC_ET=0x18129
L_DC_TCAS=0x1812A
L_DC_ACFT_SYS=0x1812B
L_DC_MFD_MAP=0x1812C
L_DC_MFD_WX=0x1812D
L_DC_SKP=0x1812E
L_DC_RCL=0x1812F
R_DC_PFD_HSI=0x18130
R_DC_PFD_WX=0x18131
R_DC_ET=0x18132
R_DC_TCAS=0x18133
R_DC_ACFT_SYS=0x18134
R_DC_MFD_MAP=0x18135
R_DC_MFD_WX=0x18136
R_DC_SKP=0x18137
R_DC_RCL=0x18138
L_RMU_LSK_1L=0x18139
L_RMU_LSK_2L=0x1813A
L_RMU_LSK_3L=0x1813B
L_RMU_LSK_4L=0x1813C
L_RMU_LSK_5L=0x1813D
L_RMU_LSK_6L=0x1813E
L_RMU_LSK_1R=0x1813F
L_RMU_LSK_2R=0x18140
L_RMU_LSK_3R=0x18141
L_RMU_LSK_4R=0x18142
L_RMU_LSK_5R=0x18143
L_RMU_LSK_6R=0x18144
L_RMU_SQ=0x18145
L_RMU_DIM=0x18146
L_RMU_12=0x18147
L_RMU_STO=0x18148
L_RMU_ID=0x18149
L_RMU_PGE=0x1814A
L_RMU_TST=0x1814B
L_RMU_DME=0x1814C
L_RMU_OUTER_KNOB_INC=0x1814D
L_RMU_OUTER_KNOB_DEC=0x1814E
L_RMU_INNER_KNOB_INC=0x1814F
L_RMU_INNER_KNOB_DEC=0x18150
R_RMU_LSK_1L=0x18151
R_RMU_LSK_2L=0x18152
R_RMU_LSK_3L=0x18153
R_RMU_LSK_4L=0x18154
R_RMU_LSK_5L=0x18155
R_RMU_LSK_6L=0x18156
R_RMU_LSK_1R=0x18157
R_RMU_LSK_2R=0x18158
R_RMU_LSK_3R=0x18159
R_RMU_LSK_4R=0x1815A
R_RMU_LSK_5R=0x1815B
R_RMU_LSK_6R=0x1815C
R_RMU_SQ=0x1815D
R_RMU_DIM=0x1815E
R_RMU_12=0x1815F
R_RMU_STO=0x18160
R_RMU_ID=0x18161
R_RMU_PGE=0x18162
R_RMU_TST=0x18163
R_RMU_DME=0x18164
R_RMU_OUTER_KNOB_INC=0x18165
R_RMU_OUTER_KNOB_DEC=0x18166
R_RMU_INNER_KNOB_INC=0x18167
R_RMU_INNER_KNOB_DEC=0x18168
CLR_HD_XFER=0x18169
CLR_HD_SQ=0x1816A
CLR_HD_NAV_AUDIO=0x1816B
CLR_HD_MODES_INC=0x1816C
CLR_HD_MODES_DEC=0x1816D
CLR_HD_OUTER_KNOB_INC=0x1816E
CLR_HD_OUTER_KNOB_DEC=0x1816F
CLR_HD_INNER_KNOB_INC=0x18170
CLR_HD_INNER_KNOB_DEC=0x18171
L_PFD_MIN_INC=0x18172
L_PFD_MIN_DEC=0x18173
L_PFD_RA_BARO=0x18174
L_PFD_STD=0x18175
L_PFD_BAROSET_INC=0x18176
L_PFD_BAROSET_DEC=0x18177
L_MFD_RTN=0x18178
L_MFD_KEY_1=0x18179
L_MFD_KEY_2=0x1817A
L_MFD_KEY_3=0x1817B
L_MFD_KEY_4=0x1817C
L_MFD_KEY_5=0x1817D
L_MFD_KNOB_INC=0x1817E
L_MFD_KNOB_DEC=0x1817F
EICAS_RTN=0x18180
EICAS_KEY_1=0x18181
EICAS_KEY_2=0x18182
EICAS_KEY_3=0x18183
EICAS_KEY_4=0x18184
EICAS_KEY_5=0x18185
EICAS_KNOB_INC=0x18186
EICAS_KNOB_DEC=0x18187
R_MFD_RTN=0x18188
R_MFD_KEY_1=0x18189
R_MFD_KEY_2=0x1818A
R_MFD_KEY_3=0x1818B
R_MFD_KEY_4=0x1818C
R_MFD_KEY_5=0x1818D
R_MFD_KNOB_INC=0x1818E
R_MFD_KNOB_DEC=0x1818F
R_PFD_MIN_INC=0x18190
R_PFD_MIN_DEC=0x18191
R_PFD_RA_BARO=0x18192
R_PFD_STD=0x18193
R_PFD_BAROSET_INC=0x18194
R_PFD_BAROSET_DEC=0x18195
EMER_LT_SW_DN=0x18196
EMER_LT_SW_UP=0x18197
DAYNITE_DIM_SW=0x18198
FLOOD_ROTARY_DN=0x18199
FLOOD_ROTARY_UP=0x1819A
EL_ROTARY_DN=0x1819B
EL_ROTARY_UP=0x1819C
LH_ROTARY_DN=0x1819D
LH_ROTARY_UP=0x1819E
CTR_ROTARY_DN=0x1819F
CTR_ROTARY_UP=0x181A0
TAXI_LIGHTS=0x181A1
L_LDG_LIGHT=0x181A2
R_LDG_LIGHT=0x181A3
L_FADEC_CUTOFF=0x181A4
R_FADEC_CUTOFF=0x181A5
LEFT_THROTTLE=0x181A6

747jet
September 2nd, 2017, 03:42
Thank you very much! I will try it

The other annoying problem is the cabin alt:

Once you are at about FL410, there comes the cabin alt warning. After about 20 minutes you get a red emergency descend warning which will not go away... The cabin alt increases and increases...
I read in another forum that during take off, you should at least give the engines full power for one second, so the alt warning should not come up. I did this, but no success. Perhaps there might be a way to edit the aircraft cfg...

Any ideas?