Joshua Che.
-
Posts
2360 -
Joined
-
Last visited
-
Days Won
51
Content Type
Profiles
Forums
Downloads
Posts posted by Joshua Che.
-
-
You Should have changed the code to this:
(L:Pause_code, bool) 0 ==
if{
<!-- Altitude callouts-->
(A:VERTICAL SPEED, Feet per second) -0.2 >=
if{
0 (> L:CALLCALLED, number)
1 (> L:CALLCALLED2, number)
}
(A:VERTICAL SPEED, Feet per second) -0.2 <=
if{
(L:CALLCALLED, number) 0 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 1000 <
(A:RADIO HEIGHT, feet) 14.4 - 990 > &&
if{
1 (> L:ASC_AIRBUSX_1000, bool)
1 (> L:CALLCALLED, number)
1 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED2, number) 1 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 500 <
(A:RADIO HEIGHT, feet) 14.4 - 490 > &&
if{
1 (> L:ASC_AIRBUSX_500, bool)
0 (> L:CALLCALLED, number)
0 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED, number) 0 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 400 <
(A:RADIO HEIGHT, feet) 14.4 - 390 > &&
if{
1 (> L:ASC_AIRBUSX_400, bool)
1 (> L:CALLCALLED, number)
1 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED2, number) 1 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 300 <
(A:RADIO HEIGHT, feet) 14.4 - 290 > &&
if{
1 (> L:ASC_AIRBUSX_300, bool)
0 (> L:CALLCALLED, number)
0 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED, number) 0 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 200 <
(A:RADIO HEIGHT, feet) 14.4 - 190 > &&
if{
1 (> L:ASC_AIRBUSX_200, bool)
1 (> L:CALLCALLED, number)
1 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED2, number) 1 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 100 <
(A:RADIO HEIGHT, feet) 14.4 - 95 > &&
if{
1 (> L:ASC_AIRBUSX_100, bool)
0 (> L:CALLCALLED, number)
0 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED, number) 0 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 050 <
(A:RADIO HEIGHT, feet) 14.4 - 047 > &&
if{
1 (> L:ASC_AIRBUSX_050, bool)
1 (> L:CALLCALLED, number)
1 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED2, number) 1 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 040 <
(A:RADIO HEIGHT, feet) 14.4 - 037 > &&
if{
1 (> L:ASC_AIRBUSX_040, bool)
0 (> L:CALLCALLED, number)
0 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED, number) 0 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 030 <
(A:RADIO HEIGHT, feet) 14.4 - 027 > &&
if{
1 (> L:ASC_AIRBUSX_030, bool)
1 (> L:CALLCALLED, number)
1 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED2, number) 1 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 020 <
(A:RADIO HEIGHT, feet) 14.4 - 017 > &&
if{
1 (> L:ASC_AIRBUSX_020, bool)
0 (> L:CALLCALLED, number)
0 (> L:CALLCALLED2, number)
} }
(L:CALLCALLED, number) 0 ==
if{
(A:RADIO HEIGHT, feet) 14.4 - 010 <
(A:RADIO HEIGHT, feet) 14.4 - 007 > &&
if{
1 (> L:ASC_AIRBUSX_010, bool)
1 (> L:CALLCALLED, number)
1 (> L:CALLCALLED2, number)
} }
}
(A:VERTICAL SPEED, Feet per second) -0.2 <=
(L:Throttle_ani_var_L, number) 5 > &&
(L:Throttle_ani_var_R, number) 5 > &&
(L:Retard_hasbeenplayed, bool) 0 == &&
(A:RADIO HEIGHT, feet) 24 <
(A:RADIO HEIGHT, feet) 14 > &&
(L:AB_AUTOLAND, bool) 1 == &&
(A:RADIO HEIGHT, feet) 34 <
(A:RADIO HEIGHT, feet) 14 > &&
(L:AB_AUTOLAND, bool) 0 == && || &&
if{
1 (> L:ASC_AIRBUSX_RETARD, bool)
(L:AB_AUTOLAND, bool) 1 ==
if{
1 (> L:Autoland_retard, bool)
1 (> L:Retard_hasbeenplayed, bool)
}
}
This code prevents double callouts
-
RELEASED FBW v0.5!
Any Feedback on current FBW is appreciated.
Regards,
Joshua
-
XML can be unstable even if the programing is theoratically correct. It can be fixed by slowly debuging ,removing components and after finding the problem component and rewrite the logic. However, the GPS_module.dll is closed source though the MCDU programing can be modified. But I dun thing the problem is with the MCDU but with the GPS module. From what I see Airbus V2 should fix it.
-
Okay After doing research and investigation, I determined the throttle problem is related to FDE. The relationship between CN2 and air ratio or whatever is affecting the N1 as speed increases. Aerosoft needs to fix this. I am no FDE expert and hence I cant fix FDEs.
On FBW, I will be releasing v0.4 soon.
RELEASED FBW v0.4!
Joshua
-
ANSWERS ABOUT MODIFICATION TO FADEC:
The Aerosoft Engine Modelling is accurate in providing accurate thrust. However, the drawback is as airspeed increases the N1 decreases inorder to output an accurate max thrust. Many developers have gone around this problem by programing a fake (or rather accurate) N1 reading on to their gauges (FSX Engine Modelling provides inaccurate low N1 at high alt). Alternatively, developers can allow super high N2 at higher mach with accutate N1 with a Custom coded PID Controller to control the Engine. However, I don't have experince in modifying Fight dynamics. Unless the Engine modelling is Option 2, I can't do anything. It is up to Aerosoft on their decision here.
-
-
Thanks for the comments. Really appreciate it . However, did your find it the bank protection is a little too rough?
And to reply about the throttle issue, I might do it during my spare time. My test are all coming and I need to study. It requires reworking the whole aerosoft FADEC. However i believe it can be done but i would want to finish polishing the FBW before going on to FADEC.
EDIT: Here I want to credit aerosoft in its open design. Please contnue the "tradtion" of open design. If not, i will not be able to make this kind of modifications.
-
NOTAM :
Guys,
I have released a new FBW that require FSUIPC here
Regards,
Joshua Che.
From now on minor updates (usually no new features will be named with a,b,c etc.) while major update (new features) will be given a new number.
THOSE WHO UPDATED TO V0.8b ,0.8c V0.8c2 MUST perform below instructions and UPDATE to the latest version
Please go to your <Microsoft Flight Simulator X Folder>\SimObjects\Airplanes\aerosoft a32<0/1> <iae/cfm> delete aircraft.cfg and rename aircraft.cfg.bak to aircraft.cfg
- 1
-
Introduction:
I have seen many people here due to nose drop or any other FBW problems, disable the FBW.
I have used xml to program a FBW gauge using XML and is still in beta. I need feedback on the gauge to improve it.
This gauge is in no way related to aerosoft and its for your own personal use.
This FBW does nor require FSUIPC.
WARNINGS:
THIS DOES NOT WORK WITH MERGES!
BACKUP FIRST
FSX MUST BE CLOSED WHEN INSTALLING
Installation:
Run the appropriate .exe patcher that will patch your files. There are four patchers.
Recommend to install one patcher first and test out then apply all.
and change joystick sensitivity to
~about sensitivity 5
Please Feedback on how real it is compared to the real a320.
LATEST VERSION: V0.8f2
THOSE WHO UPDATED TO V0.8b ,0.8c V0.8c2 MUST perform below instructions and UPDATE to the latest version
Please go to your <Microsoft Flight Simulator X Folder>\SimObjects\Airplanes\aerosoft a32<0/1> <iae/cfm> delete aircraft.cfg and rename aircraft.cfg.bak to aircraft.cfg
DOWNLOAD:
Direct from Aerosoft:
http://forum.aerosof...-fbw-code-beta/
Mirror:
http://dl.dropbox.co...EBETAv0.8f2.zip
CHANGELOG:
V0.1 -
First Release
V0.2 -
Added Bank Limit Protection (66 limit)
Refinments to FBW Pitch
v0.3 -
Added Bank angle protection (more than 33 , rollback. Need constant sidestick)
Futher refinments to pitch
Use dup2 as patcher for most users dont know how to modify.
Added Pitch Protection
v0.4 -
Added Bank Angle Hold (Will hold bank angle when zero sidestick input)
Cleanup in to a .cab file
Improved G-force accuracy
v0.5 -
Flare Mode. (Autotrim Freeze and some trim down to force pilot to flare)
Fixed Alieron Trim and Autopilot conficts.
Fixed Autotrim active on ground
v0.6-
Fixed Serious Oscillation after hand-flying for a while.
v0.7-
Improved Default Flare. (GlideSlope should be fixed as well XD)
Fixed patcher not patching A320IAE files correctly
v0.7b -
Should fix all patcher woes.
Fixed Nose down input take a long time for the FBW to trim properly.
v0.8-
Rudder Fix! (Really need testers on this one!)
Compatibility fix with LH1711 More Callouts.
v0.8b-
Refinments to Rudder Turn Coordination
v0.8c & v0.8c2 & v0.8c3 -
Patcher Woes again...
v0.8d-
Forced Auto Coordination for rudder.
Increaed Trim down for Flare (But still not too much)
v0.8e-
Fixed G-Force Accuracy. (No more FSpassengers upset.)
V0.8f-
Re-coded Flare logic from airbus FCOM.
Autotrim re-coded. More instantaneous triming after neutral now. (Need Feedback )
Uninstaller included now. (Beta. May be unreliable).
V0.8f2-
Fixed incorrect Flare Logic. (Included in v0.8f the wrong file).
Upcoming Versions (to be implemented)
- Stall Protection (Not alpha floor, but it is to keep the AoA from reaching stall)
- Overspeed Protection (Need to research)
- Any other sugestions for FBW only?
LEGAL STUFF
This mod is released as FREEWARE. You may use and modify it in any way you wish, but
you may NOT use it in any kind of money-making endeavor, and you may NOT publicly
distribute any copies of it , whether modified or not, without my permission.
Regards,
Joshua Che
- 5
-
Hi,
I would like to see
1. MCDU
Mininum Wilco FMC functionality: SID,Stars,Holding,Direct to,Perf pages like Wilco one
Better VNAV expected from the MCDU.
2. NEW FBW system
Don't use fsx FBW! It Sucks!
But if it will slice my fps by more than 35%, I would stick to the default one
3.New FADEC/Autothrottle
I think Feelthere has done a good job on this their Throttle detend moddeling is rather good. Can use F3,F4 somemore
4. Smoother flight plan lines (curved) for SID,STAR and for after seleting direct to.
5. A318 & A319
Better still Include STEEP APPROACH for operation at London City.
Refer to smart cockpit about steep approach
Modeling wise i think just leave it. Besides the drooping surface. Maybe make the advance modeling more optimised for extra system functionality?
Thank you aerosoft for everything this far. You should give yourself a pat on the back.
Joshua
-
Oh can be tweaked so ok... but see the diffrence in the numbers they resemble the actual one better
Eg:
Lucidia Console:
82.5 N1
Eg2:
320-|
|
310-|
Eg3: STATUS
HYD 1 ....... OFF
HYD 2 ....... ON
Verdana
EG1: 82.5 N1
Eg2:
320 -|
|
310 -|
Eg3:
STATUS
HYD 1 ....... OFF
HYD 2 ....... ON
See the diffrences... but nevermind since it can be tweaked
-
Will the PFD display final because i dont really like the "look" of the fonts. i would advise you use fonts like Lucida Console.I am not critising anything but just the fonts you see... It would be more realistic with the font i suggested you can try changin it for PFD,MFD,EICAS.
- 1
-
Will the Vc be intergrated into the model file or will it be two seprate model files (one for exterior and one for VC)
-
More Callouts ;D
in Aircraft General
Posted
For Wrong Aircraft Error:
In the asc.cfg change the id=something
to this:
For A320:
id=45165931
For A321:
id=45165925
FYI, Your code is incompatible with my FBW.
v0.8 Fixed it. copy the callouts then run my FBW patchcer.