amahran

Sorry, should have mentioned this was all being done on Ground Power. Netflix is a bad habit when flying, but you get the idea lol

When flying the CRJ online, I typically set the aircraft up from cold and dark, and work my way up on ground power up to just before starting the APU. Usually, the full flow, and sitting around at home and texting on facebook, watching netflix, etc., usually takes about half an hour to an hour before I start my APU. In this timeframe, I tend to notice that, at some point around the half-hour mark, the radio I had tuned to a controller frequency just dies out. I can't receive or transmit on this frequency. There are no visible system changes in the CRJ when that happens. This persists until I start the APU. Once the APU is online, the radio comes back to life. I don't observe any visible system changes. This was done with FSX, on VATSIM, with vPilot, with the latest update for the CRJ as of today. I don't observe the same behavior with other addon aircraft.

When zoomed out from far enough away, the nav lights have this weird static-y looking square around them: When zoomed back in, the ground illumination seems normal: This is with the latest CRJ update. Never noticed it before then.

When transitioning from SPD climb to capturing the cruising altitude at FL370-FL390 (the altitudes I tried this at), the CRJ's would seemingly level off 200' below, descend at 300fpm, then climb at 300fpm, and it'll keep doing that until I intervene. The displayed Autopilot Mode Annunciation is "ALT CAP" until I intervene and select V/S. After intervening, the altitude capture goes normally. This only happens with relatively high cruising flight levels. I haven't observed the same behavior at lower altitudes (10,000-FL250).

I've tried to conduct the fuel feed checkvalve test as described in the tutorial manual: I would perform the test exactly as described with only engine #2 running, but both fuel pump "ON" lights remain illuminated, and no message appears on the CAS. No change in behavior or indication is observed on the EICAS Fuel page. This is with the latest experimental update, CRJ 700&900, on an FSX Steam Installation (stand-alone, not dual install).

I was in cruise and stable when I was zooming out on the MFD to see what the route looked like up ahead. And that's when the CRJ crashed. Attached are the minidump files. Not sure why there are two, but their timestamps are both when the crash happened... fsx_62615_crash_2018_12_16T21_23_24C1.mdmp fsx_62615_crash_2018_12_16T21_22_51C0.mdmp EDIT: If it helps pin it down, the route I put down on the FMS was KATL to KTLH via BANNG2 LUCKK SZW. Nothing after SZW. Cruising altitude was set in the FMS as well.

Damn what Airbus models are those? Never seen them before

Oh, just the locking and securing mechanisms, the hydraulic/pneumatic cylinders, guiding swing-arms, and the way the top of the door kinda swings down when the door is being opened and closed. I'm sure Stefan and Mathijs know what I'm talking about

Can we have a look at the doors and the mechanisms for that again? I just wanna have another look at how good-looking that entire model is.

But what percent is cargo and what percent is pax? And what about those hundreds of Amazon packages that HQ decided to stuff into your cargo hold as well to make a quick buck in freight charges? How do you know the ratio? I gotta say I like the idea, but I also like being able to individually allocate passengers and cargo.

That did it. Thanks, guys! Consider this topic closed.

Yes I can. No it's not there. Checked via the Control Panel.

Any thoughts? It's not a show stopper, but it does make the bus look a little dumb.

I escaped steam using the "Exit Steam" option (the one that shuts it down, not the one that just closes windows). I didn't verify it in Task Manager, but Steam generally behaves itself on this PC. EDIT: I completed the reinstall doing all the above, this time verifying that steam was exited while doing the uninstalls and reinstalls. Took it a step further and even verified that my anti-virus was inactive. Nonetheless, the issue persists.

Hi, I have a bit of a weird situation here. I stopped flying the Airbus series for a few months and flew the ERJ's and PMDG 737's mostly...but I came back to the A319 recently and saw this screwy font appearing on my ND: Now I tried following steps to resolve this issue, and went over details in this thread, this thread, and this thread (although I didn't follow through with modifying the panel.cfg because that's a hackjob solution that is impossible to keep track of). Finally, in a last ditch effort, I uninstalled and reinstalled the Airbus package (A318, 19, 20, and 21), following ALL the steps of the uninstall to the letter, including restarting the computer between pretty much every single step. Nonetheless, the issue persisted, so I tried to resolve the issue using this thread one last time, and there were no changes. What should I do at this point to resolve this issue? Do note that this only appears on the MAP display on the ND, I don't see this font appearing on any other displays (as shown below): Installation details: FSX-Steam Edition Windows 7-64 Bit 16GB RAM More hard drive space than necessary i7 4790k