Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/23/2023 in all areas

  1. The ECAM "pie needle" illumination is missing, I've logged it and addressing it for the next patch. Can't explain the weird texture....XPlane 12 lighting still brings up surprised every now and then. -TK
    3 points
  2. Hi Tom/Jan, I was doing some basic hardware integration with V1.5 (specifically using @VirtualCPT's excellent XMidiCtrl), and I noticed some results that may be considered bugs and/or misbehaviours, as follows: 1. Custom autopilot "toggle" commands leave 3D cockpit buttons depressed Current behaviour: After binding custom command, e.g. ixeg/733/autopilot/HDG_mode_toggle for heading select, to keyboard key, when the key is pressed (command phase “begin”) the 3D cockpit button for HDG SEL is depressed and the mode is activated, as shown by the lamps and on the FMA. When key is released (command phase "end"), 3D cockpit button stays depressed, see below: Expected behaviour: Using custom commands should have same effect as using mouse button on 3D cockpit manipulator, i.e. after releasing key, 3D cockpit button is returned to normal "out" position. Also, while key is held (command phase "continue"), 3D cockpit button stays depressed. 2. Using default autopilot "up"/"down" commands does not animate MCP controls and no sound is played Current behaviour: After binding default autopilot command, e.g. sim/autopilot/heading_up (or airspeed_up, etc.), to keyboard key, when the key is pressed the heading value in the "window" is changed, however the corresponding 3D cockpit knob on the MCP does not rotate, and no sound is played. Same applies to course knobs when using default "obs1" or "copilot_obs2" radio commands (there's no custom ones that I could find), and surprisingly the custom "HDG_bug" IXEG autopilot commands. (And possibly others?) Expected behaviour: Using default commands should have the same effect as using mouse on 3D cockpit manipulators, i.e. value changes in "window", knob rotates, sound plays. 3. Default vertical speed commands have no effect Current behaviour: After binding default autopilot commands for vertical speed, e.g. sim/autopilot/vertical_speed_up, to keyboard key, when key is pressed the vertical speed does not change, nor does the 3D cockpit wheel animate or play sounds. Expected behaviour: See #2 above. For context, the default autopilot commands are often the first thing people will try to bind, and are also part of default or hardcoded configurations for some hardware, e.g. Saitek panels. Additionally, they have the advantage (over the custom ones of many add-ons) of "auto-repeating" when "held". Any questions please let me know. Thanks!
    2 points
  3. Thx @Pils I hope these didn't work in XP11 and then just "stopped working" in XP12 ??? We really haven't changed any of our manips / command structures. I will say that I think a really comprehensive "hardware compatiblity pass" for these kinds of things....similar to the MU2 hardware pass, is warranted. X-Plane has introduced tons of commands that weren't available when we coded this thing up...and we didn't tie into all of them at the time. Of course hardware wasn't as prolific and as full-featured as it is now.....so we do have some catching up to do here. As usual..this post is logged on my list. We're prepping a patch now for the obvious stuff from the last week...and I suspect we'll go a few more weeks seeing what else turns up, and once I feel we're stable...then I'll set about with the hardware pass. I'm also preparing 'MU2 like" online docs...and we have over 1200 custom datarefs....no telling how many commands. So it needs a good audit. -TK
    2 points
  4. I've not been getting reports about widespread stuttering, and at least on my end have made no mention of some form of a fix for it. I recall in the past some people had stuttering in the v11 version if their anti virus was kicking in. Creating an exception for the X-Plane 11 folder helped that. Either way, this topic is not about Gizmo, so let's keep it on track in here, please.
    2 points
  5. You were responded to in just over an hour of your original ticket submission. Check your spam. You've never replied since. Learn to be nice next time.
    2 points
  6. Hello All, This will serve as an official announcement that we have released the version 2.0.1 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.1 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: Fixed aircraft locked issues Fixed Cowl flaps from working without hydraulic pressure Differential power will be disabled when tail wheel is not on the ground and MAP above 35 Pilots are visible from outside, only when the aircraft is powered Cabin door manipulators are available when parking brake is set Improved American Airlines livery colors and resolution Improved Hellenic Aviation Authority livery resolution Added toe brake animation 'READ THE MANUAL' button now opens the online manual in your default browser Modern Variant: Fixed ADF1 ET timer - Does not reset when the unit turns off Fixed ADF2 timers - Not working properly Fixed Transponder ID button - Working when in STBY and TEST modes Fixed Transponder TEST mode - Three first knobs can change the code Fixed Transponder code - Resets to 1200 when unit is turned off Fixed Copilot's CI TO/FROM flag - Responding to pilot's CI Fixed some sounds not audible due to wrong coordinates (fire bell, overhead, etc) Fixed AP test tone Improved instruments night lighting As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!
    1 point
  7. X-plane 12 X-Plane 11 And this is the weird texture at night in the binder and pedestal. If any feedback is granted, I would say that the brightness of the analog pilots instrument is too intense, where you have to set it almost to minimum do handle the brightness. It could be related to HDR monitor and X-Plane HDR space, but yeah. I would describe like that. But on general. wow. That sent me back to my MCC training done in a 733 Level-D sim (motion was disabled to reduce costs).
    1 point
  8. Captains, Firstly, we'd like to express our gratitude for your recent upgrade purchases. This week has been bustling with activity, as we’ve endeavored to respond to inquiries and meet the high demand for support. Level-2 Failure - Fixed! It quickly came to our attention that a number of our customers encountered a Level-2 failure, which restricted the aircraft's systems from functioning at all. We deeply regret any inconvenience this may have caused and assure you we've been working diligently to identify and rectify the problem. While we strive for perfection, it's an unfortunate reality that despite thorough internal testing, unforeseen issues can arise when a product reaches a wider audience. This particular setback wasn't evident during our beta testing but manifested for some once released. The good news is that we've isolated the cause and have promptly deployed a patch. To access it, please re-install the IXEG 737 Classic Plus from your order history. Didn't have Level-2 Failure? For those unaffected by this issue, there’s no immediate need to update. You can comfortably continue using the aircraft and await our next scheduled update for other enhancements. We truly appreciate the patience and understanding shown by many of you during this period. Thank you once again for your continued trust and support. Blue Skies, X-Aviation & IXEG
    1 point
  9. and TBH....this UI with the cockpit is over 10 years old. There are a lot of things I want to redo for more "natural immersion"...so usability will get its turn soon. -TK
    1 point
  10. Hm, just found this line in the log: IXEG: Level-1 PASS / Level-2 FAIL. License invalid I will try the lastest update, seems like I have a license issue. However, the UI said everything is fine.
    1 point
  11. I moved the post to the Bug Reports forum. You can post here in the future.
    1 point
  12. First up, thanks to you tk, Jan and the IXEG team for bringing the 733 to XP12, and for the encouraging words about further development. I got into X-Plane specifically for the 733 when it was originally released, and there's something intangible yet unique about the feel of the IXEG cockpit - you can see the "love" that went into making it. To add to @aquarich's comments I'll second the request for availability of all rheostat position datarefs - the confusion I had is the lack of consistency that some rheostats have datarefs, some don't, and the way XP12 handles lighting makes things more complicated it you're having to work off light levels. There is a workaround to reverse-engineer rheostat setting based on ambient light and gauge brightness, but I'll happily switch back to running straight off rheostat position for simplicity. Nothing lost though as I think exporting annunciator brightness for external cockpits has to be manipulated for the XP12 version; unless IXEG has specific datarefs for annunciators lit or unlit (or dim and bright) already in the system? Can I also add a request for datarefs to provide internal FMC LNAV values? I have a flat-screen NON-EFIS cockpit built with Air Manager which displays LNAV data on the HSI, but it's a fudge, and requires route data and calculations vs aircraft position to work. Essentially I'm duplicating the FMC calculations externally and having the internal FMC values available to read directly would be superb! In the absence of internal FMC values I haven't thought about how I'll deal with Vertical Deviation yet.... Anyhows thanks again, and wish you every success with the 733! PS. Not sure if it's been mentioned previously, but should the standby ASI always read zero?
    1 point
  13. For what reason? It's not exactly clear what you're after.
    1 point
  14. Sending multiple emails isn’t going to do yourself any favours…
    1 point
  15. I have begun to isolate and document the datarefs to put on the Togasim website like I did for the MU2 here. But the 737 has...oh ...1200+ datarefs so its taking a bit to cull through them all and organized them. But we'll have these up and avail before next weekend I believe...that's the target....and this will make it a bit easier to track requests for hardware support and get those on our todo list. -tk
    1 point
  16. Hi, I use XMidiCtrl. The 733 was very handy to find Datarefs values with the suffix act, thank you. My question is that I can't find some of the light knobs, I could control the light value, but it was really the light brightness value, which is separate from the knobs, an unlimited brightness. I would like some help on where to look to find these Datarefs. Thank you.
    1 point
  17. It's safe to say that "everything is changing...all the time" and its simply a non-stop adjustment, that's just tech. X-Plane is somewhat like "The Borg" (for any Trekkies) in a way, which just absorbes more features and functionality....and in doing so, sometimes steamrolls our implementations causing us to have to re-tool. Certainly as new hardware has come available, it has continually stressed X-Plane to adapt, which further stresses our implementations and its just a bit of a merry-go-round that is the nature of the beast. -tk
    1 point
  18. IXEG 737 Classic - Exterior Cargo Conversion 0.1.0 https://forums.x-plane.org/index.php?/files/file/71874-ixeg-737-classic-exterior-cargo-conversion/ Not perfection but works for XP 12 version, simple instructions, loads of livery. The IXEG 737 Classic is my favorite and I look forward to the day we have a cargo version with working doors. This is a alternative until that day comes.
    1 point
  19. Same flight (GCFV to EDDM), now I'm over Spain, and the difference between the two is just 100 feet more or less. So it seems depending on the weather? I'm using default xp12 real weather.
    1 point
  20. Cool! thanks for looking into it
    1 point
  21. With regards to your observation of the exterior sounds...our sound engine makes no distinction between interior vs exterior with regards to the software...its simply a "sound" in all cases. All our sounds are effected only through: "play", "stop", "adjust volume", and "adjust pitch", nothing more. When you open the window from the inside view for example, we simply "ramp up the volume" of some sounds...they are already playing. Moving the camera around the interior has the same effect on other sounds...you get closer to the panel, the fan noise "ramps up" too...yet doesn't cause a crash. I think there's something more sinister going on; however, as Cameron mentioned......X-Plane and plugins is real chemistry. It only takes one unique combo to create a reaction and finding the catalyst can be a challenge. We are certainly dealing with that here in my opnion and getting Laminar to help find data points at this stage is a prudent step. Ceratainly we want to add this one to our knowledge base. -TK
    1 point
  22. @AngelOfAttack I have identified and fixed the reason for the weird pitch during takeoff and landing. It will be fixed in the next version, so dont get too used to the effect ;-)
    1 point
  23. @LitjanHow can I assign it to the TOGA command? I can't find the custom command for this in the XP12 settings. the manual says that there is the command: "ixeg/733/autopilot/TOGA" but I can't find this specific command in the xp12 control settings tree
    1 point
  24. @Rhinozherouslooking into adding the option into Options tab. You'll have to enable it to work with commands. The only culprit for this update is that this option will not be saved, and must be enabled for each flight. My thinking is to save some options into a separate file, so they are the same across all aircraft and airframes (liveries), and not be different for each one. Working now on this to try squeeze it in the first update.
    1 point
  25. Why not? How says than a user cannot have a good idea? Personally, I believe that I don't have the whole knowledge of the world, and I want to hear ideas. And I might be able to squeeze this into the first update.
    1 point
  26. Hey all, I fly the cargo version mostly, but in saying that, it's the livery only. Then I adapt the max weights etc to "roughly" match the real aircraft. I have the TNT, Western Atlantic, FEDEX, DHL, ASL liveries etc, they are all out there to download. Would love to have the real deal though, fingers crossed.
    1 point
×
×
  • Create New...