Jump to content
The simFlight Network Forums

JerryJet

Members
  • Posts

    37
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by JerryJet

  1. 31 minutes ago, Jeffrey S. Bryner said:

    Hi Jerry,

    JetBlue only flies the E190 (LR).  See https://www.planespotters.net/airline/JetBlue-Airways or https://www.airfleets.net/flottecie/JetBlue Airways.htm.  I was working on some of the other tails and the 2-color blue fuse stripe. Which reg did you have in mind?

     

    Does not really matter to me since I have an Airbus in a Southwest livery. I like the jetBlue colors and patterns but only have the 175-195 combo. Can't really justify another $50-$60 to buy the 170-190 combo. As much as I like the Ejets I don't need the whole stable.

    I also fly Delta in Europe and Africa, Austrian Airlines in the USA, etc. I try not to get bogged down with unnecessary details and just fly.

  2. On 4/27/2020 at 12:44 PM, canadagoose1 said:

    Hope this helps others with this problem.

    This must be too complicated for me. I take it I must go off the Home page and Image seems the logical choice, but DDS is not an option for "output"ing the file. None of the other choices seem appropriate. Home page doesn't offer to resize the output file like I've seen mentioned here.

    I know it's right in front of me, but I'm not seeing it.

    Put my glasses on and DOS changed to DDS. Amazing I can still function.

  3. 8 hours ago, Jeffrey S. Bryner said:

    Thanks Mate.  I keep tweaking the details on the repaints with every new release.  This one has a few minor details improved upon from the Alaska SkyWest I just released.

    Thanks for doing these repaints.

    What are the correct file dates for this (SkyWest) livery? What I got from Avsim on April 1st still had messed up textures.

    TIA

  4. 23 hours ago, KBUF_aviator said:

    Thank you for the response. Could there perhaps be a chance we could see them after the service pack is released?

     

    V2 of the Ejets has the older style winglets. Available right now. Maybe you can figure out how to attach them to the V3 Ejets.

  5. Throwing out a few ideas....

    Read thru this thread and I see no mention of where the Ejets are installed. Inside the P3D root folder or outside via an addon.xml? If outside have you set an exclusion in your antivirus program for that folder?

    You mention disabling TomatoShade, but are you returning the shader files to their original state? Same thing for any other utils that might have changed any of P3D's default files.

    Use the default House liveries until you figure this out. Stop FSUIPC and anything else loading with P3D. Plain vanilla all the way.

    Good luck!

    Quote

     

     

    • Upvote 1
  6. 2 hours ago, LecLightning56 said:

    I get the same thing with the aircraft in altitude hold establishing on the glideslope. Once the glideslope is centred, the aircraft pitches down violently. This is just WRONG and a serious shortcoming of the current product. Aircraft is the Embraer 170 v3.

    +1

    Don't have the 170 or 190. This is with the 175 and 195.

  7. 22 hours ago, Dan Moore said:

    It clearly states that "The biggest limitation: the P3D v3.2 and v4.x Add-On.XML method for add on insertion (particularly sceneries) is not supported". So the database manager can't read the new locations for FSDT and FlightBeam locations. 

      

     

    Here's a really, really crazy workaround. First read this post by Pete Dowson:

    http://forum.simflight.com/topic/83459-important-makerunways-and-new-add-ons-structure/

    "MakeRwys_scenery.cfg" is created in the root directory of your P3Dv4 installation, same place as MakeRwys.exe. FSCDbManager doesn't recognize that name or location so you have to copy and rename  it into %programdata%\Lockheed Martin\Prepar3D v4 as "scenery.cfg." Make a backup of the real "scenery.cfg" first, cuz once you're done running FSCDbManager you must delete the fake and put the real "scenery.cfg" back in place.

    Awkward but right now it's the only way I can think of to build a correct P3Dv4 database for FSCommander. Remember to backup the real "scenery.cfg" before you overwrite it.

  8. My Specs:

    Prepar3D 3.414.18870

    FSUIPC 4.958

    No Network

    FSC and Database Mange 9.6. Rev. 7

    Navigraph 1613, Rev 1

    Aerosoft Download

    Windows 10/64

    2 monitors

     

    Hi,

    All scenery areas are set to active when I run the Database Manager. Two new payware airports are properly identified but without any information for them. ie: no runways, parking spots, frequencies, airport diagram, etc., everything's blank. As a test I looked up the two airports in Avilasoft EFB and Little Navmap. The both displayed correctly with all pertinent information.

    The two airports are CYPQ and 3W9 both made by Scenery Solutions, sold by Flight1. Log file shows these two errors:

    00001 , 0211 , CYPQ  - Peterborough
    Error detection and correction in ReadAirportSubsection: CYPQAIRPORT.BGL (#9)
    E:\P3D3\SCENERY\XPRESSSIMCANADA\scenery\CYPQAirport.bgl

    00002 , 0210 , 3W9   - Middle Bass-East Point
    Error detection and correction in ReadAirportSubsection: 3W9AIRPORT.BGL (#9)
    E:\P3D3\SCENERY\XPRESSSIMUSA\scenery\3W9Airport.bgl

    Thanks in advance for any insight.

    Jerry

  9. Then... when I select 'Save' I get this message: "Flight plan for addon aircraft cannot be saved because Flight Simulator X folder unknown" Please specify Flight Simulator X Folder under Flight Plan > Save as > Tab Paths >Folder Flight Simulator X > Row 2!

     

    So I go to 'Paths' and get a path selection on the left hand side e.g

    C:\FSX\Flight Plans

     

    Hello Neil,

     

    Change Row 2 to the root folder of Flight Simulator X --> "C:\FSX" and see if that doesn't solve the problem.

     

    Jerryy

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy 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.