Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'ejetsv3'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • FS Commander Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • FScene Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • FS MAGAZIN (DE)
  • simRussia
  • FSUIPC Client DLL for .NET

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 7 results

  1. When doing managed descend, I noticed both speed and altitude restriction are not well followed by FMS speed: Say I have STAR with point WAP1, WAP2, WAP3, on WAP2, there is 210kts speed restriction, the airplane with speed knob in FMS mode will slow to 210 on WAP2, but after WAP2, it will speed up to 240 (or even faster if above FL100), and even if I also put 210 on WAP3, the airplane will speed up after WAP2, then slow down before WAP3, even when there is less than 10nm between them. alt: Any "Above" restriction will be treat as "At", say WAP1 and WAP2 both have 8000A and WAP3 have 8000, the airplane will just down to 8000' right at WAP1 and stay there until WAP3.
  2. You will need QsimPlanner (v0.4.8 as I tested) found on : https://qsimplan.wordpress.com/ This is a basic Qsimplanner v0.4.8 performance data set for Feelthere E170/E190 v3 sp1 It contants: Data from E170/190 AOM vol.1 Flaps2 and 4 take-off performance. You can get max FLEX temp based on Field and Climb limitation for given airport, weather and weight; Mission fuel calculation data for both LRC and M0.78 profile at optimal cruise flight level; Unfactored demonstrate landing distance data for E190 Flaps5 and Full; Unfactored OPREATIONAL landing disnance for E170 with autobrake BUT only for 1/8 inch standing water runway It DOSE NOT contant: Vspd calculation, due to QSP limitation; Take-off data for wet runway and flaps1/3, due to lack of data; Improved climb (aka. different V2/Vs ratio) or obstacle limitation, due to both lack of data and QSP limitation; Mission fuel calculation for a given altitue due to QSP limitation; Operational landing distance for dry runway for giving autobrake, due to lack of data. Also notice: As for feelthere EjetV3's E190, the fuel flow is a bit higher than realworld data as this use, If you want better match with this dataset, edit aircraft.cfg and change "fuel_flow_scalar = 1.1" into "= 1.0" For E170 sp1, =1.0 for LRC and =1.12 for M.78 is more accurate Feelthere's LRC is not accurate, manually manage your speed pre AOM can give you the best tripfuel match, otherwise it's close enough though... TO data I input here are rounded to 100kg/100lb, so maybe it's not as accurate as AOM; Whiel AOM includ TO data for elevation 500/1500/2500/3500 feet, I tried some data point and found linear interpolation is good enough, so I only inputed data for 0/1000/2000/3000/4000, and let QSP do the rest; Optimal cruise flight level for E190/170 for route longer than 400nmi is almost all over FL350, if you plan to fly at around FL300, add 5% of trip fuel should do the trick; Due to QSP limitation OR my ignorance, I cant get both flaps or cruise profile into one aircraft profile, so there are 4 different airplane profile, E190L2 for flaps2 T/O and LRC cruise, E170M4 for flaps4 T/O and M0.78 cruise, and so on. I don't have time to double check all the numbers I typed in blindly, so if you find a typo or so (like 45.2 inputed as 35.2), please let me know. There are EJet Vspd calculator on X-plane.org and E190 Operational landing distance calculator on Appstore if you want.... INSTALLATION: Unzip "PerformanceData" floder into C:\Users\<your username>\AppData\Local\qsimplanner\0.4.8\ merge with the one already in there, it should not override any file. There should be 8 aircraft type as "E190L2""E190L4""E190M2""E190M4" "E170L2""E170L4""E170M2""E170M4" in QSP's list, choose one fits you. Qsim_E190_Performancedata.zip Qsim_E170_PerformanceData.zip
  3. First of all, Thanks the great effort FeelThere put in to the SP1 aerodynamic tweak, the over all aerodynamic performence turn from V2 and non-sp1's totall mess into something I think only need some final adjustment. Here is 2 small thing I noticed: 1.FMS's LRC is about 0.01~0.02 Mach slower on E190, and about 0.01 faster on E170 compare to the Manual I have, not huge difference, but somewhat noticeable. 2. I see the Fuel flow for climb and cruise is about 1.1 times higher than the chart, then I look into the Aircraft.cfg, fond there are fuel_flow_scalar=1.12 and =1.1 on E170 and E190's data, once I reset them to 1.0, the crz FF and trip fuel use is dead accurate to the realworld data, is it just some typo or last minute change forgot? Hope it get fixed.
  4. Hi, with E190 SP1, every time I manually input route in MCDU FPL (like >V23.ALINK), I got more and more blank line of "----.---" at the buttom of FPL page, While I can delete them after and doen't makes any other problem, it just seems not correct and annoying....
  5. Just tried the SP1 with E190, I noticed the Throttle are changing way too fast than pitch, when initiating an FLCH climb or descend. It pushes airspeed about 15kts higher than command speed when starting a climb, or 20kts lower when starting descent. After a while, the pitch follow up and eliminate the difference, keep on speed throughout the remining FLCH phase. EDIT: I just noticed it's due to CG error, see below.
  6. I've been trying to get a confirmation email so that I could post for/regarding the new V3 eJets, but, alas no reply. Strange -- so I changed my email. Anyway, loving the new eJet V3, but the night lighting in the Virtual Cockpit is a problem indeed. Not sure when the SP will be out and how it will be addressed. I'm going ahead anyway and posting this to help out the community with the problem in the VC with night lighting. I have created FSLabs Spotlights Profiles for the 170, 175 and 190. I'll try to finish the 195 as quickly as possible. The link to the files is below along with a link to the FSLabs SpotLights page. Drop each FSLSpotLights.ini file in the folder of the respective aircraft (same folder where the aircraft.cfg file is). You will need the FSLabs Spotlight utility installed; it's free. The lighting follows the real world EJet. I have tested these with P3D V4.5. Links: FSLSpotLights.ini file for the E170: https://www.dropbox.com/s/jun2uz3jhkbobc3/FSLSpotLights.ini?dl=0 FSLSpotLights.ini file for the E175: https://www.dropbox.com/s/3tphfni953ay4tk/FSLSpotLights.ini?dl=0 FSLSpotLights.ini file for the E190: https://www.dropbox.com/s/u9bkpmly0soh3g9/FSLSpotLights.ini?dl=0 FSL Spotlights.ini file for the E195: https://www.dropbox.com/s/jkquqzcy5cq3s8r/FSLSpotLights.ini?dl=0 FSLabs Spotlight Utility: https://www.flightsimlabs.com/index.php/spotlights-2/ Enjoy, Jeffrey S. Bryner
  7. Search up and down in the config tool, it seems this function is still missing in the keyborad setup? -- mods. edit: subject line to better reflect question
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.