Jump to content

Leaderboard

Popular Content

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

  1. Version 1.0.0

    20 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 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??
    4 points
  3. 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
  4. I have fixed the issue I had, and already tested in 12.1.0b2. Needs a bit of clean up, testing for any unforeseen bugs, and then getting into release procedure. Here some late captures.
    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. 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.
    2 points
  7. Version 1.0.0

    4 downloads

    Extract the zip file, then drag and drop into your Hot Start Challenger 650 "liveries" folder.
    2 points
  8. Version 1.0.0

    52 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.
    2 points
  9. 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
  10. You’re not on Linux so please don’t use a totally unrelated thread for your issue, it’s confusing for everyone. Step 1. Disable Zink, it’s not supported by CL-650 1.7, and was auto-enabled by LR in 12.1B1.
    1 point
  11. I did notice a minor issue that I believe that I may have created by playing around with the new "Robust Contrast Adaptive Sharpening" (RCAS) setting. After setting it to 100%, the Captain's FMC display seem to layer one display over another, the more key inputs I put in, the more the screen layered on top of the old display. After a while with no further input the display started to clear on its own. I did another flight after restarting X-Plane and left the (RCAS) setting on 0% and the problem did not reappear. Not going to file a bug unless others experience the same issue. Also, the first officer's FMC did not display any issues at all.
    1 point
  12. I've been fighting with it for over a week now. I have hundreds of (mostly) problem-free hours with the CL650 on this exact machine. I took a little break recently, and now that I reinstalled my system I'm getting some weird errors. ------ MACHINE ------ i7-12700K, RTX3090 & ARC 310, 64GB DDR5, NVME SSD. I'm running Linux Arch (6.9.1), and Hyprland WM (Wayland). I have 2 GPUs in my system, I use ARC 310 to run the system on startup and for light work, the RTX 3090 if for heavy use in the host (Nvidia Prime) or in my Virtual Machines when need it. I can load and unload Nvidia kernel modules on-the-go and use the GPU when I need it. I know it sounds convoluted, but it works perfectly and it's officially supported by NVidia. X-Plane 12 runs very well on my system. When I run it via nvidia-prime it is the only process on the GPU, and I enjoy smooth 80fps+ graphics. I own multiple payware aircraft addons and they run perfectly fine (Felis 747, VMAX 767-400, X-Crafts E175) on this system. To be clear I've tried to run the CL650 on a vanilla XP12 installation first with the same results (crashes), so you can't blame the other add-ons. I have no extra Plugins installed in /Resources/plugins (besides what the installer puts there). ----- SYMPTOMS ----- (1) The aircraft (v1.7r1) loads just fine. I'm presented with the "Select Mode" screen. When I click the "Career Mode" i see the list of the Airframes, I can create/delete airframes and edit avionics options just fine. Now what's weird is on the right side (Saved States) the status is showing as "Parked" and Position "N00 00.00' E000 00.00' 0 KIAS at 0 ft. When I click "Enter FBO" the button changes to "Confirm?", and when I click that it hangs. It doesn't crash-to-desktop per se, just hangs. And as I later found out the X-Plane is dumping "--=={This application has crashed because of the plugin: Challenger 650 by Hot Start}==--" into Log.txt file at a rate of about 1GB per 10 seconds (yeah). Millions of lines. I have to issue a kill command to end the process and stop writing. (2) When I load the plane in "Non-Persistent Mode" it starts just fine (cold-and-dark). I did a couple of flights with it in non-persistent-mode and everything seems to be working fine... until it's time to shut down the sim (or change the aircraft) - when you press Alt+F4 (or select Exit from the menu) it hangs again just like in the Career Mode. ----- LOGS ----- I uploaded 2 logs - one from X-Plane (Log.txt) - I had to cut the end of it as it was over 500Mb of "--=={This application has crashed because of the plugin: Challenger 650 by Hot Start}==--". One thing I see right away is line 190: dlerror:/home/raf/X-Plane/Resources/plugins/Gizmo64.plugin/lin_x64/Gizmo64.plugin.xpl: invalid ELF header Then I get a bunch of sound FMOD errors, but the system doesn't' crash on that, it crashes after line 3927 "BOOT: pl21_fini" I also ran strace on the X-Plane-x86-64 (X-Plane.strace), once again I had to cut the file as it was over 1GB in size, but you can see X-Plane plugin requesting state.bin file located in /Output/CL650/airframes/<airframe-id>/state.bin but the file isn't there. I manually created an empty state.bin file inside that catalog to see what happens, and once I did that CL650 did NOT crash in Career Mode after clicking on "Confirm?". I was presented with another window stating "You have checked "Restore position and trajectory" but the state was saved very far ... from X-Plane's current location. Clicking "OK" will move you to that distant location." And after clicking OK - it hangs... Log.txt X-Plane.strace
    1 point
  13. I've tried that. No joy. I also tried removing the /Output completely and let X-Plane rebuild the files. Still the same. I went as far as installing XP12 and CL650 on my Win10 Virtual Machine and then copying the output of /Output/CL650 into my Linux host X-Plane/Output. That time I could actually see proper coordinates when selecting the airframe, but the sim froze after clicking "Confirm?" just like before. Now what's REALLY odd is the model works beautifully in "Non-persistent mode". I did 2h+ plus flight today, no issues. I'm suspecting the plugin or a function within that plugin responsible for creating and/or reading "state.bin" file is the culprit.
    1 point
  14. Disable Zink in XP graphics settings, and report bug to LR.
    1 point
  15. Thank you Stall Protection Switch was off on copilots side.
    1 point
  16. Volanta is a know cause of crashes. Remove the plugin
    1 point
  17. 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
  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
  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. I want to get the IXEG 737 but I would like to be able to own both the X-Plane 11 & 12 versions if possible. I see the X-Plane 11 version is now removed from the store. Please, is there any way to get both versions of the aircraft? I would be willing to pay for both if I could get some kind of package discount for buying both versions of the aircraft. I still use X-Plane 11 a lot for many reasons and I want this plane in both sims.
    1 point
  24. Yes, the installer is still downloadable and works for prior X-Plane 11 purchases.
    1 point
  25. Hi and sorry to bring it up again : besides all the pros and cons, since I am using X11 more than X12, will the installer for the X11 version still work in case I loose my installation ? Regards Joachim
    1 point
  26. That bit is just a static texture, so that can be ignored. (I'll get that bug noted to change the text there for XP12). The navdata itself is parsed from Custom Data if installed, so you should be all set.
    1 point
  27. View File N999MY Hot Start Challenger 650 This is a livery for the Hot Start Challenger 650, inspired by https://www.jetphotos.com/photo/11304543 To install, extract the zip file into the "liveries" folder. You can supply your own registration, N999MY is not printed on the cowlings. Submitter pilotdeviation Submitted 04/25/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  
    1 point
  28. 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
  29. 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  
    1 point
  30. Version 1.0.0

    29 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.
    1 point
  31. What kind of complexities would make it so difficult to keep the XP11 version available for sale on the website? That doesn't make sense to me. I don't know a lot about hosting a site that sells downloadable products, but it can't be that difficult to leave it up on the store for people to buy and download. I mean, there's nothing else you really have to do (as far as I know) except keep it available in the store than just let it sit there for sale (with a "no longer supported" disclaimer) and keep the "master" copy of the aircraft on the site (or wherever you keep your downloads) available for people to download it. What else do you have to do that wasn't already done really? There's an FSX/P3D aircraft developer that was named Milviz (now called Blackbird Simulations), they made a lot of high quality payware. About a year ago, they decided to drop out of the FSX/P3D market and focus on MSFS and then they did something very awesome for the FSX/P3D community (yes, they still exist), they re-released all 25 of there FSX/P3D aircraft as freeware and made them all available for anyone to download on their own website which they host themselves: Blackbird Simulations - Freebies (blackbirdsims.com) If they can make 25 legacy aircraft available for download for free on their site, why can't you just keep one single legacy XP11 aircraft available (for sale)? Can it be that difficult to do? As for still wanting to use XP11, I am certainly not unwilling to deal with XP12 because I own it already, I just don't use it much rn. Though it is an improvement over XP11, It's not nearly as impressive as I had hoped it would be and not much better than my heavily modified version of XP11, most of the time I find myself firing up XP11 instead. Also XP12 is barely even out of beta now. For XP11 I have many aircraft that are not and likely will not be updated for XP12 that I still enjoy flying, I have my Orbx TE scenery (most of which is not yet XP12 compatible) and loads of other types of scenery as well as many other kinds of add-ons, in fact, I have XP11 looking nearly as good as XP12 does and in some ways even better looking. I'm not going to give up XP11 and the several hundred dollars' worth of add-ons I own that goes with it just to use XP12 which has very limited amount of content compared to XP11 rn and it will likely take a very long time for developers to do their thing and make old add-ons fully compatible (many converted XP11 to XP12 aircraft and other add-ons still have plenty of bugs & other issues to work out as well as the newly released content) as well as make more new add-ons. There's still a lot of upsides to still using XP11 for me. It is going to be a very, very long time before I switch to using XP12 on a regular basis, probably at least a few years or so, in fact I'm thinking about uninstalling it because I use it so little and it's taking up so much storage just sitting there. I'm not buying the IXEG 737 if I can only get it for XP12, it's not worth it to me. I'm also not going to buy the new LES DC3 for the same reasons.
    1 point
  32. Absolutely not unfounded. ;-) The specification of my computer absolutely does not allow me to enjoy the benefits of XP12 using IXEG in VR mode (that's the only way I fly). In XP11, with all the additions and "improvers", it achieves a completely smooth VR simulation in any region, in any weather conditions. I have an XP12 and I am fully aware of its superiority over the XP11, but I have no pleasure in flying it. If I upgrade my computer, I will definitely switch 100% to XP12, but for now, the VR mode in XP12 is very lame. And still if I want to fly IXEG, I fly in XP11.... ;-)
    1 point
  33. Version 1.0.0

    34 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
  34. Version 1.0.2

    81 downloads

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

    38 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
  36. Fix will be in the next release. A beta is available via the Hot Start Discord.
    1 point
  37. 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
  38. Version 1.0.0

    33 downloads

    N624MY is a Challenger 605 presented here for the Hot Start Challenger 650. Please do not modify or redistribute without permission.
    1 point
  39. Version 1.0.1

    19 downloads

    Enjoy!
    1 point
  40. 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
  41. I just don't think nuke everything and redownload them is the bast way to go... even including the navdata I mean...
    1 point
  42. 1 point
  43. 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
  44. 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
  45. Version 1.0.0

    203 downloads

    Hotstart Challenger 650 | Alliance Executive Jets | 9H-IAR Tested for X-Plane 12 only. Normals may look weird on 11!!! Enhanced texturing including - New cockpit windshield - Improved aircraft fuselage normals - Improved riveting - Improved engine exhaust and intake - Tuned glossiness - Tuned cabin windows Please respect my work. Copying/Modification is not permitted. Happy flying!
    1 point
  46. Version 3.0.0

    126 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
  47. 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...