Search the Community
Showing results for tags 'solved'.
-
Hi, a complete virgin install of the CL650 crashes XP 12.0.8.rc1 during startup before I can even enter my licence data ;-( Log.txt
-
I have just purchased the Hotstart cl650 and am having some issues. This is a fresh install, I have also reinstalled to see if something was wrong and had the same results. I turn on the battery and/or ground power and I get "AIRCRAFT NOT ACTIVATED" across all screens. There is also an audible warning of "NOSE DOOR" that continues no matter the state of the door.
-
Freshly installed Challenger 650 v1.7 on XP12 (12.00r6) Start X-Plane Configure a new flight with the Challenger, real weather, at KSFO. ------- ...... 2022-12-26 14:21:22 CL650[gps_jammer.c:277]: Successfully downloaded GPS jammer list 2022-12-26 14:21:23 CL650[dr.c:137]: assertion "!__builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (f), double), __isnan(f), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (f), float), __isnanf(f), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (f), long double), __isnanl(f), (__builtin_trap(),f))))" failed: sim/operation/sound/master_volume_ratio (xp_snd_bridge.c526: &drs.master_volume) Backtrace is: 0 00007FFA644D441C C:\WINDOWS\System32\KERNELBASE.dll+000000000004441C () 1 0000000081F590B9 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000010E90B9 (dr_setf_impl+149) 2 00000000827986E0 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000019286E0 () 3 0000000081F5880D C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000010E880D (dr_getf_impl+5d) 4 0000026945D4E6F8 C:\X-Plane 12\X-Plane.exe+0000026945D4E6F8 () 5 00000000821ADE70 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000133DE70 () 6 000000008261C520 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000017AC520 () 7 0000000082150997 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000012E0997 () 8 000000450000020E C:\X-Plane 12\X-Plane.exe+000000450000020E () 9 0000000082150AFD C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000012E0AFD () 10 0000BEFC108F9E55 C:\X-Plane 12\X-Plane.exe+0000BEFC108F9E55 () 11 00000000827986E0 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000019286E0 () 12 000000F0745FF038 C:\X-Plane 12\X-Plane.exe+000000F0745FF038 () 13 BFF1527020000000 C:\X-Plane 12\X-Plane.exe+BFF1527020000000 () 14 00000000827986E0 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000019286E0 () 15 000000F0745FF038 C:\X-Plane 12\X-Plane.exe+000000F0745FF038 () 16 000000008261BE88 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000017ABE88 () 17 00000000813E506D C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000057506D (xp_snd_bridge_floop_cb+17cd) 18 00000000827986E0 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000019286E0 () --=={This application has crashed because of the plugin: Challenger 650 by Hot Start}==-- ------- Log.txt
-
Hello all, I have been flying the CL650 in XP11 for a while and have invested quite some time into the "perfect setup" for my tastes, configuring X-Camera, Keybinds, Honeycomb Alpha & Bravo, adding some FlyWithLua scripting, you probably know the drill when getting a new aircraft into the virtual hangar. In order to make the CL650 HUD work with my X-Camera pilot view camera position, I have modified the CL650 hud_projection.obj accordingly. This still works fine even in the latest CL650 v1.7 in XP11. But it does no longer work in XP12. It seems the projection surface defined in hud_projection.obj is completely ignored in XP12. It seems unlikely that this has something to do with XP12 per se. I would suspect that the CL650 v1.7 XP12 version (which differs significantly from the XP11 version) handles the HUD differently. So, the question then is: is this a bug or a feature? My fear is that it is a feature... Before you tell me to move the camera back to the default position and leave it there, let me elaborate why that is not an acceptable solution. In my case, I have a 1440p 27" monitor, and given the viewing distance in my setup a FOV of 60 degrees is appropriate. That will result in a "true to life" feeling/scaling of the 3D cockpit and outsides, and together with X-Camera and/or TrackIR is a good/acceptable setting. Other people with other monitor sizes and/or viewing distances might prefer different FOVs. Now, the problem with a larger FOV is that by definition it makes everything outside the cockpit very small. So you get a better overview of your cockpit, but cannot see any slightly distant details outside, and you get that unnatural fish-eye effect. When setting up a workable pilot view in the CL650 cockpit with a FOV of 60 degrees, I end up with a camera position that does not allow me to view the HUD correctly, hence my hack of the hud_projection.obj. I guess other people have done the same, so it would be very much appreciated if this behavior (working hud_projection.obj) could be restored in the XP12 version of the CL650. I realize that in the real plane, you have to adjust your seat such that you line up the eye position indicator (which is in fact modeled in the CL650). However, this is a simulation, and no amount of monitors, TrackIR and whatnot will come close to the (peripheral) view you have in the real cockpit. So I guess because of the above it would actually make sense to reverse the logic from reality and at least scale the HUD depending on camera Z position such that it fits on the glass. Yes, that is not how a real HUD behaves, but it would at least allow the use of the HUD with non-default camera positions. Or maybe simply give us a setting in the settings dialog where we can enter a HUD scaling factor. Anything would be appreciated. Thanks. Cheers, F.
-
Hi All, I performed a clean install on the TBM 900, and every time I try to load the plane into "start flight", I get a crash to desktop or X Plane just hangs. I am running Vulkan. Best, Mike Dart Log.txt TBM900_Log.txt GizmoLog.txt
-
Hi, In V1 sim/cockpit2/controls/flap_ratio dataref was working properly, seems not to be mapped in v2. I think is very important to map standard dataref and commands, at least for main autopilot and control functions, since most of the market hardware instruments for home cockpits use them. Not all allow dataref customization. Not sure if all are possible to map but just in case I will keep reporting them. I'm a home cockpit builder and this is such a great plane for it. Thanks!
-
The command xscenery/mu2b60/both_engines_RCS_stop is labelled as "shutdown right engine", while xscenery/mu2b60/right_engine_RCS_stop is labelled as "shutdown both engines". The commands work correctly, it's just the labels which are swapped between right and both (left is fine):
-
For some reason I am not getting a readout on the radar altimeter. I have tried starting a flight with engines running but the radar altimeter screen is black, no readout. I tried starting cold and dark. Put the key in and turned it on and no radar altimeter readout. Is there a switch somewhere to turn on the radar altimeter (I haven't found one)?
-
I just purchased the MU-2 Marquise v2 and cannot get the autopilot to engage in NAV mode. I'm flying the GNS 530 vairant. Have a flight plan loaded but after takeoff I cannot get NAV to select. HDG works but NAV does not. What am I missing. I also tried using the Reality XP GTN 750 but it does not couple to the HSI. -
I'm curious whether others have found that the CL650 Reverse Thrust Lever Up (left and right) no longer work in the latest update. At least I was not able to do this. The CL650 bindings for this worked fine in the earlier versions. No worries as I found the generic XP reverse thrust controls for engine 1 and engine 2 worked fine. I'm wondering if this is a new bug.
-
I am currently doing a transatlantic flight and during cruise the "R Window Heat" kept showing up as a caution item every now and then, even after turning off and on the switch. I also located the CB (F14 and F15) and tried pulling out and In, with no results. -
VNAV works great except on descent. It always defaults to 250IAS or less. I find myself manually setting the speed on descent for crossing restrictions frequently in the 280 range, then sometimes forgetting about it. Is that a bug or is it how it works in the real aircraft? -
Hey Devs, i can start and fly the plane without fuelpumps. That isn´t real or? Greetings from Hamburg
-
Since i updated to 11.10 ILS don t woking programming descent to 3000 feets for example and it stay at this altitude dont catch vor and don t catch GS....passing over the airport
-
Good day, I have following problem: always, when I change something in the IXEG 737's FMC, which isn't executed yet, my FPS drop and I'my not able for many seconds to press EXEC. It's okay for one fix change, but without pausing the sim (yes, your're able to click EXEC and stop the problem in pause mode), your're not able to change a complex STAR in the DEP/ARR page (not shown in the video), which makes this so perfect plane unflyable on IVAO. For this test I removed all plugins. Kind regards Julius
-
Since the new version has been released, betterpushback doesn't work anymore.. Any similar experiences ?
-
After PC format that i have made, i have install everything. including Windows 8.1 C++ librarys, x-plane 11, and of course IXEG. Every button and axes from my setup working except the throttle axes. I have calibrate my joystick with x-plane 11 and the actual throttle axes work with all my other aircraft ecxept zibo. I have trying to uninstall and reinstall the Aircraft with the same issue. In the log.txt there is an error that says W/ACF_CONFIG: ACF Config data file for Aircraft/X-Aviation/IXEG 737 Classic/B733_config.txt is not valid! i don't know if that the problem... i have also trying to re assign the throttle axes to other axes in other joystick but nothing happens. Again every other axes and button works except the throttles. I have also trying to move the throttles with F2 - F1 buttons .... nothing!! PLEASE help me!!!... . Log.txt
-
Hi all, I'm new here but a long time user of the .org for X Plane (same username). I'm really enjoying hotstart's TBM 900. I have an odd issue with sound. The sound plays perfectly well in 2D and VR (vive pro) but when I use the model in VR, my log.txt gets flooded by similar error messages about playing some .wav files (see attached log). I've tried to output the sound to usb devices, the headset, the internal speakers and to the other realtek ports. These errors get written very fast and the log.txt can get pretty huge in that way. Sometimes I'll get an out of memory error if the log.txt gets too big. The thing is even stranger since I don't have any error when I use the TBM in 2D. There is no error written when I go from 2D to VR either. This issue occurs only when I start directly in VR. I haven't been able yet to detect if the error stems from X Plane which might initialise openAL differently when starting in VR or if the internal initialisation procedures in the TBM plugins are slightly different when starting in VR... Anyway I attach my log here and will file a bug with laminar as well. Thanks for your hard work. Edit : I just saw this issue was mentionned over here. (BTW I don't see rain effects in my Vive headset, I will try the rift later on, not very important for me). I've already reinstalled the TBM twice, switched back to 11.34 to no avail. Log.txt TBM900_Log.txt
-
Anyone have the problem with autopilot vertical modes in X-Plane 11.32 that neither altitude hold nor vertical speed mode can be engaged? Checking this forum I see that some problems have been reported for autopilt modes, but not specifically this. I am running XP11.32 on MacOSX 10.13.6 and everything seems to work except these two modes. Speed using autothrottle, heading hold and NAV mode (FMS) are all fine. Just the vertical thats a problem.
-
my PC has just updated from WIN 10 1803 to 1809, I am now failing the License Activation screen, can you please advise on what I should do now please. Thanks Wayne
-
I am scratching my head here with an issue with the IXEG 737 in X-Plane 11.30 that I have never seen before. When I start taxiing I can't control the Aircraft properly first I have to apply very large amounts of thrust to get the aircraft moving (50%) and when I try to take a turn the only option I have is taking the turn extremely fast and ''drifting'' the aircraft into position if I try a normal turn the Aircraft will just stop as if it were braking and when I release the rudder it will start turning in the opposite direction this has caused me to taxi off the taxiway or runway when trying to turn on multiple occasions. I have tried looking in my mappings to see if I have something set to differential brakes but there is nothing as every other aircraft works perfectly. This is ruining the entire experience for me and I really want to fly the 733 but can't with this bug. I have tried everything except uninstalling and re installing the Aircraft at this point. Any advice would be most welcome. Cheers. X.L
-
Hello, just noticed the attached problem in my 737 cockpit in VR. Non VR cockpit looks fine. log file gives the error (but not sure if its related) WARNING: the named light airplane_panel_sp is actually a parameterized light. ERROR: object Aircraft/X-Aviation/IXEG 737 Classic/B733_cockpit.obj has a bad light name: airplane_panel_sp anyone have any idea what is going on? attached my log and list of plug ins as well Log.txt
-
Hey all. Whenn i make all flood lights on the Flurosent tube had no more effect on the Center Panel (Recheck HD IS ON!!!) Regards Daniel
-
Hello, I have just experienced some really strange issues with the aircraft while descending to SABE. (it looked like a nightmare hehe). I'm not sure if I have done something wrong or if it was some rare bug (never experienced this before in my more than two years flying the IXEG). I'm using version 1.21. This was my second flight with the 11.30 version of X-Plane. Situation: Flight SAEZ > SULS; then flight SULS > SABE All in the same sim and aircraft session. Landed after a normal flight, then inserted the new data on the FMC and took off. Stormy weather (real conditions). Anti-ice as far as I remember was ON. ROUTE: SULS DIRECT DAGUS SARG7C VANAR DIRECT VANAR APPR TRANS FDO24 ILS13 RW13 MISSED APPR (3000) SABE What happened: While I was descending towards SABE, after overflying EZE VOR, the aircraft made a sudden nose-up (trim) input. From then, it went completely uncontrollable. PFD airspeed suddenly dropped to zero. After this, it entered in a deep stall. MCP started showing really weird stuff: SPD was showing some four digit numbers, varying all the time. ALT was showing some extremely high numbers, also varying all the time. Stall warning. Trim wheel working all the time. Autopilot OFF. Controlling the aircraft was impossible; it was in a deep stall with no airspeed. It was like 'floating' in the air. Also it was trimming by itself. Before it slammed the ground I opened the map and set the aircraft to 0 degrees pitch, speed something like 280 TAS and 16K altitude. Also, I set clear weather. But it did exactly the same again. Airspeed dropped instantaneously to zero and again it was in a deep stall. No input would do anything since there was no airspeed, and it was still trimming by itself. While I was trying to deal with the situation the sim crashed, so I couldn't take any screenshot nor video. All I can share is this Flight Data from projectFLY: Here, you can see the nose-up input. Please note that the sudden altitude 'jump' at the end was after the map intervention, where you can also see how it entered again in a deep stall. Any ideas on what could have happened? Kind regards, franco_erco
-
Good day, Having recently started to fly in VR, there are few things that would benefit VR experience with iXeg B733, namely please consider substantially reducing "sensitivity" of course, speed, heading, altitude, and com1 knobs (critical for us flying in online networks such as IVAO/VATSIM, with precious time during critical phases of flight). Adjusting these knobs through controllers is a torture, so I had to map all these knobs to keyboard buttons, which is not desired option. I did notice that rotating NAV1 knob with controller is easy and that is what the end result for the rest of knobs should be IMO. I understand in real aircraft some of these knobs are also sensitive, but perhaps add a setting for 'VR reduced knob sensitivity'? Thank you.
