ESzczesniak

members
  • Content Count

    167
  • Joined

  • Last visited

  • Days Won

    1

ESzczesniak last won the day on February 16 2014

ESzczesniak had the most liked content!

Community Reputation

25 Excellent

About ESzczesniak

  • Rank
    Flight Student - Solo

Recent Profile Visitors

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

  1. I'm having troubles getting very far with the tutorial flight. I set the aircraft to cold and dark and turned the master battery on after completing the preflight checks as per the tutorial. Unfortunately, as early as point A in the APU start sequence, I can't get any further. I press the APU PWR/FUEL switch and nothing happens. It doesn't light up, it doesn't do anything. I can't move on because the APU isn't powered on. Any thoughts on what stupid thing I may be missing? I'm not thinking this is a bug, I'm thinking it's some setting issue.
  2. I'm looking for a PFPX profile for the CRJ 700/900. I've seen one references, but I can't seem to find it in the downloads section, or anywhere else for that matter. Could someone help point me in the right direction? A link or at least a file name? Thanks!
  3. ESzczesniak

    F=14 Extended in Prepar3D v4

    Just wondering if there any updates on this? I know generally, we'll hear if there's news. But, as many others, I'm pretty anxious for this in P3D v4!
  4. Thank you! My confusion seems to be more with Windows 10. I copied everything back in to a "Documents" folder linked in My Computer, but this doesn't seem to be the same thing as the default Windows 10 "Documents" and is in a different location. Now that I moved the PFPX files to the C:\Users\Public\PFPX Data, it all shows up.
  5. I've recently completely reformatted for a Windows 7 to Windows 10 upgrade and reinstalled everything. I have my entire old PFPX Data folder and was hoping to utlize my old schedule and aircraft data files. However, I can't find how to import or open them in PFPX. Can anyone help me? Is there a new location for the PFPX data in Windows 10? Thanks for any help.
  6. ESzczesniak

    "Meatball" Visibility - Any Way to Adjust?

    I played around with zoom settings this afternoon while flying around and it did not make any difference.
  7. ESzczesniak

    "Meatball" Visibility - Any Way to Adjust?

    Thanks for looking in to this issue. I'll play around with the zoom a bit too. I had been zooming in to try and see the light, but maybe I was just hurting myself. I agree with you that I think it's probably easier in real life, but I've still be able to fly the ball for distances under about 1 NM. I need to use the ILS needles in a case III or strictly by the numbers case I pattern to get me in position to do that though. I think that's par for reality though, as I don't think the real life FLOLS gets you much further out than 1-2 NM.
  8. ESzczesniak

    "Meatball" Visibility - Any Way to Adjust?

    Ok, so I've done some playing around and I'm still having difficulty. It clearly is not the gauge issue after more playing around. While I still don't know the cause of the vLSO warning, loading an aircraft that I have never installed the gauge on shows absolutely no lights on the FLOLS, even on deck. I've also updated the P3D client to v3.2. I am still having the same difficulties. I've attached 2 screenshots below. The first "Ball", is at the vLSO automatic ball call at 0.7NM. I can definitely not see the meatball, and can maybe only barely see the green FLOLS bar. The second "In Close" is the first time I can notice the ball, about 0.4NM. I've been flying the AWL needles to get me to this point, but it makes a true carrier approach hard not picking the ball up until about 0.4NM. Is this what's expected or am I seeing an anomoly? Any ideas how to address this issue? I've tried playing a bit with the P3D lighting settings (mainly brightness), an no changes seem to be affecting this. I understand from the manual the FLOLS is intended to be a realistic representation of size, but the manual also says it should be visible from about 1.5NM, and I don't seem to be any where near this. Thanks for any help or input.
  9. ESzczesniak

    "Meatball" Visibility - Any Way to Adjust?

    I was wondering if you are anyone else could help me look in to installation of the FLOLS gauge a bit more. I was thinking this is a visibility issue (it still may be). However, everytime I start the flights, I get a message from vLSO "The CV63 support disabled (no FLOLS gauge installed)". After looking in to this a bit more, I understand this means the gauge is not installed correclty. I get this in any aircraft I have attempted to install the gauge in to. Per the instructions, I am copying "gaugeXX =..\..\..\..\Aerosoft\F-14A\FLOLS\CV63_FLOLS!FLOLS_CV63" as the last line of the panel.cfg section vcockpit01 and editing xx to the next number in line. I notice 2 things with the panel.cfg in the F-14. I see this is under vcockpit02 (as opposed to 01) and the number 63 (next number would be 17). I also see the slashes are reversed (gauge63=../../../../Aerosoft/F-14A/FLOLS/CV63_FLOLS!FLOLS_CV63). I understand if the gauge is not installed, the FLOLS won't really work. Is there any rhyme or reason to what's going on here? Should the entry line actually include all the ..\..\.., or should that be replaced with the full path to the gauge? Thanks for any help.
  10. I'm fortunate that the throttles are working well for me with the new F-14X Extended and am loving the sim. I'm wondering about my meatball visibility though. I'm running P3D v3.1 (will eventually get to v3.2) and am finding that the ball is not at all visible at 0.7-0.8 NM (by TANCAN) when I should be "calling the ball". It's not until about 0.4 NM that I see the ball. I think I see the green bar, but it get's brighter at 0.4 NM, so I'm wondering if I'm just seeing the unlit lights. I thought I had a couple screen shots to show from my flying session, but it seems they didn't take. I'm settling down for the night, but will try to actually get screen shots during my next sim session to illustrate what I'm talking about. In the mean time, are there any settings that could adjust this?
  11. ESzczesniak

    Realism poll

    On products that have these as options, I wouldn't have it any other way. Not have maitenance and standard wear simulations are not deal breakers, but certainly love them when I see it.
  12. ESzczesniak

    No speedbug and less FPS in V.1.20

    I'm not sure it would blow the wheels, but is very frowned upon. Large commercial jets actually do not want to touch down too soft or autobrakes and spoilers may not deploy. However, on clean runways an aim will be around -50 to -150 fpm and even on wet contaminated runways your looking at maybe -250 fpm. Many airlines will push an aircraft in for a maintenance review if they are over -500 fpm. Of course, MSFS only counts it as a crash if it exceeds -1000 fpm.
  13. ESzczesniak

    No speedbug and less FPS in V.1.20

    Well, I agree Aerosoft seems to be trying hard to bring things up to speed. However, I'm one of what appears to be many who wishes they could get a refund. I knew systems wise what I was getting in to (ok, I still feel the web page overstated things a bit, but it was ballpark). However, I find the aircraft almost entirely unflyable by hand and autoland is problematic. An aircraft that doesn't fly well is very problematic.
  14. ESzczesniak

    Beyond 1.20

    The Airbus X is beautifully modeled and I am quite happy that you are looking in to an "advanced" version. I've only had a few flights, but here is what I'd add: 1. Expansion of CDU/FMGS: In particular I'd like to see the ability to build a flight plan within the FMGS including departure airport and runway, SID, airways, STAR and arrival airport and runway. After that, being able to input speed/altitude constraints would be my next choice. I'd be happy to see allowances to select custom climb, descent and cruise speeds instead of hard coded speeds. However, I rarely actually change these data, so I can't argue much for it. Holds and fixes would be nice too, but I can live without those as well. 2. INS alignment: Truthfully I am not all that concerned about modeling drift, etc. Really, I would primarily like to see an option to require an alignment time period and to require that we flip the switches to align them. 3. Tuning of the VNAV: I don't know that I really need EVERY aspect modeled, but I would like to see a more flexible modeling for both managed and open VNAV. 4. Manual handling: I understand that the Airbus X was designed to be flown the way an A320/321 is normally. However, often aircraft really are hand flown on departure and final approach and while she handle's fine on departure, handling on finals is quite stubborn (we'll see how well it may be worked out with 1.20 though). 5. More thorough climb/thrust reduction profiles. In particular, the ability to set a thrust reduction height separately from an acceleration height so that we can model noise abatement procedures (typically thrust reduction at 1500 ft AFE and acceleration height at 3000 ft AFE). 6. I would like to see an option for VC rain...although I can easily live without it. 7. I like the idea for an ACARS simulation, but that's quite a bit extra work there. Like others, I am ok without a WXR, terrain display or wing flex.
  15. ESzczesniak

    Approach stability...

    I'm curious what other people's perceptions about the approach control on manuals. I've only had the Airbus X up for a couple flights and she handles fairly well on departure. I just can't tame it on approach. I've tried flying both a manual approach from before the LOC intercept and letting the autopilot fly the LOC and G/S intercept before taking over. The problem I'm having is that the elevator controls, particularly up elevator, is laggy and over sensitive. If I am falling below G/S, I correct with just a slight bit of up elevator and go from a descent rate of about 7-800 fpm to 5-600 fpm immediately and looks good. But the elevator response just keeps ballooning over the next 1-2 seconds and even with fill down pressure on my stick (ok, yoke) the descent rate comes up to about 0 fpm. This makes tracking the G/S very difficult, something that I am actually pretty good at on most other aircraft being able to hold the G/S until about 50' AGL. I find a similar response with down elevator, but not as dramatic. I'm wondering if this is a result of my poor understanding of the FBW syste, as I'm a Boeing guy normally. I have been trying to trim the aircraft on approach like I would any other aircraft while flying manually. Perhaps I'm messing up the FBW system? I always have concerns over correct speed/weight but have been using the speeds from the CDU and flying around 120-130 kts. I'm curious what people's experience has been flying this aircraft on approach and if it's any different than my experience.