Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

JRBarrett

members
  • Content Count

    436
  • Joined

  • Last visited

Community Reputation

177 Excellent

About JRBarrett

  • Rank
    Gliderpilot

Recent Profile Visitors

1768 profile views
  1. I don’t know enough about how engines are modeled in the sim to answer number 1, but it seems to be a common problem with any FSX/P3D aircraft that uses standard SDK engine modeling. PMDG uses a very complex custom engine model, that is probably not “do-able” in an aircraft in the CRJ’s price class. Number 2 is a perplexing bug that the developer has been trying to nail down for quite some time. It appears to be quite intermittent. I’ve had the light fail to come on, and then on the next flight, it works fine. Some users never have the problem. I know Hans would like to solve it once and for all, but the reason it happens is evidently not clear. For number 3, that is exactly how it works in the real aircraft. When either fuel boost pump switch engine is pressed, they both come on. However, it is necessary to engage both switches before engine start to avoid error messages. The pumps automatically shut off and go into standby mode once both engines are running. 4: The hydraulic pumps that are controlled by the switches are all electric, and yes, they will come on anytime the aircraft has power. The number 3A pump is energized before pushback and runs continuously until the aircraft arrives at its destination and parks at the gate. The number 1 and 2 pumps are normally set to “auto” so that they will come on in case the engine-driven pumps fail, and can be turned on before engine start (or any other time), by moving the switches to “on” Number 5: The primary flight controls being able to move without hydraulic power is indeed a bug. However, the stabilizer trim is electric, and does not need hydraulics to operate.
  2. I meant to mention this previously during testing and completely forgot. In my P3D 4.4 installation, (using the default P3D “steering set” axis) the assigned controller works no matter what position the N/W steering switch is set to.
  3. Yaw dampers and stab trim switches set to “on”? They have to be on for the autopilot to engage.
  4. It indicates that there is no nearby VOR or ILS station being received on whatever frequency is currently tuned for Nav 1.
  5. In the case of the Leonardo Maddog a noisy or mis-assigned mixture control axis could definitely cause it, because they have mapped the engine fuel control levers to the engine 1 and 2 mixture control axes.
  6. Click on the “Airspeed Limits” placard located directly above the pilot’s MFD (Nav) display.
  7. If it happens after updating the AIRAC data, the new hot fix that just came out should help:
  8. Unless you check the box for “experimental updates” in the updater, you will get version 1.2.2.0. If you do check the experimental updates box, you will get 1.2.2.1 Be advised that there is a known bug in 1.2.2.0 that will cause the pressurization system to fail in flight if you try to land or depart from a high-altitude airport like Denver. 1.2.2.1 was issued to correct that bug. Other than that, there is no difference. There is one user who has been having many problems with 1.2.2.1, but I don’t think this is happening to many other customers. I have now logged over 100 hours in 1.2.2.1, (in P3D 4.3) and have had no problems whatsoever. I don’t know if you are running FSX or P3D. Some FSX users have had issues with the aircraft or the “Dave” EFB not loading properly with the 1.2 series. I don’t know if that has been resolved. If you are running P3D V4, you must have version 4.3 to run the latest CRJ update. In any case, before updating to the 1.2 series in either FSX or P3D, (using the full installer), it is very important to fully uninstall the 1.0.0.6 version first using the Windows control panel. The uninstaller leaves one folder behind that I would recommend removing manually. It will be a folder called “Digital Aviation CRJ” found under the “Aerosoft” folder in “My Documents” Also, don’t try to use any saved flights or panel states created in 1.0.0.6. Once you run the main 1.2.0.0 installer, you will then have the Aerosoft Updater, which will allow you to do an in-place update to 1.2.2.0 or 1.2.2.1 (with experimental updates checked).
  9. I have not had occasion to enter or modify constrains very often in my flights. What appears to be happening on my system is that I cannot change, delete or otherwise modify altitude/speed constraints that appear on the legs page as part of a SID or STAR, but can successfully enter new constraints at any waypoint that does not already have one, without causing anything to shift. Jim Barrett
  10. I just tried the CHA to TRI flight. The aircraft made a nice smooth 80 degree right turn at HCH with no pauses or hesitation. This is with 1.2.2.1 Almost seems like the sim is bogging down (CPU spiking?) when it gets ready to execute a course change on Jerry’s system. I don’t know if he has monitored his frame rates at the moment the aircraft misbehaves to see if there is a bad stutter at that moment. If the FSL 319 is running smoothly for him, I’d have to assume that his overall FS system is well-optimized. Speaking of that, I’m currently battling a problem on my own system caused by an interaction between two different add-ons. I own the FSL A320 and A319, and both will CTD after exactly 1 hour in flight with an API.DLL error, but only if the SODE animated jetways process is running. If I disable SODE, the A319/320 can fly for hours with no crash. This happens even when I depart from a non-SODE enabled airport. Just an example of the multitude of unexpected software interactions that can happen on an FS computer, all of which are unique in terms of installed hardware and software.
  11. It already is. It’s considered an “experimental” build, though the only two changes AFAIK are the radar and pressurization logic improvements. If you open the Aerosoft Updater, there should be a checkbox to allow “experimental updates” as well as regular ones. If you select that, version 1.2.2.1 should them show as an available download.
  12. I have no idea why there would be inconsistent loading. I’m just an end-user like you. In in my own case, I always fully load the default Cub in the location I want to depart from with parking brake set, and the engine running. Then I select the CRJ from the aircraft menu. Whether I choose to start cold and dark or with engines running, the CRJ always loads with the parking brake set, and DAVE powered. I’m not saying there is anything “wrong” with your PC, or your operating technique - but if identical software operates one way on PC “A”, and differently on PC “B”, then something specific to the computer is causing it. I’m sure Hans would like to get to the bottom of it as much as you would.
  13. A lot probably depends on the exact state of the computer operating system, and other FS-related software that may be installed. JerryJet and I both have Win10 and P3D 4.3, but he is having bad NAV tracking with version 1.2.2.1, that isn’t happening on my system. i have the Pro edition of Win 10, which I purchased specifically for the ability to opt out of mandatory Microsoft updates. I do choose to install updates that are security related, but not drivers or other non-essential stuff. Two weeks ago, I installed the July security update, and afterwards, I started getting a silent crash on exit from P3D related to API.DLL. The only reason I knew it was happening was watching the Prepar3D.exe process in Process Explorer, which would throw a WER fault in the background long after the main P3D window had closed. Further investigation showed that it seemed to be related to the FSDT Couatl process running alongside P3D, but I’m not blaming that software because the problem only started after the Win10 update. I ran the FSDT add-on manager updater yesterday, and I’m not seeing the crash on exit anymore.
  14. I'm still puzzled as to why 1.2.2.1 would have "1.0.5-like" nav tracking issues for you, that1.2.2.0 does not. I did try your example flight plan from CVG to MDW in both 1.2.2.0 and 1.2.2.1, (on P3D 4.3) and both worked identically, and tracked the route and waypoints with no problems. I did the tests with both versions using default "clear" weather, and ASP4 real-time weather. As far as I know, the only change from 1.2.2.0 to 1.2.2.1 was to fix the bug in the pressurization system at high-altitude airports, and to make some improvements in the weather radar display. Hard to understand how that could have changed anything in the FMS or autopilot NAV tracking - but Hans would know more as to which changes were made.
  15. I always fully load a default P3D aircraft (with engines running) before loading any complex add-on, as it generally seems to result in more sim stability. One problem with doing that though is that sounds from the default aircraft can carry over to the newly loaded plane. I’ve not had the fuel pump sound carry over, but I have definitely seen audio panel settings transfer. If the VOR or DME ident is selected “on” in the default aircraft, it’s possible that the ident Morse code will be heard after the complex add-on loads, and it may not be possible to shut the ident off, even if the ident switch is turned “off” in the add-on’s audio panel. For that reason, I think it is best to choose the “simplest” default add-on for the initial load. In the case of P3D, the Piper Cub, and for FSX, the Trike. Neither aircraft uses a fuel pump, and both have very minimal avionics - just a single NAV/COM radio.
×
×
  • Create New...