Jump to content

Kurt V

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by Kurt V

  1. @Matteo Veneziani
    Matteo, is an optimization pass in the works for VNY?   Even running on a fast NVMe and a 3070 ti card, this airport just murders frame rate.   Generally its ok if not looking around, but a pan to the side goes into single digits sometimes.   And today just for testing I did a low pass in the A32nx without looking around, just straight ahead and frames got so bad the scene was surging and stuttering and I nearly lost control... As soon as the last bit of airport scenery left the screen, performance snapped back to my usual.  

    It only happens when pretty close to the airport, and I'm not seeing these problems with Orbx KSBA or KBUR, so it seems something is specific to this scenery.

    • Like 2
  2. On 6/24/2021 at 10:34 PM, Matteo Veneziani said:

    Hi, probably i have another solution, i will try to change the elevation of the airport from the current elevation to runway 16R elevation (802ft ) this will fix 2 problems:

    -you will have a corrected glideslope for 16R

    -probably the windsock will be fixed

     

    I hope will be possible to do without any problems since this zone it is full of bugs.

     

    Regards


    Hey @Matteo Veneziani
    I am curious if you have been able to make this adjustment.  I haven't seen any updates to the add-on in Orbx.  Thanks for any info, really hoping to get the ILS sorted out (The wind sock too, but like the guy above, the sock isn't bothering me much -- The ILS is a more serious concern).

  3. 12 minutes ago, Matteo Veneziani said:

    And what do you think the idea to make the elevation of the airport like the elevation of 16R? So higher than now?



    Since the normal usage is 16R and 16L, and since the ILS is there, the correct threshold at 802ft would be best.  This is also considered to be the official field elevation, so again... probably best.

    While the backcourse approach on 34L is sometimes used, its not common.  Therefore, I believe you'd be best served by setting the elevation at the north end as 802ft.

     

  4. 12 hours ago, Matteo Veneziani said:

    Hi, yes the ground has been flattened because there were a lot of problem with elevation here, for example i tried without the flatten and there were a bumps in the runway, so the unique solution was to make it flat. Unfortunately in this zone where there is the photogrammetry the terrain it is not responsive like other part of the world and it is super buggy.

    Hovewer i will look what i can do to fix correct the glideslope.

     

    regards

    If it is useful to you Matteo, the runway as it was in the MSFS original version (the elevation changes) are roughly accurate to real world, more accurate than the flat version if my memory is right (haven't flown out of there in a long time, but I remember it being noticeably not flat in real world).  Elevation at taxiway C is 802ft, and at R it is 746ft, and my memory is there really was a bit of a hump to it as shown in the MSFS version... Trying to see if I have a photo somewhere.

    I am attaching a video I found at the bottom of this -- Not my video.   In it you can see there is a bit of an undulation to the runway... Not as severe as MSFS original had it, but from threshold to about half length its on a relatively flat, or slightly uphill, and then after that it slopes down to the 749 ft elevation by the south end.  The video also showcases what a great job you did with the look and feel! ;)

    So maybe if you could figure out a way to work that in?  I don't know -- I know nothing about scenery creation, or what difficulties that might cause.

    As you can see from the images, its not a deal killer or anything.  The airport is usable, but I think people who fly a lot of IFR will probably prefer it fixed if possible.
     

     

  5. 6 hours ago, wolfko said:

     

    Uhm, I am not sure if I understand you correctly.

    But according to your instruments, on the first shot you are are slightly above the glideslope and on the the second one you are slightly below.

    Also the altimeter indicates different hights. So IMO all seems to be correct.

    The altitudes are different because I'm not at the exact same spot in each shot.  Or maybe I am and the terrain is lower?   Either way, the gauge shows on target (if slightly imperfect, see below) and the visual picture is not on target.

    In order to be far enough above GS to have two white lights out the window, I'd be beyond the limits of the circle in the gauge.  Being so close that the needle is still covering the dots is effectively right on the money.  By your argument the second photo should show red lights outside.  If this condition existed in real world the approach would be taken offline for maintenance.  It's way off.
     
    While the instrument is very precise in sim and in real life, I'm not far enough out on either of those shots for the visual picture to be that wrong.  The angle to the runway in the stock VNY is what you would expect to see if on the marks... The sight picture in the Orbx shot is way high, even tho the GS indication is pretty much on the nose.

     

  6. Attached are screenshots of default scenery KVNY ILS, and Orbx KVNY ILS

    I have tested this in 1.0 and 1.1 and the problem occurs in both versions.

    I'm beginning to think that the floating windsock and this ILS might be related, because if the ground was 30ish feet lower in the Orbx version, that would explain the incorrect GS.

    See images.  It should be obvious which is which, since the Orbx one at least looks like KVNY ;)

    Thanks... 

     

    kvny gs.png

    kvny gs (stock).png

×
×
  • Create New...