Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 04/19/2024 in all areas

  1. Version 1.0.0

    19 downloads

    This is a livery for the Hot Start Challenger 650, inspired by https://www.planespotters.net/photo/166301/1203-luftwaffe-german-air-force-bombardier-cl-600-2a12-challenger-601 To install, extract the zip file into the "liveries" folder.
    5 points
  2. I thought I would start a new topic in case anyone else wants to add their comments. Just did a very short flight with the new x-plane update version 12.0.1 beta. All the systems seem to work well. The day and night lighting look good and I'm not seeing any dark cockpit issues in the daytime. I'm not sure if any modifications had to be done but the transition at least for me went well. Thank you all for your hard work.
    3 points
  3. I guess they dont, thats why they hired all those extra people, just to mock us all, and I guess all the graphic improvements, CPU performance currently worked on and all the weather, aerodynamics improvements come about because they dont care. I wonder how many user really care about laminars efforst??
    3 points
  4. Version 1.0.0

    45 downloads

    This is a livery for the Hot Start Challenger 650. Original design. To install, extract the zip file into the "liveries" folder. You can supply your own registration, HB-MNT is not printed on the cowlings. There are no country flags on the tail. You can add your own if you're so inclined.
    3 points
  5. I can't help the dissapointed. There is a quite well known phrase, "Disappointment is the difference between expectations and reality". We have tried to be as forthcoming as possible with setting expectations by telling folks it will take the majority of this year getting converted to FMOD and improving the FMS....but beyond that, there are also very big changes necessary 'under the hood'....big and time-consuming. Folks think that its always 'evolution'....just incremental work, but with tech, eventually the patches get too heavy. There is a very major overhaul of the "black box" bits to ensure future compatibility and the IXEG's continued existence....a rewriting of nearly 70,000 lines of code in a new language (that took 3 years to write originally) , stuff you won't see but I have to do to keep the IXEG compatible for the future. Guess what...its going to be silent for even longer while I work on the FMOD and code refactoring / FMS. Settle in...enjoy some other wonderful products for X-Plane, but know that it is not abandonware....and we won't be charging for updates for years to come probably. -tk
    3 points
  6. Version 1.0.0

    3 downloads

    Extract the zip file, then drag and drop into your Hot Start Challenger 650 "liveries" folder.
    2 points
  7. View File HB-MNT Hot Start Challenger 650 (Fictional) This is a livery for the Hot Start Challenger 650. Original design. To install, extract the zip file into the "liveries" folder. You can supply your own registration, HB-MNT is not printed on the cowlings. There are no country flags on the tail. You can add your own if you're so inclined. Submitter pilotdeviation Submitted 04/21/2024 Category Hot Start Challenger 650 Livery For https://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-challenger-650-p-212  
    2 points
  8. Look harder. The answer to your title question is 'No'.
    2 points
  9. Version 1.0.0

    26 downloads

    This is a livery for the Hot Start Challenger 650, inspired by https://www.jetphotos.com/registration/N604EX To install, extract the zip file into the "liveries" folder. You can supply your own registration, N604EX is not printed on the cowlings.
    2 points
  10. They are. But we may also not be able to fix it without modification to the plane. In the meantime my script linked above does the job.
    2 points
  11. For the future, I would recommend following the checklists, where the test procedure and which switches to check is explained in detail:
    1 point
  12. Thank you Stall Protection Switch was off on copilots side.
    1 point
  13. Yes, X-Plane 12.1 changing the X1000 logic flow breaking the current state tracking. We will be pushing an update to the SR with fixes once they are ready and XP 12.1 goes final.
    1 point
  14. The Chally on a transatlantic outing
    1 point
  15. Volanta is a know cause of crashes. Remove the plugin
    1 point
  16. Gizmo is not the problem, one of your other numerous (some of which are known to cause crashes) plugins is - possibly in combination with Gizmo. You will need to remove all of them temporarily (remove them, disable is not enough) and then run only vanilla X-Plane (the way it was when you first installed it) PLUS the ixeg 737. Then see if it crashes. Then add one plugin back after the other until the crash happens, then we have found the conflict. Once we know which plugin causes the conflict, one knows where to look for the problem to fix it.
    1 point
  17. All I can say on that is work is ongoing. No ETA at this time.
    1 point
  18. Attach the entire file, don’t copy and paste, please.
    1 point
  19. Tutos are here : Docs here : D:\X-Plane 12\Aircraft\X-Aviation\CL650\Documentation
    1 point
    Thank you for the great livery! Danke!
    1 point
  20. I read about this problem, It is not my intention to give false hope, perhaps it's a fluke I have other planes in my FBO. It's been a while since I used 733. I can't say when or why it stopped working, for some reason I've joined the club of this authentication error, never had before. I tried to uninstall everything, including remove gizmo plugin but nothing to do, reinstalled IXEG and nothing to do Then I've removed all plugins, also a new scenery plugin (openSAM) starting X-Plane 12 with the c172 then I've logged to Gizmo and then opened IXEG and all gone well! If my success is not accidental, and who has this problem solve it with this, you can figure out which plugin among them was the problem. good luck
    1 point
  21. Related to my posts on this thread regarding the airplane being loaded with a bunch of failures. While I thought my above explanation was the root cause, it actually covered up the real issue. I believe the real root cause is that if you save a flight (.sit) file, but then CHANGE TO ANOTHER TBM AIRFRAME, and then load a saved flight (.sit file) you can get the failures on startup like I was reporting. The fix to that is to RESAVE the flight (.sit file) with the new airframe and then the problem will not re-appear). Just posting here in case someone else runs into this issue.
    1 point
  22. We will definitely share news when there's some to share! Rest assured, you won't need to ask for it.
    1 point
  23. https://support.torquesim.com/hc/en-us/articles/360057635413-How-to-find-the-X-Plane-log-txt-file
    1 point
  24. Two likely causes: 1. Your trims aren’t centred or 2. Your control hardware needs calibration
    1 point
  25. No - sorry I was not clear. I meant I had to rename the DRT folder in the plugins folder from DataRefTool_v2.4.1 (as downloaded) to DataRefTool in addition to the setting up drt_ignore.txt with the entries below. Not doing so would make x-plane crash straightaway, irrespective of the plane.
    1 point
  26. In lack of better words : waaaaw <3
    1 point
  27. downloaded it at the 11.11.2023, but I am going to download it again... update: the new downloaded installer seemed to downlod while installation much slower, but it was succesful! YAY!
    1 point
  28. Start X-Plane using Rosetta. That will solve this issue for now.
    1 point
  29. Laminar is doing some major upgrades to xplane for next release, no developer is silly enough to do a major release until it has gone Beta and being tested by a lot of very picky consumers. I should add, "some very Vocal", consumers.
    1 point
  30. Think? I know. I deal with customers daily. It's my job. It's not a statement about one's intelligence. It's about the common occurrence of NOT reading. 50 products is more than a few. My data is a lot more relevant and true than anything you'll get your hands on. That's about all I can say to that. I'm sorry you're displeased, but I've been doing this (selling products) for 16 years. I don't care to be right, I'm just stating the facts as they are. I hope you find products that make you happy, and while I find your future purchasing decisions a bit odd, that's your choice and I respect it. Happy flying!
    1 point
  31. Lol good point. I believe you but I did a survey a couple months ago (from a popular flight sim website) asking me which simulators I use most and after I finished the survey it showed me the results which actually showed many more X-Plane users are using still using X-Plane 11 version 11.55 over X-Plane 12. Another strange result that surpised me is that some X-Plane users are still using an outdated version of X-Plane 11 (version 11.30 I believe but I could be wrong) for some reason. I am not asking for continued support and updates for XP11 add-ons. As I said before, I would be happy to buy the XP11 version of the IXEG 737 as is with no developer support or new updates. All I'm asking is that they make it available for sale, I don't think that's asking too much and it will in no way hurt development of current products.
    1 point
  32. Version 1.0.0

    32 downloads

    This is a livery for the Hot Start Challenger 650, inspired by https://www.jetphotos.com/registration/OE-INK To install, extract the zip file into the "liveries" folder. You can supply your own registration, OE-INK is not printed on the cowlings.
    1 point
  33. Version 1.0.0

    36 downloads

    This is a livery for the Hot Start Challenger 650, inspired by https://www.jetphotos.com/registration/HB-JSF To install, extract the zip file into the "liveries" folder. You can supply your own registration, HB-JSF is not printed on the cowlings.
    1 point
  34. Ah, thank you for the beautiful pictures - they bring back fond memories of flying the Classic for 12 years! The NG is supposed to fly fairly similar to the Classic (although most variants are a bit heavier), I am sure you will enjoy it!! I assume the difference might be like the one between 747-400 and 747-8 (the ones I fly now), they are subtle but noticeable nonetheless. Good luck and success with your type rating, all the best, Jan
    1 point
  35. Hello All, This will serve as an official announcement that we have released the version 2.0.3 update for the LES Douglas DC-3 v2. All customers who have purchased the LES Douglas DC-3 v2 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 LES Douglas DC-3 v2 from today forward, your purchased download will already be updated to version 2.0.3 for you. 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 LES Douglas DC-3 v2 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Both Variants: C-plugin now uses libacfutils, thanks to Saso Skiselkov. Fixed reseting the shutoff valves, not reseting fluids cutoff to previous condition. Fixed chocks not touching the ground. Mixture levers can be now cotrolled via commands, if selected in options menu. New fuel loading UI. Classic Variant: Sperry Automatic pilot, now requires autopilot hydraulic system to have hydraulic pressure. Modern Variant: Fixed copilot's attitude indicator rolling the wrong direction. As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!
    1 point
  36. The bulk of that time was spent on the CL650 update, as there was quite a bit to take care of. As there's only 2 of us, we have to prioritize the work according to various factors. Is there an ETA? Not one that we can safely stick to. We loosely planned to push out the last update for the CL650 within 2 years of release. That deadline passed 3 months ago. We're putting in the hours to get both the TBM and CL650 done as soon as we can, as we want to move on to the next project. All I ca n promise is we aren't going anywhere, and we're working to get everything done.
    1 point
  37. If you've ever looked at a Garmin GNS530 and thought "that's just a bit too mid-2000s modern for me"... today I've successfully integrated Todor Radonov / Todir's KLN 90B plugin with the MU-2: The outline of the installation process is: install the KLN90B plugin place the GPS and MD41 panels in the 3D cockpit in PlaneMaker customise where the GPS screen gets drawn on the MU-2's panel texture, along with the UV mapping for the GPS object - don't worry, I've done this step use a utility that comes with the plugin to add manipulators for the GPS and MD41 to the MU-2's cockpit Steps: Download Todir's KLN90B - get the latest .zip: https://github.com/todirbg/kln90b/releases (at time of writing this was 0.99.1b) Copy the `objects` and `plugins` folder into your MU-2 directory - don't copy `cockpit_3d` Replace the `kln90b_click_regions.obj` file in MU2/objects/kln90b with the attached version (this has the updated UV mapping) Make a backup of your 4B OEM acf file e.g. `xsMU2B60_4B_OEM.ackbak` Open the 4B OEM acf (not the backup!) in PlaneMaker Standard > Objects > Add: select `kln90b.obj` from MU2/objects/kln90b set its coordinates to 6.94, 0.10, 0.71 set lighting to Inside, shadow mode Interior Only, hi-res Yes/ticked/green/selected Add `MD41_V.obj` in the same way, coordinates 6.94, -1.68, 0.56, same parameters Save the .acf - leave PlaneMaker open for now At this point, you can test your progress by launching the MU-2. You will see the KLN90B and the MD41 mode controller on the panel, albeit with a blank screen and no clickspots. Edit MU2/plugins/KLN90B/data/modules/main.lua (in Notepad++ or VS Code or some other sensible editor): line 28ish, the KLN90_panel component, change `position = {814, 0, size[1], size[2]}` to `position = {0, 1138, size[1], size[2]}` (this determines where on the MU-2's panel texture the GPS screen is drawn. I've picked a spot which appears unused.) The next three steps are to accommodate a bug in the installer utility Copy MU2/objects/Cockpit_3D/Cockpit_3D_OEM.obj to the MU2 folder Make a temporary copy of `xsMU2B60_4B_OEM.acf` Edit the temporary copy in Notepad++ or similar: search for kln90b. you should find where the KLN90B object is specified, and just below it the MD41 mode controller search for Cockpit_3D_OEM.obj - you will probably find it just below the MD41 note the objects are identified with a number e.g. _obja/27/, _obja/28/ cut all the lines for the KLN90B and MD41 objects and paste after the Cockpit_3D_OEM.obj - for me they were numbered 27, 28 and 4 respectively. (cursed alphabetic number ordering strikes again) change "Cockpit_32/Cockpit_3D_OEM.obj" to just "Cockpit_3D_OEM.obj" Save the changes to the temporary copy .acf Run MU2/objects/kln_installer.exe: select your temporary .acf copy select Cockpit_3D_OEM.obj it should generate a new file in MU2/objects/kln90b: Cockpit_3D_OEM_kln90b.obj - this is the existing cockpit object with extra clickspots and the screen all in the right places Move MU2/objects/kln90b/Cockpit_3D_OEM_kln90b.obj into MU2/objects/Cockpit_3D In PlaneMaker, under Standard > Objects, find Cockpit_3D_OEM.obj, click the box to the left of its name and change the file to Cockpit_3D_OEM_kln90b.obj Save the plane in PlaneMaker To undo all of this: Replace xsMU2B60_4B_OEM.acf with xsMU2B60_4B_OEM.acfbak Steps 10-12 are a workaround for a couple of bugs with kln_installer.exe, which doesn't expect files to be in certain locations or for a numbered sequence to go 27, 28, 3, 4... they might become unnecessary with a future version of the KLN90B If you'd like to position the KLN90B instruments elsewhere, use the Visualisation settings in PlaneMaker to hide most of the exterior and interior objects, and make adjustments. Then run kln_installer.exe again to regenerate the _kln90b.obj cockpit object. Snags: MD41 buttons don't seem to light up properly in the 3D cockpit. You can click on the annunciators to get a 2D popup - but I'd rather the 3D instrument worked correctly and I never see the 2D popup KLN90B overlaps slightly with the top of the weather radar Autopilot / FD / HSI mapping not figured out just yet Powered by the default battery bus (or battery switch?) - you can give it a dataref representing a voltage bus but there's none available currently representing the radio bus voltages. This could be modded in though. Happy flying folks! kln90b_click_regions.obj
    1 point
  38. Sorry for the late reply. Merry Christmas/Happy Holidays to you too, sir. Not much has changed except for progress. It's one of those things where the non visible parts are progressing. We were also hoping it would be ready before Christmas, but unfortunately, it was not to be. libturbine is also progressing, but it's also taking time. Saso is a person who believes in doing a thorough and professional job, with as few bugs as possible. He really pushes himself to make sure we all get what is expected. We don't think it will be too much longer, because we want to wrap up the TBM, CL650 and start on the next project.
    1 point
  39. I do, have refined it to the new version... still need some work and I couldn't make the cargo doors to work but you can always use the interface, sometimes the doors get stuck too. XP12_737-300.xml
    1 point
  40. I REALLY don´t want this thread to devolve into the same old same old "my sim is better than your sim" discussion. We X-Plane people don´t care how many copies MSFS sells (maybe a little bit, the more the better since it introduces people to the flightsim genre that might try X-Plane as well later on), we only care about how many copies we sell and if those are enough to cover our cost and make us enough money to keep doing this. We could make a LOT more money coding some farm game where you can raise pigs or plant barley, but we like making airplanes better.
    1 point
  41. FlightFactor has recently released a compatibility update for their highly detailed A350 Advanced aircraft, making it compatible with X-Plane 12. This update primarily focuses on ensuring the aircraft works smoothly with the SimBrief flight plan downloader. It is important to note that the A350 Advanced is currently in the beta stage for X-Plane 12. While this update may not introduce any significant new features to the aircraft, it is not surprising considering the recent updates for FlightFactor's 767 and 757 models. Unfortunately, there is still no news available regarding the progress of their upcoming 787 aircraft. However, it is worth keeping an eye out for possible sneak peeks in the future. For existing owners of the A350, the beta version can be obtained from the X-Updater, a tool provided by FlightFactor. To use the aircraft in X-Plane 12, make sure to enable the "BETA" option in the updater. If you haven't purchased the A350 yet, you can find it on the X-Plane Store.
    1 point
  42. Guys - this have to get off my chest: I have been exclusively flying the Challenger 650 for many months now, and I still find enormous pleasure in every flight I make! I really still learn every day about the aircraft and it systems, be it the avionics, but also the aircraft systems itself, the flight envelope etc. The videos I watched in the beginning make much more sense now, as I now can appreciate every little detail in them, detail I can put to use now. The X-Pilot forum is an incredible source of information, with a very high level of knowledge and support. Second to none. It has also given me an edge in understanding the real life problems we encounter with our CL650. The aircraft has taken taken me all around Europe in about 150 flights, almost all of them on VATSIM creating an added dimension of 'surprise' - they never give you what you expect. In short, in my view this aircraft is absolutely worth every penny and I'm looking forward to making many, many more flights with it! The picture - Challenger meets Challenger during a VATSIM on line event in Corfu, Greece
    1 point
  43. Hi Cameron, Trying to install but get "Unable to download component SR-22 Series XP12: Component file version does not match." at the end of the download. Just an FYI. Jason
    1 point
  44. I'm curious how people are handling the pop up panels of the 650 in VR, especially the FMS. When you click on it to make it the focus, it basically becomes so large that you go cross-eyed trying to use it or just make it go away. I realize you can drag it to make it smaller, but most of the time this distorts it and is a real pain to reset. Any ideas how to make it work without resizing it every time? Thanks so much!
    1 point
  45. Version 3.0.0

    125 downloads

    Based on Sparfell's Challenger 605 OE-IIX, operated for Toto Wolff. At the rear of the fuselage there is a small difference in where a couple of lines match up. If you complain about this I will come to your house and rob your mousepad. Thanks
    1 point
  46. On the APPROCH REF 3/4 page, the approach climb gradient is for the single engine case. Landing climb gradient is 2 engine.
    1 point
×
×
  • Create New...