Richard Dastardly
-
Posts
183 -
Joined
Content Type
Profiles
Forums
Downloads
Posts posted by Richard Dastardly
-
-
15 hours ago, Joe Markowski said:
Was this the issue where if you don't Exec after adding a runway or approach to the FMS it will double up on the STAR waypoints?
No, it was the "wandeirng all over the sky instead of attempting to follow the flightplan" problem
I think it was that approach to Stansted that sends you in a loop to have a look at Duxford, but it might have been a different and a bit more direct one.
7 hours ago, Syrinx said:I believe it's happening when I'm not going fast enough.
I had the VNAV cruise say .74M, and suggest it can fly x altitude at that speed with my loadout; it lied. When I pushed the throttles 'through the firewall' and got her up to .80M, the waddling stopped.I'm always at 0.81 or more if I can ( recently seems the -900 won't go any faster, no more 0.84m cruising! ) - I try not to fly actually on the stop below climb but it's usually pretty near. Still get some LNAV issues.
-
It's certainly not manual input doing it, because I never import routes. I've flown it recently but not since SU12 ( and I can't right now because my motherboard is dying ), it was *mostly* ok provided I remembered the stick profile with the deadzone, and remembered all the things you can't tell it to do. It made a real mess of one STAR, I remember.
-
Holds are just broken - see several other threads. That seems to include leaving them, unfortunately.
-
@Mathijs KokIs it under your control whether you can unencrypt the config files for the marketplace release? the premium edition bundled aircraft have been decrypted but generally marketplace ones are still as they were. I too unfortunately bought both CRJ packages from the market before I knew any better...
-
Just flew a very heavy -1000, rotation was as usual ( albeit the SU11 gusts were doing their best to push it off the runway... ). Landing rather easier than the -900 too.
-
1
-
1
-
-
This was covered in the "LNAV Tracking Issue" thread at some length, there appear to be two separate problems with holds - first off you can't program them right, the aircraft wants to fly a reciprocal of the heading you enter the hold at rather than what you tell it to - and then it won't fly the hold pattern either ( which may or may not be something to do with the other issue, might be something to do with the general LNAV issue, or might be something entirely new ). If you could provide tracks ( I take mine from LittleNavMap ) along with hold details & what you programmed in I'm sure it'd probably help when it comes to diagnosing the problem.
-
1
-
-
I haven't, yet, but it might be worth checking if a SU has messed with the aircraft's CG. There are a couple of others that look like they've been somewhat affected. I've had a couple of 900 flights now & checked everything was showing in limits on the EFB ( and obviously hammered the button to set the a/c up ) but that doesn't mean there's no base-level problem. I had a, er, firm touchdown the first time after I overcorrected, and the second time it just floated because a gentle flare turned into a bit more than expected, so when I have time I'm going to have to do a bunch of touch & goes & see what's going on. There's a whole load of aircraft that've got pitch happy over time ( like the JF Pipers ) but I'd have thought if the source issue was from the same updates we'd have noticed before now. I'm not even really moving my stick at this point, just applying a gentle squeeze - it feels like trying to control a really light helicopter.
And for the record, no FSRealistic, just live weather.
-
1
-
-
Flew the -900 today for the first time in quite a while - had no problems following the route ( not a particularily difficult route, mind you ), but... was it always this twitchy? on final I had the pitch response of a fighter at 140kts, it was a bit disconcerting. And for some reason nobody wanted to connect a jetway, which is new.
Lot of swaying around at FL360, but that's SU11 for you.
-
1
-
-
On 1/4/2023 at 1:51 PM, DGH said:
Luckily we have working 737 LNAV ... no back and fourth swaying and happy passengers.
Almost 2 year anniversary of this LNAV bug ...
ANY NEWS ?
Given how the DC-6 AP is currently going all over the sky too, I wouldn't go too far down that hole
I haven't actually flown any of the CRJs in months, I'm presuming SU10 & 11 didn't help at all?
-
1
-
-
Certainly been reported a lot ( here was my last report from January -
) - not sure if we've found any common grund yet.
-
Fairly sure Hans is working on the ATR for Asobo atm...
-
2
-
-
Any other mods / products installed? you can tune up the ILS on the ground, so it might be worth spawning in a bunch of places & just tuning NAV1 up & see if you get something - given you *did* get a LOC once it smells of either bad nav data or outside interference. Unfortunately as I discovered, the only way to refresh navdata for this thing is to reinstall it.
-
12 hours ago, Ha_Ma said:
Well, i have tested and sadly i can report that i can reproduce that failure.
I have started the CRJ 900, Delta Livery, started up the aircraft as i always do (following checklist) and imported a flight plan from simbrief. Eyerything works as it should.
After around half an hour in the air, i decide to change the approach and runway (don't ask why, i just wanted so
)
So i go in the Legs page of the MCDU and delete all waypoints from approach transition on. Then i press DEP/APPR and the right page opens but at the same moment all systems of the aircraft do freeze. As i told above all switches and rotaries move and give acoustical feedback, but there is no more reaction to any of these. Only rudder, aileron (both without optical feedback) and roll (with optical feddback) seem to work.
The bold bit seems to indicate it's the well known long-standing systems crash. I thought that'd been fixed somewhat in the last update, though.
-
On 9/28/2022 at 6:43 PM, Tomcat_22 said:
Perhaps I phrased it wrong, I've not got the 1st clue of modding so I'm just blabbering if you will, getting rid of some frustrations I guess, what I meant with a modding is having the plance force read a different AP system or one that over-rides the default one, at least the LNAV, heck I don't know, but how it's currently, is absolutely not fun.
As for reusing some code, I believe their next plane is the A330, maybe, not sure, I should hope they wont use any of this code, probably can't anyways as the FBW has different logic... But yeah, at the end of the day, I hope this gets fixed because I've also parked the CRJ for now, I'll use a bigger GA plane or the 736 for short hops, one that can actually fly an LNAV plan.I've no doubt you could insert your own code in there if you patched the entire plane to look at it instead of the aerosoft code, but then you'd have to write an awful lot of the system yourself anyway. You'll love how it actually works... as far as I remember any code a third party uses has to drive the MSFS built-in autopilot rather than taking direct control of the aircraft. I could be misremembering that but I'm pretty sure that's how it works.
An autopilot is an autopilot, a FMS is a FMS, they all do the same job inn the end with differeint front-ends, so reusing CRJ code for an Airbus or anything else is quite possible.
-
I'm quite interested if SU10 did anything about jet engine responsiveness... Justflight have complained about that issue too.
-
On 9/17/2022 at 4:36 PM, Tomcat_22 said:
The CRJ series has been been out for months and sadly there has been no talk of a fix, I believe the best I read was ''we'll look into it'' then nothing again.
At this point I'm hoping a modder or modding group and sort this out as it seems Aerosoft isn't capable of fixing it, whatever that may cause it.
It's a pity tho, I love flying the CRJ but it just sucks that the LNAV is so bad usually, when it works it's great tho but that's seldom
This isn't the sort of thing a modder can fix unless they somehow decompile a bunch of code libs ( and if they did, they wouldn't dare say anything because that's well outside even generous T&C ). If Aerrosoft are reusing some code for a future project like the Airbus then it needs fixing anyway.
-
2
-
-
16 hours ago, CRJay said:
No clue, I have never started a RL flight that way. You always know the runway for departure, and if you know it, why would you not put it in?
I don't know how you'd end up in that situation - my own training & various jobs make me consider these sorts of ambiguities, so I ask just in case.
-
You're doing 140kts, that is a long way below a decent climb speed ( about half! ).
-
3
-
-
Related question for the CRJ pilots, what does the LEGS page look like before departure if you haven't put an originating runway in yet? if you've ever managed to be in that situation. In the model the active WP ( at the gate ) is the first WP, but there's no blue leg origin entry. As soon as you add a runway, that enters as the leg origin. I suspect if you take off without the runway entry the FMS will start sequencing & decide the head of the legs page ( which I assume is literally just listing the internal WP list ) is the origin. Sanity wise it does feel like the aircraft should take it's location at weight off wheels ( plus enough seconds to be sure ) & compare that to the first leg entry to see what it should sequence, but no idea what it actually does.
-
I have to admit to copying later waypoints over the current one to cut out bits of the FP in the legs page ( in both the CRJ and the 146, which is the only other thing with a FMS I fly ), but I've never done that with the current one itself. Deliberately going direct to the current waypoint is a confusing idea
if the aircraft isn't going to the active waypoint then there's something a bit wrong with either the nav system or the display - and in this case I think the displays do get a bit confused at times, cf my initial WP in the FPL changing all by itself. I still think the root cause is my departure runway not getting entered but the ambiguous state that leaves the FMS in is not good.
-
On 8/20/2022 at 12:11 AM, Chuck Adams said:
and when you get the CRJ pointed toward waypoint1 (but not on the route line on the map), got to the legs page, put waypoint1 in scratchpad and try to re-enter it as the active waypoint.
We were asking why you are doing this - you are saying "copy waypoint1 over waypoint1 to make it active", which makes absolutely no sense. In my last flight on your route I took off & flew in HDG to gain altitude for a while, not pointing at the current WP - the current WP started as FUSCO & stayed FUSCO no matter what mode I had the aircraft in, until I reached it.
The *previous* flight had problems - I'm pretty sure because the runway entry didn't stick for whatever reason ( probably me not checking properly ) and the FMS chose FUSCO as the originating waypoint & then got partly confused. I fixed that by putting FUSCO in via DIR INTC page, not by playing with the legs page.
-
1
-
-
13 minutes ago, Tomcat_22 said:
Not easy to reproduce... it's been happen on almost every flight since the CRJ was released, fly into LSZH coming from the north in a north to south wind (so you have to fly past the airport, do a ''U-Turn'' to land on either RWY32 or 34. You'll see it struggle with VNAV
This is about LNAV though, and even for me who's had problems since the start ( a rig upgrade ago ) LNAV issues are inconsistent.
-
Oops, think I found out what *I* did at least - originating runway didn't get entered somehow, so the FMS didn't generate an originating WP. What does the real one do? either way might need a basic sanity check there. If I were writing a FMS I'd probably default the initial waypoint to the aircraft's position when the first leg is created, but I don't write FMS, thankfully!
Second go at the flight is going properly. Didn't need to do anything special, just gained some altitude on runway heading & put it in NAV. Need to try that somewhere with a closer first waypoint sometime.
-
Ooh boy yes, some systems are getting awfully confused - progress page thinks it's on FUSCO-JCT, hud WP target is JCT, aircraft.. .steering somewhere. DCT INTC & entering FUSCO did actually point the plane at FUSCO, but the hud target didn't change ( is it meant to? ). Reaching FUSCO sent the a/c towards JCT, and reaching JCT has sequenced the hud to LEJON, so functionally it seems ok.
Don't think you can copy a waypoint over itself, which seems to be what you were trying to do ( I mean, why would you ). You can copy later WPs over the current one.
Edit: took another look at the FPLN page, first WP is now DCT JCT, when I did enter DCT FUSCO & it was originally showing that.
How do you clear error this from the FMS?
in Systems
Posted
Pull the speedbrake handle up a bit to make sure it's not grabbing the mouse click for CLR...