joga

Goran, i found this in xp-wiki, maybe it helps: http://wiki.x-plane.com/What's_New_in_X-Plane_10#New_Trim_Model see point "5.4 New Trim Model" Cheers, Jo

Here is my max pitch position (also out of scale). I thought it was a common XP10 bug/feature (higher trim resolution?), as i also experience trimming "ways" are about tripple as much in XP10 than in XP9 with almost every plane (only the CRJ seems to trim exactly the same)? Eg. Bonanza F33A needs about 270deg ailerons-trim to fly straight in XP10 (which can't be correct). I'm running XP10.05r1 on Win7x64/8GB/GTX680 (Please let me know if you need additional infos).

and surprise, surprise, the LJLJ issue is because of the same problem... waypoint LBL exists twice in SID BERT1W (renaming them to LBL1 & LBL2 did the trick) heres the SID <Sid Name="BERT1W" Runways="30"> <Sid_Waypoint ID="1"> <Name>LBL</Name> <Type>DmeIntc</Type> <Latitude>46.238500</Latitude> <Longitude>14.428553</Longitude> <Speed>0</Speed> <Altitude>1673</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>304</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <DMEtoIntercept>0.5</DMEtoIntercept> <Sp_Turn>Auto</Sp_Turn> </Sid_Waypoint> <Sid_Waypoint ID="2"> <Name>(1800)</Name> <Type>ConstHdgtoAlt</Type> <Latitude>0.000000</Latitude> <Longitude>0.000000</Longitude> <Speed>0</Speed> <Altitude>1800</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>304</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Sid_Waypoint> <Sid_Waypoint ID="3"> <Name>(INTC)</Name> <Type>Intc</Type> <Latitude>46.238500</Latitude> <Longitude>14.428553</Longitude> <Speed>210</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Hdg_Crs>1</Hdg_Crs> <Hdg_Crs_value>161</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <RadialtoIntercept>191</RadialtoIntercept> <Sp_Turn>Left</Sp_Turn> </Sid_Waypoint> <Sid_Waypoint ID="4"> <Name>LBL</Name> <Type>DmeIntc</Type> <Latitude>46.238500</Latitude> <Longitude>14.428553</Longitude> <Speed>0</Speed> <Altitude>6000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>191</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <DMEtoIntercept>11.0</DMEtoIntercept> <Sp_Turn>Auto</Sp_Turn> </Sid_Waypoint> <Sid_Waypoint ID="5"> <Name>D250C</Name> <Type>Normal</Type> <Latitude>46.071442</Latitude> <Longitude>14.719011</Longitude> <Speed>0</Speed> <Altitude>9500</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Left</Sp_Turn> </Sid_Waypoint> <Sid_Waypoint ID="6"> <Name>BERTA</Name> <Type>Normal</Type> <Latitude>46.449708</Latitude> <Longitude>14.625236</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Sid_Waypoint> </Sid> and here is the shot of the working departure... cessna729 thank you very much for your support! so the solution is not by renaming waypoints, its making their names "unique" which makes the difference... philipp, maybe you should take a closer look on this issue please note i've changed nothing with my configuration except the two waypoint-names. cheers, jo EDIT: may i ask how the xml is parsed? maybe some microsoft-xml-component responsible? ms-patchdays/windows-updates are coming and going...

in the meantime i tried Emalices route and i can confirm his problem (flown with XP9.70, original navdata) as soon you activate arrival STAR RUDA5S, RWY ILS07 TRANS KFL07 stuttering starts (complete stutter about every 0.5sec, feels like good old fsx... sorry about that )... i'm running at about 30FPS at this time when deactivating KFL07, stuttering ends... also i noticed that FMS couldn't keep on track (i was using 35R/FARA5P TRANS ABE9U for departure), at waypoint D038E it flown straight forward here's the route and a shot (no distance changing/zooming)... connection with LJLJ bug? unknown, but i'm trying with AIRAC 1205 next EDIT: tried with 1205, exactly same behavior, except the transition is now called KL07L (again no turning at D038E, so it's a SID "and" a STAR problem)... stuttering starts/ends immediately when you press the EXEC button EDIT2: same with XP10.05r1 AIRAC1205 (this time i activated TRANS KL07 after overshooting D038E, so both issues seem to be independent) ...but now i have to spend time with my familiy, otherwise im running into a third "problem" EMALICE.zip

Cessna729, you are right about the shaking... it was because of real-weather turbulance (pretty heavy, but ok, it's mountainous area). i really thought it was in conjuction with the MFD zooming/distance running up/down that starts about the same time (distance to EDDM should be 225nm). here are two shots (weather is now on CAVOC, so shaking is gone, my "flightmodels per frame" were already on 2): distances are constantly changing (354 and 623nm on the shots) ...next i'm trying Emalices route (LIMC-EDDB)

here is a shot of the effect... please take a look at the speed-trend-flex (its oscilating about 3-4 times per second, while the aircraft is heavy shaking) in the meantime i tried following things: original navdata: no sid available for RWY 30, absolutly no problems during take off climb, but sid-less route ends with a nice mountain crash airac 1202: no sid available for RWY 30, not flown airac 1204: same effect like with 1205 interesting is that original navdata and 1202 contain SIDs for RWY 31 in LJLJ.xml (but not for 30, and are not selectable because of that)... no idea if thats some kind of clue? i also tried updating x-plane data resources (2012.04)... without success please note that this is a very specific problem, only occuring at one of my routes and i'm overall very very happy with the CRJ

javier, it has nothing to do with overspeed pitch-up (as stated above, SPEED mode is still on during take-off climb at about 170kn, aircraft is shaking wild and speed-trend-flex moves constantly up and down). but please take a look at tristans problem first... i'm doing more investigations with original nav-data tomorrow cheers, jo

same problem? probably only philipp can answer this question... sorry i don't know, but it's for sure a SID/STAR related problem thats messes up with the FMC. mine creates heavy airplane oscilation (on XP10) which could probably bring down FPS on a weaker GFX (im running GTX680 3GB). so my intention was to report similar problems and not overtaking your thread... but what we could do is checking our flightplans vice versa (and i'm going back to original-navdata) to see if the problem is directly related/reproducable on our machines... ok? (i've got time for this on thursday)

sorry, i recalled the SID wrong, it's BERT1W and it's in LJLJ.xml. i tried same route in XP9.70, same thing happens about half way to waypoint 1800 (first waypoint), but without the heavy oscilation (seems to be a XP10 thingy). zooming of the MFD is because distance is running up and down constantly (distance was between 360 and 400nm before i shut down XP9). i also attached the routefile for you. maybe it's all because of the latest AIRAC, so i'm trying to obtain cycle 1202 next (i only have 1205 available at the moment). ps: of course i'm doing IRS realignment on each attempt. BUG.zip

i'm sorry, i have to report similar problems using SIDs. i'm taking of LJLJ RWY 30 (heading to EDDM) using BERT1L. as soon i engage AP/intercept route, FMC start to act crazy (MFD zooms in and out, freezes) and the aircraft behaves like it's in heavy turbulence (SPEED mode still on, but speed seems to oscilate constantly). without using the SID, everythings just fine, except the "sidless" route guides me directly in the next mountain my XP10 and CRJ are up-to-date (preferences deleted, flightmodel on 2), latest navigraph data (1205), win7x64, reproduced the issue about 5 times (also with closing/reopening xp10) it's really strange, because other routes seem to work perfectly fine (did today some LOWI-LOWW, LOWW-LILJ flights without any issue). please tell me if you need additional info for hunting down the bug... greetings, jo ps: i'll fly the same route tomorrow using XP9.7 and let you know what happens.

Thanks for looking into it Goran! I just want to add, it looks like there is also a trimming problem with other planes using XP10 (i.e. the F33A almost needs tripple as much aileron-trim than in XP9). Maybe some change in the trimming resolution, which is not compatible to XP9? Still a long way to go with XP10, but i'm really glad to hear that at least the DC-3 will be tweaked and fine-tuned to perform correctly!

Due to the release of Keflavik, i'm spending currently more time in XP10 and i have noticed that the DC-3 flight-model behaves slightly different from XP9 (which feels really good to me). Example: 2000ft (no winds), props@22.5, map@30, pitch trim@4 gives me a perfectly trimmed level flight @140knots (which seems very very realistic) While in XP10 same settings gives me only about @115knots with alway a tendency to climb further (even with trim@8!) Any idea about this? XP10 fault/beta state, or needs the dc-3 v10 flight-model more tweaking? cheers and happy easter, jo ps: if helpful, i can send you the corresponding screenshots. both sims are up to date, default payloads, X52 full linear @0%, stability @25%

thanks for the tail-dragger option, much appreciated! one other small issue (maybe my misunderstanding?): even i refueled the plane to the max, the right fuel indicator (main) always shows "zero"... aux seems to work fine (same with xp 9.70/10.05b). as for the doors, i meant there are no visible doors in external view (left side pilot/cargo-passenger doors) besides these small issues, it's really a blast to fly... fantastic job on the flight model!

thanks for this great aircraft... visuals and flight-model are stunning! i only have to report two small issues (xp9 version): when toggling the tail wheel lock by button, the virtual-cockpit lever stays in position (unlike the parking brake, which works fine when toggling) and where are the doors? i'm trapped in my C-FLFR and have to fly forever anyway, by far my favorite x-plane... it's definitely not an option to go back to a FSX dc-3 after flying this one! cheers, jo