We got a new video from World of Aircraft: Glider Simulator and are asking for some alpha/beta testers! Check this post.

 

Jump to content

Hanse

Deputy Sheriffs
  • Content Count

    2670
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Hanse

  1. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  2. I just interpreted your a. m. statement. Maybe I am wrong. But the delays are necessary so that you also have time to look outside and "pilot" the plane when the CL is running. In the first VIEW FOCUS version I did not implement those breaks and users complained that they were not able to steer the plane when the CL was running. Such delays are only implemented when the plane is moving and p. e. not available in the Cockpit Preparation or Parking CL. I am also always open for improvements if those are valuable and if those add a handling plus / more value for all users. But in your case e.g. your suggestion to "delete" the breaks in the CL would only annoy a lot of other users (see the a. m. argument) ....... Rolf
  3. Wolfgang, I do not agree with you. People flying "online" is according to my knowledge not the majority of the A330 users. Our intention when we implemented the CL was to "guide" the user through the various procedures and not take away some work from him. In RL a "computer" is also not doing this but the checks / settings are made by the PF and PNF while flying. The VIEW FOCUS is just a help for those who really "care" for the CL and its items / settings. But if you do not care what is going on in RL, want to do in parallel other things while the CL is running and think that the CL is just an automated settings feature, then you are right. But this is not the idea when we implemented the new version of the CL into the A330. Rolf
  4. Are you comparing the CL sequence with the one from the smaller models? In the A330 we implemented a new features VIEW FOCUS which automatically changes the view where the settings should be made. But when the plane is moving, we implemented brakes between the various CL items so that in between the pilot can look outside to see where is the plane is heading. This means there a longer brakes between some of thew CL items.
  5. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  6. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  7. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  8. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  9. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  10. Sorry but that cabincrew message / sound is not "played" anymore in the A330 (the sound file is just "silenced") because it means that the CC can just open the cockpit door by themselves and making the accouncement - which is according to the implemented safety features (door bell and opening only from inside the VC) not possible anymore.
  11. https://forum.aerosoft.com/index.php?/forum/865-voice-sets/
  12. There are no other options available. But you can create your own own one. Please have a look into the specific chapter in this forum to get more information on this.
  13. Why you guys do not search the forum before starting a new thread? Just below you entry is another one dealing with this issue:
  14. Have you also installed the A330 in P3D 4.5 on your system? I do not understand why CP does not detect the A330 in P3D v5 on your system? The only reason I see is that because both A330 version are using the same description that CP does not detect the A330 v5 version. I think I send you a detailed information and why are you not answering the questions? Just to say "I have not solved" is not the solution to the problem and does not give us the information to help you. The problem is that CP does not detect the A330 in v5! Normally CP should create a new aircraft.cfg and renames the original one. But as you have only one aircraft.cfg on your system it means that CP has not detected the A330. If you also run the A330 in v4.5 then you should copy the two files e. g. "aircraft.cfg" and "aircraft.cfg.fsfx_CP.bkp" from your 4.5 version to the v5 version. If you are not running the A330 v4.5 version on your system then it is not an Aerosoft problem and you should contact the ChasePlane support......
  15. Regarding the "Aerosoft Airbus A330 Pro V5" and "ChasePlane" there are few important things: ChasePlane should automatically detect that there is a new "aircraft.cfg" file (for the V5 version of the A330) - not already altered by ChasePlane . If yes it will automatically change this file and make a backup of the original file. Those two files you find in xxxxxx\Aerosoft A330 Pro V5\SimObjects\Airplanes\Aerosoft A333 RR Professional\ folder e. g. "aircraft.cfg" and "aircraft.cfg.fsfx_CP.bkp" If you are also running 4.5. sometimes CP does not detect the new v5 version of the A330 because of identical names. Then please copy those two files from your 4.5 version "Aerososft A333 RR Professional" to the v5 version of the "Aerosoft A333 RR Professional" and overwrite the existing "aircraft.cfg". If you start the A330 v5 the first time there will be a view conflict because automatically also the internal MCDU3 ViewSystem is enabled. Please set this in the OPTIONS / VIEWS menu to OFF and close P3D v5 as well as ChasePlane. Then start P3D v5, ChasePlane and the A330 v5 again and everything should be OK.
  16. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  17. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  18. Please have look into the following topic because this might solve your problem:
  19. I think I now know what causes that behaviour. It is related to the ECAM RECALL check - the next one after the APU FIRE TEST. For this test it is necessary that the Displays-Selftest is finished (app. after 40 seconds) and the standards are displayed. To me it seems that after the C&D aircraft state has been loaded you are immediately starting the Cockpit Preparation CL. Normally before starting the CL the EXT PWR is set to ON, then the 3 batteries are set off and the NAV & LOGO as well as the STROBE light are set to AUTO = 1. Make sure that the displays selftest has been finished and then start the CL. I strongly advise to follow SOP and as well care for the CL - do not do something different when it is running - and maybe also use ViewFocus. Then you would have realized that when the ECAM lower screen is in selftest that the ECAM Recall check cannot be performed.
  20. Please then tell me exactly what happens: Do you thear the PnF call "APU Fire Test"? Do you hear and see that the test is performed e.g. is the light blinking and do you hear the bell? Do you hear after that the call "Checked"?
  21. If you search the forum you will find another thread regarding the same issue. Are you also using FSCrew or any of their products? Until now we do not know why but if FSCrew is used there is a 40 sec break after the APU fire test. In this case please contact their support....... Regards, Rolf
  22. But anyway the MCDU was not completely set up because I see on the PFD 100 as target speed and that menas to me the MCDU PERF DATA are still missing. OK but let us stop this discussion. Are you able to reproduce the issue you mentioned? Does this happen every time or did it just happen once? In the first case I need much more information (or a video would be the best) so that I am also able to reproduce it. If I cannot reproduce it I cannot help. Sorry!
  23. Looking at the provided screenshot I see that there is no F-PLAN loaded as well as the MCDU not completely setup. Normally this should have no influence on the CL but to me it means that you did not follow the normal SOP to get to this point e. g. TAXI. Another point I do not understand is why after manually loading the aircraft state TAXI in the MCDU3 CL menu the TAXI CL is not displayed in "orange", Please see the screenshot attached how it should look like....... To me it seems that there is something wrong with your installtion.......!
  24. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  25. Sorry but I just tried to reproduce the issue you mentioned e.g. that using the A320-A321 after a turnaround there are problems in connection with starting the BEFORE ENGINE START CL. I cannot confirm it e. g. on my system it worked without any problems. The procedure I used is as follows: After arriving at the gate and the PARKING CL has been finished I completely followed the instructions on the INFOBAR and also waited until after 4 minutes the plane status was automatically completely reset. I connected using GSX the jetway / stairs Then I started (using GSX) to board pax, cargo as well as fuel. During this process I already started the COCKP PREP CL. When GSX boarding / loading was completed I used the GSX option to "Prepare for PB" Automatically the jetway was removed, doors were closed and the BEFORE ENGINE START CL started. I am out of any option to help you. If you follow the a. m. procedure it should work as intended. If not then there is something wrong on your installation - either the Airbus or GSX - .
×
×
  • Create New...