Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

13 Good

About JerryJet

  • Rank
    Flight Student - Solo

Recent Profile Visitors

1170 profile views
  1. Product.cfg in E:\AddonXML\Aerosoft\Aerosoft CRJ ProfessionalAerosoft\Aerosoft [Installer] ProductCode= ProductName=Aerosoft CRJ Professional Version= ProductPage=http://www.aerosoft.com ManualName=Manual.pdf ReadmeName=Readme.txt Product.cfg in E:\AddonXML\Aerosoft\Aerosoft CRJ Professional\Data [Installer] ProductCode=90001 ProductName=CRJ 700/900/1000 Professional Version= ProductPage=http://www.aerosoft.com ManualName=*.PDF ReadmeName=Readme.txt ______________________________________________________________ I guess it depends on where you look and which you choose to believe.
  2. Ditto. I only downloaded the V4 zip file. You guys sure the V4 zip archive is really V4? I can find no way to figure out if I have the correct version. Product.cfg says I believe so that's no help. I'll try a reinstall. Yes, AV was off while installing as Administrator.
  3. In my case it was default items (on the MFD map) and using the scrollwheel on the mouse to change the range which caused the CTD. Everything on the mouse, keyboard and yoke is handled by P3D, nothing by FSUIPC or another program.
  4. Poor Stefan. It will be a month before he finds out he was thrown under the bus.
  5. Please, can we wait until the topic is really answered before the Deputies say it is, and then lock the thread???? As of this writing date there's still a problem with the A320-321 family in the v1.2.1.0 release. I believe that's the latest official release, not experimental. Thanks for looking into this.
  6. Same thing with the A320 IAE stock United livery using the experimental v1.2.1.3.. Rolled back to v1.2.1.0 and the problem goes away. V1.2.1.3 lets you choose KG or LBS. I switched to LBS and can't help but wonder if the non-Boeing FMS is seeing the weights as KG, not LBS. ??
  7. Knob, using the mouse wheel to rotate it.
  8. Just happened to me in the A321 IAE, version Was just coming out of 4X time acceleration before the TOD into KJAC. Worked in previous versions without shutting everything off so I don't know why this new version wants to complain. Did not realize the systems might come back on after a few minutes as I closed P3Dv4.3 after confirming all the electronics were indeed not working.
  9. I needed to add: model=EXTIAE in the "aircraft.cfg" to get the plane to display properly
  10. ?? All the views are zoomable in the A319 but not in the A321 so I don't understand your answer. I haven't looked at the A318 or the A320 yet so cannot comment on those. I guess this is an "odd" day, pun intended.
  11. A321 v (Installer version), P3Dv4.3, Win10-64 Using the preselected cockpit views I am unable to zoom in or out in the OVERHEAD, LOWER OVERHEAD, ECAM and PEDESTAL views. Other views zoom in and out as you would expect. Anyone else notice this?
  12. I've spent the last week doing a complete reinstall. New NET Frameworks and C++ Redistributibles. Fresh install of P3Dv4.3, FSUIPC v5.14, ASCRJ v1.2.0.0 updated to v1.2.2.0, TrackIR5 and CH yoke. Everything newly downloaded, only place I cheated was the "standard.xml" with the button and switch mappings for the CH yoke. No other aircraft, scenery, uttilities installed. KCHA Rwy02 HCH VXV HOSEM KTRI(ILS05) completed with the FD and AP working properly. Right turn after crossing HCH was better, but still awkward and uncoordinated. ILS guidance wasn't and has never been an issue. KORF Rwy23 - KCLT Rwy36C. Fair weather, daytime, no ATIS, FL260. No waypoints, leave KORF and immediately get on STAR CHSLY3.COUPN to ILS36C. Same issues as in previous flight. As soon as KRISS becomes the active waypoint the AP goes berserk. PFD course indicator turns into an ADF and becomes impossible to track towards. Hand flew to intercept ILS36C and engaged the AP. Plane intercepted the LOC and followed GS to runway. Installed some planes. Same route in Aerosoft Airbus A319 - no problems. Same route in Flight1 Mustang v2 (brand new) - no problems The only thing this re-installation has shown me is how incredibly easy it is to re-install planes, airports and other packages using the "addon.xml" method. Other than that ...
  13. The real interesting story here is that I don't have a problem with the A319 Pro. Don't think I've ever flown the A318 yet but the A319 ... no problem. Well maybe the checklist occasionally gets hung up during the Start Pushback, but navigation is not an issue. FD and AP are not giving erroneous prompts or readings. It flies from here to there following a flightplan, altitude, speed. So according to your definition of not having issues my computer must be OK. I'll not call it 100% cuz statements like that have a tendency to come back and bite you. CRJ is a different story. Just because you're "unable to understand" my issue does not mean the onus for support is on me. If I was having problems with other aircraft, scenery, or P3D itself I'd be the first to consider a reinstall. But I'm not. If I stay away from the CRJ I don't give myself headaches and actually enjoy flight simming.
  14. Yikes! It's the Aerosoft 319, part of the Professional series. I bought all four of the planes but only the 318 and 319 have been released. Sorry about the confusion. As far as the FPS goes I use P3D to limit the FPS to 30. When I do fly with any Shift-Z info showing I'm pretty consistent in the 27.x - 30 range. Sim is smooth with only an occasional pause as I approach some 3rd party airport scenery (Flightbeam KMSP). And when I fly/test the CRJ I keep things to a minimum. P3D, TrackIR5 and CH yoke. Fair weather during the day. Vanilla. Thought I was onto something yesterday when I realized I was completely overlooking FSUIPC. I have a registered version but only use it to calibrate the CH yoke axes and nothing else. Any fsuipc.ini file created has default values except for the yoke calibration section. Let FSUIPC make a new .ini file and compared to the old one. New .ini file had two things not listed in the old one, both in the [General] section. RestoreSimcWindows=No Console=No Makes no sense to me but maybe to someone else. CRJ v1.2.2.0. Flew the KCHA HCH VXV KTRI flightplan including the ILS05 approach perfectly. Turn from HCH to VXV was still uncoordinated and awkward but the AP got the job done. LOC and GS worked but I've never had a problem with them. Before I got excited I tried another flightplan: KORF Rwy23 - KCLT Rwy18C. Fair weather, daytime, no ATIS, FL260. No waypoints, leave KORF and immediately get on STAR CHSLY3.COUPN to ILS18C via JEDKO. Lots and lots of waypoints. I ignored the altitude and speed restrictions and did a constant descent from TOD to JEDKO @ 8000ft. CRJ flew things correctly until KRISS became active leg and it continued to fly straight ahead. I disconnected the AP and turned to intercept the flightplan but the flight path on the PFD kept turning ahead of me. It was like the PFD turned into an automatic direction finder that kept pointing to the KRISS waypoint location. I was not able to intercept and did a Dir To JEDKO. Intercepted the LOC and landed. 18C doesn't have a GS. Flew that same flightplan today under the same conditions with the same result. As soon as KRISS becomes active the AP goes spastic. Going to try this with the v1.2.2.1 ascrj.dll but I am not confident that will matter.
  • Create New...