Jump to content

Greg Goodavish

Members
  • Posts

    45
  • Joined

  • Last visited

About Greg Goodavish

Recent Profile Visitors

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

Greg Goodavish's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. How do I get access to the aircraft.cfg folder, since I want to manually add a livery. It said access to that folder is denied when I make the changes and try to save. Can someone help? I am using Windows 10 with P3DV4.5
  2. I tried manual install, but aerosoft has the aircraft.cfg file locked so you can't add the entries for the new livery.
  3. I made the change in the captain's FMS, but did not press the EXE button. See my post directly above this one, however, for continued weirdness.
  4. I have the livery installer for the Aerosoft CRJ Pro. I downloaded a livery from your forums for the Northwest livery for the CRJ900. I followed your .pdf file instructions to make it so the livery installer would install it. It will not do it. I have attached the file. :Please let me know what I am doing wrong. Aerosoft_CRJ9_NWAAirlink_N901XJ.zip
  5. OK, pressing the EXE button helped. However, the ND display still does some strange things. Instead of drawing a direct DIRECT TO line to the next waypoint, it draws another line to some unknown point, and then the DIRECT TO wappoint. However, the aircraft does go directly to the DIRECT TO waypoint. Very strange. It never did this before the latest update.
  6. ever since the latest update to the CRJ Pro, the Direct To function in the FMS does not work right. When I click to the Direct Int button, and then click the left LSK next to the waypoint I want to go direct to, nothing happens. I get a "Xside Edit in Progress" message in the scratchpad in yellow, but that is it. It does not change to where I can go direct. For instance, I flew out of CYQM, off runway 24. After takeoff, you are supposed to go direct to waypoint BEMEK. In the FMS, after the runway, there is a VECT entry and then BEMEK is after that. After trying to go direct to BEMEK, the VECT entry remains lit up in magenta, and BEMEK stays in its original spot after that. Other than the XSIDE Edit in Progress, nothing changes, and I cannot go direct BEMEK. Help!
  7. Ok, did another flight and it worked as it should. Looks like all is well.
  8. That is exactly what I did on my previous flights, and it did not work as I described. On my last flight, I pressed the VS adjustment knob as an experiment, and then the altitude adjustment knob, and then the aircraft worked as it should, as described. I will experiment further and report back.
  9. OK, I flew another flight tonight from CYYZ to CYUL. About ten miles from TOD, I pressed the vertical speed button once, and got the VS ____ display. I then pulled it, and then pressed the Alt select button. This time, the white dot for managed descent came on, and the green dot to the left of the speed tape on the PFD was now there. It performed a managed descent admirably. I will continue some flights to see if I can reproduce this again, and will report back.
  10. OK, my pics are below. This was a flight from KORD to KMSP. ATC lowered me to FL340 at ROBBY. I was at FL360. I changed the flight level in the MCDU and with the altitude knob, and started the descent about 10 miles before the TOD cue, by pressing the Altitude knob, which should arm the descent in managed mode, with a white dot in the altitude disply. It did not. It just showed a display to the right for a VS mode, instead of a dot. To get it to descend in managed mode, I had to pull the altitude knob with a right click, but it still did not put the right dot in the altitude display showing managed mode, and did not show the green dot on the left side of the speed tape in the PFD. It did start the descent though. This is exactly opposite how that knob should work. Something is not right here. I installed this aircraft and did the update for it via the aerosoft update app.
  11. I did do that, and it worked. However, to activate it, I had to PULL the altitude knob, which is the opposite of how it should work. For managed descent, you PUSH that knob, and a white dot should appear on the altitude display. Also, a green dot should appear on the left side of the speed tape on the PFD, showing you whether you are on the vertical managed path (dot in center), or above or below it. That dot does not show up. Please advise.
  12. I seem to be having an issue in P3DV4.5 with this aircraft. When I approach the TOD, I click in on the Altitude knob, which should arm the managed descent. However, what it does is go into VS mode, requiring me to pick a VS. When I pull out on the Altitude knob, it goes into OP Desc mode and seems to somwhat follow the descent path. Also, there is no green dot on the left side of the speed tape on the PFD, which would show if I am on the descent path, above it or below it. This behavior does not seem right. Can you advise?
  13. I have a ton of Aerosoft sceneries that are labeled FSX/FSXSE/P3D. Are those sceneries compatible with P3DV4?
  14. I am trying to reinstall my Budapest airport for FSX. I noticed there is version 1.40 ( the main version), and then update version 130 and 150. Which do I need, and in what order? Does V130 get installed after 140? That doesn't seem to make sense. Please advise.
  15. Problem is now solved! For some reason, I still had version 2.04 files in my AES folder. I deleted the entire folder, and reinstalled Version 2.09, and now everything works. Sorry for the confusion on my part. Thanks.
×
×
  • Create New...