Jump to content

FelixM

Member
  • Posts

    33
  • Joined

  • Last visited

Recent Profile Visitors

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

FelixM's Achievements

4

Reputation

  1. Hi, unfortunately I bought EGLL over the market place and I saw that on my other products I can actually configure the airport in the Ini-Manager. The reason Iam bringing that up is that with both the Fenix and the PMDG I experience a smooth experience at EGLL except that there is a heavy freeze/stutter every 5 second approx. I have cleared dx/gl shader files, i have cleared rolling cache, in fact i do not use rolling cache at all. also updated nvidia driver etc. I have a pretty strong system and on other heavy scenery airports i dont experience that (tested several airports inibuilds jfk, corfu flytampa etc). BTW I also tried to turn off online functionality completely so even with no photogrammetric data at all there is this freeze or stutter. I also set LOD to 20 same freeze stutter. Only on EGLL. I also deinstalled the Asobo version. 1. Do you have an idea what can cause that? Or what I can do? 2. I read that there might be a chance to transfer my market place order to an order so that I can use my ini manager. Here I could try to configure the airport better, maybe that helps. At the time I bought this i didnt know about the drawbacks of that damn marketplace. If there is a fee for that I would pay it. Thx for your time and best regards, Felix
  2. Hi, hmm no comments on this ? Best regards, Felix
  3. Hi, just read that there is an update for LEIB. Is that comming for the marketplace version as well? Best regards, Felix
  4. Ok disregard that, there already is a post about that issue. Sry did not see that.
  5. Hi, justed visited LEIB (store version, PC) again and as I was vacating the runway I was totally confused with the taxiways letters. Apparently I vacated on foxtrot F according to what I could see in the scenery but looking at the navigraph taxilayout there is no taxiway foxtrot. It was one of the E3 or E4 cant remember. And there is also no alpha taxyway adjacent to that. The scenery itself is in perfect shape just the taxi description is wrong, or am I missing something here? Best regards, Felix
  6. When I remember correctly VLOC or pure vor navigation is bugged at the moment and should be fixed next update. VLOC doesn’t work properly on my side as well. best regards felix
  7. Hi, BTW it is the same with the pause system. Pausing the SIM (while flying the A310) in particular if you go into a menu will cause the A310 to go totally crazy when you resume the game. Unrecoverable. Best regards, Felix
  8. Hi, Land ASAP 😉 1. RAT : On (Ram Air Turbine, there is a handle on the left side of the Captain seats) RAT will allow the yellow hydraulic system to be powered and will give you flight controls to operate. 2. Throttles: IDLE Optimum Speed: green dot speed (average rate of descent 1700 ft/min) 3. Emer Exit LT : Disarm 4. Flaps 15° for approach 5. At 2000 ft AGL Emer Exit LT On 6. Before "impact" Ram Air on, Pitch approx 11° 7. at Touchdown: fuel levers off, pull all fire handles I took the relevant steps from the QRH (Quick Reference Handbook for Both Engine Flame Out Scenario with no Fuel remaining). I listed not all steps, just the most important. Most important thing to to do is to turn on RAT to power the yellow hydraulic system. Hope the helps. Best regards Felix
  9. FelixM

    MSFS 2020 A310

    Hi, Have you installed the Dirty Livery Pack from Dreamscenery? That livery package causes exactly the issue you have described. Best regards, Felix
  10. Hi together, just as an information for other pilots. If you have installed the Dirty Livery Pack from Dreamscenery then I highly recommend deinstalling it as it seems to interfere with the A310. As a result of this livery package you will the yourself with an animated Captain and a Copilot in the seats and all switches are not clickable. Iam running on Xbox, but I have seen a post on the official MSFS forum for PC as well. Best regards, Felix
      • 2
      • Like
  11. @gumbygerJust spot something. Is it possible that in your case your new step climb altitude was lower that the optimized FL in the FMC ? In my case I had 373 FL Max and something like 365 FL for optimized. I then tried 370 FL for the step. This did not work. Maybe the algorithm compares the new step climb altitude to the optimized instead to the max level, so it essentially thinks no you can't go that high. Just guessing here. Will test that after christmas.
  12. This is really strange. I will make a video as well after Christmas. I'm doing it exactly the same way and the plane doesn't climb. Maybe you can spot something I have done wrong. But I mean there is actually not much you can do wrong hmm....
  13. Hi, thx for taking care. Btw if you need another Xbox tester let me know. I have most of your scenery and would be happy to help sort things on XBox relevant topics. Atm I have flown around 60000 km with the A310 on my first around the world trip. I have already a small list of little things I have found on the A310. Will make a post about them, when I have finished the whole trip. Best regards and merry Christmas to all of you. Best reagrds, Felix
  14. Hi, (Iam on XBoxX) after landing I taxi to the gate, turn on the APU shut down the engines and then would instantly like to prepare for the next flight (without exiting). So I do refueling through the EFB , new flight plan through simbrief and start from the beginning. This will result in 100% CTD. I did now 10 tests and it always crashes to the XBoxX main menu, mostly during taxi. You can actually accelerate the CTD by changing views (in the cockpit left/right etc....). It only happens with the A310. No problems with other aircrafts doing this. Maybe that is something to look into the future. Not a major thing, since you can always start a new flight via the menu. Best regards, Felix
  15. HI, I just tested it myself and can confirm that it is not working as shown in the Video. (Running on Xbox X) 1. Flying leveled at CRZ Alt FL340 2. Insert Step Climb for the next Waypoint to FL370 (FMS is now updated to FL370) 3. Changing Altitude knob to FL 370 4. Getting P.CLB flashing Blue in the FMA shortly before reaching the waypoint 4. Crossing the Waypoint - nothing happens. P.CLB flashing in blue just vanished. Comment: There was no turn followed after waypoint , pretty much a straight line. Best regards, Felix
×
×
  • Create New...