Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/12/2022 in all areas

  1. Version 1.1.2

    1,820 downloads

    This repaint is made for the payware Challenger 650 by Hotstart. This livery was taken from a variety of close-up photos of the aircraft. To install, extract the liveries folder to: .\X-Plane\Aircraft\X-Aviation\CL650\liveries Optional: (WARNING IT WILL AFFECT ALL LIVERIES, BACKUP THE FOLDER OTHERWISE A FRESH REINSTALL WILL BE NEEDED TO REVERT) If you wish to use NetJets specific extra's, extract the plugins folder to: .\X-Plane\Aircraft\X-Aviation\CL650\plugins If you like the livery, feel free to leave feedback and if you spot any errors, please do point them out! If you want to use aspects of the livery in your paints you must credit this one or myself & John if it will be public. Enjoy! Side notes: If you want to use aspects of the livery in your paints you must credit this one or myself & John if your will be publicly downloaded. If you like the livery, feel free to leave some feedback and if you spot any errors, please do point them out! Matteo & John
    3 points
  2. View File Hot Start Challenger 650 NetJets Livery This repaint is made for the payware Challenger 650 by Hotstart. This paint was taken from a variety of close-up photos of the aircraft. Installation: To install, just extract the liveries file to: .......\X-Plane 11\Aircraft\X-Aviation\CL650\liveries Optional if you want netjets specific extra's extract plugins folder content to: (WARNING IT WILL AFFECT ALL LIVERIES, BACKUP THE FOLDER OTHERWISE A FRESH REINSTALL WILL BE NEEDED TO REVERT) .......\X-Plane 11\Aircraft\X-Aviation\CL650\plugins Start the simulator and enjoy!! Side notes: If you have any issues missing the QS, on the FMS on the Tuning page 2 you can add the QS in Flight-ID If you want to use aspects of the livery in your paints you must credit this one or myself & John if your will be publicly downloaded. If you like the livery, feel free to leave some feedback and if you spot any errors, please do point them out! Matteo & John Submitter pilot_matt Submitted 01/11/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?osCsid=redmukm7he79lo2ou63juv11s1  
    3 points
  3. Note: this is already integrated directly on Simbrief (see above) so the link below now only exists as a backup. LINK HERE Note: aircraft name is clipped to 12 characters for custom airframes, sadly (limit does not apply to default profiles). Fixed by SimBrief Based on the already-accurate default CL60, with the following adjustments: equipment codes and extra flight plan remarks kindly provided by Graeme_77 here: OEW/BOW updated to match the Hot Start airframe without passengers (12,315 -> 12,556kg, includes two pilots) passenger weights updated to somewhat more closely match the randomized weights as simulated, going with 74+15kg so you can still carry 5 passengers+luggage and full fuel at MTOW if you are flying Kim Dotcom around (supposedly ~141kg or thereabouts), sorry, you will have to make adjustments, or just count him as two passengers see below for more information: Don't forget to add extra crew (anything above the two included in OEW) as passengers when planning your flight! Cheers, Tim
    2 points
  4. I'm hoping to have it out by midnight Friday 14th GMT+10. This will give everyone a weekend update and hopefully "peak enjoyment".
    2 points
  5. Might want to think about replacing or re-charging the cockpit fire extinguisher. No-go item
    2 points
  6. Please do not redistribute our cockpit object file, or any other files in the CL650. The obj files undergo constant changes through updates. Please, just post the self made vrconfig file, with instructions on how to implement it. I don't have any issues about vrconfig files being created, as long as there is a disclaimer stating that the file is not officially supported by X-Aviation, Hot Start or LES. If you want to modify the cockpit object file, please contact me directly, either though these forums or on discord, and I'm happy to work with you to help create one. If I have it in my blend file, I can export it with each update, so your one doesn't get overwritten. The very first update will have major changes to the cockpit object file.
    2 points
  7. Hello, Thank you for bringing this to our attention. I have reproduced this behaviour on my system and will log for fixing. Kind regards,
    2 points
  8. When the fueler comes into the cockpit and ask how much fuel is needed, I sometimes accidently clicked "Tanks full" or "Pump this many liters" (before selecting an amount). Therefore, I think it would be nice if confirmation was required. This is already the case when calling the FBO for example and asking to prepare a van after arrival.
    1 point
  9. Nose wheel steering only controls the nose wheel up to 55 degrees of deflection. When steering is not engaged, the nose wheel can castor up to 99 degrees each side. If the nose wheel is deflected further when the “NOSE STEER” switch is set to ARM, it will not engage and the CAS will display an amber “STEERING INOP” message. In order to recover nose wheel steering, the nose wheel must first be brought back within 55 degree deflection. This can be achieved by taxiing forward a bit. Steering can then be engage by cycling the NOSE STEER switch to the OFF position, then back into the ARM position.
    1 point
  10. As promised (in case anyone still cares), here's links to the profiles I developed while beta testing this aircraft. These were my personal choices, and you're free to do with them what you will. For example, I really only use Xsaitekpanels for the radio panel and the trim wheel on the multi panel, everything else is on the Bravo. Edit 2022-01-21: I’ve added the AP buttons (not lights!) to the Xsaitekpanels by request. Edit 2022-01-22: Added AP lights and knobs to Xsaitekpanels. Displays are not possible at this time. https://github.com/pilsnerish/Xsaitekpanels-Configurations/blob/main/CL650_xsaitekpanels.ini https://github.com/pilsnerish/Honeycomb-Profiles/blob/main/CL-650.json However, I suggest referring to the following thread for a much more complete Honeycomb profile kindly provided by @Goodfixins.
    1 point
  11. A few pilots are having issues with AUX TANK HEAVY messages. This is totally understandable as (A) we didn't tell you how to work the refuelling system and (B) Good grief - never let a pilot near a refuelling truck! The docs will be reviewed to see if something better can be written, in the mean time... Refuelling - Easy Method Tell the fueller how much fuel you want. He's going to say "I'll start up the pumps". Wait for him to go downstairs, then only switch the L WING and R WING shut off valve (SOV) on. Check the OP lights (OPen) indicate. The fuel values are pressure operated, no refuel pump pressure, no valves open. The open setting on the switch can also "time out" and the valves won't open even when pressure is applied, so watch the panel until the valves indicate open. The wing tanks will fill, the HL (high level = full) lights will indicate and the fueller will tell you he's done. If you don't have enough fuel, tell him to keep pumping, and this time open the TAIL and AUX valves together (always together - note the white line on the panel between TAIL---AUX indicating they work together. Again, watch the panel until the valves indicate OP. If you don't have all the open lights on, the fuel balance between aux and tail will be incorrect. When the fueller finishes this time and you have enough fuel, close the SOVs and switch the fuel switch off. You cannot defuel in the simulation, it's virtually impossible in the real world outside of maintenance operations. If you want to help the fueller out, you can work the pump yourself using the menu Challenger 650 \ Ground Services \ Refuel \ Refuel Truck. It's fairly simple, like a fancy gas pump! The pump symbol at the top left of the display indicates the pump is running. Start and Finish are the only buttons you need for basic operation. But I've still got AUX TANK HEAVY when refuelling on the ground! Did you land or start refuelling with a significant amount of fuel in the aux tank? You may need to balance the aux and tail fuel when refuelling to keep the aircraft in trim. To do this, ask the fueler to start the pump, on the refuelling panel switch only the TAIL SOV to open and then press and hold the override button. With this button you have great power, but also great responsibility - be very careful! Refuel with the override button pressed until the AUX TANK HEAVY message disappears, then resume normal fuelling if required.
    1 point
  12. Whilst shutting down this evening, the First Officer was diligently reading the checklist aloud and I was completing the required items. At the point in time where the APU generator was turned off and the aircraft was running only on battery power, the First Officer just... Stopped. Whilst I understand that the checklist was displayed on the FOs MFD and that this is unpowered from the battery, it seems a but abrupt that the FO would just 'stop'. Surely he would have a paper copy of the checklist for the remaining items..?
    1 point
  13. I'm sure this is because I don't understand something! Was flying EGBB > EGPB, FL270. Selected ILS27 as approach whilst on ground at Birmingham. During the cruise, looking at the EGPB approach charts, I decided to add a hold at SUM at the end of the route before the CI27 from the start of the approach sequence. I wanted the aircraft to calculate a TOD to get me to SUM at 5000' so I put 5000A in the scratchpad and added it to both SUM and the hold at SUM. I expected that the MFD VNAV window would therefore show me SUM as it was the next waypoint in the flight plan that contained a altitude restriction, but it seemed to only want to show me what it had shown originally which was the FF27 altitude of 2100'. As I passed KOKAL I did get a magenta 5000 in the PFD so I set 5000 in the MCP and made sure VNAV was armed. Got a TOD chime and a magenta diamond on the glidepath indicator showing that the desired path was above me - however the diamond never descended and then I noticed the green TOD marker was behind me on the map so I went manual at that point and VS'd myself down. All a bit of a mess - where did I go wrong?
    1 point
  14. Thanks for the feedback. Yes the avionics are non-volatile so a power down of the simulated systems is needed, even after a sim restart.
    1 point
  15. Looks like there's a free standby ASI with the oxygen instead of I'm guessing a flow indicator.
    1 point
  16. I have all the configurations to make all the other 3 position switches work correctly on my other computer - @Wavecourage I will send them to you tomorrow - they will require more OBJ file edits, but it's only 5 or 6 of them and I'll post each line that needs changing so it's just a quick copy/paste exercise. Regarding direction of the hotspots see: PRESET_PSI 180.0000 Best, James
    1 point
  17. Know your all focusing on the CL650, but just want to confirm that Navigraph will be in the TBM900 soon? I.e still on the roadmap for updates. Just bought the TBM today and was a bit surprised that Navigraph was not supported on the MFD. (My bad really for not researching it)
    1 point
  18. Let me explain why I think this mode should be kept and expanded to allow saving states: Yesterday, I was doing some practice approaches using saved career mode flights. Today, I wanted to fly a "real" flight. But my career mode state was set in the weird way the plane was left after my most recent practice approach. If non-persistent mode worked the way I would argue it should, then these different uses could be totally separated.
    1 point
  19. She is not present in the product. We just can't get over how bad people look in X-Plane, and until the following are supported it probably won't happen: 1) deformable meshes 2) skeletal animation 3) subsurface scattering
    1 point
  20. Yes. That's how it happened on the TBM too. The community helped Goran and Toto a lot.
    1 point
  21. I am definitely not an expert, but I think hitting FLC will tell the plane to descend immediately. When I setup for VNAV, I simply set the desired altitude that I want to descend to (the plane will honour restrictions, so I usually set it to the base altitude on the final approach if I am offline), leave everything else alone (plane is usually LNAV1, ALTS or similar with ATS on and VANV button activated) and one the plane hits TOD, it begins to descend. Very similar to the 737 behaviour in my experience. Again, I think the FLC will cause it to descend to the dialed-in ALT immediately.
    1 point
  22. You are in SPEED mode which is indicated by the blue marker on the speed tape and SPEED in the ATS display, it’s also only set to 127knots. The ATS display should show N1-TO if you were in the correct mode. edit I’m too slow too lol
    1 point
  23. The issue here is the ATS system is in speed mode, and the target speed is 127 kts, so it has made a power reduction. Being aware of the flight mode annunciators or “FMAs” is key to flying a complex aircraft. It doesn’t matter what buttons are pressed on the panel, only the modes showing in the FMA strip and ATS panel. In this case you can see LNV1 and PITCH, with ALTS armed and ATS SPEED. The reason this particular issue has occurred is with LNV1 armed before takeoff, at 400ft the aircraft swaps from TO/TO to LNV1 and PTCH, but the vertical change from TO to PTCH results in a more subtle change on the ATS panel from “N1 TO” to “SPEED”, when the adjusts the thrust to follow the speed target. It’s more obvious in a real jet where the thrust levers move, but Airbus pilots with detent levers are conditioned to be aware of that thrust mode annunciator at all times, it’s the only proper way to tell what the automation is trying to do, so very similar to sim hardware in that regard. For takeoff we recommend speed be selected to 200 kts, or the departure speed limit if more limiting. Keep an eye on the ATS panel and you’ll see it swap to N1 mode when using TO or FLC, and SPEED mode when using VS, PTCH or ALT.
    1 point
  24. How do you start the TCAS test? Thanks!
    1 point
  25. Ok found it. On the CDU: TUNE and then click on the squawk code with nothing in the scratchpad. Test is on the upper right of the page.
    1 point
  26. Hi Coop. Great, that worked. Much appreciated. Cheers
    1 point
  27. With respect to audio I am seeing a special thing with the CL650 as well. Often (not always) when I load a saved state volume is at zero, when bringing it back to higher volume all is fine. This only happens with the CL.
    1 point
  28. Move the Field Of View slider until you are happy with the view, it’s just at the bottom of your screenshot where it says field of view.
    1 point
  29. Wonder if the one they modelled it after was also bad, hopefully not on the actual aircraft haha
    1 point
  30. that's hilarious, they modeled a bad fire extinguisher.
    1 point
  31. Thanks. I think there’s a piece of the puzzle missing because I set up this curve like yours, tested it in the default 737 while watching datarefs you mentioned and it worked, however the same dataref changes didn’t happen in the 650. Hopefully there’s some obvious switch in Plane Maker that they can find.
    1 point
  32. After some consideration, and after reading your post, I’ve decided to allow it. Feel free to edit your post and re-attach the file. But please add a disclaimer that we don’t officially support it for now. For more permanent changes, please get in touch with me so we can collaborate.
    1 point
  33. When I hear the gong for TOD, usually 1 minute out, I simply activate VNAV, FLC, and set the Altitude to the base of the descent (where the approach alt starts). Once you do that, then if ATS is on and profile is setup for approach, it will throttle back to M.72 (default) and start the descent.
    1 point
  34. Uploaded a new version as someone brought to my attention the throttle reverser and idle/shutoff bindings were missing from the original. See post above
    1 point
  35. Yes indeed. Will be fixed, sorry for not spotting that before release.
    1 point
  36. Version 1.0.0

    499 downloads

    This is the Bombardier House livery for the Challenger 650 by Hotstart. The reg use is the C-GZKL. Some details are missing, see it as a WIP. Happy Landings
    1 point
  37. That's not your "electrical connection" door - the AC GPU plug-in point is further up the fuselage near the nose. That's your fuel, there is no way to close in the air. It is your responsibility to ensure all doors are closed prior to departure.
    1 point
  38. Good evening. I have some trouble with the FPL recall function. My Simbrief ID is entered in thje user settings. But there are a few questions I have about the "out of jet pocedures". 1) I can just use my browser and set up the flight, without the sim runnung, or do I have to use th flight planning room? 2) Must the page shown in the screenshot be open, Guess not, but one time it worked this was the case, on the return trip the browser was closed, it did not work. 3) fin number vs dep/ARR. If I have multiple flights starting from one Airport I have to use DEP/ARR, because I always use the same fin number (650), right? I have encountered these scenarios: 1) Sucsessful FPL download 2) FPL download rejected ( Pilot ID not changed or deleted from the settings 3) Request pending disapears, no other MSG, FPL not loaded Thank you.
    1 point
  39. No, not necessary for the IRS to be aligned, it's just a radio link. If you find yourself somewhere with no VHF datalink, you will need the GPS system to be working in order to utilise the Inmarsat datalink, as the antenna inside the vertical stab/tail has to actually steer to track the satellites, but this is a bit of a fringe case. (And yes, it's simulated too!)
    1 point
  40. Hi, during a cold-weather start up, you can start the aircraft APU at -40°C, ensuring that you have a minimum of 22 V for your APU showing on your DC electrical page. You can also start your engines at -40°C, when you do this, you will likely have a very high oil pressure during the start and obviously a low oil temperature. You do not want to increase the thrust until you have oil pressure in the green! The engine oil temperatures must be in the green for takeoff. There is a note for oil pressure that after cold start you might see 156 psi, 130 psi at idle for 10 minutes maximum. It also states that engines must remain at idle until oil pressure returns to within the normal range. Another cold-weather consideration is before the first flight of the day when the airplane is called soaked and an ambient temperature of -30 or below for more than eight hours, the engines must be motored for 60 seconds, and fan rotation (N1) must be verified, before the engine start is initiated. Thrust reversers must be actuated until deploy install cycles are less than five seconds. So to summarize you can start if the temperature is -40°C, you must have 22 V or greater for the APU to start, once you start the engines, as mentioned you were going to have a high oil pressure, low oil temperature, You should not increase the Thrust of either engine and (remain at idle) until the oil pressure returns to normal. As far as takeoff, the oil pressure and the oil temperature all have to be in the green. Hope that helps, Rob
    1 point
  41. Not an error. When you press the start switch the pack valves close automatically, and reopen when the start cycle is finished. Just like an Airbus. You can also see this behaviour on the Study window for the Bleed system.
    1 point
  42. I agree. At the moment the FO is essentially tied to the MFD checks. Future enhancements to the FO reading the checklists are being discussed, but no promises or timeline. The paper checklists are available in the documentation folder and via the Avitab plugin.
    1 point
  43. Fixed the blocking issue with dev branch just now. Need to sleep on it, then review for packaging... Shouldn't be too much longer.
    1 point
  44. Just a note to my fellow VR users - I'm nearly finished creating a vr config file that makes VR even better. Also fixes the 3 position switches and makes then snap back to center again. PM me if you would like it when finished and I will send a link...
    1 point
  45. Thank you for the reply, I wouldn't look down on someone reporting things and keep them as simple sim pilots. I have flown sims for 20 years and professionally in real life over 10. None on the aircraft that I've flown IRL doesn't behave like that. None. FD shouldn't be part of pilots movements but the other way around to be were APFD-system wants it to. I haven't flown with ProLine21A plane but I highly doubt that it should work like that.
    1 point
  46. For me the flickering comes and goes. I've found that a view change (exterior then back to interior) can "reset" things for you so that the flickering may go away. I've also found that manipulating screens can cause the flickering to go away.
    1 point
  47. Version 1.1

    229 downloads

    Turbo Raven by VRibeiro This high performance aerobatic aircraft was a fantastic airshow performer. It could climb vertically at 60knots, brake on descend using "beta" and stop the propeller in flight. This model does all this and inverted flat spins. I had a recovery parachute just in case of structural failure. To brake on step descent reduce speed and then wait for propeller to reverse, the speed will drop and should keep the aircraft horizontal as a controlled stall. Need lots of training. -VNE 300KIAS To know more visit: http://www.waynehandley.com/archive.html It's a real fun to fly this one. VRibeiro
    1 point
  48. Version 1.0

    221 downloads

    Hello! It's been almost half of a year since I released the Cassutt Racer. It's time for something new! It's time for... MX Aircraft 2! From Wikipedia, the Free Encyclopedia: The MX2 was based on the Giles G-202 aerobatic trainer, the first prototype was a modified G-202 and first flew in May 2002. The first aircraft of the initial production batch of five first flew in May 2005. The MX2 is a carbon-fibre low wing cantilever monoplane with full span ailerons and a conventional landing gear with a tailwheel. It has an enclosed cockpit for two in tandem on recling seats and a single piece canopy. The MX2 is powered by a 260 hp (194 kW) Lycoming IO-540 flat-six piston engine with a three-blade tractor propeller. Optimised for aerobatic speed and agility the MX2 can pull a G-load of plus and minus 12 Gs, giving it tight turns and loops and a range of aerobatic maneuvers. Promo Video 1 (more to come): This project started a few months after the Cassutt. I abandoned it soon after I saw that I won't be able to pull that project off. So, I posted it on the org forum as an unfinished airplane. After a while (a few months ago), I saw it abandoned in my Hangar - In Work folder. I decided to work on it again. So I started the work and I began enjoy building it. I had to re-build the wings, the control surfaces, the canopy, gear, nose of the aircraft and edit the body. It started to look really good, so I continued it. I published a topic on the org about the development of this aircraft which was labeled as [Freeware]. I worked hard on it every day. I had quite some trouble finding a painter for this aircraft but then I remembered Hampster; he made the textures for the Cassutt Racer. He was in as soon as I asked him. So, time started to run, I got the Greg Pee livery within one week. It's been almost 3 weeks since then. I wanted to release the MX2 on the day I got the Greg Pee livery. But since Hampster didn't reply to any of my emails, I started to shape my own white paint. I believe that Hampster has some goodies in his "liveries" folder and as soon as I get them, I'll update the file with the liveries. For now, there are only three liveries: - White Paint (by me, Brent123) - MX2 Default (by Jack Wilette, UltimateFlyer) - Greg Pee (by Hamish Hall-Smith, Hampster) Let's go to the features of this aircraft: - Hi-Res textures - Custom Prop Disc - 3 Liveries - Detailed 3D Cockpit - Highly Detailed 3D Exterior Model - Custom Sounds - Normal Maps (mostly to hide the triangles on the model) - A side menu made with SASL (Checklist, Aerobations & Credits) There are two more acf files, one is v10 and the other one is "If You Dare". Tested in X-Plane 9.7, X-Plane 10.20+, 32bit & 64bit. The creation of this aircraft would not be possible if there weren't for these people: - Steve Hatfield (support, flight model development, betatesting) - Ilias Tselios (help with the cockpit, animations and SASL) - Jack Willette (for making the "Default MX2" Livery) - Hamish Hall-Smith (for making the "Greg Pee" livery) - Jordan Palmer, Nathan Powell & Sara Gomboc (betatesters) - Peter Tram, Oz Grinfeld & others (for support) I'm really excited about what you guys think about it! Please rate and comment! Remember: it won't make the aircraft better if you say that it sucks, neither will if you say this is a great airplane, 4*. I will fix all of the bugs that will appear. Enjoy it guys! Mat
    1 point
×
×
  • Create New...