Don t moderate me this way

... or it could be that they want us to open a new thread so that aspects and opinions before and after version 1.0.1 are neatly separated ... A short explanation posted in the old threads, just before locking them, would be appreciated, though.

Excerpt, if Nuno is too lazy to read it all @Nuno Pinto: Nuuuuunooooo!!!!!

Hi Mohamed, since the development of the PMDG MD-11 has ended, I simply added 3rd party addon gauges to the panel. These work as separate 2D popups, so not integrated into the navigation display. For the weather radar I use the wx advantage radar by REX and MilViz. Oliver Märtens (Maertens)

Version 1.0.1 is now available in Aerosoft customer accounts, but maybe not quite yet from other vendors. They may still need a few more hours or, in some cases, even days to update their files: Not yet the official release statement, but: http://forum.aerosoft.com/index.php?/topic/126621-rudder/&do=findComment&comment=838792 What to expect: http://forum.aerosoft.com/index.php?/topic/126457-new-build/&do=findComment&comment=838478 EDIT: Official release statement with final changelog: http://forum.aerosoft.com/index.php?/topic/126625-crj-updated-to-101/

Quite shockingly, in the "AS can do no wrong" vs. "Why shouldn't bugs be reported once they've been spotted?" battle, Hans Hartmann and Aerosoft have teamed up with the "bug reporters" (): The misunderstanding on which the currently flawed pressurization system is based has been identified. (Identification equals chance für rectification.) And AS wants this system to be reasonably modeled just like anyone else. (Reasonably does *NOT* equal perfectly.) We also have been provided an explanation for the currently limited functions of the TCAS. (Resolution advisories have not yet been implemented because the whole TCAS had/has to be build up from scratch in 64bit because of P3Dv4 - now that is some task! Again, reasonable/plausible advisories are welcome, *NO* 1:1 implementation of the real thing would be feasible or required ... or affordable.) In conclusion, there isn't really much of a difference between how Hans Hartmann/Aerosoft would like to have their product and what "bug reporters" would like to see corrected and/or implemented.

A looong changelog emphasizing "all the lateral stuff": http://forum.aerosoft.com/index.php?/topic/126457-new-build/&do=findComment&comment=838478 Time-to-go (my own uneducated guess only): 48 hours or more.

Aerosoft controller: "CR7/9, you can have delay vectors or holding instructions, what's your choice?" CRJ driver: "OK, we'll take the pattern then." http://forum.aerosoft.com/index.php?/topic/126457-new-build/&do=findComment&comment=838443 EDIT: Hans' reasoning for the intentional delay actually makes a lot of sense to me.

Aerosoft are aiming at a new full installer release (including latest hotfixes) for tomorrow. 3rd party vendors will need a couple of additional hours (or even days) to make it available in their stores. Keeping my fingers crossed for a (L)NAV fix, most of all. http://forum.aerosoft.com/index.php?/topic/126532-i-might-be-stupid-but/&do=findComment&comment=838238

M8, mid-level is what I've been saying and mid-level bugs are what I've been reporting. The things you quoted have been working in mid-level aircraft like the ... feelThere ERJ v2 (40 USD) AS A32x (50 USD) F1 ATR 72-500 (45 USD) F1 Fokker 70/100 (50 USD) and many more FYI, the AS CRJ 700/900 is 60 USD.

Confirmation bias. In the CRJ, some systems do work in a weird way. (Arming thrust reversers? Seriously???) FCOMs are always imprecise one way or the other, but RW CRJ manuals are even worse. Guess, Aerosoft peeps expected the CRJ pressurization system to be ... exotic as well, so they implemented a documented manual mode as an assumed automatic one. It could have been sooo much easier, folks ...

It's getting slightly absurd (just slightly ): http://forum.aerosoft.com/index.php?/topic/126270-pressurization-systemdescent-mode/&do=findComment&comment=837968 "Strange as it sounds, we also do not know if this is a bug. We got tables that are exactly as it is now implemented, but we agree, it is damned weird and we'll try to find more information and might redo that system."

Not extremely broken and unflyable, IMO, but - again, IMO only - it should not have been released with those obvious (L)NAV issues. As someone on the fence I'd wait a week or so to see how current users get along with the hotfixes/update to be released after the weekend. After that there are still some systems where corners seem to habe been cut for an (too?) early release.(*) Those few systems deserve a comprehensive servicepack (within weeks or a very few months, maybe) to bring them up to the standard the CRJ is aiming at and Hans Hartmann has earned his reputation for. (*) Too early after seven years of development? Well, it has been a single dev/part time system development with some setbacks in between. So it's not exactly seven years like we would normally perceive that time span. All that's required are a few more months in systems refining, testing, and debugging, and then this discussion should come to a positive(!) end.

If not, the PMDG MD-11 manuals are freely available from their website, including two tutorials and a few conversion notes for Boeing people (in their intro doc). Those may help, especially since the TFDi documentation is very ... sparse. Also, somewhere in the TFDi forum there's a link buried that leads to a more comprehensive B717 documentation. A quick search over there should bring it up.

Aerosoft have just announced some hotfixes for the CRJ which might(!) be released next week. If they make a new full installer it will take a few more days until it's available from other vendors' sites. I'm hoping it will be "more flyable" then, but even then some systems should receive a more comprehensive servicepack to bring them up to the standard the CRJ is aiming for. With the B717, unfortunately I've been experiencing short pauses (about one per second). I tried their full public release and after that opted into their beta program, and tried most of the fixes discussed at the TFDi forum, but currently I cannot really fly the B717. It looks, though, as this may be a local problem with my system and/or some of my addons do not play nicely with the B717. Overall, the B717 currently seems way more mature than the CRJ (which obviously was released only some three weeks ago, so ...).

Also, the AS CRJ is 25% more expensive than the AS Airbus. Without the virtual F/O from the Airbus and without deeper system modeling, how would AS explain the price increase? Still, my expectation is "mid-level with a plus", not study level sim. The potential is there, but some CRJ systems need to catch up (... with the release date, LOL!)

No mirroring in the CRJ, the two sides are independent. You could activate all pop-up displays (both sides) at the same time, and even opt for continuing display rendering in the VC despite the active popups. (Default is, with popups active, the VC displays are off.) There's also an option to switch off the offside displays in the VC. I have no issues undocking the popups, dragging them to a 2nd screen and resizing them. Now, let's get rid of the (L)NAV issues, give me the rest of the system details (medium-depth only is requested) in a SP and I'll be a happy camper ...

Actually ... yes: http://forum.aerosoft.com/index.php?/topic/126156-further-systems-refinement-frank-do-not-read-this/ http://forum.aerosoft.com/index.php?/topic/126270-pressurization-systemdescent-mode/ http://forum.aerosoft.com/index.php?/topic/126382-more-on-tcas-tas-and-ras-missing/ http://forum.aerosoft.com/index.php?/topic/126320-fake-tcas-relabs-selection/ http://forum.aerosoft.com/index.php?/topic/126220-the-final-word-on-maximum-wx-radar-tilt/

After discovering a flawed pressurization logic (any RW pilot would notice that during his first CRJ flight), an only rudimentary implementation of TCAS (the dev must know), the wx radar being off in gain and tilt (easy to notice, even for someone who's new to testing), and the various (L)NAV and CTD issues (project manager, where did the release decision come from?), I ended up hangaring the plane until a comprehensive servicepack has been released.

My thoughts are with those victims, too, and I am sure you posted this with the best of intentions, Anders. What keeps irritating me is why we never see these topics on AVSIM and elsewhere when those kinds of attacks take place in countries like Afghanistan, Iran and Iraq? (Or Russia, for example.) People in those countries suffer from terroristic attacks more frequently (and often more badly) than we, "the Western world", do ... and all people are created equal, is that correct?

Their Mega Airport Frankfurt V2.0 professional - P3D V4 only - now is 35 EUR including German VAT (19%): http://www.aerosoft.com/en/fsxp3d/prepar3d/sceneries/2152/mega-airport-frankfurt-v2.0-professional Last Mega Airport I bought for FSX was 25 EUR - included my VAT as well. 40% increase in price!

Aerosoft has the right to ask for your money, but it's your prerogative to deny it. (Like in "Vote with your wallet.")

Definitely in my OC, just checked. (DC-6 installed in FSX-SE.) Did you select the DC-6 in the OC? Oliver Märtens (Maertens)

Looks like Hans had a bad day yesterday, but today he's in much better shape again. Still it seems that Aerosoft released this CRJ two months earlier than Hans could ever get it ready for release ... ;-) Pretty sure it will look much more convincing in a couple of weeks.

That's because he's a simmer like me. IRL you'd probably get pitch oscillations (at least that is what I was told), so you'd want to avoid speed on elevators for the descent. Instead, in V/S mode the pitch changes get converted into speed changes, but flying within a narrow speed window should be OK under most circumstances. Must say, though, speed mode works pretty nicely in the sim - virtual passengers don't complain, so ... why not there?

+1: I'm a consumer, so P3D licences are no option for me.