Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

22 Excellent

About Aplato

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. POSCON requires you to monitor the guard frequency (121.5) on COM2 at all times. I'm able to hear other people on there, but haven't been able to get my own messages to transmit. As you can see in the screenshot below, I even set both sides of the pedestal to transmit on VHF2, though I don't think that's necessary. However, when I press my push-to-talk button, POSCON is always detecting COM1. It's not because I have the same frequency in both for testing either as the behavior is the same if I change one of them. I did find this topic asking the same question from mid-
  2. Just to add to this, yesterday I experienced another oddity with this screen. It's possible that it was for TOC rather than TOD (though I think it was TOD), and unfortunately I didn't grab a screenshot, but it showed fuel as 0 for that point even though everything before and after it had seemingly correct amounts.
  3. Just to add to this question, I know Airbus allows you to enter custom waypoints in a format like "FIXBRG/DST", such as : MERIT270/15. I'm not sure if this is a thing in a real CRJ or if it's modeled in the Aerosoft version, but if it is I'd be interested to know how it's done.
  4. Nope, I do not. The only thing I can think of is it's possible I clicked B to automatically set the altimeter while I was scrolling, but I'm not sure about that and haven't been able to reproduce this by performing that step. It seems like it should be easy enough to add a check for a non-100 multiple though and round up or down to prevent this.
  5. I clicked on the MFD DATA button on the FMS to see where my top of descent is, but it's not on the first page (notice the 1/4 on the window. I wasn't able to figure out how to move to the next page (using next/previous page or the arrow buttons on the FMS had no effect). Anyone know how to do this?
  6. I'm not sure about the speed issue, but I can comment on two of the others: There is a bug with either the aircraft or the sim that causes you to click the button to load fuel based on your settings twice. Whenever I do that at least I notice the cross-hairs move to the correct location. I'm not sure exactly what happens if you only click it once but I don't believe it's the correct behavior. The S-turns is a commonly reported issue that the Aerosoft team is already reviewing. As for the speed, do you recall if you clicked escape to load the menu at any point during your f
  7. The FMC excludes airports that don't have any runways that meet the CRJ's operating requirements (I believe I've read 4500 ft. but don't hold me to that. BGSS' lone runway is much shorter than that.
  8. I've seen this happen on a number of my flights. My route is KBOS PATSS5 PATSS NELIE VALRE HAARP3 KLGA, and I entered a crossing restriction of 8000 for BAYSE. Earlier in the flight, it showed my ETA for TOD as 3:08 which seems pretty accurate, but at some point it jumped to be after (3:14) the ETA for the following waypoint (3:11) which should be impossible.
  9. I'm not 100% sure how I managed to do this, but I suspect it was probably when a slight movement of the aircraft while turning the knob with my mouse wheel caused me to zoom in. I somehow got my altitude selector to 16002 ft., and to my knowledge it should only be possible to select a multiple of 100. The only way to fix this was to go back down to 0 and then up to 16000 again. I would imagine it should be pretty easy to add a check to this on any altitude setting change and round to the nearest 100.
  10. Excellent, thank you for the clarification. I'm optimistic this will be addressed in the next patch which will hopefully help me control my speeds better as that's been a struggle so far.
  11. I just want to make sure I'm understanding how this is supposed to work. N1 is basically just the percentage of maximum thrust, correct? I haven't seen any wild swings, but I notice that if I'm slightly above or below my targeted speed and make a small correction to try to fix it, the response doesn't seem to be linear. For example, if I'm at 70% N1 and move my throttle up slightly, it will often fluctuate down a bit instead to around 67% and then I will have to move it further forward to actually increase thrust. I assume this is not the correct behavior but please let me know if I'm wrong.
  12. I would love for one of the Aerosoft developers to take a look at this. It seems like this could be the reason that changes in the aircraft do not trigger Mode C on vPilot.
  13. @JRBarrett Excellent, thank you. Very minor, but probably a quick thing to fix too.
  14. It's possible this is not an issue and is instead a lack of understanding on my part, but this seems weird to me. I entered M37 for my climb wind on PERF INIT 2/3 and wanted to copy that to the cruise wind. However, when I click the button on the right of the top line, instead of copying M37 into the scratchpad, it copies 1/37 instead.
  • Create New...