Jump to content

Mephic

Frozen-Inactivity
  • Content Count

    896
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by Mephic

  1. Did they fix livery specific settings installation issue? (currently they land in Simobjects folder instead of PMDG and have to be manually transferred). I think this would be perfect moment to fix this bug.
  2. When you'll get FS2Crew it's very nice to practice Touch & Go procedure. good luck and have lot of fun with this amazing bird
  3. With PTA 2.04 works like a charm. Amazing work, I think it's more all around than other presets and does not need reshade to look nice!
  4. Weather injection fps drops are often related to shadows. Try the cloud shadows texture size 512 to 256. It can really boost fps and there is no loss in quality.
  5. Understood. I guess I will just start the APU a bit earlier and let it warm the aircraft. As for isolating a pack goes, I thought it's only used in high temps to increase pax comfort but after some thinking it can warm up the aircraft so it really makes sense to isolate it when temperature is below 5 degrees. Thanks!
  6. ENVTEX (just for sky, moon and sun textures).
  7. I got it few weeks ago and can't imagine flight without it, plus I use it in truck sims too. Thing about TIR5 is you need to have a good profile. Fortunately there is plenty to choose from.
  8. Hi I'm trying to understand how this process is handled in real life: 1. I run before start checklist to the line 2. I start APU and set it on the bus 3. I ask ground crew to disconnect Air Conditioning cart (and GPU offcourse) 4. APU bleed air goes on At this point I would normally run before start checklist below the line and ask for pushback. As I'm using GSX, in cold weather I do get information that due to cold weather engines should be started after pusback is completed and brakes set. Issue: between the time when AC cart is disconnected and engines are on, Cabin gets really cold. Can I avoid this by setting packs to ON when on APU Bleed air and switch them off after pushback is completed and before I start the engines, so I don't run engine start on packs ON? This is what I'm actually doing and cabin gets warm enough to not get cool again when I turn packs off and start engines, but wanted to make sure if that's something that would happen IRL?
  9. I have PMDG 737 NGX and PMDG 777 as far as study level aircrafts are concerned (got 2 A2A birds too but they are far less complex IRL, so no need to bring them up). As a first step I always spawn on default airport and look around the cockpit to see what do I know from other aircrafts and what I don't know, where is the radio and nav stack, where is the engine panel, APU switches and so on - just to have some general awareness. I usually spend around an hour looking around to familiarize myself with cockpit layout. Next step are tutorials. Whatever manufacturer provided in his package. This allows me to understand how to fly the aircraft. With PMDG I did it in following way: 1. Fly tutorial flight from and to destination which it was designed for. 2. Fly tutorial flight again but change destinations to ones I'm familiarized with procedures wise (e.g. EPKT to EDDL which I fly frequently). This allows me to go out of the comfort zone of tutorial where I can't do everything exactly step by step, but systems wise I'm still being held by hand. After completing this, I usually get myself a checklist and start to practice flows. Whenever I don't know where to find the button, switch or understand why am I switching it I start to use google. After I feel comfortable enough to fly from one place to the other following normal checklist, I start to read rest of manuals supplied by manufacturer when in Cruise. I don't read them from beginning to the end (exception is 737 manuals, I read them all twice when on holiday ). I usually come up with some challenge and try to find answer there, e.g. "how to fly VOR approach" with this baby or "what is RNP". Usually I read about one subject per flight and try to memorize what I learned. With time, I got to know most of 737 systems and procedures enough to get myself FS2Crew and fly it more realistically (although decreasing the workload but increasing the immersion). To practice I try to fly one flight by myself with FS2Crew switched off - I usually do it once per quarter with some challenging approach to make sure I don't forget important stuff. One thing I realized is the more complex and intimidating at first the aircraft is, the easier it is to fly it later when you learn new systems. E.g. - I didn't use FIX page in NGX FMC for 1 year. After I learned it I understood how powerful thing it is and how it can assist me in various situations. After I feel comfortable with systems programming, I move on to manual flying. Currently I usually hand-fly 737 to 10k or from beginning of STAR manually, to increase workload and have more fun. But it took time to get there for sure. Practice, practice and practice - I have almost 1 thousand hours on NGX and I would not exchange this time for anything else. But one thing is worth to mention - with study level sim you HAVE TO study. Only after that time I felt comfortable enough to turn service based failures on, print out QRH and wait what will happen (although lately I started to practice non-standard situations like engine fire on takeoff or cabin depressurization in flight to ensure I'll know what to do if it happens when I'm not so prepared.)
  10. I bought lot of aircrafts for this sim but NGX is the one I fly the most. Good for short and long flights, able to land on really short runways (LGSK - pure fun!) and also doing real world long hauls (e.g. Poland to Kenia with short stop in Egypt to refuel while flying Enter Air is awesome). You can fly it ETOPS, you can fly it on domestic routes, it's just really flexible. I didn't repurchase -600, -700 package for P3D (only had it in FSX) as I fly 800 mostly anyway. When it comes to smooth landings I started with 500 FPM (so nowhere near smooth) but now 80% of them is below 200 FPM and yesterday I also did 140 which was (to me) a great success with Saitek Yoke which is known for not-so-easy pitch management. The two tips I can give you for manual landing are: 1. Disconnect the autopilot much earlier than on minimums (I do it when I have runway in sight and sometimes even at 10k to practice, especially if there is a need to fly traffic pattern). The reason is simple - you'll get use to controls after flight on auto-pilot and won't make sudden moves when on final. If you find yourself doing overaggressive moves on NGX causing instability, that means you need to go back to Cessna (preferably A2A) as this one is also very tricky for pitch management when landing with flaps 30 but allows you to practice with slower speed. 2. Start disconnecting throttles on 50 and by 30 have them completely off. I'm not sure if the real thing is not somewhere around 20, but I found 30 to work best here. I start the flare (very delicate) at around 25 feet but if I see I'm going to do long landing, I release and land it firmly. Prefer pax to feel little butt-pain than end up in sea or buildings. EXTRA TIP: as long as you're not in IFR conditions, look out of the window. Easier said than done as we have tendency to check glidepath indicator and make sure we're on track, but really it's easier when you look where you go. (much easier with TrackIR though)
  11. Last one in 737-800 Smartwings. LEVC -> EPGD
  12. Actually I applied conservative settings to PTA (modified Pe11e preset) as there was too much blue haze But yeah, I think now it's spot on
  13. go to sdk, reinstall simconnect and lets see from there
  14. No, that is not normal. Rename your p3d.cfg file in Appdata/Roaming/LockheedMartin/prepar3dv3 and let it rebuild with new settings. Go to P3d.cfg and change cloud shadow texture size to 256 (default is 512) - it can give you huge FPS gain in overcast conditions. Don't apply any tweaks to p3d cfg, they are not needed. Disable VSYNC, disable triple buffering (you will try to work on vsync after you get normal FPS back). Set terrain cast shadow distance to 0 - that is one of top performance killers. Set tesselation to ULTRA - you need to increase GPU load. Set Anisotropic Filtering to 16x. try performance again, report back and we'll see what's next
  15. Yes, I remember I found this fix on HiFi (AS16) forum. They were really helpful back then, glad it helped you too!
  16. I forgot about it as I rebuilt my cfg. It's easy to be fixed. All that needs to be modified is ground shadow texture size in p3d cfg (I think default is 512 or 1024, after changing it to 256 performance goes up! )
  17. Few shots from departure and cruise to Valencia. SIM: P3D 3.4 HF2
  18. Can you share your option screens (especially part with shadows) and also inform if you use PTA shaders?
  19. Ahhh... impressive plane. Not yet there to forgive it 1 GB of VAS but almost, almost...
×
×
  • Create New...