Jump to content

Hanse

Deputy Sheriffs
  • Posts

    2908
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Hanse

  1. vor 11 Stunden schrieb SoarandSkor:

    In the last image I saw the jetway connected to the L2 door, does this mean you guys have found a workaround to choose which door is used for jetway connections?

    Yes there is a way in MSFS to define the "priority" door the jetway connects to. As MSFS handles only one jetway we defined for the Aerosoft A330 the 2L door as standard. But often (especially when the stop position is not correctly defined in the airport bgl-file) it will automatically connect to 1L or not at all to any door.

    • Like 7
    • Thanks 1
    • Upvote 1
  2. vor 22 Stunden schrieb Mathijs Kok:

    Is this possible to change as GSX currently has pax go to 1L.

    Please read my following comment very carful again:

    Remember MSFS can currently handle only one jetway. To which door the jetway will be connected is defined in the plane settings. For the Aerosoft A330 this is the door 2L according to RL when only one jetway at a gate is available and GSX uses the same MSFS function to connect a jetway. This only works in MSFS and with GSX if the plane has stopped at the right position. If the AFCAD file is not correct ,the jetway will try to connect to 1L or fails to move at all. But in GSX you have the opportunity to modify the stop-position so that always the jetway will always be connected to door 2L.

    GSX connects according to the plane settings and this is the 2L door, but only ,if the stop position ir correctly defined in the AFCAD file of the airport/gate. Otherwise it will connect to the 1L door or even not move at all. But if you are using GSX you can define the stop position for GSX youself (for the plane and the gate) and then GSX will connect also to the 2L door. 

    • Like 1
  3. vor einer Stunde schrieb mopperle:

    It is not a good idea to move away from what the standard expects and GSX is not the standard. And as the other user said, you can change the GSX profile.

    Remember MSFS can currently handle only one jetway. To which door the jetway will be connected is defined in the plane settings. For the Aerosoft A330 this is the door 2L according to RL when only one jetway at a gate is available and GSX uses the same MSFS function to connect a jetway. This only works in MSFS and with GSX if the plane has stopped at the right position. If the AFCAD file is not correct ,the jetway will try to connect to 1L or fails to move at all. But in GSX you have the opportunity to modify the stop-position so that always the jetway will always be connected to door 2L.

  4. After a re-install of MSFS (not using disk) I have the problem that I am not able to add anymore custom views. Them I detected that the folder for such files = C:\Users\Rolf\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe is write protected. I now have two questions:

    1. Can this be changed (changing the attributes of the folder does not help)? Or

    2. How I can "clean" re-install MSFS from disks?

    Regards,

    Rolf

  5. After updating to SU11 Beta the loading of EDDH stucks after selecting EDDH from the drop-down menu. There is no way to finish the loading than to quit MSFS using the Task Manager. Any solution to that problem? Thanks.

     

    Regards,

    Rolf

  6. Anyway if you have problems with views (colours, brightness etc.) you should previously delete all shaders. The standard shaders then will be rebuilt the next you are starting P3D and all our views are based on the standard P3D shaders......

  7. Jerry,

     

    first thing is that you should check / try the correct necessary settings in the OPTIONS MCDU (SHIFT+4):

    • OPTIONS - CHECKLIST - Set INFO BAR and HOTKEYS to ON. This means you will see messages on top of your screen what should be done next and also offers the possibility to start the necessary action just with one "key".
    • GROUND SERVICES - Set GSX PUSHBACK to YES and the GSX pushback process will be fully integrated into the Engine Start CL.

    Hope those hints solve your problem.

     

    Regards,

    Rolf 

  8. Gary,

    most of the existing repaints are prepared for v4 and not for v5. In v5 the VC is different from v4. Because of the different registration number and selcal code (compared to the standard VC textures) repainters also provide a part of the VC with the correct information (registration and selcal code) for their models. But if those are prepared for v4 then you will get exactly what your are describing. So try my proposal and everything will be fine. 

     

    If you want the VC of your repaint with the correct registration and selcal code then you have to do it yourself p.e. using Photoshop or GIMP. Take the file  "AIRBUSX_VC_PREPARV4_MAINPANEL_C.dds" from one of the original textures and change the numbers in Photoshop or GIMP. Then save this modified file into the texture file of your repaint. 

     

    Rolf

  9. ETOPS: The entry and exit points are in reality entered at cruise level as "Pilots Waypoints" in MCDU / DATA / DATA INDEX /. The functionality "Display of MSA sectors" is not used for ETOPS. For the display of MSA sectors at one waypoint LAT REV and FIX INFO is used.

  10. What I recognized is that LM with P3Dv5.3 HF2 enhanced something in connection with performance. Now approaching an add-on airport (a "heavy" one like EGLL) the FPS do not drop anymore to values below 10 and stay around 20 FPS. But this depends on your hardware and settings. At least you should give the new HF a try and see if this enhances your situation.

  11. Hi Peter,

     

    I suddenly have the following problem. When starting the software, first a small empty windows displays on the desktop and then automatically the program is sent to the task bar. If I click on that small program window I get a message that the program is already running e. g. currently I cannot use SimStarter. In the log-file (see attachment) it states that the program is running properly.

     

    Since last time running the program without any problems I only updated the NVidia driver to 511.23 as well as Navigraph SimLink to version 1.1.24.0118. Changing back the NVidia driver to the previous version as well as disabling SimLink does not change the behaviour. I also newly installed SimStarter NG but this also was no solution to solve my problem.

     

    Any suggestion what else to try?

     

    Regards,

    Rolf

    SIMstarter NG.log

  12. Bernd, hast Du evtl. wie von LM vorgeschlagen nach der Installation von P3D v5.3 HF1 im Installationsverzeichnis von Prepar3D die Verknüpfung „Delete Generated Files“ ausgeführt? Diese setzt leider den Simulator in den Standardzustand zurück und löscht u.a. alle manuellen Einträge in den beiden Add-on.cfg, der Scenery.cfg und auch evtl. Joystick-Belegungen. Ich kann nur davon abraten oder man sollte sich vorher Backups der o.a. Dateien machen.

     

    Liebe Grüße

    Rolf 

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use