Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 03/28/2023 in all areas

  1. Captains, Mark your calendars! This Friday, September 15th, we're releasing the IXEG 737 Classic Plus! This is a next era re-brand for what the IXEG 737 Classic has become after many months of labor. The primary goal in this endeavor was to bring full X-Plane 12 compatibility to this amazing aircraft, squeeze in a few new features, and set the stage for improvements in the future. To us, it's a rebirth of a classic, tailored for X-Plane 12. Truly, stepping into the cockpit feels so good in the new X-Plane 12 environment! A Special Note on Pricing: For our customers who acquired the IXEG 737 Classic on or after February 7th, 2022, this update is for free for you to honor our promise of a free update at the time you made the purchase. As for our dedicated pilots who've been with us since the beginning and purchased the IXEG 737 Classic on or before February 6th, 2022, the upgrade to the Classic Plus version will be available at a nominal fee of $14.95 USD. We believe this price point offers tremendous value, and you'll have 60 days to take advantage of this upgrade offer once the product is released. The IXEG 737 Classic Plus doesn't just bring new features; it rejuvenates the entire flying experience, making this aircraft feel brand new. Here's a quick rundown of what's been brewing over the past 9 months: Fixes & Enhancements (from the XP11 version): Engine Bleed Configuration: Now accurately impacts Takeoff N1. FMS PERF Page: Resets to blank entries post-landing and deceleration below 60kts. Code Optimization: Streamlined and revamped for quicker future updates. Brand New Features for the XP12 Version: Wingflex: Experience the subtle flex of the 737's sturdy wing in our 3D model. 3D Cabin: Dive into a fully detailed cabin, complete with operational galleys (Fancy a cup of coffee?). Moving Cabin Doors: Open and close each cabin door, influencing differential pressure just like the cockpit windows. Loading Stations Concept: Assign weights to specific seat rows and cargo holds for accurate physical effects on the aircraft. Cockpit & Cabin Lighting: Updated for XP12's lighting engine, including interactive cabin lights. X-Plane GUI Integration: Set up your load and fuel seamlessly. GUI Enhancements: A fresh look for the IXEG interface, now VR-accessible. Hide Yoke: With default XP12 key assignment. FOV Slider: Added to preferences for a tailored viewing experience. Cockpit Windows: Upgraded to XP12 tech, showcasing rain and ice effects. Outside Lighting: Balanced for an immersive XP12 photometric experience. Aerodynamics & Engine Tuning: Optimized for XP12's advanced modeling. To our loyal customers transitioning from the X-Plane 11 version, we've poured countless hours into this upgrade, ensuring it's worth every penny. We're confident you'll find the enhancements enjoyable, and with the help of full X-Plane 12 compatibility, transformative! We can't wait for you to take to the skies with the IXEG 737 Classic Plus this Friday. Clear skies and happy flying! IXEG and X-Aviation
    36 points
  2. Captains, It's with a lot of excitement and appreciated patience that we are ready to announce what's to come for IXEG's future! The team chose to let the dust settle a bit and not have too wide of a moving target in the early days of X-Plane 12 so as to not waste development time. The following will serve as a brief summary of what's to come, as well as a bit of a roadmap on where things will go. Things have changed a lot since the last X-Plane 11 update, one of them being that @tkyler is now full time in add-on development instead of juggling between real life jobs and that of our virtual world. This has given us the ability to focus on where we want the 737 to go into the future, and we hope you'll like what you initially see! Cost Back on February 7th, 2022, a little after Laminar Research announced X-Plane 12 was coming, we published on the IXEG 737 product page that purchasing customers would receive a free product update to the X-Plane 12 version. Per that statement, we are honoring this free update for customers who purchased the IXEG 737 on or after February 7th, 2022. For customers having purchased the IXEG 737 on or before February 6th, 2022, the upgrade will be a paid upgrade of $14.95 USD. Why this pricing structure? Our goal is to keep the upgrade pricing within reach of all customers at a fair price, and will ensure continued development of the IXEG 737 into the future. This all said, we also want to provide existing customers with additional value for the upgrade cost, above and beyond just the 'porting' work required to gain Version 12 compatibility. So in order to provide additional value, we decided to develop an all-new 3D cabin, working cabin doors and wing-flex to include in the update and gain momentum towards overhauling the 733 to modern 3D standards. This work has been ongoing for the previous months and is responsible for most of the development time by @tkyler thus far. We've included some pics / links of the interior work in progress below. Background on why this news is only just coming out… Flight testing was delayed slightly while Laminar made alterations that affect certain areas of our models, but also because @Litjan, who handles the flight model, was working towards his 747 Captain rating (now since completed....congratulations Jan!). With the pesky 747 certification process out of the way, Jan has actively resumed flight testing / tweaking things, and if anybody is curious, the team does NOT plan to develop a 747 product . What's to come prior to the initial v12 release? Items to be included in the initial v12 release: All-new, high resolution 3D cabin interior Animated doors Wing flex Ensure satisfactory flight and systems performance Rework our GUI interface to a more flexible, imGUI based infrastructure Once these are complete, we will release the update. A good portion of this has already been completed, and other bits are still in the works. We believe we can do this work before the fall in the USA, and have a solid platform to continue improvements. Once released and stabilized after addressing any bugs or issues, we will immediately continue the work of improving the 733 in several areas. Some items we will be addressing and improving are: FMS VNAV Prediction / Performance Holds Performance / Progress predictions. Swap to XP11 NavData format. FMOD Sound Implementation, allowing us to more easily expand our sound set. New exterior 3D and high-resolution textures Enhanced GUI for accommodating more robust interactions with operations. So that's where we are in the development. The IXEG 733 is being worked on continuously and we're excited about evolving the product as both X-Plane and computer technology / performance evolves, chasing immersion as far as we possibly can. We want to thank you all for being customers and hope we can deliver satisfying experiences through this iterative journey that is flight simulation development. On behalf of the IXEG team, especially @tkyler and @Litjan, we thank all of your for your excitement and patience that has so far driven us to this point. Enjoy the previews! Please Note: All images are showcasing continued work in progress and things, including texture work, are subject to change.
    35 points
  3. you and me both. Still working on it every day (except weekends...really need my mental breaks)....there's just tons of little details to tend to, especially with lighting control and tweaks. I just finished swapping out all the old exterior lighting with the new V12 lighting yesteday, so that's the latest thing I worked on. Still moving down the punchlist. -tk
    19 points
  4. Sneak peek for the regulars....and a form of update I guess. All the cabin/galley 3D geometry is done...I'm working my way through the cabin currently, adding / texturing the smaller details and tweaking the lighting. A few more days of this I suspect, then I'll hit the final punchlist and tests with Jan. An unknown....XP12 b06 is hitting us devs shortly with some rendering changes...hopefully it won't affect us too much, if at all. Fingers crossed. -tk
    18 points
  5. I would like to chime in here - I have worked with Tom on this over the last week intensively - previously I had test flown the 737 in XP12 (after we fixed the major roadblocks of even getting if flyable, like making the flaps work, etc.) and I had tuned the flight model. Tom worked hard on 3D modeling over the last months with little for me to do (I am too stupid for blender and those things) and now with him approaching the end of that work, I dove back into flight and system testing. The more I test, the more stuff shows up that does not work anymore, because Laminar changed things - and these changes are all improvements in modeling systems, yet they still leave our "old" way of doing/overriding them unusable. So in a very real way we have to redo a lot of the things we already did for XP11, it is not a quick conversion at all - and this is something we definitely underestimated when we initially said to "upgrade to XP12 for free". The move from XP11 to XP12 is not an upgrade, it is in many areas a repeat of the dev work work we already did for XP11. And I am thankful for most of our customers to be very understanding of the fact that we charge a small price to compensate us for this! I think the old 737-300 still has a lot of life in her, I thoroughly enjoy my "test flights" and find myself again and again to "just finish this approach" even though I was just testing some autopilot PID constant ... simply because it is fun to fly and looks great in XP12 . Cheers, Jan
    17 points
  6. I absolutely understand the anticipation you must be feeling as you wait for this release! It's a thrilling time for all of us, and I can assure you that our team is diligently working away to bring it to you. We're following the latest update from Tom just last week, so everything is still on track. Please keep an eye on our announcements, and we'll make sure to keep you informed as soon as there's news to share. Your patience and excitement mean a lot to us, and we're eager to deliver something fantastic for you!
    16 points
  7. Tom and I met at FSExpo last weekend and planned the final steps we need to take before release.
    16 points
  8. slow but steady on the lighting...this is cabin emergency lighting. XP12 has really opened up new opportunities with its lighting engine, though a learning process. Trying to balance lighting effects for a natural look across multiple x-plane 3D objects with multiple light sources is an exercise is patience for sure, but as a simmer since 1981, I can't say I mind. It fascinates me how far these graphics have evolved. -tkyler
    16 points
  9. Well the MU-2 detour work didn't help.....but beyond that, in the world of custom engineering / design work, there are unknowns in the process. Perhaps the results we are able to get out of x-plane might not be what we want and we have to backtrack and try different techniques, or we make conscious choices to implement things we didn't plan on implementing initially. May be the software we use is giving us fits (*cough Substance Painter). In estimating efforts for stuff like this, I like to call such targets, "personal carrots" we dangle in front of our own faces to keep us moving and motivated. I can reel off a large list of custom efforts that went well beyond time and cost estimates ....by Boeing, NASA, Icon aircraft, Cirrus, Space-X ...really smart folks with billions of bucks to work with etc...so it just comes with the territory. We're happy when we get it right...and just keep our heads down when we don't. One example though....we have working cabin doors. You can open these doors via the GUI by clicking a checkbox to have the doors open/close. BUT....I guarantee some folks will want to open these doors more like the real thing, by grabbing the handles and rotating them. So....I put that feature in, and it was a bit more work than clicking my heels together 3 times....and when I did that, now the checkboxes via the GUI need to reflect the door state if opened by mouse first. If you open the door halfway with the mouse and then open the GUI dialog....what do you see then, what should the checkboxes show? What feels natural and logical? This disconnect between possible actuation methods caused animating 'jumps' and I had to run a bunch of tests to see what worked and felt logical and natural, and add custom code to handle all that and it just added some extra time, etc. But in the end, I know that the customers that like to move stuff with the mouse will be happy and those that don't care can still use the checkboxes. But until I tried it, I wasn't exactly sure what worked best. I have to view the interactivity in this example from the perspective of a LOT of customers with different preferences and expectations. In the end, its a win-win for all customers, at the expense of my time estimate being delayed because I decided to add in a feature I didn't before, etc. There's been a few other areas regarding lighting that didn't quite work out like I hoped, eating up too many FPS and I had to backtrack and make some changes there also. Until I tried it though, I wasn't sure what the performance cost would be..and the alternative method turned out to be quite a bit of work. So...its stuff like this that stretches the time estimates. Your comment though, that you love the product gives me confidence that my choices when doing the work are mostly the right ones, and taking the time to do it right, even if it goes past my estimates, are usually worth it. -tkyler
    15 points
  10. 15 points
  11. 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.
    14 points
  12. its a fancy way of saying "reprogramming". We use a very old XML data format for our navigation data for the FMS...and we are wanting to move to XPlane's 'V11' navdata format , which is bit more modern with regard to flight plan leg types. So I have to "reprogram" all my code that parses these navdata files. You can expect a new 3D exterior at some point. Its my goal to make the IXEG as 'modern' as can be, similar to the MU2, so that it can be viable for many years to come. It takes a while, but if done right, it also lasts a while. And squeezing in a 'pop-report', I'll be wrapping up the last of the 'port +' visual mods today and focusing on the last few items in our todo list. I have a 10 day break for Oshkosh here beginning in about a week, but right after, we'll start the packaging for deployment process. I'll post a more in-depth video tomorrow morning ~ish (GMT-6) on the visual improvements...till then, here's the rear galley lighting. -tk
    14 points
  13. Thanks for all the sentiments and kind words. I myself am happy to be working on X-Plane full time and will strive to continue to do so. I can 'partially' sympathize with those who are...lets say...."on the fence" to put it nicely, regarding upgrade costs for software development, as I myself am one of those old-timers who came from what I like to call the "golden age of software" where it would obviously be great to buy it once and get upgrades forever, but as it stands, I now have at least 4 software subscriptions to software, billed every month, that is constantly evolving and some don't have the 'obvious features' I want and I understand it now as a developer. It used to be we could model a few polygons, slap a photo texture and we're done, because that's all the technology could handle. Now I have to model a few million polygons, slice them up and lay them all out neatly and texture them all and it takes a lot longer than it used to. I never had to worry about detail lighting before because X-Plane didn't have it, now its a whole "lighting pass" by itself. Same for sound engineering, etc. The technology has expanded a lot faster than the market. For those of us who remember playing Sublogic / Microsoft Flight Sim in 1981....we've come a long way technologically and I for one love it! The growth comes with some pains. I'll note that X-Plane dev requires more specialized knowledge now and finding folks with that knowledge and time is quite hard to find so its a challenge to execute what we now have the ability to produce. After nearly 20+ years of messing about with X-Plane, the important thing, I believe, is to keep moving and there've been some 'not insignificant' sacrifices in the background so that we can keep moving on this X-Plane work...as niche as it is. Its defininitely a labor of love and we all have to live with who we are. I figure if I can do what I love, I'll never work a day .....but I do need a paycheck to keep at it. I appreciate everyone out there who understands that. Thanks again. Back at it. -tkyler
    14 points
  14. Getting close to next patch. As Q8 mentioned, the Preflight menu was a "step back", but I still contend we had to take that step back to take some steps forward. So in the next patch, the following GUI will be avail on the PREFLIGHT tab. From this GUI, you'll be able to set the start state as usual (via the RESTART button + checkbox state). Also the quick "Plan fuel calculator" for quick fuel calcs is back. For loading fuel, you'll now use a "Aircraft fuel request" panel to add your fuel. You can hit the 'typical' button, which uses a common fuel config for most short hauls...or the "plan fuel" button, which takes its fuel amount from the "plan fuel calculator" ...or finally, you just move the sliders manually. Each of these actions constitutes a 'fuel request'. As fuel is requested, then you will see the amount requested below, along with the estimated time to refuel. If you have the "real time fueling" pref enabled, then this will be on the order of minutes normally, but if that preference is unchecked, then the estimated time will show only a few seconds. To actually add the fuel, you hit the 'start fueling' button. The 'meters' on the right show the requested fuel (red lines) as well as the actual fuel. The load sheet GUI is used to configure the weight and CG of the aircraft, by adding passengers and cargo and shifting the cargo around. I don't have passenger shifting atm, they're currently 'well balanced' throughout. You can drag a slider to add/remove passengers. There is also a "weight factor" slider, that defaults to one, which represents 'average weights" for humans / baggage"....BUT if you want to overload the plane, or simulate say, a plane full of Sumo wrestlers, then you can up this slider to add some extra "density" to the passenger cabin payload. There's a pulldown to view the cabin vs. cargo hold. When viewing the cargo hold, there'll be two sliders, one for "additional cargo", which is cargo not related to the passengers, which many airlines do carry...and there'll also be a "bias slider", where you can shift cargo between the front/rear holds to adjust the CG range and get the trim units value. Adjusting the cargo hold loading between front/rear is the preferred way to tweak the CG. Sorry we had to backtrack a bit before we could get this back in, but hope it helps maintain immersion by not having to go to the default XP menus for fuel and payload. Down below is what the cargo sliders look like (more or less...this was a few days back and there's been some slight improvements since then) -tk cargo_slider.mp4
    13 points
  15. And just a heads-up from my side: I will be away flying DLH507 from Friday afternoon to Saturday morning, landing around 8:45Z in EDDF. I won´t be able to man the forums and give technical advice and log problems until later that afternoon, plus I have a family outing planned on Saturday night to celebrate my 53rd birthday that I spent here in Sao Paulo, away from my family. So give us a chance to catch up with everything over the weekend, I will certainly try to get through the backlog on Sunday. There are bound to be some problems and issues that slipped by me and my testflights, but as Tom already said, we are going to be on deck in the days and week after the launch and the plan is to have a very short turnaround time on critical fixes. I am excited to hear what you guys think! Cheers, Jan
    13 points
  16. that's kinda correct Frank... though 'sometime later' is actually to begin asap after the bug-fix phase following release. The term "major lift" is probably somewhat relative to each individual though. This is more evolution than revolution. The plan is to prioritize the FMS/VNAV improvements first, then in parallel as able, swap the sounds over to FMOD and begin a new 3D exterior model. So for folks who spend 95% of their time enjoying the cockpit and don't care about the rest much....then elements of a "major lift" may not seem so major. For folks who live for VNAV descents, then they may see the VNAV work as a major lift etc. Either/or, the plan is to continue on those elements listed above after release for sure and we'll evaluate other features along the way. -tk
    13 points
  17. not very likely no. The cockpit texture, being the center of attention and in view for the majority of the time was optimized quite well for 96 DPI monitors IMO and still looks good......assuming a reasonable camera distance from surfaces. Also, since we did this work way back when, before Substance Painter was a thing...it'd be a massive undertaking to try that. Of course if you put the camera quite close to a surface, there will be 'jaggies', but philosophically, I'm not in that camp. I'd rather optimize performance for the 95% use case (pilot-ish viewpoint +/-) rather than the 5% use case (peruse 3D closeup under a microscope after buying). -tk
    13 points
  18. 13 points
  19. Thx. Somewhere in that endeavor is revealed the next projects we'll be working on...curious if anybody will figure it out Anyhow....the WIP of the cockpit lighting.
    13 points
  20. Hello All, This will serve as an official announcement that we have released the version 1.51 update for the Take Command! IXEG 737 Classic Plus. All customers who have purchased the IXEG 737 Classic Plus 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 IXEG 737 Classic Plus from today forward, your purchased download will already be updated to version 1.5.1 for you. IXEG also has a new website documenting changes, so click here if you'd like to keep continually updated! 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 IXEG 737 Classic download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Bug fixes: Level-2 Validation failure Wiper Switch didn't work Standby airspeed indicator drum was not rotating Floating 3D polygons outboard of the rear doors VRconfig.txt file was missing Weak starter at high density altitudes Engine start too fast after lightoff. SLIGHT improvement implemented. Laminar acknowledged bug. Will revisit after. Wing lights were not working Visual texture glitch was underside of left wing Taxi light was too dim MCP backlighting was too dim Right side window heat annunciators were swapped Right Turnoff light was missing INVALID ENTRY msg appearing when trying to manually enter V1 on TAKEOFF REF page Pitch up moment change during liftoff and landing was too strong Idle fuel flow was too low - fixed for next patch CDU keys were not backlit FMC would cause Gizmo crash during VNAV calculation with only 1 waypoint in the route ECAM pie needles were not illuminated at night Improvements: Fuel Crossfeed annunciator annunciator is now more dim with xfeed valve open Additions: Four new commands to command the fuel levers 1 & 2 to idle/cutoff. Useful for single button/click action Cockpit door defaults to open in turn-around mode. Cockpit door occludes light from galley when shut. Linked to Default XP Commands (below) to connect/disconnect/toggle the GPU. Helpful in VR ixeg/733/left_fuel_lever_to_idle ixeg/733/left_fuel_lever_to_cutoff ixeg/733/right_fuel_lever_to_idle ixeg/733/right_fuel_lever_to_cutoff As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!
    12 points
  21. Version 1.0.0

    610 downloads

    Hotstart Challenger 650 | R&J Air (Laminar Blue)| N1219L 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!
    12 points
  22. Been quiet here a while. Sorry for that. Yes, still on this every day We have slapped a release date on our own calendars finally, but of course we're not tossing that date out because our crystal ball isn't the latest model. To at least be able to see a firm date is encouraging. The delay since wrapping up the 3D/visual work is mostly due to my reworking of my code infrastructure to be more 'decoupled' and "libraryish", such that it can more easily be reused and applied to future work. Because we're wanting to do new projects while improving the 737 also, I needed my old code to be a bit more flexible and it was just easier to begin that process now. So hopefully the benefit of this phase of work will be seen with more rapid development down the line. I hope that's the case . Sorry for delay in reporting, I'm still happy to be doing this and ensuring I can continue to do so. -tkyler
    12 points
  23. It is now (thanks Pils)...and I'm still making my way back home. We're pretty much done with the issues list for deployment and only have to get though technical infrastructure and deployment prep, but as mentioned before, that's not an overnight thing, but it is the 'final leg' of this route. The plan is to get this 'port + compatibility patch' out, which I'm sure will result in plenty of issues reported, but then immediately begin addressing those issues and start the road towards our planned improvements. The obvious 'improvement roadmap' consists of converting our sound work to FMOD, improve FMS operation and finally a new 3D exterior, these are the things to bring the IXEG into 'modern times'. I'm sure this work will roll well into 2024 and the goal is to just keep going. After those obvious items are addressed is when will think about any other 'options' to the product. Its enough of a heavy lift job to overhaul this thing from 2009 tech as it is. -tkyler
    12 points
  24. Ok...a little more on the -ish side than the morning side, but here's a peek into the cabin lighting as I tested the functionality.....with the intro showing some cabin door interaction. The video compression is a bit heinous though.
    12 points
  25. That is correct. Four of us originally. Each of the others on the team have graciously reduced their stake so as to allow me to continue work on it and keep it alive. Without their sacrifice, the IXEG would have reached end of life at V11. I'm eternally grateful to them and wanted to honor them openly this way for their wonderful work. Their fingerprints will always be on the IXEG... Jan Vogel, Nils Danielson and Morten Melhuus! Thx guys! -tkyler
    12 points
  26. Too easy! Anybody with access to the 717 willing to help..or a friend of a friend of a friend with access.....please hit me up in PM. This is well into late 2024 at best...737 comes first so i won't talk 717 much. Its just out there waiting its turn....but I reserve the right to work on it nights/weekends It doesn't quite work that way...besides, interior mostly done anyhow. The 'standard' is the standard. Immersion is a huge part of the product and many customers enjoy it all around. Lots of folks like replay mode from the cabin etc. Once this interior is done, I won't have to worry about it and can get back to the FMS and such. -tkyler
    12 points
  27. Hi everyone! Thanks for everyone´s support and feedback for our initial launch of the IXEG 737 in XP12. This post will detail the bugs that were reported and confirmed by us. This post will be updated regularly and shall serve as a tool to check if something you observe has already been reported. Activation issues with the DRM that revolve around the "Level 2 check" failing - fixed Wiper switches not working - fixed for next patch Standby airspeed indicator drum not moving - fixed for next patch Bullseye windows on doors 3L and 3R too far outboard - fixed for next patch VRconfig.txt file missing - fixed for next patch Starter not strong enough at high density altitudes - fixed for next patch Engine start process going too fast - improved (total duration matches) but fix in LR´s court Wing illumination light not working - fixed for next patch Visual texture glitch on underside of left wing - fixed for next patch Taxi light a bit too dim MCP backlighting a bit too dim Window heat OFF logic reversed for right side windows - fixed for next patch No turnoff light for right side - fixed for next patch INVALID ENTRY message when trying to manually enter a V1 on TAKEOFF REF page - fixed for next patch Pitch up moment change during liftoff and landing too strong - fixed for next patch Idle fuel flow too low - fixed for next patch No CDU backlit keys - fixed for next patch. FMC / Gizmo crash when executing VNAV calc with only one waypoint in LEGS - fixed for next patch. ECAM gauge needles not lit up at night - fixed for next patch. Added four commands to command the fuel lever to idle/cutoff. For hardware binding to buttons/switches. Linked to default XP commands to connect/disconnect/toggle the GPU. Helpful for VR users. Cockpit door default to pen in the Turn-around mode Cockpit door occludes front galley lighting at night when closed. Fuel Crossfeed annunciator dimmer (less bright) when crossfeed valve open. Was too bright. - fixed for next patch.
    11 points
  28. I'm campaigning for this to Laminar.....the ability to exclude light sources from reflective surfaces...but as of this moment, I don't believe we can. I'll squeeze in a quick report here also. Just completed all the interior cabin texturing....at least 99.5% of it....and now I'm working on the lighting for the rear galley. Lighting for cabin/front galley already done. Next week some time I'll begin the final punchlist items list and we'll start looking to wrap things up to package for release...that's not an overnight step, lots of checks have to be made, but we're definitely coming to the end of this V12 port + process. I'm going to start calling this the "V12 compatibility patch + (plus)"....becuase its exactly that. A port of the existing V11 functionality to V12, PLUS a few extra 3D stuffs thrown in. I want to make sure people understand this isn't some "V2" with all new 3D throughout, revised FMS/VNAV etc.....that work comes after this release...this is to get folks flying the 733 in V12. Here's a update screenshot of the new cabin/rear galley....the works that's been going on the last 4 weeks. -tkyler
    11 points
  29. Not for some time. The cockpit looks great in XP12, even after 13 years since its first incarnation. PBR effects are applied in several areas of the cockpit already. There is a limit to the resolution of the textures where more does not necessarily equal better and a specific balance was chosen at the onset. One thing that has not changed much over the years is monitor "dot pitch'...with a few exceptions (Apple's retina display). Having chosen a minimum distance from camera to surfaces that we consider reasonable for a good simulation experience....and also in consideration of anti-aliasing algorithms, we have found that going higher and higher resolution results in poorer detail at the nominal viewing distances and there is a 'sweet-spot' balance between resolution and anti-aliasing algorithms. Anti-aliasing gets less effective at 'too high' resolutions and you get more 'jaggies', not less. Sure, when you get the camera right up on the surfaces, they look good then, but if a real pilot had to get as equally close to a surface to see its detail, you would most certainly question his last eye exam. As such, we selected a nominal range of camera distances from surfaces for typical simming activites and developed our resolutions based on those use cases. Going any higher doesn't yield any worthwhile benefit in our experience as of yet. I'm not saying there's not room for improvements in a few areas...but relative to other ares of the 3D, its certainly one of the better textured areas and not at the top of the list for improvement.....and we're quite proud of how good it still looks in XP12 after 13 years. Nils Danielson did an unbelievable job of texturing the cockpit, best I've ever seen to this day IMO, and those who have experienced his work and the immersion it imbues (myself included) know what I'm talking about. We'll keep on eye on it, vs the state of the art technologically, and if there's something we feel we can do that will improve the immersion experience, we'll ceratainly put it on our wish / todo list and try and knock that out. -tkyler
    11 points
  30. Preview of X-Plane's window icing effects, in case anybody hasn't seen it. This was my first time seeing it https://www.dropbox.com/s/o261awvzn9rotog/thermal_inertia_opt.mp4?dl=0 DISCLAIMER: This is Laminar's default window icing effect and in-sim developer tools....I'm only implementing it. They did a good job! It has been thought through fully. Without it, the IXEG 733 would have to be retired. You want some shock....ICON aircraft was 'selling' their aircraft at an estimated 140k about 5 years before it hit the market (and taking deposits against that estimate too)...it ended up hitting the market at over 350,000.00 (over 400k now maybe?) And their board of directors consisted of a prior Google CEO, Boeing executives, etc. The point is things change and you adapt as best as you can. We're not looking back, just forward. -tkyler
    11 points
  31. 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
    10 points
  32. We're thinking "time is money". My mortgage payments runs on a timeframe...my internet fees...my software subscriptions, my commissions.....special offers in the mail......all time frame limited to encourage folks to act to keep the economic cycle moving. Time and money is inextricably linked. Without this principle, no business would survive and we've have no products...no add-ons, no x-plane, etc. Who is John Galt anyhow. TK
    10 points
  33. @spreilly a bit of of background about this whole variant thing. The ability to upgrade our work and make variants is very much tied to both the toolchain we use to develop the IXEG, as well as our 'techniques'. Like anything else, we get better over time at what we do and how we do things and the tools we use evolve as well. In the beginning (2010), we used Blender 2.49, a software quite difficult to make changes in. Also, we wrote our own exporting scripts to leverage emerging X-Plane tech. So after some time, we have this enormous amount of data/assets in a software format that is aging (like every software title). Fast forward a bit in the future and Blender 2.8 releases.....that was such a major....really major paradigm shift in organization of 3D assets....that it changed everything and we set about converting all our work to that format. Blender 2.49 was being abandoned by all. That was a really really laborious and long process that you guys didn't see any change from from ..it was our own challenge to keep the IXEG poised for the future. Even thinking about variants at this point wasn't an option. Fast forward a bit more...we get everything into Blender 2.8, things settle down for a year or so, I work on the MU2, which handles...count em....6 variants... and then X-Plane 12 drops. *sigh...here we go again. and so for the better part of a year, we start this process of integrating everything into X-Plane 12 format. On top of that, I'm swapping out lots of code for more "template" code, getting ready to start some new products also and we've just been building this 'infrastructure' on top of Blender 2.8+ (now 3.6) and XP12 for quite a long time. So....we still have to catch up on all that FMS stuff, still have to make the swap to FMOD and redo the 3D exterioro to keep the IXEG 'up with the times'....and after ALL that, then we can think about variants. BUT....best we can tell, we are in a technical place to do so. Its not that we don't want to...we just have 'the priority list' based on many years of customer input. I know this stuff takes a while, but in my quiet moments, I remind myself that I've been flight simming since 1981...still do it, its a lifelong hobby, most of the 'IXEG type' customers are probably the same...and I should just keep on moving. I'd like the variants in at some point...even those old mechnical ADIs / HSIs. Fingers crossed we'll get there. -TomK
    10 points
  34. Version 1.0.0

    239 downloads

    Hotstart Challenger 650 | Lewis Hamilton | G-LCDH 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 - Full Custom Interior Please respect my work. Copying/Modification is not permitted. Happy flying!
    10 points
  35. definitely. we're not touching that. On another note, we are back full steam on the IXEG after that short MU2 detour for Sporty's Pilot Shop. Working the lighting pass now, probably one of the bigger jobs. We have over 700 inidividual surfaces / lights that we have to audit 1 by 1 for the proper brightness values in XP12. After that, I'll hit the wing-flex and then the final punchlist items list. Jan is performing more test flights for any obvious bugs also. After the V12 compatibility / port release and bug chasing dies down, we'll start the "improvement" phase. -tkyler
    10 points
  36. I have a confession. I was approached about 10 days ago to participate in a short-notice endeavor (X-Plane related) that was tough to refuse and had me put the IXEG work on hold for this time frame....so this short delay in our original time estimate is squarely on my shoulders.....but I feel was the wiser decision for my continued work in X-Plane. I'm back on to the IXEG tomorrow. This side endeavor will become known sometime today I suspect. The good news (hint) is that completion of this endeavor will allow me to continue on the IXEG development right after the V12 port version comes out, and not have to detour back onto any other work....and there is a bit of an 'Easter Egg' in this endeavor that reveals the two projects we plan on working on in 2024. So we'll roll out the V12 port and I'll jump right back onto the FMS and other improvements planned for the remainder of the year. So this endeavor delays the V12 port, but moves forward the follow-on work. Those improvments (FMS, new nav data, beginnings of new 3D exterior) will take the better part of 2023 I'm sure, but we'll start that immedately after the V12 port release. As far as time frame for the V12 port now.... I can't say exactly. we always feel "close" because all the big stuff is out of the way. My todo list largely consists of finishing the interior texturing (rear galley), putting in the wing flex and squashing Jan's list of 'mostly small' issues, that's the list. I am dealing with 3 graduations of my kids this weekend (and family get-togethers).... and they will get my time to celebrate their achievements. I'd like to be done within 3 weeks, that's all I'll say. Will we be done in 3 weeks? I don't know. If not, I'll certainly be closer than I am today and still moving! -tkyler
    10 points
  37. Hello All, This will serve as an official announcement that we have released the version 1.5.2 update for the Take Command! IXEG 737 Classic Plus. All customers who have purchased the IXEG 737 Classic Plus 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 IXEG 737 Classic Plus from today forward, your purchased download will already be updated to version 1.5.2 for you. IXEG also has a new website documenting changes, so click here if you'd like to keep continually updated! 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 IXEG 737 Classic download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Bug fixes: Wing light didn't show with winglets. Also, wing light source wasn't visible Eyebrow window preference was not getting saved Transponder was not reporting altitude (mode C). Updated to use XP12 mode enumerations Incorrect lat/lon representation on CDU Duplicates / Disambiguation CDU page No button click sound on CDU CLR keys MCP Panel Lighting Removed the DDS texture, incorporated spills and PM effect Improvements: IAS speedbug manipulators now of the rotate type. Drag mouse around the IAS bezel to move speed bugs. Much more natural. Additions: Added preference to synchronize CPT and FO speedbugs and altimeter bug setting. Added preference to set the plastic speed bugs to Vspeeds automatically (for VR users, disables manual control) Added the following new commands ixeg/733/show_settings_window ixeg/733/close_settings_window // will auto-save prefs when closing ixeg/733/toggle_settings_window sim/flight_controls/landing_gear_off // default command now moves LG lever to OFF when able (not always able) New GUI elements in the PREFLIGHT panel for fueling & flight planning As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!
    9 points
  38. We respect your opinion and understand where you're coming from. The flight simulation community is diverse and people have strong feelings towards their preferred platforms. You do come off quite bias rather than basing your opinion on factual information (like actual IXEG or other product sales numbers, which we have plenty of data on). Both X-Plane and MSFS offer different experiences, and our internal data does indicate a positive trend for X-Plane 12. Let's focus on providing the best simulation experience for everyone, regardless of the platform they prefer.
    9 points
  39. We do appreciate your support Hermann, but your conclusion here is a subjective one. The product pages at XA are provided "for prospective customers consideration when evaluating a purchase", They are not policy pages, warranties or guarantees. Once one has made a purchase, that page, conceptually, goes out of context. I find this reasonable. I bought a Dell monitor a year ago. For me to keep an eye on Dell's "sales page" and try and argue that "current deals offered to prospective customers" on those pages should be retroactively applied to my purchase over a year ago is not reasonable in my opinion. I respect you have your perspective though mine is different. Certainly your perspective will be taken into consideration for future wordings so your points are noted. On a broader level though...you stated previously that you thought the IXEG was great and I thank you for that. If we didn't charge for this update, then I would have never started the update and we would have absolutely declared the IXEG end of life at Version 11 and I would have moved on from X-Plane development. As it stands, I hope to now support the IXEG for years to come and also develop new products. Your support, whether you agree with some elements of the effort or not, does play a part in that. If you choose to purchase the upgrade, I hope you still find the IXEG to your liking and we'll endeavor to keep at it making it better. -tkyler
    9 points
  40. A year ago, a friend bought his son (now 14) a copy of the IXEG. Before, his son was not in a life place to desire/enjoy the 737 but has recently become interested in Aviation and flight simulation. Is he undedicated because he purchased within the last year? There are 'new' flight sim enthusiasts every day. They do not deserve to be called undedicated. For the rest of you folks who understand economics and the software dev cycle....and value your time / work and also respect the value/time of others work, I thank you and appreciate you. I know there's a of you out there. This update is intended to be a foundation from which to continue improvements on the IXEG. XP12 broke a lot of stuff and "band-aids" weren't going to get it done. Towards that end, some answers to recurring questions..which will be regurgitated elsewhere at release. Operational functionality is the same as V11 currently. (i.e. no change to FMS) Last 9 months were spent in 'repair' of areas broken in V12 and getting back to baseline. Plan going forward is to focus on 4 areas (in no particular order). FMS/vnav FMOD sounds New 3D exterior. Mac ARM suppport The above items will take a while. We'll begin work on this immediately, indeed already in process. Any cargo, 400/500 variants takes a back seat to the items above, if at all. Minimal demand. Unsure the time frame for ARM support. I myself deal with this and run Rosetta currently. we understand many MAC users may not find this acceptable until ARM support. We're on it. A new 3D exterior will be provided one day. When so, the old liveries won't work; however, folks can still use the old 3D exterior if desired. Again, I thank those who understand the economics! -TomK
    9 points
  41. Version v0.104

    85 downloads

    This LUA script enables random failures for the HotStart Challenger 650. Requirement: The script requires FlyWithLua: Download the correct version for your simulator. FlyWithLua for X-Plane 11: - https://forums.x-plane.org/index.php?/files/file/38445-flywithlua-ng-next-generation-edition-for-x-plane-11-win-lin-mac/ FlyWithLua for X-Plane 12: - https://forums.x-plane.org/index.php?/files/file/82888-flywithlua-ng-next-generation-plus-edition-for-x-plane-12-win-lin-mac/ Installation: - Unzip the files in [X-Plane]\Resources\plugins\FlyWithLua\Scripts Settings: (edit the lua script) -- Here you set if the failures should be default enabled or disabled when your starting up X-Plane. -- You can also enable and disable this option (for the current session) in the FlyWithLua menu. -- Set true to enable failures, false to disable. Default is true. true and false have to be written with lowercase letters. EnableFailures_WizVar = true -- Mean time between failures (MTBF) is the predicted elapsed time between inherent failures of a system during operation. -- Default is MTBF_hours = 10.0 local MTBF_hours = 10.0 -- Max failures pr session -- Default is Max_Failures = 2 local Max_Failures = 2 -- Severity 1 to 5. 1 least severe, 5 most severe. i.e. if you select 3, you will get failures from severity 1 to 3. local Severity = 5 -- Clear all failures when starting x-plane. Default is false. true and false have to be written with lowercase letters. local ClearAllFailures = false Logfile: When a failure occurs it will log the event to the logfile Wizball_CL650_Failures.log in your X-Plane root folder. example: MTBF: This graph shows a example how often you can expect a failure when you set the MTBF to 10 hours. Failures included in the script: CL650/failures/systems/ats/failed/state Auto Throttle System has failed CL650/failures/systems/ats/msd/1/failed/state Left ATS MSD has failed CL650/failures/systems/ats/msd/2/failed/state Right ATS MSD has failed CL650/failures/systems/afcs/yd/1/failed/state Yaw Damper Channel 1 has failed CL650/failures/systems/afcs/yd/2/failed/state Yaw Damper Channel 2 has failed CL650/failures/systems/elec/comp/HTR_L_WSHLD_1/failed/state Left windshield heater 1 has failed CL650/failures/systems/elec/comp/HTR_L_WSHLD_2/failed/state Left windshield heater 2 has failed CL650/failures/systems/elec/comp/R_WSHLD_1/failed/state R windshield heater 1 has failed CL650/failures/systems/elec/comp/R_WSHLD_2/failed/state R windshield heater 2 has failed CL650/failures/systems/elec/comp/HTR_R_WIND/failed/state Right window heater has failed CL650/failures/systems/elec/comp/CABIN_TEMP_SENSE/failed/state Cabin temperature sensor has failed CL650/failures/systems/elec/comp/LDG_TAXI_LTS_R_NOSE/failed/state Right nose LDG-taxi lights has failed CL650/failures/systems/elec/comp/LDG_TAXI_LTS_R_WING/failed/state Right wing LDG-taxi lights has failed CL650/failures/systems/elec/comp/HTR_L_WIND/failed/state Left window heater has failed CL650/failures/systems/elec/comp/ANTI_SKID_1/failed/state Anti-skid 1 has failed CL650/failures/systems/elec/comp/AUTO_THROTTLE/failed/state Autothrottle has failed CL650/failures/systems/elec/comp/CABIN_TEMP_CONT_AUTO/failed/state Cabin temp ctrl (auto) has failed CL650/failures/systems/elec/comp/ANTI_SKID_2/failed/state Anti-skid 2 has failed CL650/failures/systems/elec/comp/STAB_CH_1_HSTCU/failed/state Stab trim channel 1 ctrl has failed CL650/failures/systems/elec/comp/STAB_CH_2_HSTCU/failed/state Stab trim channel 2 controller has failed CL650/failures/systems/iceprot/wnd_heat/1/failed/state Left window heat has failed CL650/failures/systems/iceprot/wnd_heat/2/failed/state Left windshield heat has failed CL650/failures/systems/iceprot/wnd_heat/3/failed/state Right windshield heat has failed CL650/failures/systems/iceprot/wnd_heat/4/failed/state Right window heat has failed CL650/failures/env/birdstrike/strike/state Birdstrike that doesn't lead to any damage CL650/failures/env/smoke/baggage/state Smoke in the baggage bay CL650/failures/env/smoke/lavatory/state Smoke in the toilet CL650/failures/systems/elec/ac/gen/1/failed/state Generator 1 has failed CL650/failures/systems/elec/ac/gen/2/failed/state Generator 2 has failed CL650/failures/systems/elec/comp/HYD_PMP_3B/failed/state Hydraulic pump 3B has failed CL650/failures/systems/elec/comp/HYD_PMP_2B/failed/state Hydraulic pump 2B has failed CL650/failures/systems/elec/comp/HYD_PMP_3A/failed/state Hydraulic pump 3A has failed CL650/failures/systems/elec/comp/HYD_PMP_1B/failed/state Hydraulic pump 1B has failed CL650/failures/systems/elec/comp/FLAP_MOTOR_2/failed/state Flap motor 2 has failed CL650/failures/systems/elec/comp/FLAP_MOTOR_1/failed/state Flap motor 1 has failed CL650/failures/systems/elec/comp/HUD/failed/state Heads Up Display has failed CL650/failures/systems/hyd/1/pump/A/state Engine-driven pump 1A has failed CL650/failures/systems/hyd/1/pump/B/state AC electric pump 1B has failed CL650/failures/systems/hyd/2/pump/A/state Engine-driven pump 2A has failed CL650/failures/systems/hyd/2/pump/B/state AC electric pump 2B has failed CL650/failures/systems/hyd/3/pump/A/state AC electric pump 3A has failed CL650/failures/systems/hyd/3/pump/B/state AC electric pump 3B has failed CL650/failures/sensors/ads/pitot/3/leak_small/state Standby pitot tube is leaking pressure (inaccurate speed reading) CL650/failures/avionics/efis/hud/failed/state Heads Up Display has failed CL650/failures/systems/eng/left/compr/stall/trans/state Left engine compressor stall (transient, self-clearing) CL650/failures/systems/eng/right/compr/stall/trans/state Right engine compressor stall (transient, self-clearing) CL650/failures/systems/eng/left/oil/pump/weak/state Left engine oil pump is producing low pressure and low flow CL650/failures/systems/eng/right/oil/pump/weak/state Right engine oil pump is producing low pressure and low flow CL650/failures/env/birdstrike/windshield/state Birdstrike that leads to the left windshield's outer pane shattering CL650/failures/systems/aircond/leak/500/state Cabin is leaking pressure at ~500 ft/min CL650/failures/systems/comm/sdu/1/failed/state Satellite Data Unit 1 has failed CL650/failures/systems/comm/sdu/2/failed/state Satellite Data Unit 2 has failed CL650/failures/systems/fuel/tank/aux/leak/slow/state Auxiliary tank is leaking slowly CL650/failures/systems/fuel/tank/main/left/leak/slow/state Left main tank is leaking slowly CL650/failures/systems/fuel/tank/main/right/leak/slow/state Right main tank is leaking slowly CL650/failures/systems/fuel/tank/tail/leak/slow/state Tail tank system is leaking slowly CL650/failures/systems/hyd/1/leak_slow/state Hydraulic system 1 is leaking slowly CL650/failures/systems/hyd/2/leak_slow/state Hydraulic system 2 is leaking slowly CL650/failures/systems/hyd/3/leak_slow/state Hydraulic system 3 is leaking slowly CL650/failures/sensors/ads/pitot/1/leak_small/state ADC 1 pitot tube is leaking pressure (inaccurate speed reading) CL650/failures/sensors/ads/pitot/2/leak_small/state ADC 2 pitot tube is leaking pressure (inaccurate speed reading) CL650/failures/avionics/efis/pfd/1/failed/state PFD 1 has failed CL650/failures/avionics/efis/mfd/1/failed/state MFD 1 has failed CL650/failures/avionics/efis/mfd/2/failed/state MFD 2 has failed CL650/failures/avionics/efis/pfd/2/failed/state PFD 2 has failed CL650/failures/avionics/efis/isi/failed/state ISI has failed CL650/failures/avionics/efis/isi/pitot/state ISI pitot sensor has failed CL650/failures/avionics/efis/isi/static/state ISI static sensor has failed CL650/failures/avionics/efis/isi/att_fail/state ISI attitude indication has failed CL650/failures/avionics/efis/isi/att_drift/state ISI attitude indication is drifting randomly CL650/failures/systems/oxygen/tank/leak/slow/state Oxygen tank is leaking slowly CL650/failures/systems/eng/left/n1_vib_high/state Left engine is experiencing excessive N1 vibration CL650/failures/systems/eng/left/n2_vib_high/state Left engine is experiencing excessive N2 vibration CL650/failures/systems/eng/left/combust/flameout/trans/state Left engine combustion has flamed out (momentarily) CL650/failures/systems/eng/right/n1_vib_high/state Right engine is experiencing excessive N1 vibration CL650/failures/systems/eng/right/n2_vib_high/state Right engine is experiencing excessive N2 vibration CL650/failures/systems/eng/right/combust/flameout/trans/state Right engine combustion has flamed out (momentarily) CL650/failures/systems/aircond/leak/1000/state Cabin is leaking pressure at ~1000 ft/min CL650/failures/systems/ats/svo/1/failed/state Left ATS Servo has failed CL650/failures/systems/ats/svo/2/failed/state Right ATS Servo has failed CL650/failures/systems/elec/comp/FMS_CDU_2/failed/state CDU 2 has failed CL650/failures/systems/elec/comp/FMS_CDU_3/failed/state CDU 3 has failed CL650/failures/systems/elec/comp/FMS_CDU_1/failed/state CDU 1 has failed CL650/failures/systems/fuel/tank/aux/leak/fast/state Auxiliary tank is leaking quickly CL650/failures/systems/fuel/tank/main/left/leak/fast/state Left main tank is leaking quickly CL650/failures/systems/fuel/tank/main/right/leak/fast/state Right main tank is leaking quickly CL650/failures/systems/fuel/tank/tail/leak/fast/state Tail tank system is leaking quickly CL650/failures/systems/hyd/1/leak_fast/state Hydraulic system 1 is leaking quickly CL650/failures/systems/hyd/2/leak_fast/state Hydraulic system 2 is leaking quickly CL650/failures/systems/hyd/3/leak_fast/state Hydraulic system 3 is leaking quickly CL650/failures/systems/oxygen/tank/leak/fast/state Oxygen tank is leaking quickly CL650/failures/systems/eng/left/compr/stall/clear/state Left engine compressor stall (clearable by reducing power) CL650/failures/systems/eng/right/compr/stall/clear/state Right engine compressor stall (clearable by reducing power) CL650/failures/env/birdstrike/pitot/left/state Birdstrike that leads to the left pitot tube becoming blocked CL650/failures/env/birdstrike/pitot/right/state Birdstrike that leads to the right pitot tube becoming blocked CL650/failures/systems/aircond/leak/fast/state Cabin is leaking pressure quickly CL650/failures/systems/gear/handle/failed/state Landing gear handle failed CL650/failures/systems/gear/nose/leg/act/failed/state Nose gear leg actuator has failed CL650/failures/systems/gear/main/left/leg/act/failed/state Left gear leg actuator has failed CL650/failures/systems/gear/main/right/leg/act/failed/state Right gear leg actuator has failed CL650/failures/sensors/rss/gps/1/failed/state GPS 1 receiver has failed CL650/failures/sensors/rss/gps/2/failed/state GPS 2 receiver has failed CL650/failures/systems/eng/left/combust/flameout/perm/state Left engine combustion has flamed out (permanently) CL650/failures/systems/eng/right/combust/flameout/perm/state Right engine combustion has flamed out (permanently) CL650/failures/env/birdstrike/eng/left/state Birdstrike that leads to a non-recoverable left engine failure CL650/failures/env/birdstrike/eng/right/state Birdstrike that leads to a non-recoverable right engine failure
    9 points
  42. wingflex done. Kudos again to Laminar...someone there snuck in a good implementation of it while I wasn't paying attention, saving me coding time. Moving on to wrapping up the cabin lighting and texturing and then final punchlist and QA checks. -tkyler
    9 points
  43. This thread (and this forum at large) are the correct place - although there will be an email newsletter when the plane is ready for XP12. We are in the final stages of updating, I am not going to dare and put a date on it, but the plane is flying fine and the remaining work is some 3D, some minor bug squashing and a final user-experience polish. Cheers, Jan
    9 points
  44. Those are generally custom implementations, many times handled be a dedicated developer. While I am interested in VR interactivity, I view it as a 'interface layer' to be built on top of existing functionalities.....but the functionality development takes priority. That being said, during the course of development on other things, I do take time to peek into solutions towards catering to VR users....so its not completely lost on me Bulva and I will turn my mind to VR issues. -tkyler
    9 points
  45. Did you read anything that was said above in the initial announcement? Anyone who purchased the product from the date the product page was updated will receive the upgrade for free. That promise has not been broken. We made ZERO announcements about a free update to existing customers anywhere. We did publish on the product page clearly made for new customers they would get a free update for X-Plane 12. There was a reason for that, and this is not uncommon in the software industry when products are in transition. A product page is an advertisement for potential customers. And, we are holding up that promise as was outlined in the announcement. A product page is not a means of communication to existing customers. We communicate by e-mail and forum announcements to existing customers, and always have. You're stretching things here.
    9 points
  46. Hi all, with the upgrade transition finished, I thought I'd report on whats planned to help set expectations for the future and into 2024. A high priority is weening off of technologies that may cause "show-stoppers" for customers or in danger of causing conflicts as XPlane and computers evolve. This means the transition to the FMOD sound engine is first up...as we've seen some issues for customers and is a sign that things aren't going to get better. This is a pretty good sized job as we have quite a few sounds we have to port and we also have a LOT of code we have to excise without breaking other things. A port to FMOD easily sets the stage for many more years of compatibility. We don't work completely linearly...so in interstitial gaps in time between FMOD work, we'll also begin integrating in the XP11 Navdata format. Users won't see this for some time as its a big under the hood change. This is necessary not only to improve the IXEG FMS, but is also necessary for two future products with FMSs and as with FMOD...ensures forward compatibility...so this move to the XP default is also quite important. Third, we'll also begin work on the FMS VNAV / holds / performance predicitions. This work depends on the XP11 navadata to some degree, but not competely so we'll be able to make strides in this department while working on the XP11 navdata format transition also. Also, we're refactoring (rewriting) an enormouse amount of code for future-proofing and developing a new graphics library along the lines of what the RSG and TorqueSim folks are using. This will open the door to more engaging graphics for GUIs and value-added interfaces such as failures and EFBs etc. and Finally, we'll work on a new, high-resolution exterior model with new paint kit. We expect this work to take most of 2024....but it very much has applicability in the other projects we're doing so the end of the road isn't just some "under the hood" stuff on the IXEG, but also new models. Thank you for your support, we'll continue to keep working. -Tom Kyler
    8 points
  47. This isnt' the kind of thing I'd normally throw out there....I don't like excuses, but there is some behind the scenes info on whats going on time wise. ...and I know how hard the team is working despite the circumstances. We had planned the release earlier, when everyone was avail to support, but my elderly mother had a AAA (Aortic aneurism) a short while ago and I had to bolt out of town for the emergency, and this delayed the release. I don't want sympathies or well wishes here or in PMs, please keep those to yourself.....that's not what this post is for. This delay pushed the release back a bit.....to this weekend where some of our team are out of town (one out of country) for events with their families they scheduled months ago...and unable to work efficiently as they'd like. They're trying the best they can..and we're trying to get back together as fast as possible so we can get on with the business of improving the IXEG. We'll be hitting this hard tomorrow as well. We are fully committed to getting everyone up and running. This post is simply to let folks know that "life happened" to us these past few weeks and we're not just ignoring folks or don't care, or have lowered our standards. With all that said, I'll be hammering away all week on the things I can control. The other team members will continue as well and we'll be running on all cylinders again very shortly. TomK
    8 points
  48. Version 1.1.0

    184 downloads

    Hotstart Challenger 650 | New Era | N5950E 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!
    8 points
  49. Great news guys! Can't wait to see this in my XP12 fleet. I have recently been involved in porting another product across from 11 to 12 and omg I have seen with my own eyes how much work is involved in doing this - it's nothing like a straightforward task like some people imagine. With the flight model alone you end up wishing you could have just started over with an empty sheet. The transition seems to have almost killed off some projects. You have my gratitude for not letting this drop, I really miss the classics! I'm also delighted to pay 15 dollars for this, I think its really good value for the work that will have had to go into it (especially as you now have to cover the additional overhead of someone going full time). I don't get why some people are moaning about 15 bucks - I spent more than that on Pizza yesterday, now all I have left to show for the pizza is wind. After upgrading the IXEG to XP-12 we will have that in a whole new sim for years to come. There's no comparison really. Keep up the good work!
    8 points
×
×
  • Create New...