Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 04/20/2022 in all areas

  1. I don't think I'm going to make it in April Marco.....though I am very close to wrapping things up. Targeting first half of May it looks like now. Right now there is a lot of quality control checks being done. With 3 variants it is quite a lot of flight testing. The last week has been compatiblity work with all the probable hardware configurations and setting up the preferences etc. All the lighting / night lighting is done and the only thing that remains is a punchlist of small items, a few more liveries to do and the last thing will be the sound. This certainly won't drag out, there is nothing else on my plate and this work is all day every day for me until release. -Tom
    15 points
  2. 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
    11 points
  3. Version 1.0.0

    78 downloads

    Jet Edge now operates Challenger 605s as part of their branded fleet. Jet Edge is based in Southern California and was bought in 2022 by Vista. This is in no way affiliated with Jet Edge and is offered for free for community enjoyment only. Please do not modify and redistribute without permission.
    6 points
  4. 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
  5. Patience, please. There’s another big update coming.
    4 points
  6. Captains, It's with a lot of excitement that I get to announce this product officially now! Back in 2008 we started X-Aviation with the MU-2 as our first product for sale, and now we're re-inventing it with this beautiful new version. Many people in the X-Plane community found the original v1 we sold as one of their very first payware aircraft back in the day. Today will be the first of a series of progress updates leading up to the forthcoming release of the Mitsubishi MU-2B-60 Marquise 2.0 simulation for X-Plane. Since its beginnings in 2005, the MU2 has been a labor of love by @tkyler and has been nursed for 13 years and for the upcoming 2.0 release, has incorporated the latest X-Plane features. The MU2 is poised to last for many more years to come and certainly through future versions of X-Plane. We are also pleased to announce all previous owners of v1 will be receiving an upgrade discount to v2! The MU-2 is a perfect GA airplane to have in your hangar and get you around X-Plane quickly when you need to feed your flight simulation addiction and actually cover some ground but don't feel like flying tube-liners. With its distinctive profile, engine sound and a cruise speed of 270+ knots, it can cover a lot of X-Plane scenery in a simulator session and have you off the computer before dinner time. In this first report, we'll discuss the most obvious improvement in version 2.0, the visual 3D model and textures. When looking at the MU2 Version 1.0 series 3D, it it quite apparent that there was major room for improvement (mind you this was X-Plane 9 days). As it turned out, trying to remodel the existing 3D was not a viable option and the 2.0 version had to be completely redone from scratch. There are a few noteworthy factors that have enabled the improvements to the 3D detail. Major advancements in Blender 3D, the modeling tool used as well as advancements to the exporter by Laminar, have facilitated a painless workflow between Blender and X-Plane, allowing focus on the geometric detail. In addition, the capability of today's graphic cards to handle fantastic numbers of polygons and high-resolution texture sets have really taken the visual aspect of flight-simming to a level barely imaginable a decade ago. The first order of business was to increase the geometric fidelity of the model and get the challenging shapes and curves more accurate. It is a difficult aircraft to get to look right. Increased geometric fidelity results in much sharper and crisper detail at close camera angles and generally a more natural look all-around. The two images below shows the Version 1.0 3D model against the Version 2.0 3D model. Version 1.x Wireframe Version 2.0 Wireframe If you study the two images above, you will see version 2.0 has a higher density 3D model all around; however, note the darker areas of the 3D wireframe mesh. These are areas where higher 3D detail has been applied in order to achieve sharper visual results that reflect light more realistically as you move the camera around. The traditional way such details are added is through the use of higher resolution texture "decals", much like the decals on plastic models. While decals are a great technique and absolutely useful, they do lack the accuracy of subtle light interaction around geometric edges at closer camera angles. Lighting details on 3D edges have always been one of those areas that make the difference between a fake looking 3D model and one that comes alive. The image below shows a few areas where the 3D detail makes a difference to the lighting. Though higher detail is applied where it counts, it wasn't added where not needed, yielding an efficient 3D model that is very performant in X-Plane. With the 3D detail in place, you have to bring it alive with texturing. X-Plane's PBR (Physically Based Rendering) has always yielded a wonderfully crisp and beautiful color palette when taken to its limits, and X-Plane 12 looks to improve that even more when it arrives. One critical component of believable texturing is a solid implementation of what is known as 'ambient occlusion', or AO as 3D artists like to say. AO is a phenomenon where light loses energy as it bounces around into corners, resulting in darker corners and recesses. Below is a comparison of a 3D model with and without ambient occlusion. The results are quite stark! AO in real time for lots of 3D polygons is still quite performance heavy. X-Plane actually has a small bit of real time AO between the ground and airplane when in HDR mode. You may note the subtle darkening of the ground around the landing gear tires sometime as aircraft taxi; however, X-plane provides no AO effects for aircraft. We obtain this AO effect by "painting" the shadowing into our textures. This is a process known as "baking" in the 3D community and our 3D software tools actually do most of the painting work for us. By baking AO effects into our textures, we can achieve a much more realistic lighting look throughout the 3D model. Baking AO lighting though is a bit of an art and can be a bit time consuming but when done well, the results are quite immersive! AO really shines when applied to interior spaces, giving lots of visual depth and avoiding that flat, cartoony look. When all of the 3D elements come together: the geometric 3D detail, attentive ambient occlusion effects, PBR texturing and X-Plane's great PBR engine, the results are exactly what we've been waiting for 13 years! A SPECIAL NOTE is warranted about this last screenshot. We include it because it shows the 3D detail and texturing in the cockpit at its best! However, the G500/600 GLASS display shown will NOT be included with the MU2 purchase. It is a separate product available by Real Sim Gear through X-Aviation, but for those folks who wish to have some glass in their MU-2, then you'll be happy to know that we support it fully and it will be available straightaway when the MU2 is release for owners of the Real Sim Gear G500! In our next progress update, we'll talk about the cockpit variants, controls and animations and how they play a major role in our immersion! Until next report, Blue Skies and tailwinds!
    3 points
  7. Version 1.0.0

    55 downloads

    N670BP is a Challenger 605 presented here for the Hot Start Challenger 650. Please do not modify and redistribute without permission.
    3 points
  8. Version 1.0.0

    37 downloads

    Fictional - AirShare only operates Challenger 300s but here's their livery on the Challenger 650. This is in no way affiliated with AirShare. Please do not modify and redistribute without permission.
    3 points
  9. Hi Pils, I contacted my retired Collins customer liaison/training pilot about this behavior. He gave me a good explanation of how this works. When you enter the ORIG and DEST airports, you create two DEP/ARR page selection "silos", one for the ORIG airport and one for the DEST airport. On the ground, or airborne within 50 miles of the ORIG or less than 1/2 way between the ORIG and DEST airports if the distance between the two is less than 100 miles, the first press of the DEP/ARR key bring up the DEPART page (if on ground) or the ARRIVALS page (if airborne) for the ORIG airport. The second press brings up the DEP/ARR INDEX Page, where you select DEPARTURE or ARRIVAL page for either the ORIG (first option) or the DEST (second option): In the air, the first press of the DEP/ARR button bring up the ARRIVALS for the ORIG airport is less than 50 miles or less than 1/2 of the distance between the two airports if they are separated by less than 100 miles. More than 50 miles or more than 1/2 of the distance between the two airports, it brings up the ARRIVALS page for the DEST airport. These are the two "silos" ARRIVAL options that can be selected once airborne. The engineer's intent was that in an emergency return the departure airport, the pilot will want quick access to the approaches available at the departure airport, which is why the first key press of the DEP/ARR key brings up the arrivals for the ORIG airport. The closer the two airports are together, the greater the chance the airport selection can confusing. For example, a short flight from Wichita - Eisenhower (KICT) to Wichita - Jabarra (KAAO), separated by about 10 miles. After takeoff and while getting radar vectors to Jabarra, if you load the approach and complete the landing data on the APPROACH Performance page, but then for whatever reason start getting vectors back to towards KICT and the distance to KICT becomes closer than KAAO, the FMS can think that you're now trying to return to KICT, the FMS has moved back to the ORIG silo and the APPROACH Performance page has moved back to the ORIG airport and as result has dropped the V-Speeds and performance data. If you look on the APPROACH REF page of the FMS, there are two airports - the ORIG and DEST: The FMS has gone back to the ORIG airport in this case and dropped the V-Speeds. It gets more confusing when you're in a round-robin training mode, for example the ORIG and DEST airports are both "KICT". in the air If you press the DEP/ARR key, the FMS brings up the ARRIVAL page for the ORIG airport, KICT. If you load the approach and then complete the APPROACH REF page based on the ORIG airport ARRIVAL loaded in the FMS, as you fly downwind for the return approach, at some point the FMS will think it's more than 1/2 way away from the ORIG airport and switch to the DEST airport's silo, and its APPROACH REF page is blank because you have not entered any data for this runway. The FLT PLN and LEGS page still show the approach you selected using the ORIG airport, but the Performance page has switch from the ORIG airport to the DEST airport. If you press the DEP/ARR key twice to bring up the DEP/ARR INDEX page, select the approach from the DEST airport (i.e., the second airport in the list) AND....you select the DEST airport on the APPROACH REF page (i.e. the second airport option - in the example above that shows KMSP/KLAX, select "KLAX") you are less likely to have the V-Speeds dumped. He says it's not impossible, but much less likely. Again, if you turn back around and it thinks you're going back to the ORIG airport, the FMS can switch back to the ORIG airport performance page. The behavior I was seeing in HS CL650 did initially mimic this behavior, and it's what I have seen in the Level D CL300 simulators when we're doing circuit training, i.e. multiple back to back approaches. What I was also seeing in HS CL650 was the FMS drop the V-speeds multiple times on final. My contact says that should not happen. As long as you're in one branch or "silo" of the ORIG or DEST airport, the V-Speeds should not drop unless you switch silos, which is not likely as your final approach and you've set one or the other branch/silo - the ORIG or DEST. Please let me know if this makes sense? Thanks! Rich Boll
    3 points
  10. Hi Coop... So I unplugged the monitor, and then ran it from the laptop monitor and yes, the Gizmo login screen was visible! I logged in and now the G5 works. So the key point I learned is to open xPlane11 with just the one screen and the login is visible. thanks for your help. Paul
    2 points
  11. Hi guys, had our pilots take this little video on the aircraft VID-20220510-WA0004.mp4
    2 points
  12. I hope so too Jan! An aircraft much loved in the XP community of course: deserves all the TLC you can give it.
    2 points
  13. My European brain can't fathom routes with discontinuities in them! Direct direct direct with no airways please! FMS-6000 doesn't allow this and the 605/650 manual words it almost identically to Textron's PTM. Filed up for fix, nice one!
    2 points
  14. Version 1.0.0

    19 downloads

    N908WS is a fictional Challenger 650 paint loosely inspired by several existing Challengers and Globals. Please do not modify and redistribute without permission.
    2 points
  15. They are still looking for staff at the NTSB Rich!
    2 points
  16. I have to laugh at this. I have worked on various industry & FAA working groups for last 18 years. We see these discrepancies flying, and now they're following me into the flight sim world! Gotta love it! Thanks for hunting this down! Again, kudos for HS CL650! Rich Boll
    2 points
  17. Hi Skiselkov, Explanation makes perfect sense and the issue is actually quite well known in the real aviation community. MagVar discrepancies between the aircraft, the IRU, the procedure source (i.e., the 8260 Forms) have been a known source of problems on instrument procedures for a long time. It resulted in a real mess in ORD last Fall on the STARs. it's also the the reason why we lost a bunch of CAT II and CAT III approaches in the US a few years ago for older airplanes where the The fact that you have modeled these MagVar discrepancies between the avionics and the procedure source data (i.e., 8260 Forms in the US) is another feather in your cap. I've never seen this discrepancy modeled in a flight simulator product before, so I did not even occur to me that this could be the issue. Been a lot of talk of going to True in various part of the world. Airbus and Dassault are pushing for it. Again, excellent job with the HS CL650! I withdrawal the issue. Thanks! Rich Boll
    2 points
  18. I had a look at this and it doesn't appear to be a bug or badly implemented track indicator. What you are seeing is the accurate magnetic ground track donut. The problem appears to be that the database-provided magnetic variation for the Pine Bluff VOR/DME is incorrect. You are quite correct that the databases say it's 4°E. However, and here's a funny one: the Pine Bluff airport near to the VOR/DME is is declared as 2°E: Now, as to how the airplane knows its magnetic heading - the IRSes contain a magnetic variation database, which is valid from 2020 through to 2025. The IRS feeds the current date + position and this database computes the actual magnetic variation expected at that position and that's what you're seeing on your avionics. And here's the kicker: the magnetic variation database says the actual magnetic variation should be around 0.3°WEST: Similar results using the IGRF magnetic model: You can run the computations for select positions yourself here: https://www.ngdc.noaa.gov/geomag/calculators/magcalc.shtml Investigating enroute charts, there's a 3 degree declination change over the span of a mere 65 miles. This seem to suggest that the Pine Bluff VOR/DME is misaligned and needs to be realigned IRL: To summarize: doesn't look like a bug to me. Seems more like either the navaid is misaligned IRL, or the navigational database needs to be updated.
    2 points
  19. 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 ..
    2 points
  20. Hi all, changes have been made to the beta build to eliminate this behaviour. This will be included in the next release.
    2 points
  21. This isn't just about online ATC programs--the nonstandard altimetry breaks compatibility with other utilities that determine altitude using the provided X-Plane dataref. Why can't Hot Start just provide a user switch to turn the "realistic" altimetry off? It's got to be a whole lot simpler than auto-detecting online communications from specific ATC programs, and it would preserve the option to employ the standard interface to X-Plane. This *is* a Hot Start issue--this is the *only* add-on I am aware of that chooses to do its altimetry independently of the X-Plane platform dataref, which breaks compatibility with anything not specifically coded for that...in other words, lots of stuff. In my case it's Radar Contact v4, which is not being developed any longer but which works flawlessly with any aircraft that adheres to use of the standard platform dataref. It's also an issue with the Pilot2ATC and PF3 offline ATC add-ons as well. Why is it considered preferable to build complex auto-detection routines in for a select group of ATC clients, rather than just allowing the user to de-select the nonstandard HotStart altimetry with a tickbox?
    2 points
  22. Version 1.0.0

    105 downloads

    Hello everyone, here is the livery of the executive Qatar Cl60. Enjoy!!
    2 points
  23. 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
  24. 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
  25. 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
  26. Version 1.0.0

    15 downloads

    French registered Challenger 650
    1 point
  27. Simmers don’t verify their flight plan fully every time?? I’m shocked, shocked I tell ye.
    1 point
  28. Captains, This will serve as a formal forum announcement that we have released the version 1.1.0 update for the RealSimGear G500 Avionics Suite. All customers who have purchased the G500 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the G500 from today forward, your purchased download will already be updated to version 1.1.0 for you. Please Note: This installer will update the Cessna 172SP, BN-2B/2T Islanders, as well as any other aircraft you have previously installed the G500 too. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original G500 Avionics Suite download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Improvements/Bug Fixes: [T-390] Add support for RealSimGear G500 hardware [T-359] Add option to rescan for RealSimGear displays in-sim Misc bug fixes and improvements Updated internal frameworks and libraries As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.
    1 point
  29. View File AirShare Challenger 650 - N725AS Fictional - AirShare only operates Challenger 300s but here's their livery on the Challenger 650. This is in no way affiliated with AirShare. Submitter reversethrust Submitted 05/02/2022 Category Hot Start Challenger 650 Livery For https://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-challenger-650-p-212  
    1 point
  30. I figured it out. It was my joystick that needed to be recalibrated
    1 point
  31. I’ve had this happen as well. The issue was that VNAV and managed speed were engaged during the cruise and the cruise speed was selected as LRC. At some point the FMS went nuts and computed the LRC speed as Mach 0.4, which causes the power levers to idle and the speed to drop and the autopilot disconnects so the airplane… spirals slowly into the ground. My solution until a fix is implemented is to manually select speed (cyan indication vs. magenta) if I need to leave the flight deck, as well as always saving the airframe state before walking away. You can confirm this is the cause by looking at the FDR report for your flight in the XPlane outputs folder. Check out the selected speed column and see if you find a super low speed right before the spiral.
    1 point
  32. Version 1.0.0

    16 downloads

    This specific aircraft is owned by European Flight Academy and is used for the training of student pilots who are currently in the proccess of obtaining all the licenses required to fly airliners. N832EF is a 2017 Cirrus SR20 G6, equipped with the Cirrus Perspective avionics suite and a lovely blue bird at the back. To install the livery, drag and drop the folder called: 'EFA Lufthansa N832EF' into X-Plane 11/Aircraft/X-Aviation/TorqueSim SR20/liveries. NOTE: Please do not change the registration in the livery manager as this can do some magic ending up with a broken livery. I love making all this stuff for free and will happily continue doing so, but if you feel like buying me a coffee, you can do so here: https://paypal.me/notgmcm?country.x=NL&locale.x=nl_NL
    1 point
  33. AH2 also has rudimentary GPWS call-outs (for some reason).
    1 point
  34. 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
  35. Challenger 650 - Hamilton Livery (G-LCDH) View File This is the first livery I make. I start by saying that as a basis I looked at that of MadProf whitch i thank This livery will not be updated, except in case of visual bugs that ruin its appearance. But I accept any advice for future ones. Features: Custom PBR metallic effect Custom Interiors Submitter CptHeike Submitted 04/05/2022 Category General Aviation Livery For https://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-challenger-650-p-212 X-Plane Version(s) X-Plane 11  
    1 point
  36. Version 1.0.0

    465 downloads

    Based loosely off of the real world G-LCDH but with my own flair! Presented with a fictional registration (M-DPRF) as she is based in the Isle of Man but you are free to change the airframe registration to your preference in the Hot Start Airframe Manager. Features: Beautiful custom PBR metallic effect Adjusted AO layers Colour-adjusted exterior labels Custom antenna colours Not to be distributed or copied without explicit permission.
    1 point
  37. @zrh28 apologies for the radio silence here. At this point in time work is ongoing on new features and outstanding bug fixes. It is worth mentioning that any new features have been in the works for a long time and are not taking precedence over the start of VR work. As there is no official development roadmap I cannot give you a timeframe of when VR compatibility will happen. I can tell you however that it is most definitely on the list as a significant minority of customers are VR users. Brgds
    1 point
  38. I will take care of the XMidiCtrl integration
    1 point
  39. for the record.....I am absolutely willing and anxious to look at popular 3rd party products and integration with such; however, only after I get everything working smooth with default X-Plane first. So any love for these 3rd party add-ons will have to wait until after release. The G500/600 received a little extra love because a lot of MU2s have these nowadays and the integration was discussed early in the MU2 rework with the G500/600 developer. The weather radar specifically is a bit of a odd duck at the moment in that we are close to transitioning to XP12 with its completely new weather engine and possibly new weather radar....so the weather radar is not getting any love at this instant and will initially ship with default XP11 weather radar. I want a properly functioning "old school" radar for sure, but am currently in a 'wait and see' with XP12 being around the corner. I do not have visual 3D icing effects yet but intend to. I'm reluctant to quickly toss on 'stacking show/hide polygons' to simulate 3D ice buildup as I think its a bit cheesy. For myself, given the choice of "do nothing" vs. "do something, but it looks kind of cheesy to me", I'd rather do nothing until I can do it to what I feel is a quality implementation. As far as whats "planned", all I can say is "everything I can"....in due time. The Moo is really a labor of love and I have quite a long list of extras I want to add to it once this new foundation is in. Right now its 10 things at once leading up to release, but afterwards, I can begin developing high quality extra features that will really improve the Moo experience. 2022 is basically slated for IXEG and Moo improvements. -tkyler
    1 point
  40. we are looking into it. We have reached out to Reality XP but have not heard back yet. I certainly want to, but if/when it happens, it will be after the initial MU2 release stabilizes a bit. I have been planning for it however.
    1 point
  41. Version 1.0.0

    36 downloads

    Hello, I present to you the livery of the Danish Air Force. Enjoy!!!
    1 point
  42. Version 1.0.0

    64 downloads

    About This File This is a repaint of a RCAF Challenger 650 for the excellent HotStart 650. More information on the real life aircraft can be read here http://www.rcaf-arc.forces.gc.ca/en/aircraft-current/cc-144.page To install, place the RCAF folder into \X-Plane 11\Aircraft\X-Aviation\CL650\liveries Thank you for downloading Paul Edwards
    1 point
  43. Version 2.2.0

    968 downloads

    This is a 3D model of the Challenger 650 for use when flying in online networks like VATSIM. This will be visible for multiplayer traffic flying type code CL60. Downloading and Installation Instructions: Download and then extract the CL60 folder into your pilot client CSL folder (X-Plane 11/Resources/plugins/xPilot/Resources/CSL/Bluebell/ for default installs) to see this model. This model includes lights (Nav, Beacon, Landing), retractable gear, and rotating engines. There are also animated Flaps, Spoilers, Speedbrakes, and Taxi Lights, but there appears to be some dataref issues (these don't appear to animate in the sim). Hopefully we can have HotStart resolve with future updates! I do hope that we see a proper CSL done by Hot Start and the goal wasn't to replace that, but in the meantime I hope the community can enjoy this work! This model uses some parts from the XCSL C750, which were shared with permission. Please do not resell this work. Thank you!
    1 point
  44. Acutally great if misuse failures could be implemented as opposed to random...
    1 point
  45. Version 0.0.2

    211 downloads

    Challenger 650 from REGA - Swiss Air Ambulance STILL A WORK IN PROGRES!
    1 point
  46. Version 1.0.0

    93 downloads

    Repaint based on T-752 Swiss Air Force Challenger 604.
    1 point
    Beautiful livery, Plz make more liveries for the 734 RG Mod
    1 point
  47. Version 1.20b

    176 downloads

    ACF Mesh Tools for Linux, Windows and MacOsX ACF Mesh Tools allows you to edit and modify the plane's meshes from the ACF file. Be aware: those tools are not made to edit the OBJ8 files as they work only with the ACF file format. HOW ACF MESH TOOLS WORKS Let's take as example the default Laminar's Cessna 172, a great model very well done (aestetically and internally). We know that in Plane Maker the fuselage is made out of cross-sections: ...and those cross-sections creates a mesh: Those meshes, made out of cross-sections, are the ones that PlaneMaker uses as model for the plane and X-Plane uses for its physics calculations. Before v.8 that meshes were used as visual and physics model. Now, in most cases, this meshes are hidded from view and X-Planes uses a dedicated file, in OBJ8 proprietary format, for the visual rendering. Using the tool 'acf_mesh_extract', the meshes inside the ACF are saved in a standard Wavefront OBJ file, that can be edited with Blender or with any other software that supports the format. Once converted, the mesh can be modified: Then the edited mesh is converted back in ACF format, using 'acf_mesh_insert', and the resulting ACF file can be loaded in Plane Maker: Everything shown here was entirely done automatically with a conversion script. Except moving the points to alter the shape, no additional task has been done in Blender. I'm using Blender, but this method can be used with any 3D software. A PRACTICAL EXAMPLE This is a quick reshaping that I've done on the fuselage of B-377 Stratoscruser made by Kauffmann. I've found that the hidden fuselage doesn't match the shape of the plane model, the visual one, as we can see in Plane Maker and in the version imported in Blender: (the wireframe in black, the unselected one, is the OBJ8 mesh for this plane; the selected object is the fuselage mesh from the ACF file) After a quick reshaping, I've managed to make che ACF mesh match the shape of the OBJ8; then and I've reimported it back in the ACF file: Loading the resulting ACF file in PlaneMaker we see that the cross-sections have changed from this: to this: THE TOOLS In the zip file you'll get: acf_mesh_extract acf_mesh_insert Launch those commands without options to get an help page. acf_mesh_extract extracts all the meshes from the ACF file and converts them in a single (wavefront) OBJ file with multiple objects. You can import this file in any 3D software that supports the format, and alter the meshes as you wish. You can not delete or add points nor change in any way the topology; you are just limited to move points. You'll find that some objects, like the engine's nacelles, are not in their final position; that is because PM positions them with a translation value. You can not move those objects to their final positions, otherwise when you'll reimport them back in the ACF file, it won't work; You are allowed to delete objects that you don't need. Some objects, although they can be modified and reimported in the ACF file, once this one is opened in Plane Maker are reset to their original shape; this applies to those parts, such the wings, that are made out of airfoils. You can not alter the UV informations of the vertices, as they are used to store the ACF's topology informations and they are needed later to reinsert the meshes back in the original file. Make sure that your 3D sofware exports the UV informations, without altering them. acf_mesh_insert allows to reinsert the modified meshes back in the original ACF file. It can be used only with meshes converted with 'acf_mesh_extract'. You can not overwrite the original ACF file; this command will save the output in a different file. Your original ACF file is always preserved. Inserting the meshes does not alter in any way the informations of other parts present in the file. You don't need to reinsert all the meshes; you can insert only the ones you have modified. DEVELOPMENT This tools are under active development and their functionalities may change in the future. The primary development platform is Linux. Special thanks to @xraydelta1 for compiling the Mac version. Feedbacks, reports, suggestions or ideas are strongly welcomed: feel free to send me a message with your thoughts. X-Pilot's forum is the primary and sole forum for support, announcements and new releases. PLEASE DO NOT REDISTRIBUTE THIS TOOLS THROUGH OTHERS FORUMS OR PLATFORMS
    1 point
  48. Hey there. Not sure why this isn't addressed in the manual, but what are we supposed to use the "Manifold Pressure Target" and "Fuel Flow at Manifold Pressure Target" features for on the General tab? Also not addressed is the difference between the Iskra Starter (always selected by default) and the C24ST5? Thanks. p.s. for minor update - the tiedowns and fuselage cover are not persistent between flights.
    1 point
×
×
  • Create New...