Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/13/2022 in Posts

  1. Another update. Though its been quiet here, it is still very much full speed on my end. There simply is a lot of infrastructure work and double-checks to get ready for release. One of the things I'm doing is moving the documentation to be browser based. That was a bit of a last minute decision but one I think will pay dividends moving forward. This makes the documentation searchable and navigated much more quickly and in addition, much easier to update and read IMO. I also forsee the need to facilitate tutorials and such and this format will allow the addition of such material to be added more quickly and presented more effectively. This infrastructure will also serve as a foundation for similar documentation efforts we plan to bring to the ixeg 737. We should be able to publish the docs to PDF also for those that desire such. The paint kit is also complete, which required its fair share of prep and documentation also. The documentation will probably drag on another day or two. At this stage, its looking like early June release. I will say I'm disappointed its not in the 3 week time span I had hoped and predicted, but not disappointed with why...because I simply want to refine lots of little things to ensure its a first class simming experience and its coming along very well. -tkyler
    5 points
  2. Patience, please. There’s another big update coming.
    4 points
  3. Quick report. I'm moving things back oh so slightly. At this point, I'm updating the docs and working on the sound engineering. The sound is the long straw here, FMOD is a bit new to me and quite intimidating for first timers and taking a bit more time than I hoped to get up to speed..... and I'm quite picky about sound. I am still working on it daily and safe to say that when the sound is done, we'll get it out. I won't say when, but I myself will be quite disappointed if its more than 3 weeks. -tkyler
    3 points
  4. Update: The ATS works just fine with non-persistent mode. The ATS FAIL is there as soon as I turn on the APU GENs. I will just use a new airframe for tonight. I have the old one saved in case someone wants to debug further, but as long as the new one works, the issues is resolved for me. Thanks again for your help.
    1 point
  5. Very well done Marco. Congratulations. Cheers. Best wishes ... Carsten
    1 point
  6. Ok, then you should disable whatever blocked that file from being installed and run the CL-650’s installer again. If you’re generally concerned about PC security, reasonably so, run the subsequently installed XPL file through VirusTotal before starting the sim, you’ll find it’s “clean” and safe.
    1 point
  7. Can you check if this file exists …/X-Plane 11/Aircraft/X-Aviation/CL650/plugins/systems/win_x64/systems.xpl ? I’m guessing your antivirus has blocked the install or loading of this code.
    1 point
  8. I'd like to request commands for Ground Services -> Refuel -> Refuel Truck Ground Services -> Refuel -> Interior Refuel/Defuel panel So that I can map keyboard shortcuts to these pop-ups. Thanks!
    1 point
  9. Most likely you don’t have the Gizmo plugin installed or running. Please check your Log.txt.
    1 point
  10. Hi guys, some work-in-progress shots for: a) a 'Go Fly' fleet pack (c.2002) b) a Jet2 fleet pack (featuring G-GDFG, FK, FL, FM, FN, FO & FT)
    1 point
  11. Thanks guys, I only have XPUIPC installed because a VA 'tracking' plugin requires it to read sim status, I don't use any of it's control assignment features. BTW I found 2.0.4.7 here: https://vasystem.org/support/vas-acars/x-plane/, So will give that a go. Grateful to hear others don't have the issue between the IXEG737 and the FF757, suggesting it's a local issue.
    1 point
  12. Hi Coop, I have the same problem with Pocket Rocket. I loaded the oldest NVIDIA driver compatible with Windows 11 and it still won't work. The X-Plane 11.55 start-up screen simply disappears briefly after the plane starts loading. Log file attached. Regards, Sjors Log.txt
    1 point
  13. Problem Found. After I had installed the RSG G5 V2.0.1, my Reality XP GTN650 was no longer activated. It occurred to me if the GTN650 had been deactivated, perhaps its settings had also changed. Sure enough "Connect HSI/CRS (auto-slew)" was not selected. I selected it and now DTK agrees between the G5 and the 650.
    1 point
  14. Attempts to contact the xpuipc author were unsuccessful. Xpuipc is unsupported and known to cause issues. Removal or exploring older versions are your only options.
    1 point
  15. If you mean whether it will release this weekend, I don't think so. Tom posted a quick update last week, where the time frame sounded more like end of May - cf. this post:
    1 point
  16. Thanks Goran, appreciate your presence here!
    1 point
  17. Ah. Unfortunately that really only works with default/basic aircraft addons, not complex third party ones with custom systems like the CL-650. You’ll need to use the 650’s own state saving system via Airframe Manager.
    1 point
  18. Hi guys, had our pilots take this little video on the aircraft VID-20220510-WA0004.mp4
    1 point
  19. Thank you for keeping us updated! Really looking forward to this model!
    1 point
  20. Captains, In the days since release of the Hot Start Challenger 650 there have been concerns that Gizmo and even the Challenger 650 plugins were causing a major performance impact. We went investigating this, and even got Laminar Research involved to understand what was happening under the hood of X-Plane to try and sort this out. As it turns out, Gizmo is NOT the source of problems, and neither is the 650 plugin; not directly, anyhow. What's happening is somewhat complicated, but I'll do my best to be descriptive, yet brief. X-Plane is programmed to use up all of your CPU cores in order to try and attain higher frame rates. In doing so, there's some major texture paging going on. The problem here is that it leaves almost no room for the Challenger to get its CPU operations done in the process, and mixed with a ton of texture paging, everything goes bust and tasks get stuck in a queue where X-Plane drastically slows down, things pause/stutter, and the experience becomes abysmal. If you happen to have your Plugin Manager open in X-Plane while this happens it will present itself as if Gizmo or the Challenger are using up an insane amount of performance, but this is actually just a mean trick when looking at it from a user perspective. X-Plane slows down so much that it LOOKS like our plugins are to blame as their tasks are not yet performed while X-Plane does other things. Before I go further, I should note, this is NOT applicable to everyone! Most customers here seem to have a great CPU/GPU combination that can handle all of this, but if you're one of the people on the struggling end of the spectrum, you'll want to keep reading this post! Version 1.1.0 of the Challenger 650 introduces a new installer that has a selection for GPUs with more or less than 6GB so we can best optimize your install for you. This will help with some of the VRAM/texture paging operations. That said, there's still more to the puzzle. Because X-Plane is using all the cores/threads on your CPU, it is not saving "room" for the Challenger 650 to do its operations efficiently and the CPU becomes oversubscribed. Laminar Research is likely to fix this issue for developers at a later date after X-Plane 12, so in the meantime we have a workaround to use that Laminar has sanctioned to give out to those affected. If you are affected by this issue, please do the following (this is for Windows users, as the issue seems most prevalent with Vulkan): 1. First, find X-Plane's application and create a shortcut so that we can create parameters. Right click on X-Plane > New > Shortcut 2. Right-click on your shortcut, and select Properties on its contextual menu to open the shortcut's Properties window. 3. The shortcut's Properties window is the place where you can add command-line parameters for that shortcut. Select the Shortcut tab and look for the Target field. 4. You will see a place that has the path to X-Plane labelled Target. X-Plane's path will be in quotes. At the end of the quotes, make sure there is a space after the quotes, then type/paste: --num_workers=n <==Replace the red 'n' with two less CPU cores/threads than your CPU has. As an example, if you have a 6 physical core + 6 virtual core CPU (known as Hyper-threading for Intel, SMT for AMD) for a total of 12 threads, you should put the number 10 in place of the red 'n'. Also be sure you have the TWO hyphens/dashes in front of 'num_workers'! 5. You can now rename this shortcut to something like Challenger 650 if you like. That way you can just click this one when you know you'll be flying the Challenger. If you are unsure how many CPU cores/threads your CPU has, go into your About Computer setting and Google your CPU model number to find out. Be sure to use the total number with Hyper-threading/SMT as your starting point! We know this is a bit unorthodox, but we're doing our best to make whatever solutions we can for as many people as possible. Hopefully this makes your flying more enjoyable!
    1 point
  21. Hi, thought I’ll show the electrical panel . Still not wired but Almost there . ive decided to paint the panels all in black , think it provides a better contrast with the white backlight . I know it’s not like the original grey-ish , but hopefully I won’t regret it later requires the bolt cutouts painting ..
    1 point
  22. How about a time line(if possible) and an upgrade price from v1.9(if possible)? The reason I ask is because this plane has really piqued my interest in the MU-2 again and I'm not sure I can wait for v2, I might just buy V1.9 the pay for the upgrade later, depending on the timeline and upgrade price. If it's days I might be able to wait, if it's months there is no way I'm waiting.....
    1 point
  23. The Hot Start Challenger 650 is a proper simulation. The way weather works in X-Plane 11 isn't conducive to a realistic weather radar simulation. Right now it appears that X-Plane 12 will be able to facilitate the radar.
    1 point
  24. You're welcome. For anybody else wondering what is actually being discussed here, it's the flightplan equipment codes that indicate the aircraft navigation and communication capabilities. M-SBDE1E2E3FGHIJ1J4J5J7M3RWXYZ/LB1V1D1 M Medium Wake Vortex Category S Standard Com / Nav Equipment B LPV SBAS D DME E1 FMC WPR ACARS E2 D-FIS ACARS E3 PDC ACARS F ADF G GNSS H HF Radio I Inertial Navigation J1 CPDLC ATM VDL Mode 2 J4 PDLC FANS 1/A Mode 2 J5 CPDLC FANS 1/A Inmarsat J7 CPDLC FANS 1/A Iridium M3 ATC RTF Iridium (Aircraft Number on FPL) R PBN Approved W RVSM Approved X MNPS Approved Y VHF 8.33 Channel Spacing Z Other Equipment L Mode S Transponder with ES B1 ADS-B Out via 1090 ES V1 ADS-B Out via VDL Mode 4 D1 ADS-C with FANS 1/A PBN/A1L1B1C1D1O1S2T1 A1 RNAV 10 (RNP 10) L1 RNP 4 B1 RNAV 5 all permitted sensors C1 RNAV 2 all permitted sensors D1 RNAV 1 all permitted sensors O1 Basic RNP 1 all permitted sensors S2 RNP APCH with BARO-VNAV T1 RNP AR APCH with RF (special authorization required) DAT/1FANSER2PDC 1: FANSER Primary: CPDLC-DCL and en route clearances. 2: PDC Secondary (will be used if primary is not available) SUR/260B Compliance with RTCA DO-260B (Minimum Operational Performance Standards for 1090 MHz Extended Squitter ADS-B and TIS-B RSP180 Aircraft is authorized for Required Surveillance Performance RSP180
    1 point
  25. That did the trick! I totally missed the maintenance menu. Thanks for the prompt support. R
    1 point
  26. @Champguy The answer is already in this thread to not start with engines running. Additionally, this IS documented in the included documentation. You could have entirely avoided that by reading said documentation.
    1 point
  27. @ChampguyThis aircraft does not go into "crash mode" right out of the box. Or hundreds of users would be posting here. There is something else at play and it's on your "side" of things. Why not attach a log.txt from a flight where this occurred and let some of the experts here (not me) have a look.
    1 point
  28. On a recent flight on our company CL650 I noted a small difference with our Hotstart CL650: the levers are silver rather than black. Apparently the 605 was black, but the 650 is silver. Can someone confirm this? Maybe Rich?
    -1 points
×
×
  • Create New...