Jump to content

X24

Members
  • Content Count

    94
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by X24


  1. 3 hours ago, thepitts said:

    I can't comment as I don't have the plane. However I was considering purchasing it given the glowing review on XPlaneReviews website. Maybe another site "not to have an honest discussion" about matters software. Pity.

     

    It is a pity.

    The guy from X-Crafts who wrote back to me seemed sincere, and I like to think people will do what they say will. If they keep developing this product then in time it could be quite good. It was confirmed that the dev team is basically down to a couple of guys at present, and that this was never intended to be a hi-fidelity study-level project because that would be beyond their ability. At least he was honest in that regard, and it's anybody's guess what will ultimately be considered acceptable further down the track.

    From what I could glean before being locked out of the X-Plane forum, a number of people reported similar issues with the automatics especially, and the developers admitted to challenges which they hope to resolve once they work out what XP12 needs to make things work properly.

    I'm still waiting to hear back about getting my account re-opened.

    • Upvote 1

  2. I wish I had read this forum first, I definitely would not have bought this product.

    Despite initial reservations I thought I would give it a go, and now having reported a long list of missing features and buggy behaviour on the native forum, X-plane have suspended my account so be careful. X-Crafts themselves have been very gracious responding to my observations and even offered me a spot as beta tester. However I cannot respond to them after being excommunicated.

    This has definitely been misrepresented in advertising and I cannot recommend the product, which has been sold way too early. Their website states: "The E-Jets Family for X-Plane 12 and X-Plane 11 sets a new standard for these regional jets in commercial flight simulation, and we are proud to finally give you a chance to experience a truly authentic version of the E-Jets."

    As someone who flies these in real life, I can state categorically that it is not authentic, but a collection of workarounds that may bear a close resemblance to the real thing in some instances but nonetheless falls way short of the marketing propaganda. It was not "exciting", but frustrating, surprising and disappointing.

    • Like 3

  3. I'm having exactly the same issue as the OP. I used the aircraft configurator menu to replace the default GNS 530 in a PA31T Cheyenne. It's replacing the unit, but you can tell from the welcoming message on the GPS screen that the gauge is too big somehow and the edges of the welcome screen script are cut off.

    Mousing over the click spots reveals that the nav and com buttons are alive as are the rotating knobs at the bottom, i.e. they show a mouse reaction and you can turn the unit on and off, but none of the other buttons do. It is not possible to click "ENTER" because the ENT button doesn't work.

    I do not have this issue with the GTN750, it goes in to replace the previous product and works fine. To remove any doubt, I am not trying to replace a 750 with a 530 either. The 530 bezel is intact. This issue occurs with AV off.

    I'd appreciate any advice. I had this issue with the Porter a while back but that seems to have been resolved over the past 6-12 months after an update.


  4. Hi all,

     

    Just been reading this again and noted the discussion about generator usage during start so thought the following might be useful.

    I used to fly Twin Otters which also have PT6s and there was a limitation requiring us to turn the generator of the operating engine OFF while starting the second engine using battery power. It's to do with the design of that particular electrical system and generator configuration. The airplane flight manual has this caution:

    "CROSS GENERATOR STARTING IS DETRIMENTAL TO
    GENERATOR BRUSHES AND TO REVERSE CURRENT
    CUT-OUT OPERATION (WHICH MAY CAUSE EVENTUAL
    CONTACT WELDING). CROSS GENERATOR STARTING,
    THEREFORE, SHOULD BE AVOIDED WHENEVER POSSIBLE.

    It's obviously a feature of this particular aircraft as I have not seen this requirement or limitation in any of the other turboprops I've flown like the Dash 8 or ATR42. I get the impression that there's not as much protection built into the older smaller starter generators like they use on the Otter.

    • Like 1

  5. On 12/13/2018 at 11:04 AM, dbw1 said:

    Real Air Turbine Duke

    Beautifully crafted and one of my all-time favourites. So happy I was able to purchase a copy while it was still available and I still fly it often.

    More recently I bought the MilViz (now Blackbird) KingAir 350i and PC-6. If you want contemporary aircraft with really good flight dynamics and turboprop modelling I recommend these two.

    I also fly in real life and although I have gone out and bought and tried a bunch of the other products mentioned in this thread, even with mods there comes a time where I get frustrated with them and lose interest. 


  6. Hi all,

    Firstly, I apologise to anyone who has been unable to access the downloads for the performance file and template via the links in my original post. I inadvertently deleted them from the online drive but they are back now: template here and the performance file here. Let me know if you have any trouble getting access.

    None of the data has changed since I originally posted it in 2015.


    Enjoy!

    • Like 1

  7. This is from the devs: "Looking into the issue I noted that the 530 / 430 for RXP only wasn't supporting an animated node position for a 530 unit on top but was supporting a pair of 430 units , its something of an undertaking to resolve this through a product update , I can offer you a console cfg that eliminates the issue in the interim."

    OP replied: "Thanks for looking into this and for the console file. But there is some collateral damages, as the mixing box disappeared, and if the popups seem to work fine, the 430 is inop in the VC (black screen and no buttons), as most of the buttons and switches on the 530 (again in VC). Only some switches on the left side are working."

    This again from the devs: "With humility I would recommend using the twin RXP 430 units, these would appear unaffected by this glitch .
    Thanks for your patience in this matter , the issue has been included on the PC6 list for the next iteration cycle .
    Best CJ

    Since then, it has been confirmed by other users that the problem remains - blank screens and lack of animations. We are awaiting an update apparently.

    Meanwhile, thank you for the tip about the license and the XML. The modeldef was referred to at some point in the dev's response to the OP . The 750/650 combo seems to integrate and work just fine. 

    • Like 1

  8. On 12/1/2021 at 11:42 AM, RXP said:

    Unfortunately I believe they must be spending a lot of time and efforts catching up on FS2020 bugs and SDK changes every month, but there is no reason this can't be resolved if they are still spending time to maintain their P3D aircraft, which I hope they still do.

    Jean-Luc, I found another thread on the MV forums for the PC-6, there is a known issue with the RXP 530/430 installation that they are looking into however there has been no new information since January so I guess we just have to wait. The thread link is attached, not sure if you have seen this.

     


  9. On 12/1/2021 at 11:42 AM, RXP said:

    here is that the trainer is not found.

    Indeed - I noticed that too. I re-installed the RXP and I can get one 2D pop-up of the 430 to appear which now tells me that I have an invalid license and to stop using the product. In the VC, the buttons work on the 530 except the screen is blank, but on the 430 all the buttons appear to be active except the power switch. When I mouse over it the mouse pointer doesn't change.


  10. Spoiler

    21/11/29 02:51:28.968 05560 -    ] # rxpGNS2.dll version 2.4.21.6
    21/11/29 02:51:28.968 05560 INFO ] 
    21/11/29 02:51:31.554 05560 INFO ] using GNSADBFILE = "C:\ProgramData\Reality XP\Common\GnsTrainer\dbfiles\006-d0170-00.bin"
    21/11/29 02:51:31.649 05560 INFO ] using: C:\ProgramData\Reality XP\Drivers\PFC\PFCHidReports64.dll
     

    Spoiler

    21/11/29 02:30:31.955 17472 -    ] # rxpGNS2_menu.dll version 2.4.21.4
    21/11/29 02:30:31.966 17472 INFO ] edit panel: F:\Prepar3D v4\SimObjects\Airplanes\MV_PC-6_Base\panel\panel.cfg
     

    Spoiler

    21/11/29 02:51:31.262 05560 -    ] # rxpGnsSim64.dll version 2.4.21.0
    21/11/29 02:51:31.261 05560 INFO ] 
    21/11/29 02:51:33.537 05560 INFO ] using: C:\ProgramData\Reality XP\Common\GnsTrainer\dbfiles\006-d0170-00.bin
    21/11/29 02:51:33.552 05560 ERROR] trainer not found
    21/11/29 02:51:33.573 05560 ERROR] invalid count for G530.1
     

     


  11. Spoiler

    // This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
    // Built Thursday, June 19, 2014 at 16:37 FSPS Build:22767
    [Window Titles]
    Window00=Main Panel
    Window01=GPS
    Window02=Autopilot
    Window03=Reality XP GNS Unit 1 (managed)
    Window04=Reality XP GNS Unit 2 (managed)


    [VIEWS]
    VIEW_FORWARD_WINDOWS=MAIN_PANEL,GPS_PANEL
    VIEW_FORWARD_DIR=10.000, 0.000, 0.000

    //--------------------------------------------------------
    [Window00]
    Background_color=0,0,0 
    size_mm=1024,768
    position=1
    visible=0
    ident=10
    //--------------------------------------------------------

    [Window01]
    Background_color=0,0,0 
    size_mm=1280,650
    window_size_ratio=1.000  
    position=2
    visible=0
    ident=GPS_PANEL
    window_size= 0.710, 0.552
    window_pos= 0.290, 0.480

    gauge00=rxpGNS2!GNS_430_2,640, 0,640,268
    gauge01=..\panel\PC6_XMLGauges!KR 87 ADF,  640,268,640,134
    gauge02=rxpGNS2!GNS_530_1,  0,0,640,468
    gauge03=..\panel\PC6_XMLGauges!FBS_GTX330,  0,468,640,170


    [Window02]
    BACKGROUND_COLOR=1,1,1
    size_mm=170,84
    window_size_ratio=1.000  
    position=8
    visible=0
    ident=Autopilot

    window_size= 0.400, 0.128
    window_pos= 0.500, 0.180

    gauge00=..\panel\KAP140_HSI!MV_KAP140_PopupDisplay,  0,0,170,84

    [Window03]
    size_mm=100,100
    window_pos=0.617188,0.201796
    window_size=0.382812,0.506144
    visible=1
    always_visible=0
    zorder=99
    background_color=0,0,0
    ident=15531
    gauge00=rxpGNS2!GNS_530_1, 0, 0,100,100

    //--------------------------------------------------------
    [Window04]
    size_mm=100,100
    window_pos=0.617188,0.707940
    window_size=0.382812,0.292060
    visible=1
    always_visible=0
    zorder=99
    background_color=0,0,0
    ident=15432
    gauge00=rxpGNS2!GNS_430_2, 0, 0,100,100

    //--------------------------------------------------------
    [Vcockpit01]
    Background_color=0,0,0 
    size_mm=256,256
    visible=0
    pixel_size=1024,1024
    texture=$vpanel


    gauge00=..\panel\PC6!PC6_Controllers,1,1,1,1
    gauge01=..\panel\PC6!PC6_SysEvents,1,1,1,1
    gauge02=..\panel\PorterSystems!PorterSystems,  0,0,1,1
    gauge04=..\panel\amsinterop!amsinterop,1,1,1,1
    gauge05=..\panel\MV3DSound!MV3DS,  0,0,1,1,SimObjects\\Airplanes\\MV_PC-6_Base\\PC6_XML_Sounds#80
    gauge06=TrueGlass!Core,0,0,1,1
    gauge07=RealLight!Core,0,0,1,1

    [Vcockpit02]
    Background_color=20,20,20
    size_mm=1024,1024
    visible=0
    pixel_size=1024,1024
    texture=$C310_VC_01
    gauge00=rxpGNS2!GNS_430_2,  0,451,640,262
    gauge01=..\panel\KAP140_HSI!MV_KAP140Display,  0,852,640,163
    gauge02=..\panel\KAP140_HSI!MV_KAP140Servos,  0,0,1,1
    gauge03=..\panel\PC6_XMLGauges!KR 87 ADF,  0,715,640,134
    gauge04=rxpGNS2!GNS_530_1,  0,0,640,448
    gauge05=Console!console_RXP_GNS530_430,  0,0,1,1

    gauge07=..\panel\PC6_XMLGauges!n1_2,  822,105,200,81
    gauge08=..\panel\PC6_XMLGauges!n1,  823,225,200,81
    gauge09=..\panel\PC6_XMLGauges!egt1,  822,376,200,81
    gauge10=..\panel\PC6_XMLGauges!np1,  822,860,200,81


    //---------------------------------------------------------


    [Vcockpit03]
    Background_color=0,0,0
    size_mm=2048,2048
    visible=1
    pixel_size=2048,2048
    texture=$VC_01
    texture00=RL_1, 0,0,2048,2048


    [Vcockpit04]
    Background_color=0,0,0
    size_mm=2048,2048
    visible=1
    pixel_size=2048,2048
    texture=$VC_02
    texture00=RL_2, 0,0,2048,2048


    [Vcockpit05]
    Background_color=0,0,0
    size_mm=2048,2048
    visible=1
    pixel_size=2048,2048
    texture=$VC_03
    texture00=RL_3, 0,0,2048,2048

    [Vcockpit06]
    Background_color=0,0,0
    size_mm=2048,2048
    visible=1
    pixel_size=2048,2048
    texture=$VC_04
    texture00=RL_4, 0,0,2048,2048
    [Vcockpit07]
    Background_color=0,0,0
    size_mm=2048,2048
    visible=1
    pixel_size=2048,2048
    texture=$VC_05
    texture00=RL_5, 0,0,2048,2048

    [Vcockpit08]
    Background_color=0,0,0
    size_mm=2048,2048
    visible=1
    pixel_size=2048,2048
    texture=$VC_06
    texture00=RL_6, 0,0,2048,2048

    [Vcockpit09]
    Background_color=0,0,0
    size_mm=2048,2048
    visible=1
    pixel_size=2048,2048
    texture=$VC_07
    texture00=RL_7, 0,0,2048,2048

    [Vcockpit10]
    Background_color=0,0,0
    size_mm=4096,4096
    visible=1
    pixel_size=4096,4096
    texture=$VC_08
    texture00=RL_8, 0,0,4096,4096


    [Vcockpit11]
    Background_color=0,0,0
    size_mm=4096,4096
    visible=1
    pixel_size=4096,4096
    texture=$VC_09
    texture00=RL_9, 0,0,4096,4096


    //--------------------------------------------------------
    [Vcockpit12]
    background_color=0,0,0
    size_mm=2048,2048
    pixel_size=2048,2048
    texture=$Int_TG_0

    texture00=TG_0, 0,0,2048,2048

    //--------------------------------------------------------
    [Vcockpit13]
    background_color=0,0,0
    size_mm=2048,2048
    pixel_size=2048,2048
    texture=$Int_TG_1

    texture00=TG_1, 0,0,2048,2048


    [Vcockpit14]
    Background_color=0,0,0 
    size_mm=512,512
    visible=0
    pixel_size=1024,1024
    texture=$C310_VC_02
    gauge00=..\panel\PC6_XMLGauges!FBS_GTX330,  0,0,512,135

    //--------------------------------------------------------

    [Vcockpit15]

    Background_color=0,0,0 
    size_mm=1024,1024
    visible=1
    pixel_size=1024,1024
    texture=$Bell_407


    gauge01=..\panel\PC6_XMLGauges!Chronometer,   270,410,630,630
    gauge02=..\panel\PC6_XMLGauges!C310_DME, 10, 0,300,80

    [Default View]
    X=0
    Y=0
    SIZE_X=8192
    SIZE_Y=6143
     

     


  12. Hi Jean-Luc,

    Thank you very much for your response - unfortunately I only just saw this.

    I have just re-installed the PC-6 on a new computer and will re-install the RXP software as well and report back as you have asked. The RXP is a great add-on and I look forward to getting it working.

    Thanks again. 

    • Like 1

  13. I discovered an update to the aircraft in the MV forums which supposedly addresses some "avionics" issues - this announcement was not specific.

    That is installed now, and the 430 is showing up in the 2D popup now, but the VC 430 is still dead.

    MilViz have expressed displeasure at the amount of time, money and effort they have had to expend dealing with issues that they claim arise from other products, and this one is on the list.


  14. I am trying to use the GNS 530/430 in the Milviz PC-6 in Prepar3D v4 but continue to have a lot of issues with it.

    I have had this gauge since June 2020, and used it without any trouble at all in the A2A light singles, plug-and-play, dead simple. I keep the gauge updated, most recent version is "rxpGNS2-FSIM-Setup 2.4.21.5" which still works fine in the A2A planes.

    I've been trawling the forums and the user guide and got to the point where I could get the knobs and buttons to respond in the VC, and was able to SHIFT+ right click on the bezel to do some configuring. However the 430 would only display in the 2D pop-up, and it was impossible to enter the configuration menu for the 430, only the 530. Trying to enter the Addons > RXP GNS menu caused the simulator to stop responding and I had to shut it down with the Task Manager. The 430 bezel in the VC was just that, with a blank screen, and was completely unresponsive.

    After re-starting the sim, I can now access the 430 configuration menu, but it is impossible to turn the unit on ie both the 2D and 3D versions of the 430 are completely blank.

    The GTN750 works perfectly well without all this faffing about. "Why would I want the 530/430?"  I hear you ask. Well, I suppose I still like to dabble with older technology sometimes and grew up using real Garmin 100s and KNL90s much earlier in life but never got to have a go with the later bigger Garmin units.

    I'd be curious to know if anyone else has had similar issues, and what configurations settings (if any) have proven to be ideal for this aircraft. The fact that the installation is configurable like this is theoretically a great concept but in this instance it seems unstable and unreliable and I have no idea if it's to with the gauge or the plane or both. I love it when things just work. I suppose one option is to choose just the 530 without the 430...

    I have seen some interesting questions in response to similar queries in the past, so please be advised that:

    1. Both the 530 and 430 are legally owned by me, are installed in the default location, are up to date, and work in every other addon that uses them.
    2. The GTN trainer is installed, hence why the 530 and the 430 work properly in all the other aircraft.
    3. P4D is v4.5.14.34698 and is working just fine. This is the only addon/combo I have a problem with.
    4. The aircraft in question works fine with and/or without this GNS installation.
    5. I am running Windows 10 with the latest updates installed.
    6. My AV has exceptions for every instance of anything to do with the sim and all the addons that I can find.
    7. I am posting this in the MilViz forum too.

    There is often a very simple solution or explanation but it's got me stumped, hence my appeal to the collective intelligence and experience out there in the forums.


  15. Hi folks,

    I just tried to PM Bill (whamil) to get his mods but he is not receiving messages. 

    Does anyone know how I can get the mods for the Carenado Cheyenne II. I've just re-installed it in P5D and am quite enjoying it in its raw state, but if there is some way of improving it I wold be most grateful. Also, do you think the III is worth a shot or is it simply not different or better enough to warrant the 15 cups of coffee it will cost to buy it? A Cheyenne 400 would seem like a good move up whereas the III is just a bit bigger, faster and flies a little higher. I fly for a living (Dash 8, A320, B737) so simming for me is a constant search for immersion and realism. A lot of these planes look gorgeous but the flying can let them down. So far I'm really liking the II without any mods. 


  16. On 5/20/2020 at 5:16 AM, Crossair_Pilot_Kevin said:

    Dear Community,

    Today I bought the Carenado ATR 72-500,after the Installation as an Administrator and turning my antivirus Software off I went into the Simulator to discover the plane. After I spawned I saw an FMC Message "Loading Database" which didn't disappear. I read that I should add some lines in the Lockheed Martin AppData File with these lines:

    <?xml version="1.0" encoding="Windows-1252"?>
    <SimBase.Document Type="Launch" version="1,0">
        <Descr>Launch</Descr>
        <Filename>dll.xml</Filename>
        <Disabled>False</Disabled>
        <Launch.ManualLoad>False</Launch.ManualLoad
            <Launch.Addon>
            <Name>Carenavigraph</Name>
            <Disabled>False</Disabled>
    <Path>.\Carenavigraphx64.dll</Path>
            </Launch.Addon>
            </SimBase.Document>
     

     After trying that it still didn't work,then I tried to add a file from a developer,and it also didn't work. I tried many fixes but this message is still there.

    May someone help me please?

    Regards,

    Kevin

    Kevin -  this is what worked for me. Go to %ProgramData%\Lockheed Martin\Prepar3D v...(whatever version yours is) and open the dll.xml with a text editor.  I added the following lines to the end just before </SimBase.Document> which should be the very bottom line:

        <Launch.Addon>
            <Name>Carenavigraph</Name>
            <Disabled>False</Disabled>
            <Path>.\Carenavigraphx64.dll</Path>
        </Launch.Addon>

    I saved it, opened the sim, and now the Carenado Navigraph database works as it should. I hope this helps. This is very similar to what you did but with the "other" dll.xml. I'm not sure what the difference is between them or why your fix didn't work. I'm using P5D and there is no dll.xml in the AppData folder, only the ProgramData folder.

    Cheers

     

     

     

    • Like 1
    • Upvote 1

  17. I just installed in P5D and the FMS doesn't work at all. It's stuck on "LOADING DATABASE". The rest of the aircraft seems to work fine.

     

    ***STOP PRESS***

     

    Problem fixed by editing dll.xml - the nav database updated properly and is working.

    About the only thing this FMS does is allow you to create a flight plan and then fly along it. You can create a flight plan using airways, however once you get going, the flight plan doesn't update as you move along. In other words, the TO waypoint doesn't sequence in the LEGS page. The PERF pages show the fuel flow, but not the fuel used, and there is still that 380 lbs or kgs of APU fuel that has been in every FMS since they started making them. It never changes and doesn't do anything.


  18. Hi Kevin,

     

    I just sent you a PM in the hopes that I can get my Chase Plane reactivated. I just uninstalled it from my laptop but the main PC won't let me use it as I have exceeded the number of computers allowed. I'm not planning to use it on the laptop at all from now on.

    Cheers,

     

    Chris Allan,

    Oz

×
×
  • Create New...