amahran

RESOLVED: Went to the FSX/Fonts older and right clicked glassga, and installed the font. Restarted my computer. Would recommend this method to anyone that has this issue with the ND. You can mark this as closed now.

Bumping this, any thoughts? I recently formatted my boot drive and lost all my data, so I reinstalled FSX:SE , and installed the Airbus's as recommended: Restart the computer Don't start steam (for FSX:SE) (for this part, I stopped all background programs from running) Run the installer Restart your computer And this is what I have on my ND now. I don't know how to resolve this; it seems like a font pack is missing. If you know what font it is, would it be possible to just give me the font file so I can manually install it myself? I know how to do so... EDIT: This is for Windows 10

I recently upgraded my OS from Windows 7 64bit to Windows 10, and now I have the fonts on the ND appearing as shown: All are normal except for some ND text. Last time I had funky ND fonts, I was asked to make sure that glassga.ttf is installed. However, this time, it is. Does anyone have any thoughts as to which font is missing, or what the problem is? I could reinstall the bus, but that's a last resort I want to avoid unless there's no other clear fix.

Bumping this old thread, I'm finding the same issue: A plane shown on the TCAS in the format on the left is twice as close as it actually is. The display scale for traffic on the left is incorrect and should be corrected.

Sure, hit me up™!

I don't think so in the case I'm seeing, the problem I have is that the cabin alt doesn't climb (i.e., cabin altitude remains at 0 feet, and the delta P keeps rising). I haven't been able to recreate it yet.

This sums up my experience with the pressurization issues as well. It's difficult to document into a condensed step-by-step list because it's such an inconsistent and non-repeatable problem. I'm trying to see if it has to do with cycling the packs or Bleed Air switch on the ground, maybe that's confusing the ECS system?

I want to add that the ECS diagnostic page shows the packs to be on, even though the cabin altitude doesn't change. In my case, after take-off, the cabin altitude remains at the airport altitude and doesn't climb to 8000', and in my case I leave the packs on "AUTO" after engine shutdown through preflight, pre-start, after start, and take-off. I think michale's is the opposite, that the cabin isn't pressurizing.

When moving the yoke and almost immediately pressing the A/P disconnect button (quarter-second delay, possibly less), the CRJ's sounds almost entirely stop. The only way to get the sound to return is to cycle the autopilot on and off to get the A/P disconnect sound to play again. Moving the yoke disconnects the autopilot, and my autopilot disconnect button is on my joystick, so the sloppy button push is how I discovered this issue.

1) Which cabin rate is actually valid, 200 or 300 fpm?: 2) Emergency depress is very ineffective. 3) When cabin rate manual is selected, the manual controls don't seem to do anything. 4) Doors open doesn't immediately depressurize the aircraft 5) There's no master warning for when the aircraft is over-underpressurized (i.e., delta P falls below -0.5 PSID) 6) EXTRA: This mess happened in the left primary display. I'm not sure what it's actually supposed to look like, but I think the text isn't supposed to overlap like that:

That's true if the discontinuity is in the middle of the route... ...but then how do you eliminate this discontinuity if it has nothing after it? Then to the DEP/ARR page to select the KAYLN1 departure off 04R: Hit execute, then to the legs page: You can't delete the discontinuity, you can't put anything in front of it, you can't put anything in it, and like I said at the start of the topic, if you try hard enough to eliminate it on the LEGS page, you crash the sim. I know you're trying to be helpful by telling me how it's supposed to be done, but I don't need help in figuring out how to make the flightplan in the MCDU, I'm trying to raise awareness of the fact that there's a trailing discontinuity, and that it's possible to CTD the sim.

64 bit simulators. Hands down. It's such a simple change, but opened up possibility for lots of innovative features that would have otherwise been memory-prohibitive.

Then how do you eliminate that trailing discontinuity? That's what I'm talking about, an attempt to delete the discontinuity in the legs page breaks the legs page. If you try to fix the damage by deleting the elements, it breaks the simulator and causes a CTD. And I know it's the wrong way to do things, I'm bringing up two topics here: 1) There's a trailing discontinuity that can't be erased 2) It's possible to CTD the sim very easily. EDIT: To clarify, I thought this was an experimental update. It's not, I also have 1.2.3.0 installed.

When filing a flight (in this example, KDTW to KBUF) into the FMS, I would go through the following sequence: Enter origin, destination, alternate, and flight number Go to the DEP/ARR page and select the appropriate departure and runway Go back to the route page (NOTE: At this point, the route will show the departure procedure and transition, but the next line will be a discontinuity) Enter the next waypoint (DKK) into the discontinuity line (NOTE: The discontinuity will just move to the next line This time, I decided to try something different to get rid of the discontinuity line: Go to the LEGS page Copy the "DKK" line and paste it into the discontinuity (didn't work) Paste it ahead of the discontinuity (NOTE: At this point, the original DKK line disappeared and is replaced with DIRECT) After the above, I tried entering DKK into the blank DIRECT line that was created, which made the direct line disappear. Tried it again, and the sim crashed. If needed, I could recreate it. Obviously won't try again unless specifically asked to... This is FSX, with the experimental update as of today. Attached are the error dump files from the above. fsx_62615_crash_2019_4_19T15_53_58C0.mdmp fsx_62615_crash_2019_4_19T15_54_33C1.mdmp

What's the APU fuel burn modeled to be? It seems awfully high, I'm estimating around 600-800 lbs/hr, but that seems unreasonably high, even for large jetliners.